Agenda:

1. Casablanca goals are being defined here https://wiki.onap.org/display/DW/Casablanca+goals

2. CSIT tests status - jenkins jobs

3. Defect fixing

Attendees:

Sireesh, Hima, Robert, Naveen, Naveen,  Farhan, Sunder, Manoop

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; 

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

• set up new test cases

• found some bugs, to work out with the development team

• environment set up; scheduled call on this for this afternoon

• For PORTAL-173 : 24 test cases from before, added 12 more , will check in test case scripts this week into gerrit (deadline - RC0 - 04/19)

  • Issue: DB connection issue making the CSIT verify job to fail.

  • Sireesh will commit the cases to gerrit - depends on CSIT verify job.

2. Defects List focused for RC0 - 4/19:

3. Leimeng will send document to partners (check with Sunder too) ASDC descoped AAF integration 

• plan to integrate with portal only, just got details about a running instance, next action item is to test it, needs info from Sai

• will decide whether to include in Beijing - We provided below comments to the on-boarded teams about AAF integration plan:

  • The current status for Beijing release is that the Portal team have integrated the AAF libraries and pending on testing with the live AAF instances in the Lab environment (now it is too late for this testing, so it cannot be completed in Beijing, so this will be completed in Casablanca release).

    
    
    

    What does this mean to on-boarded apps about authentication and authorization?

    The Portal handles the authentication. However, the Portal use AAF for authorization. So, all the user roles can be loaded into AAF. But, for example, the roles specific to SDC will not be accessible to them unless they upgrade to the latest SDK that support AAF changes. The SDC team have scoped their SDK upgrade for later release. So, as the partners upgrade their portal’s SDK, their user roles will be supported by Portal through AAF in following releases. Until then, the portal supports backward compatibility for the roles support.

4. Portal-182 

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?)

2. Another working call was made and Making progress - check with Sunder

3. this ticket is in reopened state

4. Naveen will close

5. Closed

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

• Allow guest access to integrate CLI app

• New docker version number of CLI docker images - create JIRA item (Manoop) and Check with @Former user (Deleted)

5. Security issues status from CLM (Nexus IQ)  - Sudeep  -  this is Portal-155

• pull request made, fixed in portal; but not SDK, new pull request for SDK will be made for what is working

• ETA today for pull request - SDK

• merged in portal/sdk - done

• sdk onap issue working

• this ticket is in open state

• Farhan and Sudeep working on it

• wiki page for pending security issues - Farhan  -Portal Platform Security/Vulnerability Threats - updated wiki

• made some changes, working on new issues

• Reply to Stephen (from Ericsson) about the questions on the vulnerabilities - (Farhan/Manoop) - ETA 4/4

6. Extend Portal-119 to split DB for Portal and SDK - Robert - design session pending and ETA on dev tasks.  - Robert working on it now

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

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

3.  

   1. demo repo (heat templates) - done

   2. integration repo (CSIT test deployment scripts) - done

   3. OOM deployment - Michael O'Brian

   4. Provide new update script for OOM (basically updating fn_app and menu tables) - check with Gary for oom yaml file update (Manoop) - ETA RC0 - 4/19

7. 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 - resolved check email

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

3. * ECOMP is a trademark and service mark of AT&T Intellectual Property.        ---------- Can be removed

4. Catherine suggested via email: I would suggest to remove it in the License.txt file posted on the root repo. Then later on, change in file you are updating.

5. assigned to Hima ECOMP trademark; will assign to someone else (waiting on CSIT tests to succeed before pushing this change) - ETA 4/4.

6. Lorraine to run grep scan for ecomp keyword 3/28/18

8. JUnit /Sonar coverage to 50% on SDK and Portal. - Deadline March 15th for SDK

1.  

   1. SDK - JUnit test coverage reached 19.7% - Hima (pending code review and push to gerrit) - Code need to push to gerrit - PORTAL-161  -  Add the JUNIT plumbing for PortalSDK   Delivered

   2.  

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

      2. Local version is up to 24-25%, planning on pushing today - Sitharaman

      3. 26.1%

      4. Saravanan  now  37.7%

      5. JIRA ticket is in delivered state; I recommend reopening and putting in in progress state until 50% is reached

      6. 49.6*

      7. 50%+ Hima will close

Portal - target 30% to 50% - Girish/Hari team will continue from Gerrit -     PORTAL-136   -  Raise JUnit test coverage ONAP Portal to 50% for Beijing   Open

1.  

   1.  

      1. Hari is coordinating the remaining code coverage on Portal (right now it is at 48.7%) - Kishore,

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

      3. 50.2 close ticket

      4. now 50.5 Portal-136 should be Closed, it is still in open state

      5. delivered state - Hima will close

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

3. on-track, couple days to wrap up development

4. Robert 80% finished; needs more testing - Tested now.

5. 100% done, needs verification - Sunder

12.  Need to:

• to release SDK & release docker artifacts in-progress - depends on CSIT - ETAs?

• documentation - release notes - Lorraine

• critical  JIRA ticket

• test-automation scripts

13. Beijing Release Planning:

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 - done

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

5. M4 Code Freeze Mar 29, 2018

6. RC0 Checklist Apr 19, 2018

7. RC1 Checklist May 3, 2018

8. RC2 Checklist May 17, 2018

9. Release Delivery May 24, 2018