There may be a case like there was for the 3.0.0-ONAP tag where AAI and POMBA vary - AAI took 1.3.2, pomba stayed with 1.3.1 because of issues deploying 1.3.3

The current manifest does not always account for 2 projects using different versions of common images

Result:

integration is running with 1.3.3 across both projects before both projects themselves have upgraded.

If you apply the manifest - it will overwrite both of these versions - but we may want a variance.

we get

Code Block

theme	Midnight

aai:
  image: onap/data-router:1.3.3
pomba: 
  image: onap/data-router:1.3.3

we may want

Code Block

theme	Midnight

aai:
  image: onap/data-router:1.3.3
pomba: 
  image: onap/data-router:1.3.2

2) docker version responsibility

PTLs should be responsible for their docker image versions in OOM - however since the manifest drives the version truth some images are updated at the last minute during the manifest/oom sync - these should be better coordinated/tested with the team

Yesterday there was a last minute change to sync POMBA with AAI because the manifest lists the common data-router version as 1.3.3. Regression testing may have been done for POMBA under 1.3.3 but the POMBA team was not aware of the new version - Ideally the project team themselves test new docker versions to be sure it works. Changing the image tag at the last minute before 3.0.1-ONAP is tagged is problematic - as I am kind of doing this blind without a fully vFW post audit (HC and CD deploy were ok) - this has happened twice so far.

3.0.0 = 1.3.1 reverted from 1.3.2 auto-up-rev for LOG-932

Jira Legacy

server	System Jira
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	LOG-932

https://git.onap.org/oom/tree/kubernetes/pomba/charts/pomba-data-router/values.yaml?h=3.0.0-ONAP#n30

3.0.1 = 1.3.3

dup

Jira Legacy

server	System Jira
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	INT-901

submitted 20190220:2000EST for CMR

Jira Legacy

server	System Jira
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176
key	LOG-982

https://git.onap.org/oom/tree/kubernetes/pomba/charts/pomba-data-router/values.yaml?h=casablanca#n30

example

I recommend we work out the details of MRs before we do the DMR.

Fix #2

Another option would be to duplicate/label common images so they can vary independently - but this would defeat the offline installer and the CIA initiative - but would follow what dmaap does for the DR

Any Infrastructure Improvement/Plan

Linux Foundation

5 mins

Any LF showstopper

#66785: add SO weekly meeting to the wiki calendar
#67727: AAI ONAP Meeting Request - "Monitoring / health checks on long running ONAP deployments" - Tuesday Feb 19 @ 0900 Eastern, 1400 UTC
#67450: Jira board for Vulnerability Management
Committer changes blocked on INFO.yaml
#68804: [Onap-seccom] Known vulnerability analysis of APPC in Casablanca maintenance release

Help-desk Feedback provided

#66623 - RTD Project onap ... Webhook API Deprecated
#67224: ONAP Docker registry doesn't support manifest lists (Image Manifest V2) - related to work already planned as part of the CIA Dublin Release Planning
#68474: 1/31/2019 Gerrit Upgrade did not preserve allow Superproject subscription permission on all release branches

Completed

#66028: [linuxfoundation.org #66484] RE: ONAP Meeting Request
#68174: Inactive Contributes and Committers - DmaaP
#68232: New DMaaP Committers - Bhanu Ramesh and Mandar Sawant
#68267: https://jenkins.onap.org/job/portal-docker-master-two-scm-verify-script/301/ : FAILURE
#68417: Re: [Onap-release] URGENT - Casablanca Maintenance - Formally release the artifacts
#68735: All docker builds stuck
#68787: Login not working on ONAP toolkit
#68788: AutoReply: Gerrit Login does not work

Other

git is not showing all the tags

for example 3.0.0-ONAP exists via the URL - but you can't select it from the drop down - it shows 2.0.0-ONAP - minor

https://git.onap.org/oom/tree/kubernetes/pomba/charts/pomba-data-router/values.yaml?h=3.0.0-ONAP#n30

PTL Update

Yang Xu

Hui Deng

15 mins

- Integration - Committer Promotion's request:

Brian Freeman - GO
Mariusz Wagner - only 1 contribution to the Integration project over the last 90 days; 9 over the last 6 months - approved post TSC Call

- Modeling project - Zero commit removal Request and Separate the committer for parsers repo - GO

Subcommittee - Modeling

cl664y@att.com

15 mins

Modeling Checklist - what's the path to move forward?

TSC did not approve M2/M3 Modeling Checklist add-ons for the Dublin Release. Follow-up discussions with PTLs are required to consider them as part of El-alto release. Suggestion is to prototype these checklists with few projects.

TSC Activities and Deadlines

cl664y@att.com

Feedback about TSC Seat election: