Page Comparison

Dublin Release

RC2 Follow-up

Sign-Off?

•  MUSIC – 58% -https://sonar.onap.org/dashboard?id=org.onap.music%3AMUSIC

Milestone Status 

• Projects: Project Status in Dublin Release
• RC2 status
  • 100% green for RC2 checklists
  • a few pair-wise tests still in process (passing %: 89% SO; 78% Policy)
  • RC2 TSC Recommendations -  RC2 GO - Approved by TSC - Congrats Team !
    
• Sign-Off status
  • 29 projects (excluding Doc) 
    
    • 9 out of 29 are completed
    • 7 out of 29 are reporting with issues
    • 13 out of 29 have no reports
  • Sign-Off TSC Recommendations -  GO or NO GO 
  • TODOs
    1. Continue rapid find/fix cycle
    2. Complete 7day stability tests
    3. Assess all requirements for testing completion and determine IN/OUT status for each
    4. Release notes, security docs, and other documentation
    5. Communicate our best guess schedule

Release Details

• Latest "Release" Images?
• Security Feedback - Vulnerability Tables, CII Bagding, Release Note, OSJI, etc. - 26 CVE issued, pushing updates of release notes - please merge ASAP
  
• Integration Blockers: Dublin Release Integration Test Blocking Issues
• Remaining Highest/High Defects: Defect Status for Dublin
• Integration Tests Status: Dublin Release Integration Testing Status
  • 34 use cases/functional/non-functional requirements require E2E testing.
    • 21 out of 34 are completed (including N/A)
      
    • 4 out of 34 are at >=80% test completion
    • 9 out of 34 <80% test completion
  • Review all RED status (evaluate for removal from release)
    • #3 – 60% vCPE with TOSCA - drop from release - Candidate to be descoped (Ypan to confirm by 6/7 EOD)
      
    • #8 - 68% PNF Pre-onboarding - probably completed (Ben to confirm by 6/7 EOD)
    • #10 80% Scale Out - Require 2 days and integration with CDS (Scott to provide feedback on PTL call 6/10)
    • #11 74% CCVPN - Lab issues - scope change (Seshu to provide an update of the content to the LF Mkt Team + Readthedoc)
    • #18 60% & 20% BBS -proposition to phase it - PH1 Completed. PH2 Blocked by issues in SO & SDNC.(David to provide PH2 feedback on PTL call 6/10)
    • #23 50% Consistent ID of a cloud Region - SO issue (Bin to provide  feedback on PTL call 6/10)
    • #25, #33 - no update
    • #30, 31 - Security & Magnus to follow-up
    • #34 - Ypan to follow-up
• Documentation Tickets: Documentation Status for Dublin
  • Please update Readthedoc asap Dublin Release Notes
• Dublin release branch NOT created – Long list to the right.... except Documentation since 5/15 (so cherry-pick)
  
• Review Marketing Messages - https://lists.onap.org/g/onap-discuss/message/17065
• Please update JIRA bugs, tasks, user stories, etc, but do not close tickets when the work is not done

      JIRA Query - Remaining 526 Items

status != Closed AND status != Done AND project != "Sandbox Project" AND project != CI-Management AND project != "ONAP TSC" and fixVersion = "Dublin Release" ORDER BY key ASC, priority DESC, updated DESC

Global-jjb update - 11 of 29 projects complete!

• Post-Dublin automation of info.yaml/LDAP (don't disrupt the release)

Dockerhub migration - proposed start 2019-07-22 

• Will update at PTL call (post-DDF)

Contributor License Agreements (CLA)

• Enforcement of CLAs will start on July 1. 
• Information sent to the contacts from all companies that have contributed code to Dublin
• Commits will be blocked if companies do not have a CLA in place

Any LF showstopper

Completed

#76345: Please help release Usecase-UI repos for Dublin Release

#76359: Need help with the info.Yaml change

In ODL, for instance, during release time-frame a few folks are granted “Supercommitter” rights, empowering them with merge rights on all repos. That way, when version number changes, or bug fix validated but no one to merge, etc., these set of people can take care of merging the needed patches and getting the release forward. Given our current structure in ONAP, where the integration team as to “vouch” for the state of ONAP before its release, it could make sense having Integration’s committer given such right.

Suggestion: Integration Committers - 1 in APAC, 1 in EMEA & 1 in NAR to cover all the time-zones

Scope: Code and Documentation

Successful Story with OOM

Alexis/Brian will prepare a detailed proposition to be reviewed by TSC

Congratulations Lorraine Welch !

Portal Committer Promotion Requests for Lorraine Welch

Frankfurt Activity's plan proposal from M0 to M1

ONAP_Frankfurt_M0_M1_Proposal_V1.xlsx

• The next DDF event will be organized in Stockholm from June 11th to June 14th 2019 jointly with other LFN Open source communities i.e. OPNFV, Tungsten Fabric, etc. - https://wiki.lfnetworking.org/display/LN/June+2019+LFN+DDF+Schedule

Any remaining open question?

• ONAP Joint SubC Meetings Europe (September, Belgium) - Vote in progress before or after ONS Europe https://lists.onap.org/g/onap-tsc/message/5062
• Fall DDF dates have been approved by the TSC:  Nov 19 - 22. The LF will begin working on a location. Companies with facilities in geo-politically neutral countries that are interested in hosting should contact Kenny Paul