02-21-2018 Portal Platform Weekly Meeting

Owned by Manoop Talasila
Last updated: Feb 22, 2018
3 min read

Agenda:

  1. Check readiness of new CSIT team (Sireesh) on Robot test plan - Portal R2 Beijing Functional Test Cases

  2. Portal JUnit code coverage 50% target (Hari team)

  3. Review status on items assigned to dev team

  4. Go over JIRA list assigned for Beijing release

Attendees:

Sireesh, Hari, Girish, Naveen, Raghavendra, Ritesh, Snigdha, Surajit,  @Weiting, @Leimeng Shi, @Sunder Tattavarada, BINDU ELISETTY, HIMA (hbindu@research.att.com),

 Farhan Mir, @Manoop Talasila

Discussion Items:

  1. Sireesh started setting up local environment for robot test and reviewing test cases from previous release. 

    1. will contact Leimeng to know new features; 

    2. Hima will help setup the Portal in local testers machine.

  2. vm11 test environment to check the bugs and to perform testing - Sunder/Leimeng  discovered issue where new function code introduced, but not in DML script.

  3. AAF integration with SDC - help Micheal Lando - Sunder/Leimeng  Leimeng will send document to partners (check with Sunder too)

  4. Portal-182 - CLI integration help - Leimeng to setup a working session - @Sunder Tattavarada/@Former user (Deleted) 

    1. Start working on Jan 31st – Leimeng will organize a call with Sunder/CLI team on Wed 9:00am (Sunder could not join the meeting, when is the next meeting?)

  5. Portal-155 - security issues scan - Nexus IQ and Coverity scans

    1. Need Access on Nexus IQ - Farhan/S

    2. Coverity scan followup with Stephen.terrill@ericsson.com - Farhan

    3. many user stories created regarding this big item, pending to assign to developer. (assigned to Sudeep)

  6. Security issues status from CLM - Sudeep

  7. Plan to release SDK 2.1.0 version and then communicate to partners to update their poms - Sunder/Leimeng - ETA 1/19.  ==> update ETA to 1/25 - Sunder need help to find 

    1. Sunder emailed to LF team - however, LF team asked for latest build reference as the last build is 2 weeks old.

  8. Extend Portal-119 to split DB for Portal and SDK - Robert - design session pending and ETA on dev tasks. 

    1. Robert is using VM3 for this effort. → 70% done by Robert

    2. Update the deployment scripts with docker image name changes - 

      1. demo repo (heat templates); 

      2. integration repo (CSIT test deployment scripts); 

      3. OOM deployment;

  9. Sent grep scan on "master_dev" branch to check if "ecomp" appears in Portal - done - Hima will be cleaning up - ETA 1/10.

    1. ECOMP keyword in license text - followup with Catherine - Manoop ETA 2/16 ==> still pending

    2. java class names - we can leave it as is 

  10. JUnit /Sonar coverage to 50% on SDK and Portal. 

    1. SDK - JUnit test coverage reached 14% - Hima (pending code review and push to gerrit) - Code need to push to gerrit - https://lf-onap.atlassian.net/browse/PORTAL-161

      1. Shireesh will coordinate his team with Hima and Kishore Gujja

    2. Portal - target 30% to 50% - Girish/Hari team will continue from Gerrit -https://lf-onap.atlassian.net/browse/PORTAL-136

      1. Hari is coordinating the remaining code coverage on Portal (right now it is at 44%)

      2. Manoop to followup with Gildas on the Sonar upgrade issue which got 2% down for portal form 40 - 38% (this is due to change in sonar calculation with new upgrade).

  11. Discussed remaining JIRA items in great details → portal-151 

    1. (assign priority from items in wiki page to JIRA by Leimeng)

  12. MUSIC integration - add JIRA epic/US - Sunder to provide the % complete

    1. Development is targeting to complete by 02/28

    2. Leimeng to coordinate a meeting to share the MUSIC integration details with testing teams to plan the test strategy for these features.

  13. AAF, if AAF is not ready for testing by 2/15, then Portal will not integrated with AAF for Beijing release - Leimeng send email to Sai - Is the AAF instance ready in LAB env to test the integration?

  14. Defect tracking of Critical and Highs - Naveen and Shireesh to coordinate with Leimeng to test and close them and raise as concern if cannot be closed.

  15. Beijing Release Planning:

  16.  

    1. M0 - dev kick-off, Nov 16

    2. M1 - planning Jan 16

    3. M2 Functionality Freeze Feb 12, 2018 →  fill in the contents by Manoop & Leimeng

    4. M3 API/Data Model Freeze Mar 8, 2018

    5. M4 Code Freeze Mar 29, 2018