Page Comparison

Morgan Richomme

Lasse Kaihlavirta

David McBride  as proxy for Former user (Deleted)

djhunt

Paweł Pawlak

Brian Freeman

Morgan Richomme

Project Status in El-Alto Release

• El Alto milestone status - RC0 has been pushed 
  • CODE COMPLETE HAS PAST - Close/move all open/in-process jiras to a future release
• 1: El Alto Release Integration Test Blocking Issues
• Brian Freeman review the integration/test status of El Alto RC0
  • El Alto final version = 5.0.1
• Platform Maturity (djhunt ): Feedback - El-Alto Release Platform Maturity (No update given)
• 0: Integration Weather Board for El Alto Release
• Review El-Alto Risks
• Security (Pawel)/Amy): 
  • OJSI tickets for CVEs in El Alto status Paweł Pawlak
  • Known vulnerabilities wiki link
• El Alto branch naming convention and tagging Vijay Kumar
• El Alto Remaining Milestones
  • Completion of Integration Testing: Oct 3rd, 2019
  • El-Alto Sign-Off on Oct 10th, 2918

Actions

• 2: El Alto Release Integration Testing Status - check with all owners to get their latest status ASAP
• OOM to review OOM-2117
• CL Loops in progress but facing some issues (Marco will follow-up)
• Expectations to get a new SO container (Staging available but need the 'Release' version by 10/2)
• Shankar is reporting some concerns about CADI issue related to AAF => reverting changes associated to the new CADI and will deliver a new OOF container
  • Christopher MCcray will follow up with Jonathan - new CADI to be planned as part of Frankfurt, no time to fix this as part of El-Alto
  • Christopher McCray to check if any other component is impacted
• PTLs to review your CII badging answer based on El-alto content + complete your Known vulnerabilities wiki page
• PTLs to finalize the review of OJSI
• Christopher MCcray/Amy Z. to follow-up with the Portal team about the repository upgrade without impacting the other teams.
• OOM & PTLs - please help to close any remaining OOM gerrit related to El-Alto- https://gerrit.onap.org/r/#/q/status:open+projects:oom
• PTLs posted the results of your deployment to accelerate the review of these OOM gerrit Reviews

David McBride

Paweł Pawlak

Alla.Goldner

Stephen terrill

Hui Deng  Andy Mayer

Pamela Dragosh

Frankfurt Release Requirements v95

Frankfurt Next Milestones

• Frankfurt Requirements

• to be frozen by Sept 27th, 2019 so TSC can start to review/prioritize them.
• Prioritization to be completed by Oct 3rd, 2019.
• M1 currently planned on Oct 10th, 2019.

Jessica Gonzalez

Kenny Paul

cristinapauna

• Dan T. - Python issue is fixed - thanks but Request raised to LF to delay these types of activities for the next 2 weeks
• DockerHub migration - missing cross-project dependencies
  • Self-releases - progress report
  • Update on multi-arch discussion from ONS
  • No issue reported this week
  • Feedback from Cristina - working currently with the Policy Team
    • Identify a concern with the tag used to release the containers while moving to Dockerhub
    • Proposal is to create a new Dockerhub space and to push the tag created during the development activities
    • Mirroring Dockerhub and Nexus to avoid any testing break until clear cut off
    • PTLs - do you see any issue if we create another ONAP user?
    • ACTIONS: PTLS to review the following wiki: https://lf-onap.atlassian.net/wiki/display/DW/Migration+to+DockerHub
      • Feedback expected by October 2nd, 2019
      • Here is an example of the implementation: https://hub.docker.com/r/onap/policy-base-alpine/tags
      • Cristina to raise a ticket for LF
• How to get support: http://support.linuxfoundation.org (DO NOT use helpdesk@onap.org)
• ACTIONS (LF): Any update about
• https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-17722
  
• https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-17739
  corresponding RELENG tickt - https://jira.linuxfoundation.org/browse/RELENG-2422
  

Chaker Al-Hakim

Task force has been created to review Release Cadence and milestone checklist

Any new change will be trialed as part of Guilin release

Considering previous retrospectives (Dublin & El-Alto)

Inputs for the action plan - JIRA TSC-20

• https://lf-onap.atlassian.net/wiki/display/DW/Community+Feedback
• https://lf-onap.atlassian.net/wiki/display/DW/ONAP+Beijing+Lesson+Learned+and+Casablanca+Process+Improvement
• https://wiki.onap.org/download/attachments/25434845/ONAP%20Beijing%20Lessons%20LearnedV1.pdf?version=1&modificationDate=1529543605000&api=v2
• https://wiki.onap.org/download/attachments/28382837/ONAP%20Casablanca%20Process%20ImprovementsV4.pdf?version=1&modificationDate=1529479359000&api=v2)
• Deck attached to TSC-9
• https://lf-onap.atlassian.net/wiki/display/DW/Use+Case+Evaluation+Process
• https://lf-onap.atlassian.net/wiki/display/DW/ONAP+Casablanca+Lesson+Learned+and+Dublin+Process+Improvement

Processes to be reviewed on a yearly basis

If you are interested to be part of the Task force then contact Chaker Al-Hakim

-Brian & Morgan from the Integration to the Task Force

-Currently part of the task force: @Amhad (Tata), Eric (Orange), etc - check the people who raised their hands during F2F

Recurrent slot for the next 4 weeks as part of the PTL call to discuss progress, questions, etc

Former user (Deleted)