02-07-2018 Portal Platform Weekly Meeting

Owned by Manoop Talasila
Last updated: Feb 07, 2018 by Former user (Deleted)
3 min read

Agenda:

  1. Check readiness of new CSIT team (Sireesh) on Robot test plan

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

  3. Weekly meeting time change to accommodate new team in India - Manoop requested the time change to Wed 11AM EST - ONAP Helpdesk #51641

  4. Review status on items assigned to dev team

  5. 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. will contact Leimeng to know new features.

  2. Sunder is syncing Portal code between codecloud to gerrit tonight, so TechM team can have latest version for JUnit test.

  3. 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.

  4. AAF integration with SDC - help Micheal Lando - Sunder/Leimeng    Leimeng will send document to partners

  5. Add Hari, Vikram, and Sireesh to resource list - Leimeng/Manoop 

  6. Who is the replacement for testing lead? - Leimeng to followup - Done 

  7. Session to be scheduled to plan for the JUnit and Robot tests for Beijing - Sireesh

  8. Portal-151 - followup with usecaseui and schedule a session to review the architecture - Leimeng - Done - scheduled at 4:30PM EST today.

  9. Portal-182 - CLI integration help - Leimeng to setup a working session - @Sunder Tattavarada/@Former user (Deleted) - Start working on Jan 31st – Leimeng will organize a call with Sunder/CLI team on Wed 9:00am

  10. 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   many user stories created regarding this big item, pending to assign to developer.

  11. 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 

  12. Extend Portal-119 to split DB for Portal and SDK - Robert - design session pending and ETA on dev tasks. ==> Robert is using VM3 for this effort. → 70% done by Robert

  13. 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 and java class names - followup with Catherine - Manoop ETA 1/17 ==> still pending

  14. SDK will be next to scan - Lorraine - ETA 1/11 - done

  15. Split Portal-19 to Hima and Robert (based on Lorraine's scan output)  - create tasks based on the scan 

    1. Robert to analyze the font "Omnes-ECOMP-W02".

    2. Analyze backend changes - Hima. 

  16. 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 - PORTAL-161: Add the JUNIT plumbing for PortalSDKClosed

    2. Portal - target 30% to 50% - Girish/Hari team will continue from Gerrit -PORTAL-136: Raise JUnit test coverage ONAP Portal to 50% for BeijingClosed

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

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

  18. M1 due on 1/18/2018 (same template as Amsterdam) - Manoop/Leimeng - Done

    1. Portal Platform M1 Release Planning (Beijing Release)

    2. Portal Platform Deliverables for Planning Milestone Checklist (Beijing Release)

  19. Check with IBM team members - Manoop/Abbas/Sunder - Done

  20. MUSIC integration - add JIRA epic/US

  21. 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

  22. Beijing Release Planning:

  23.  

    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