Agenda:

1. ONAP project news:

   • RocketChat replaced by Slack (onapproject.slack.com)

2. Guilin Maintenance Release status:

   • For CCSDK/SDNC, Guilin maintenance release contains fixes for transport slicing use case:

     • CCSDK-3075: CCSDK is using incorrect version of AAI interface.Closed

     • SDNC-1431: CCVPN - Transport Slicing: SDNC development - Using Same names for OTN tunnels and Ethernet Services in both domains, plus bug fixingClosed

   • Release builds created for CCSDK and SDNC, and helm charts have been updated. 

   • Only remaining item is certificate refresh for cds-ui

     • OOM has a pending change to generate cert using init container.  However, need to confirm that certificate is being installed properly.

3. Honolulu Release status
   
   

   • CCSDK and SDNC were both approved as passed M2 (Spec Freeze) milestone at special TSC meeting 1/25.  Release planning templates :

     • CCSDK Honolulu Release Planning

     • SDNC Honolulu Release Planning

   • ODL Aluminum port complete

     • Currently, using Aluminum SR1

     • SR2 is available, but has a  security vulnerability in restconf project that will be addressed in SR3

     • SR3 should be available later this month, per OpenDaylight community.  When available, we'll want to upgrade in order to pick up security vulnerability fix.

   • Next project milestone is M3 - Feature Freeze:

     • TSC vote scheduled for Feb 25, 2021 

       • M3 criteria includes that all release builds must be complete and helm chart changes must be submitted to OOM to deliver released dockers

         • Note: original plan assumed that helm chart changes needed to be MERGED by M3.  However, all that is required is that changes be SUBMITTED by M3. 

       • To allow time for code reviews, release builds and OOM review, final code reviews for CCSDK and SDNC Honolulu should be submitted no later than Feb 19, 2021
         
         

         • Note: this is a week later than our original plan, which allocated about a week for helm chart changes to be merged before M3.  Since that is no longer a requirement, we were able to relax our date for final code submissions.

4. Open Discussion