Page Comparison

...

1. Action items:
   1. Design documentation on OJSI - 190 - Sunder Tattavarada
   2. Saisree to provide update versions for few components - Sunder Tattavarada/Saisree
   3. Create a Jira item to notify the breaking changes on portal due to portal/sdk changes. (submodule changes and merge jenkins jobs changes) - Lorraine A. Welch
2. 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
3. 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
4. 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. Jira Legacy
      server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=GerritSubmittedReviews serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

5. 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. Jira Legacy
      server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=ElAltoHighHighest project = PORTAL AND issuetype = Bug AND priority in (Highest, High) AND resolution = Unresolved ORDER BY updated DESC serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

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

   4. Jira Legacy
      server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=ElAltoMedium serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

   5. Medium not assigned to a release

   6. Jira Legacy
      server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=ElAltoMediumRest serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

   7. LowLowest

   8. Jira Legacy
      server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=ElAltoLowLowest serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176

...