Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Versioning For Stable ONAP HEAT/Kubernetes Deployment

Description

We need to have a mechanism for setting the stable ONAP deployment with it's Repo's versions in some info file.

This should give us the information of the 3 weeks stable configuration that we use and the last stable configuration of ONAP deployment until it's been broken.

And be able to understand which component caused the issue and what Repo version number in order to get it fixed ASAP.

 

Possibly: blindly daily tag jar/war/dockers - then after CD runs - mark the tag set as good later

 

Confluence content

mentioned on

Activity

Show:

Former user December 6, 2018 at 10:30 AM

Close as it not relevant for this version, still need to handle on upper versions.

Former user December 6, 2018 at 8:53 AM

Good morning Ran- can we close this ticket or are you still working on it? thank you

Former user August 12, 2018 at 11:34 AM

Some changes had done i will update this task as well.

Former user August 8, 2018 at 4:28 AM

Any update on this one?

Helen

Former user December 7, 2017 at 3:40 PM

Yes, will check this quickly in the values.yaml and report back

Done

Details

Assignee

Reporter

Labels

Components

Fix versions

Priority

Created December 4, 2017 at 2:24 PM
Updated July 10, 2019 at 5:30 PM
Resolved December 6, 2018 at 10:30 AM

Flag notifications