Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 88 Current »

Duration 90 minutes - https://zoom.us/j/661303200

Agenda ItemsPresented ByTimeNotes/LinksJIRA Tasks

Dublin Release

M2 Follow-Up

20 mins
  • M2 TSC Recommendations
  • Recommendation is to accept the M2 milestone as complete - Approved by TSC
  • M3 Preparation Discussions: Checklist for Use Case & Functional Requirements, Architecture Review, Security

Any Infrastructure Improvement/Plan10 mins

Presentation of the LF Toolchain Roadmap

Any LF showstopper?

  • #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 - (in process) adding verify job that insures LDAP matches INFO.yaml

Help-desk Feedback provided

  • #66623 - RTD Project onap ... Webhook API Deprecated - await response

Completed

  • Integration - Committer Promotion's request (Brian & Mariusz)
  • #68804: [Onap-seccom] Known vulnerability analysis of APPC in Casablanca maintenance release
  • [multicloud] removing committers on MultiCloud project (2/22)
  • All docker builds stuck - all Jenkins docker build nodes appear to be in “Suspended” state. (2/18)
    • Failure with Vexx host, notification worked as designed
  • #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
  • #66785: add SO weekly meeting to the wiki calendar - Fix post TSC Call
  • git is not showing all the tags

TSC-58 - Getting issue details... STATUS

Task Force Update  - Footprint Optimization Follow-up25 mins

Container Image Minimization Guidelines

https://lists.onap.org/g/onap-tsc/message/4673

Docker images produced by project should be optimized and become the images to be used by Integration included in the ONAP release


Task force Update - CI/CD30 mins

Version management enhancement - Mid term vision


PTL Update - Usecase UI5 mins

Committer Promotion's request:

  • Anbing Zhang and Chuyi Guo - GO

3.0.1-ONAP release tag

4

mins

