Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 2.10 #5211

Closed
26 tasks done
planetf1 opened this issue May 20, 2021 · 14 comments
Closed
26 tasks done

Release 2.10 #5211

planetf1 opened this issue May 20, 2021 · 14 comments
Assignees
Labels
release Work to create a new releae

Comments

@planetf1
Copy link
Member

planetf1 commented May 20, 2021

Create 2.10 release

  • slack post
  • agree in team call
  • Create branch
  • Reassign any issues not being worked on to the next release
  • Update master
  • Ensure any remaining fixes are merged
  • Update branch version
  • Remove release notes from branch
  • Update image versions for compose & charts
  • update release notes & rename
  • Verify notebooks
  • Check polymer UI
  • Check node (ps) UI
  • Run CTS
  • Check samples
  • Check swagger doc
  • Verify odpi-egeria-lab chart
  • Verify egeria-base chart
  • verify docker-compose
  • create release candidate (manual github action)
  • Verify RC packaging on MC
  • Fix up maven artifacts as needed
  • Create final github releases (launches pipeline)
  • Verify artifacts all on maven central
  • Release on maven central
  • ensure any fixes ported to master

The branch for 2.10 release is 27th May 2021 (agreed community call, 20 May 2021)

@planetf1 planetf1 added this to the 2021.05 (2.10) milestone May 20, 2021
@planetf1 planetf1 self-assigned this May 24, 2021
planetf1 added a commit to planetf1/egeria that referenced this issue May 27, 2021
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
planetf1 added a commit to planetf1/egeria that referenced this issue May 27, 2021
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
@planetf1
Copy link
Member Author

Agreed in dev call 2021-05-27 to go ahead with branch.

@planetf1
Copy link
Member Author

