Versions Compared

Key

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

zoom bridge: https://zoom.us/j/283628617

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 today
  • Stability 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 RisksSecurity (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)highlights 
  • 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
  • Platform Maturity - Update the wiki: El-Alto Release Platform Maturity
  • 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
    • 2741/35 44 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
  • SECCOM recommendations for Frankfurt various software platforms upgrades 
    • Programming languages
    • Docker, Kubernetes
    • Alpine
    • Databases
      View file
      name19_10_14_ONAPSoftwarePlatformVersionUpgradesV2.pptx
      height150
  • Python2 to python3 upgrade is a requirement for Frankfurt
5minLF Infrastructure/Rel process
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

onap-discuss message: https://lists.onap.org/g/onap-discuss/topic/dockerhub_migration_and/34447632?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,34447632

wiki: Migration to DockerHub

From TSC Chat:

"The proposal is to generate the release tag only by the release Jenkins job (now it's also generated by the staging job). I will not be able to join the PTL meeting next week, so I will go to the OOM and CSIT meetings next Wednsday to discuss it. I will come back next week at the TSC meeting with the result."

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

...

Zoom Chat Log 
Anchor
chat
chat

06:13:48 From Guangrong FU : Some of the disabled CSIT jobs are still useful (although they have not been running for a long time), who should we report that to?
06:14:11 From Lasse Kaihlavirta (Samsung) : You should fix them and restore them :)
06:14:16 From Lasse Kaihlavirta (Samsung) : no need to report them to anyone else
06:14:24 From Guangrong FU : OK, gotcha.
06:14:26 From Guangrong FU : Thx.
06:28:41 From Guangrong FU : I'm sorry to disturb. But I do have a question for El Alto. Catherine email me, asking me to update the release notes. But the fact is that I pushed the latest release notes to the master branch a couple of days ago. But the changes seem not to be reflected on readthedocs. Does anyone have any idea?
06:34:05 From David McBride : https://lf-onap.atlassian.net/wiki/display/DW/El+Alto+Release+Key+Updates
06:37:44 From Brian Freeman (AT&T) : cherry pick from master to elalto
06:37:46 From Guangrong FU : OK. Thanks.
06:37:48 From Brian Freeman (AT&T) : for documentation updates
06:49:41 From Eric Debeau : https://docs.onap.org/en/dublin/release/index.html
07:04:30 From Sofia Wallin : I need to leave. but I encourage everyone with open documentation issues or tasks to join the doc call on Thursday.
07:15:59 From Dan Timoney : CCSDK does not agree to deliver a Frankfurt drop at M3
07:17:14 From Dan Timoney : (Problem is there wont be anyone around in mid-late Dec to do fixes … so better to target early Jan for first code drop)
07:19:48 From Brian Freeman (AT&T) : lets get feedback from each client of an SDK and what date makes sense to folks. we can have two dates or we may find that portal and sdc sdk receivers have the same schedule and are fine with a early january delivery of the updated sdk's but not late Feb


Action Items 
Anchor
action
action