Is the CMR ready for 3.0.1-ONAP tagging - are there any pending changes to oom (chart changes or docker image tag updates from the teams

I get asked all the time by customers and developers if Casablanca is released!

We need to decide when to tag oom with 3.0.1-ONAP - we are not effectively released until then

https://gerrit.onap.org/r/#/admin/projects/oom,tags

Workaround: Currently Telecoms deploying the CMR workaround this by deploying the Casablanca branch itself and trying to follow the known issues.

Special meeting between the Integration/OOM Teams will be organized on 2/28 to fix the tagging issue.

we are good - notes on the last comment on OOM-1560 - Getting issue details... STATUS


Dublin Deployment confusion - manifest vs oom values.yaml5 min

Affecting: CD and Dev deployment integrity

Can we discuss the decision on plans around movement/adjustment/merging of the manifest now that TSC 2019-02-28 is back. Highest jiras are still being added this week on the diff gap between the integration and oom repo - sometimes the manifest is behind oom as was the case for LOG-966 - Getting issue details... STATUS .

I recommend that before we finalize any move of the manifest - likely to oom - we first fix the ambiguity by forcing the manifest override inside the helm plugin script around a curl from the integration repo - so that developers deploying the system have this forced override

sudo curl https://git.onap.org/integration/plain/version-manifest/src/main/resources/docker-manifest.csv?h=$BRANCH > docker-manifest-$BRANCH.csv

This would help any project that is not actively updating one of their repos with the staging tag.

specifically 2 and 3 mismatches in Morgan Richomme slide above

TSC-86 - Getting issue details... STATUS

Propose to add passing Integration sanity test to Dublin Release milestone checklist

10

mins

Explain what Integration sanity test is and why we need to add it in Dublin Release milestone checklist - approved by TSC

Proposal to add integration sanity to Dublin Release milestone checklist.pptx


Vulnerability Management Procedure Update15 mins

Overview of updated Vulnerability Management Procedure + vote

ONAP Vulnerability Management - TBA


Subcommittee Update
Build the agenda for 2019 Silicon Valley Meeting Proposals
TSC Activities and Deadlines
Feedback about Special TSC Seat election:
  • TSC vacant Seat: Timo Perala

Incoming ONAP Events5 mins

San Jose - April 1st & 2nd 2019 ONAP Joint Subcommittees Silicon Valley - PLEASE REGISTER ASAP - Thank you

San Jose - April 3rd to 5th - https://events.linuxfoundation.org/events/open-networking-summit-north-america-2019/


Additional HousekeepingLinux Foundation

Daylight saving time 2019

  • in the US will begin on Sunday, March 10, 2019,
  • in Europe will begin on Sunday, March 31
  • in Australia will begin on Sunday, April 7, 2019,

No Clock change in China, India

No Calendar change for TSC Calls




Zoom Chat Log 

05:49:22 From Kenny Paul (LFN) : #topic rollcall
05:57:08 From Stephen Terrill : #info Stephen Terrill, Ericsson
05:57:18 From Murat Turpcu,Turk Telekom : #info, Murat Turpcu, Turk Telekom
05:58:51 From ALLAGO : #info Alla Goldner, Amdocs
05:59:08 From Bin Yang (Wind River) : #info Bin Yang, Wind River
05:59:10 From Viswa : #info Viswa, Verizon
05:59:29 From Sitharaman : #info Sitharaman, IBM proxy for Jason Hunt
06:00:36 From Eric Debeau : #info Eric Debeau, Orange
06:01:35 From Srini Addepalli (Intel) : #info Srinivasa Addepalli, Intel
06:01:38 From Timo Perala (Nokia) : #info Timo Perala, Nokia
06:01:38 From Yan Chen : #info Yan Chen, China Telecom
06:01:45 From Catherine Lefevre : #info, catherine lefevre, at&t
06:01:47 From Alexis de Talhouët : #info Alexis de Talhouët, Bell Canada
06:02:08 From Lingli,CMCC : #info Lingli, CMCC
06:02:11 From Milind Jalwadi : #info Milind Jalwadi, TechMahindra
06:02:26 From Susana (VF) : #Susana Sabater Vodafone
06:02:42 From Susana (VF) : #info Susana Sabater Vodafone
06:03:30 From Kenny Paul (LFN) : #topic Dublin M2
06:03:48 From Andreas Geissler (Deutsche Telekom) : #info Andreas Geissler, DT
06:04:12 From Kenny Paul (LFN) : @Andreas. seen. thanks
06:06:38 From Kenny Paul (LFN) : Jim reports all proijects have plans to address issues and recommends approval of passing M2
06:07:08 From Jonathan Gathman : FYI, Jim Baker: I did provide a Plan for aaf-authz 55%
06:07:23 From Jonathan Gathman : (AAF)
06:07:35 From Catherine Lefevre : Congratulations Team - great catch-up since last week !
06:07:37 From NingSo : #info Ning So, Reliance Jio
06:07:47 From Catherine Lefevre : #vote +1
06:07:54 From Kenny Paul (LFN) : #vote Does the TSC approve the Dublin release passing the M2 Milestone? +1, 0 -1
06:07:58 From Alexis de Talhouët : #vote +1
06:07:59 From Bin Yang (Wind River) : #vote +1
06:07:59 From Stephen Terrill : #vote +1
06:08:00 From Andreas Geissler (Deutsche Telekom) : #vote +1
06:08:01 From Srini Addepalli (Intel) : #vote +1
06:08:06 From Eric Debeau : #vote +1
06:08:06 From NingSo : #vote +1
06:08:08 From Murat Turpcu,Turk Telekom : #vote +1
06:08:09 From Viswa : #vote +1
06:08:10 From Sitharaman : #vote +1
06:08:13 From ALLAGO : #vote +1
06:08:14 From Milind Jalwadi : #vote +1
06:08:14 From Lingli,CMCC : #vote +1
06:08:15 From Yan Chen : #vote +1
06:08:16 From Timo Perala (Nokia) : #vote +1
06:09:16 From Sitharaman : #vote +1
06:09:39 From Kenny Paul (LFN) : #endvote
06:09:47 From Brian : Yea !
06:09:58 From Jonathan Gathman : Ditto
06:10:04 From Kenny Paul (LFN) : #agreed he TSC approves the Dublin release passing the M2 Milestone
06:10:15 From Kenny Paul (LFN) : :-)
06:11:12 From Michael O'Brien(LOG,Amdocs,MBP3) : I don’t know who owns me yet
06:11:14 From Kenny Paul (LFN) : #topic Discussion of M3
06:13:06 From Kenny Paul (LFN) : Alla reports that usecases will be looked at E2E as part of M3 review
06:14:41 From Keong Lim k00759777 : https://jira.onap.org/browse/AAI-2148
06:15:15 From Kenny Paul (LFN) : Concerns raised over a non-backward compatible API change in AAI. It has been flagged and discussed at the PTL meeting. (AAI-2184)
06:16:41 From Kenny Paul (LFN) : Jimmy reports that a "less ugly" solution may be found.
06:17:38 From Kenny Paul (LFN) : Stephen T recommends setting a formal TSC policy on backwards compatibility
06:17:40 From Catherine Lefevre : #action - Provide TSC policy about backward compatibility
06:19:21 From Kenny Paul (LFN) : #LF Rel-eng /infrastructure
06:19:43 From Kenny Paul (LFN) : #topic LF Rel-eng /infrastructure
06:19:47 From Michael O'Brien(LOG, Amdocs,MBP2) : I'll do the 3.0.0-ONAP tag at the bottom
06:20:50 From Kenny Paul (LFN) : @Jim B reviewed the slide deck which will be attached to the minutes
06:24:02 From Kenny Paul (LFN) : #action Jessica PTL feedback is required on dockerhub
06:24:28 From Michael O'Brien(LOG, Amdocs,MBP2) : added the 3.0.1-ONAP tag/CMR line before the manifest discussion
06:27:52 From Tina Tsou : When can finish the migration to dockerhub?
06:27:57 From Kenny Paul (LFN) : Orange has taken over the E2E and gated pre-checkin for testing.
06:28:35 From Tina Tsou : How many percentage have we achieved for migration to dockerhub?
06:28:43 From Keong Lim k00759777 : TSC-58 should be an epic with each tool as a story
06:32:26 From Catherine Lefevre : @Tina - no % yet I guess since TSC did not approve yet - plan will be shared on 3/4
06:33:03 From Tina Tsou : Merci Catherine
06:33:10 From Kenny Paul (LFN) : #topic Footprint Optimization
06:34:40 From Kenny Paul (LFN) : https://wiki.onap.org/display/DW/Container+Image+Minimization+Guidelines
06:37:17 From Keong Lim k00759777 : is it goal that the alpine-based images and ubuntu-based images should be fungible? if so, the testing can mix-and-match at random and should expect identical results
06:37:30 From Pamela Dragosh : Is Alpine then the default for ONAP?
06:39:40 From Catherine Lefevre : good morning @morgan - you will be the next one to present the long term strategy about version management enhancement
06:39:41 From Brian : they are not imutables - alpine doesnt use apt-get for installation of packages it uses apk-get or something
06:39:56 From Brian : we have alpine containers today - SO, ansible , and more
06:40:27 From Kenny Paul (LFN) : there is no forced direction on which OS to use. Objective it to build docker based on the smallest footprint you can. Just don't pull in unnecessarry modules
06:41:42 From Viswa : Will CIA team make sure that there are no OS specific assumptions in the release process, which will enable others to use their own OS image ?
06:41:52 From Kenny Paul (LFN) : The CIA team will not provide staffing assistance to projcets that stay with ubuntu.
06:43:08 From Pamela Dragosh : Policy is IN PROGRESS also
06:44:44 From Srini Addepalli (Intel) : I wish we have chosen 'Ubuntu Minimal' instead of Alpine as Ubuntu Minimal is open source and LTS (means that any security issues found in future wil be fixed).
06:44:50 From Dan Timoney : Also (on fungible question before), there are a few other differences between Alpine and Ubuntu you have to be careful about - e.g. JAVA_HOME is different …. so it’s supporting multiple OSs is feasible (I do for some of my base CCSDK containers(, but its not free
06:44:54 From Jonathan Gathman : Is there some sort of command in Docker that will tell you what the various Layers an Image is built with?
06:45:40 From Catherine Lefevre : agreed Dan T. - that's why we can only certify one flavour for the moment due to resources capactity
06:46:45 From Keong Lim k00759777 : @jonathan I think that each command is a layer
06:46:54 From Keong Lim k00759777 : in the dockerfile
06:47:31 From adolfo : @Jonathan "docker history" will list the layers
06:48:19 From Keong Lim k00759777 : worked example http://blog.arungupta.me/show-layers-of-docker-image/
06:48:31 From Srini Addepalli (Intel) : We found that some packages are not available in Alpine distribution. There is an extra work of getting hold of source code, build it and make it avialable in the docker. Ubuntu repository is comprehensive. Almost all packages can be installed using apt-get (no need for source code and building)
06:48:59 From Michael O'Brien(LOG, Amdocs,MBP2) : Can we discuss the CMR status
06:50:43 From Keong Lim k00759777 : what will the dublin passing criteria be for the container min feature?
06:51:29 From Jonathan Gathman : Thanks Adolfo.
06:51:45 From Jonathan Gathman : Now that I look. “Docker inspect” seems to show the layers in JSON format.
06:52:22 From Chaker Al-Hakim : #info Chaker Al-Hakim, Huawei
06:52:34 From Kenny Paul (LFN) : @chaker. seen
06:52:57 From Kenny Paul (LFN) : #topic CICD taskforce
06:53:26 From Kenny Paul (LFN) : @Morgan shared his sllides
06:54:01 From Catherine Lefevre : @Michael - yes but after what was originally planned
06:56:08 From Keong Lim k00759777 : how will this work with introduction of AAI-2148?
06:59:24 From Keong Lim k00759777 : docker version is committed in a file, how can it predict the gerrit ID?
07:00:02 From Eric Debeau : @Keong: good question for "the dublin passing criteria be for the container min feature". We will propose some criteria.
07:00:34 From Mike Elliott : @Morgan we should tie in versioning of the OOM Helm Charts as part of this process
07:01:26 From Mike Elliott : For example: onap-4.0.0-2019281000
07:03:17 From Michael O'Brien(LOG, Amdocs,MBP2) : the developer can mark the commit as SRL/LRG and deploy a single vm or all 13vms in either case
07:06:51 From Srini Addepalli (Intel) : On CI/CD: Very impressive work.
07:07:04 From Michael O'Brien(LOG, Amdocs,MBP2) : ok covered by DEPLOYMENT_TYPE - for VM sizing
07:09:26 From Michael O'Brien(LOG, Amdocs,MBP2) : oof is failing likely because of aaf not dmaap (which itself is failing because of aaf likely) - see partial dependency oof--aaf
07:09:27 From Michael O'Brien(LOG, Amdocs,MBP2) : https://wiki.onap.org/display/DW/Log+Streaming+Compliance+and+API#LogStreamingComplianceandAPI-DeploymentDependencyTree-Containerlevel
07:09:50 From Viswa : @Morgan / Orange - Very impressive work… Congrats!
07:10:13 From Michael O'Brien(LOG, Amdocs,MBP2) : 5 hours for a "safe" sequenced deploy based on dependencies
07:11:06 From Catherine Lefevre : Great presentation but more important we have a great future thanks to this long term vision and first implementation !!
07:11:58 From Brian : Seshu - I would like SO to be plugged into this in all honesty so that we can prevent breaking changes
07:13:19 From Catherine Lefevre : goal to have all setup as part of El-Alto :-)
07:13:26 From Honor : Yes Brian, I agree with you
07:16:22 From Michael O'Brien(LOG, Amdocs,MBP2) : right now CD can only effectively test oom helm chart changes - we assume that the docker image version is built/deployed to nexus3 already
07:19:22 From Catherine Lefevre : @Michael - Is the CMR ready for 3.0.1-ONAP tagging ? Yes since several weeks. It was discussed again on the PTL this week so unclear why OOM is not yet aligned on this
07:19:23 From Michael O'Brien(LOG, Amdocs,MBP2) : magic words on https://jira.onap.org/browse/TSC-25
07:19:47 From Michael O'Brien(LOG, Amdocs,MBP2) : manual magic word "run-helm-deploy" will kick in a helm-deploy jjb job that deploys robot and the particular pod to a 16-32g VM (preconfigured with rancher as a single node) - how? jenkins will run a remote ssh shell to a server using a cached key - a cd.sh script will need to be written - see the 2 pocs below already running
07:20:14 From Keong Lim k00759777 : how will it work with helm charts owned by individual projects? will it still appear as an OOM gerrit patch?
07:20:59 From Michael O'Brien(LOG, Amdocs,MBP2) : CMR is not released until OOM is tagged with 3.0.1-ONAP - we should discuss the state of the casablanca branch so we can decide to release 3.0.1
07:22:15 From Michael O'Brien(LOG, Amdocs,MBP2) : for example a customer (a telecom) running the CMR - they need to clone -b casablanca (because there is no 3.0.1-ONAP tag to use)
07:22:56 From Michael O'Brien(LOG, Amdocs,MBP2) : helm charts owned by teams work like the DOC project subproject links - all still show in oom
07:23:32 From Michael O'Brien(LOG, Amdocs,MBP2) : no project should merge until HC and P
07:23:37 From Michael O'Brien(LOG, Amdocs,MBP2) : ODS are +1
07:23:50 From Catherine Lefevre : @Michale- please sync-up with Mike since it took the action on 2/25 to complete this
07:24:03 From Michael O'Brien(LOG, Amdocs,MBP2) : I have synced with Mike - he is on the call
07:24:04 From Kenny Paul (LFN) : 7 mins left in the meeting
07:24:18 From Catherine Lefevre : we have been discussing since 4 weeks so unclear why the question continously is raised
07:24:28 From Catherine Lefevre : sync-up with Mike please
07:24:45 From Michael O'Brien(LOG, Amdocs,MBP2) : if you try to deploy onap casablanca you will see the issue
07:25:03 From Catherine Lefevre : raise the HIGHEST bug to OOM then????
07:25:06 From Brian : @Michael - we found a few references to 3.0.0-ONAP in the master OOM charts as well -grep -R that sting and the 3 refernces pop put - they need to be master
07:27:31 From Michael O'Brien(LOG, Amdocs,MBP2) : we can't see the screen
07:27:38 From Jonathan Gathman : Thanks for presentation. I think the Gating strategy is the point… answers my concern.
07:28:19 From Michael O'Brien(LOG, Amdocs,MBP2) : sounds good - we will continue to use the casablanca branch for now to clone CMR - until we get the ok on 3.0.1-ONAP tag creation
07:28:42 From Catherine Lefevre : kenny to investigate - Is the CMR ready for 3.0.1-ONAP tagging
07:28:59 From Kenny Paul (LFN) : #topic Integration Sanity Test.
07:29:00 From Catherine Lefevre : oups sorry -- #66785: add SO weekly meeting to the wiki calendar
07:29:26 From Honor : Yes
07:29:26 From Honor : :)
07:29:43 From Kenny Paul (LFN) : @Yang shared his slides
07:34:40 From Honor : +1 on the idea and the effort
07:34:47 From Pamela Dragosh : +1 this is great!!
07:36:39 From Michael O'Brien(LOG, Amdocs,MBP2) : only a couple pods failing in dublin - but one of the issues also blocks casablanca
07:36:39 From Michael O'Brien(LOG, Amdocs,MBP2) : http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS
07:38:38 From Kenny Paul (LFN) : #vote does the TSC approve making the Sanity Test requirtement to be an M3 gating item?
07:39:00 From Andreas Geissler (Deutsche Telekom) : #vote +1
07:39:01 From Stephen Terrill : #vote +1
07:39:06 From ALLAGO : #vote +1
07:39:11 From Murat Turpcu,Turk Telekom : #vote +1
07:39:21 From Bin Yang (Wind River) : #vote +1
07:39:22 From Yan Chen : #vote +1
07:39:23 From Lingli,CMCC : #vote +1
07:39:24 From Timo Perala (Nokia) : #vote +1
07:39:26 From Catherine Lefevre : @Mike, Michael - can you stay on the call after TSC meeting because I am confused by your statement
07:39:26 From Sitharaman : #vote +1
07:39:29 From Chaker Al-Hakim : #vote +1
07:39:51 From Catherine Lefevre : CRM signed off on 1/31 and ONAP release note also released communicated at TSC/PTL calls and via e-mail
07:39:56 From Catherine Lefevre : #votre +1
07:40:02 From Michael O'Brien(LOG, Amdocs,MBP2) : willdo
07:40:06 From Milind Jalwadi : #vote +1
07:40:08 From Viswa : #vote +1
07:40:09 From Catherine Lefevre : thanks
07:40:12 From Catherine Lefevre : #vote +1
07:40:17 From Kenny Paul (LFN) : #endvote.
07:40:40 From Michael O'Brien(LOG, Amdocs,MBP2) : CMR has no teeth until OOM is 3.0.1-ONAP tagged
07:40:48 From Kenny Paul (LFN) : #agreed the TSC approves making the Sanity Test requirtement to be an M3 gating item for Dublin/.




Zoom Attendance Log  

TSC Members Attendance based on Zoom Chat Log: 100%

AMDOCS1Alla Goldner
AT&T1Catherine Lefevre
Bell Canada1Alexis de Talhouët
China Mobile1Lingli Deng
China Telecom1Yan Chen
DT1Andreas Geissler
Ericsson1Stephen Terrill
Huawei1Chaker Al-Hakim
IBM1
Intel1Srini Addepalli 
Nokia1Timo Perala
Orange1Eric Debeau
Reliance Jio1Ning So
Tech Mahindra1Milind Jalwadi 
Turk Telecom1Murat Tupcu
Verizon1Viswa Kumar Skand Priya
Vodafone1Susana Sabater
WindRiver1Bin Yang



TSC Decisions  

2019 TSC Decisions



Action Items:

  • No labels