@sarbull @lpalashevski @bogdan-sava If you wish to create a new version of the UI for us to use in our helm charts etc please post here. Without any further change, we will point to a docker image 2.8.0 (see https://hub.docker.com/repository/registry-1.docker.io/odpi/egeria-ui/tags?page=1&ordering=last_updated)

planetf1 added a commit that referenced this issue May 27, 2021
#5211 update master to 2.11-SNAPSHOT
planetf1 added a commit to planetf1/egeria that referenced this issue May 27, 2021
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
planetf1 added a commit to planetf1/egeria that referenced this issue May 27, 2021
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
@planetf1
Copy link
Member Author

Testing currently blocked due to :

 Warning  Failed          19s               kubelet            Failed to pull image "docker.io/odpi/egeria:2.10": rpc error: code = Unknown desc = Error reading manifest 2.10 in docker.io/odpi/egeria: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

See #4046 - previously identified.

This is a limit for all users. the counter does reset within 6 hours, but it's an indication other users of the egeria repo could get into difficulty and we need to urgently consider an alternate repo for egeria images such as quay.io, possibly publishing to both locations

@planetf1
Copy link
Member Author

CTS inmem successful:

        "testCaseCount": 5093,
        "testFailedCount": 0,
        "testPassCount": 5093,
name	description	profilePriority	conformanceStatus
0	Metadata sharing	The technology under test is able to share met...	MANDATORY_PROFILE	CONFORMANT_FULL_SUPPORT
1	Reference copies	The technology under test is able to save, loc...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
2	Metadata maintenance	The technology under test supports requests to...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
3	Dynamic types	The technology under test supports changes to ...	OPTIONAL_PROFILE	UNKNOWN_STATUS
4	Graph queries	The technology under test supports graph-like ...	OPTIONAL_PROFILE	CONFORMANT_PARTIAL_SUPPORT
5	Historical search	The technology under test supports search for ...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
6	Entity proxies	The technology under test is able to store stu...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
7	Soft-delete and restore	The technology under test allows an instance t...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
8	Undo an update	The technology under test is able to restore a...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
9	Reidentify instance	The technology under test supports the command...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
10	Retype instance	The technology under test supports the command...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
11	Rehome instance	The technology under test supports the command...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
12	Entity search	The technology under test supports the ability...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
13	Relationship search	The technology under test supports the ability...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
14	Entity advanced search	The technology under test supports the use of ...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT

@planetf1
Copy link
Member Author

Notebook

Polymer UI

  • odd initial panels: #5238 cc: @

React UI

@lpalashevski
Copy link
Contributor

lpalashevski commented May 28, 2021

@sarbull @lpalashevski @bogdan-sava If you wish to create a new version of the UI for us to use in our helm charts etc please post here. Without any further change, we will point to a docker image 2.8.0 (see https://hub.docker.com/repository/registry-1.docker.io/odpi/egeria-ui/tags?page=1&ordering=last_updated)

Lets keep 2.8.0 in the charts for this release since we have not published new version for egeria-ui. Recently there was major refactoring so we still need to polish out few details (#5238 might be related to this or some additional default configuration we are missing for the backed api)

@planetf1
Copy link
Member Author

planetf1 commented May 28, 2021

@sarbull @lpalashevski @bogdan-sava If you wish to create a new version of the UI for us to use in our helm charts etc please post here. Without any further change, we will point to a docker image 2.8.0 (see https://hub.docker.com/repository/registry-1.docker.io/odpi/egeria-ui/tags?page=1&ordering=last_updated)

Lets keep 2.8.0 in the charts for this release since we have not published new version. Recently there was major refactoring so we still need to polish out details (#5238 looks related to this)

Currently the helm chart does indeed point to the 2.8.0 release, but perhaps so is ongoing development, so the image continues to evolve. We really need to target a fixed code level for integration with demos etc.

We could go back to 2.7.0 ?

Or we retrospectively create a branch from an appropriate point to capture a 2.8.0 release?

For the react ui we have master/main containing something like 2.10.0-rc.0. Then when we branch we update that to '2.10.0' and change main/master to 2.11.0-rc.0 . The docker image ci/ci process takes the version number to use for the label of the docker image. this way when egeria 2.11 ships, it points to egeria-react-ui image 2.11.0 which will not change, so should be stable.

For the components we use in the images we know multiple people are using I think we need to go through that stabilization as testing on the UI side in concert with the egeria base. It can lag a release or more, that's fine, but some testing or ideally automation is needed for the polymer UI as currently I am unable to test it as thoroughly as I would like (sample data, scripting, notebook etc)

It may be easier to manage if we deploy the UI independently - it could be a seperate helm chart for example , that would make it easier for the UI team to test in compose and k8s without being overly concerned with deployment of the base components? This would lead us to remove it from the lab chart, where in any case it isn't currently really documented or have any supporting materials

@planetf1
Copy link
Member Author

Graph CTS has completed successfully with:

      "testCaseCount": 5093,
        "testFailedCount": 0,
        "testPassCount": 5093,

name | description | profilePriority | conformanceStatus
-- | -- | -- | --
Metadata sharing | The technology under test is able to share met... | MANDATORY_PROFILE | CONFORMANT_FULL_SUPPORT
Reference copies | The technology under test is able to save, loc... | OPTIONAL_PROFILE | CONFORMANT_FULL_SUPPORT
Metadata maintenance | The technology under test supports requests to... | OPTIONAL_PROFILE | CONFORMANT_FULL_SUPPORT
Dynamic types | The technology under test supports changes to ... | OPTIONAL_PROFILE | UNKNOWN_STATUS
Graph queries | The technology under test supports graph-like ... | OPTIONAL_PROFILE | CONFORMANT_FULL_SUPPORT
Historical search | The technology under test supports search for ... | OPTIONAL_PROFILE | CONFORMANT_NO_SUPPORT
Entity proxies | The technology under test is able to store stu... | OPTIONAL_PROFILE | CONFORMANT_FULL_SUPPORT
Soft-delete and restore | The technology under test allows an instance t... | OPTIONAL_PROFILE | CONFORMANT_FULL_SUPPORT
Undo an update | The technology under test is able to restore a... | OPTIONAL_PROFILE | CONFORMANT_NO_SUPPORT
Reidentify instance | The technology under test supports the command... | OPTIONAL_PROFILE | CONFORMANT_FULL_SUPPORT
Retype instance | The technology under test supports the command... | OPTIONAL_PROFILE | CONFORMANT_FULL_SUPPORT
Rehome instance | The technology under test supports the command... | OPTIONAL_PROFILE | CONFORMANT_FULL_SUPPORT
Entity search | The technology under test supports the ability... | OPTIONAL_PROFILE | CONFORMANT_FULL_SUPPORT
Relationship search | The technology under test supports the ability... | OPTIONAL_PROFILE | CONFORMANT_FULL_SUPPORT
Entity advanced search | The technology under test supports the use of ... | OPTIONAL_PROFILE | CONFORMANT_FULL_SUPPORT

planetf1 added a commit to planetf1/egeria that referenced this issue May 28, 2021
…nloads

Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
planetf1 added a commit to planetf1/egeria that referenced this issue May 28, 2021
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
@planetf1
Copy link
Member Author

Currently blocked on #5241

Alternatives

Leave UI as broken, add note to readme
Remove UI from lab chart/compose (currently no content uses it). Long term this is probably the better option, and a separate approach should be used to deploy the polymer UI

planetf1 added a commit to planetf1/egeria that referenced this issue Jun 1, 2021
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
@planetf1
Copy link
Member Author

planetf1 commented Jun 1, 2021

Note when testing react ui - see odpi/egeria-react-ui#41 (/coco fails, /coco/login works ok)

@planetf1
Copy link
Member Author

planetf1 commented Jun 1, 2021

#5241 is now fixed, polymer UI is now ok in 2.10

@planetf1
Copy link
Member Author

planetf1 commented Jun 2, 2021

#5300 #5299 opened to track issues in samples - no proposal to fix for this release

@planetf1
Copy link
Member Author

planetf1 commented Jun 2, 2021

Testing now complete

planetf1 added a commit to planetf1/egeria that referenced this issue Jun 2, 2021
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
planetf1 added a commit to planetf1/egeria that referenced this issue Jun 2, 2021
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
planetf1 added a commit to planetf1/egeria that referenced this issue Jun 4, 2021
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
@planetf1
Copy link
Member Author

planetf1 commented Jun 4, 2021

2.10 was released on github & maven central on 2 June.

@planetf1 planetf1 added the release Work to create a new releae label Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Work to create a new releae
Projects
None yet
Development

No branches or pull requests

2 participants