Agenda:

  1. Update the wiki pages - Casablanca Release Requirements and https://wiki.onap.org/display/DW/Casablanca+Risks
  2. Casablanca goals are being defined here https://wiki.onap.org/display/DW/Casablanca+goals
  3. Code Coverage needs to be improved to 80% - require TechM and IBM resources to commit for the plan
    1. SDK repo - Naveen is working on new SDK code coverage changes. New SDK commits made - Please add more reviewers ("Amrita Kundu" <amrkundu@in.ibm.com> and Mani are working part time on the code coverage - Saravanan to check with resources to mostly work on Javascript tests). 
    2. Prasad/Swapnali - Please use Epic - PORTAL-268 - for code coverage - PORTAL-273; for sonar issues - PORTAL-247; (focused on Portal repo).
    3. Portal's Javascript unit test plan? Yes it should be done in Casablanca- Prasad/Swapnali (Manoop to followup with TSC on the requirement on JS code coverage), Karma - look into it (Yatindra looking into it) plugin like jacoco
    4. Code Coverage: recommendation from TSC is to keep 50% Code Coverage for Casablanca including JavaScript. (In Beijing Release code coverage was only covering Java and Python code)
  4. Design for Angular update - Saravanan to provide the Design review and plan; listed out items, testing one screen, needs a week for this , another week for design document
    1. Portal Admin screen - for POC to migrate to latest Angular - Saravanan (Design discussion to understand the impact - Thurs 05/31).

      1. Meeting minutes:

        1. Advantages of upgrade:
          1. Rich UI, performance (quick UI response 5x better than older version), optimization (helps to move away from bower as it is deprecated)
          2. Internationalization support
          3. Easy development in latest version compared 1.4 version – with typescript multiple IDE support to compilation error in angular JS code reduces the development time
          4. JavaScript unit test coverage (analyzing, if we can reuse the Karma existing tests)
          5. could help security aspect – (analyzing)
        2. Estimates: 81 (Dev), 16 (Unit testing), 20 (Integration testing) days for 1 resource
        3. Check if IBM can have one more resource to work on this task (Saravanan to check)
        4. Request TechM resources to contribute, if they are interested (check in the next Portal scrum)
        5. Based on current analysis, it is possible to maintain both Angular version 1 and latest. We can try SDK support both versions but needs to figure out a plan to convert the SDK.
        6. Should we support both versions in same SDK or switch SDK completely to latest version and only do critical patches to older SDK? Will partnering apps upgrade ever to latest SDK?
    2. Demo with one screen with Angular 5, Karma testing - Demo shown to Sunder
    3. Bring up the application with Angular 1 and latest version 5 - Saravanan (Analysis: move away from bower and use node. Trying in portal with FE and BE).
    4. Should we split SDK FE and BE? - need more discussion and impact analysis - suggested to go-ahead with out splitting - but requires analysis on SDK - Saravanan
    5. Estimate of the migration to latest Angular - Saravanan
    6. fonts and icons abstraction so that they can be switched with a flag configuration - Saravanan (decided to achieve this configuration during the build rather than at runtime).
  5. Lorraine to run grep scan for ecomp keyword  - done - Review with Sunder/Manoop - will send them result in email
    1. Look for the vm host names in the files - to clean up - Lorraine already made commit for this changes - Hima can help if requires java file changes.
  6. Design to be scheduled for Simplify etc/hosts, OOM and AAF changes - Sunder (forward to Ritesh Nadkarni and team too)
    1. Leimeng to schedule the AAF review session for Casablanca changes
    2. VID, SDC, Policy agreed to keep the both http and https endpoints.

  7. VM11 test environment xDemo app access issue - Leimeng to verify

  8. HEAT-based ONAP deployment support should be dropped once OOM-based ONAP deployment's issues are fully identified and resolved.

    Recommendation from TSC: keep supporting HEAT in Casablanca for testing and integration purposes. However, HEAT won't be a gating item at Release Sign-Off.

  9. Platform Maturity - S3P goal: Absolute Minimum expectation:


    • CII badging passing level
    • Continuously retaining no critical or high known vulnerabilities > 60 days old
    • All communication shall be able to be encrypted and have common role-based access control and authorization.

    Desired expectation is full CII badging silver level, if not 75% towards that.

Attendees:

Discussion Items:

  1. Internationalization language support plan for Casablanca - PORTAL-267 - (Tao Shen shentao@chinamobile.com)
    1. Choose language/internal components
    2. In discussion by larger community (Use Case UI Team), expecting implementation details (Leimeng to followup)
    3. Leimeng has sent email to Tao Shen shentao@chinamobile.com on this topic and is waiing fr his return email
  2. Testing
    1. CSIT test for new Casablanca features - Sunder to schedule a session to go over the new features.
    2. Convert ECOMP selenium tests into CSIT ONAP Robot Framework tests - Sunder/Sireesh - Sunder to provide the ECOMP test scripts to Sireesh.
    3. Enable JavaScript Unit tests. (How will this impact the angular upgrade? Will these unit tests work as is even after upgrade?).
    4. Code Coverage needs to be maintained at 50% on both portal and portal/sdk repos without JS coverage.
  3. Reporting feature enhancement in portal/sdk -  OOM-1143 - Getting issue details... STATUS
  4. Defect fixes (Hima looking into items)

Casablanca Release (Nov 2018)

  • M1 Release Planning 
  • M1 Release Planning Checklist  
  • M2 Functionality Freeze 
  • M3 API/Data Model Freeze 
  • M4 Code Freeze 
  • RC0 Checklist 
  • RC1 Checklist 
  • RC2 Checklist 
  • Release Delivery