Attendees:  

  Lorraine Welch, Piyush Garg, Sunder Tattavarada, Amy Zwarico, Krzysztof Opasiak, Manoop Talasila, Dominik Mizyn, THIRILOSHINI KRISHNAKUMAR

When: Occurs every Wednesday from 11:00 AM to 12:00 PM effective 1/23/2019. (UTC-05:00) Eastern Time (US & Canada)
Where: https://zoom.us/j/895776501

Agenda:

 Today

El Alto plans:

  1. Database DML and DDL scripts, including Apps_Users_Onboarding_Script.sql and oom_updates.sql.
    1. Naming conventions currently 
    2. Are migration scripts necessary or just fresh installs? (from Dublin to El Alto release)
      1. MariaDB - https://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_user_guide.html#upgrade
      2. Cassandra - only fresh installs are necessary
    3. Proposed from last week: Move  Apps_Users_Onboarding_Script.sql from Portal/Deliveries  to OOM directory ([oom.git] / kubernetes / portal / charts / portal-mariadb / resources / config / mariadb / )
    4. Proposed from last week: Sunder will disable the old  Apps_Users_Onboarding_Script.sql in the old image
    5. Piyush Garg is interested in migration scripts ; Lorraine would assist as necessary
  2. OJSI - 190  user/passwords in Portal?
    1. AAF supports passwords for users. ask Jonathan for user/password authentication
    2. does CADI have session cookie? fallback -  hash the passwords. 
    3. App id/password for system to system - their password needs to be hashed too
    4. AAF now stores password hashed ; supports basic AUTH (is not hashed, just encoded)
    5. Portal partners don't have to hash their own but Portal needs to hash them
    6. should be reasonable to plugin CADI - do they support cookie-based?
    7. Changes will be for  user to system and system to system
  3. Security gerrit reviews have to be completed; conflicts have to be resolved: Manoop will talk to them for smaller decoupled commits (3-5 is preferable)
    1. Sunder will connect Dominic with Portal team making similar a change  

    2. Key Summary T Created Updated Due Assignee Reporter P Status Resolution
      Refresh

  4. Go over the Jira tickets related to El Alto and  discuss  what is appropriate to include and what resources to accomplish it.
    1. High and Highest Jiras:

    2. Key Summary T Created Updated Due Assignee Reporter P Status Resolution
      Refresh

    3. Medium assigned to a release (Is the VID issue PORTAL-555 a portal issue or a VID issue?)

    4. Key Summary T Created Updated Due Assignee Reporter P Status Resolution
      Refresh

    5. Medium not assigned to a release

    6. Key Summary T Created Updated Due Assignee Reporter P Status Resolution
      Refresh

    7. LowLowest

    8. Key Summary T Created Updated Due Assignee Reporter P Status Resolution
      Refresh


Next week:

  1. Raptor feature changes made for ENMT SDK need to be added to ONAP Portal SDK
  2. Check documentation
  3. Testing - check with Sireesh
  4. Log improvement


Older Issues:

  1. request Sunder to review the open gerrit reviews; Sunder's team is going to review the gerrit commits and if good, we will merge

  2. Sireesh to update on his testcases; Sireesh is working on it

  3. Sireesh will ask Saravanan about his Angular changes and get back to us; we need to find his code, ng-app - how to trigger this page


  • PORTAL-330 - Getting issue details... STATUS  - Deven and Saravanan started the userstories. - Action item - Manoop review and push to next release - update: still in progress
    • PORTAL-507 - Getting issue details... STATUS  - Saravavanan to explore the new screens to identify best screen to upgrade polymer. - update: still in progress
    • PORTAL-516 - Getting issue details... STATUS  - Deven upgrading the springboot - starting with os, common (might not be needed) overlay projects to load the system.properties file. - update: still in progress
            • all springboot dependancies were found and code is getting complied
            • hibernate update needed to be compatible with springboot 2.1.3 - might possibly use jpa
            • identify properties across app, where should they be put (should load at runtime) ; 2 ways to do it external configuration or property placeholder configuror 
              • app-os needs properties - need to combine from different file of different project - this will go in the resources section of app-os
              • in spring.xml there will be a property placeholder configuror section 
              • spring application json is the other way - looking at it
            • converting to springboot needs appl context has to be created from one class; discovering how to do this
            • annotations or xml (or both)
            • usually a java class to implement (starting point of springboot application ) application context - needs more info on this concept
            • will look at sample application to figure how configuration is stored
            • started a sample springboot app - Deven still working on this
    • PORTAL-508 - Getting issue details... STATUS  - Saravanan was working on Angular and Polymer - update: still in progress
      • Last discussion was on to use Polymer or not - status??
      • Roles page -example is in Gitlab
      • Deven worked other projects this past week, will try and spend time this week on this - Deven not working this now


  • Highest and High Defects:  




All portal bugs

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

El Alto Release (Sep 23 2019) aug 9 dev sprint end



  • No labels