Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Duration 60 minutes

Question to teams/LF if x.y.z-KEYWORD-yyyymmddThhmmssZ tagging necessary and to be continued as python job templates do not support it.

Independent Versioning and Release Process

IT-17739/RELENG-2422 opened to address the template changes for timestamp based image tagging
Duration

Agenda Item

Requested byNotes / Links
START RECORDING AntiTrust Message
10minCSIT review

Currently few failing jobs - please direct attention to getting these tests functioning correctly.

Useless CSIT test elimination

20 minsEl-Alto Release

Project Status in El-Alto Release

  • OJSI CVE patches due  - this will trigger the longevity build/test run
  • OOM branch for El Alto - Mike Elliott branching todayStability Run will be kicked off as soon as latest SO/Policy containers are available (Target: Saturday, Oct 12th, 2019)

  • Close/move all open/in-process jiras to a future release
  • Check the certification expiry of your application. It should be valid for the next 9 months after RC0.
  • 1: El Alto Release Integration Test Blocking Issues
  • 0: Integration Weather Board for El Alto Release
  • Review El-Alto Risks
  • Security (Pawel)/Amy): 
    • Review CII-badging status  Paweł Pawlak 
    • OJSI status
    • Vulnerability wiki updates needed - CCSDK, DCAE, DmaaP, Holmes, UUI, VNFSDK
  • El Alto Remaining Milestones
    • Completion of Integration Testing: Oct 3rd, 2019 → Oct 17th, 2019
    • El-Alto Sign-Off on Oct 10th, 2918 → Oct 24th, 2019

  • Request from the marketing team for El Alto highlights (Coming Soon) INSERT Amar page here
  • Documentation branch has been created
    • Update the release name in RTD
    • Frankfurt to update the deliverables by milestone and doc types (dev guides, theory of ops, user guides...) tracking
    • Tracker similar to Integration Weather Board/pair-wise testing with use cases
    • Proposal for a per release docs champion - volunteers?
    https://gerritr#c/oom/+/96405/
 OOM to review (and merge) gerrit
 - blocking OOFPTLs: Help close out open OOM issues
  • Security items:
    • Project Teams to update their security issues: https://gerritlists.onap.org/rg/#onap-release/q/status:open+projects:oomNeed to attach the healthcheck results of your build to the patch to OOM to expedite the mergemessage/1431
    • Remove all open OJSI tickets from "fixed security issues" section It's fine to leave them in "Known security issues" section
 
    • 14 Open CVEs still unresolved Should we prioritize these?
    • Vulnerability tables not yet complete License Scan Review Stephen Winslow Will publish license scan results within the week. TSC recommendation delivered
10minFrankfurt Planning - Focus on the subcommittees 
  • Frankfurt schedule review
  • Frankfurt Release Requirements
    • Requirements freeze - Sept 27
    • 27/35 requirements with corresponding JIRA issues in REQ
  • oparent/AAF/CCSDK/Portal/SDC SDK released jar artifacts - need a deliverable milestone (M3? before M4) David McBride
  • Python2 to python3 upgrade is a requirement for Frankfurt
10minONAP deliverables outside the releasecl664y@att.com

The following activities are implemented outside the normal cycles by the project teams:

  1.  Completion of Self-Serve releases (Jessica Wagantall )
  2.  Dockerhub migration (Cristina Pauna )
  3.  Move OOM Helm Charts ownership to project team (Mike Elliott )
  4.  Ingress Controllers (Krzysztof Opasiak)
15minDockerHub Migration updatecristinapauna

Cross project dependencies


5minLF Infrastructure/Rel process
10 minsRemaining Action ItemsPTL Weekly ONAP12, Mon UTC 13:005 minDocker tagging  
15minONAP release cadence Chaker Al-HakimExplore release process cadence

...

Action Items 
Anchor
action
action

  •  David McBrideadd check on certificate status (update if < 9 mos) to RC0 requirements for Frankfurt
  •  David McBride add Frankfurt requirement for Python2 ==> Python3 change