...
- PORTAL-429 Failed to access Policy GUI from Portal Portal (POLICY-1210)
- need to confirm the reason, could be the OnBoarding script / URL update
- George & Michael from Policy team confirmed it's the URL issue, port number issue
- same reason as PORTAL-457
- OOM images are not getting automatically updated? we need to open a defect - Manoop action item (done):
https://jira.onap.org/browse/OOM-1483 high defect
- Their docker image is used to run the OnBoarding sql file - who updates it
- are they done for Casablanca?
- it is done manually now
- in Dublin, we can use the OOM update script, put the OnBoarding script in OOM and remove it from the deliveries folder, change the script to update rather than insert
- for Casablanca : take update statements and put in OOM update script
- JIRA ticket OOM- this is to remove the manual aspect - ticket by Michael; we can add to this ticket to tell them about the docker image issue
- this docker image has our Mariadb in it; in our PORTAL folder in OOM
- Our OOM script was pushed 8 days ago, we made changes 4 days ago, needs to be pushed again OR we can just add update statements in /oom/kubernetes/portal/charts/portal-mariadb/resources/config/mariadb/oom_updates.sql
- PORTAL-434 needs update encrypted password in the same script
- PORTAL-457 some of the tables are not getting updated - fn_role;
- OOM script needs our latest OnBoarding script, they are taking the wrong version
- temp fix update the Beijing release script that OOM is using - Manoop and Sunder, Sireesh will test
- Policy meeting later today
...