...
- progress of Angular UNIT test cases - need to edit the pom files for angular (Lorraine sent email last week)
- https://nexus3.onap.org/#browse/search=keyword%3Dportal - how do we get the portal-BE here - ask Sunder, and then contact Dominikthere - read https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process
- SDC-2684Service Design and Creation - Update to Portal SDK v2.6 - SDC needs help https://wiki.onap.org/display/DW/Portal+SDK+usage - we need to document the changes if they are not already; if they are, where is it documented? - Sunder is willing to have a working call with Ofir to work this issue.
- Leimeng will send email to AAI to see if they need help upgrading to SDK 2.6.0
- https://wiki.onap.org/display/DW/OOM+NodePort+List for port info - create Jira ticket in OOM if you need a port; also ask Sunder why we have it was asked why are there so many ports listed for portal, in checking oom I see in:[oom.git] / kubernetes / portal / charts / portal-app / values.yaml that several are due to the loadbalancer:
19 global:
20 nodePortPrefix: 302
53 service:
54 type: LoadBalancer
55 name: portal-app
56 portName: portal-app
57 externalPort: 8989
58 internalPort: 8080
59 nodePort: 15
60 externalPort2: 8006
61 internalPort2: 8005
62 nodePort2: 13
63 externalPort3: 8010
64 internalPort3: 8009
65 nodePort3: 14
66 externalPort4: 8443
67 internalPort4: 8443
68 nodePort4: 25
- Wind River is UP: The WindRiver lab that we used so far for ONAP testing has been moved to a new location, so we need to change the IP address in the ovpn file from 192.55.48.241 to 146.152.204.133. Please upload the ovpn file again into your ovpn client to make changes effective. Your ovpn client may ask you to reinsert your username and password, you should have them in the original configuration package that Stephen Gooch sent you when you were granted access to the Intel VPN. Wind River hasn't been up and running - ask at the ONAP Stand up meeting where to test - Lorraine - it was suppose to be up 1/13 or 1/14 and as of 9 PM 1/14, it is still not up
- It was reported by Dominik that using Java 11 did not work due to the Jenkins job; To move to Java 11 in Frankfurt the Jenkins processes need to be upgraded.
Please take a look at this example review for your ci-management jobs to work with JDK 11, need to add a field to specify using Java 11 as 8 is default.
https://gerrit.onap.org/r/c/ci-management/+/99138/1/jjb/externalapi/externalapi-nbi.yaml
- our junit tests would not work if we upgrade right now, we need time and resources to upgrade; sdk also fails to build; when integration with Portal-BE happens we can work on migrating all parts to java 11. - Portal high and highest bugs:
...
- Security Vulnerability going forward need to be addressed by creating Jira tickets in the backlog and as time permits developers should make the upgrades SDK Upgrades - AAI needs to be contacted for status, VID, DCAE are being worked with, we are waiting to hear back from SDC
Dec 18 2019:
Sonar coverage stats: The reports will now be posted under: https://sonarcloud.io/organizations/onap/projects
...