...
When: Occurs every Wednesday from 9:00 AM to 10:00 AM. (UTC-05:00) Eastern Time (US & Canada)
Changes saved
Where: https://zoom.us/j/895776501
Agenda:
Today:
Last Week:
- progress of Angular UNIT test cases (email from Mamtha Sabesan - mamtha.sabesan@in.ibm.com)
Team has started committing Angular Test cases (I believe around 7 commits done so far by Rupinder).
To reach 55%, ( considering teams leave plan also), is 3 weeks. So by Feb 17th we should be good state.
We have setup sonar in our local system to see the coverage, but team is not sure what in pom.xml needs configuration changes to setup coverage observation in build environment. We are continuing our analysis, meanwhile any directions on this front would be helpful.
- Wind River - ONAP Portal running in Integration Release Daily with Image: 10.12.5.2:5000/onap/portal-app:2.6.0 - ask Sunder when we will have a new image; based on testing in this environment Portal-653 Can't access AAI from Portal was marked as delivered; Created AAI-2772 asking AAI to register UI’s new role “ui_view” in AAF
- Cassandra issue - Portal-796
- Integrate the new oparent into the build process - Portal-739
- PORTAL doesn't work correctly when using default k8s ingress - Portal-806
- Portal SDK usage
- gerrit reviews: https://gerrit.onap.org/r/#/q/project:portal/sdk and https://gerrit.onap.org/r/#/q/project:portal
Prior:
- - need to edit the pom files for angular - we need to get to 50% coverage for Angular code in the next week or two:
- https://nexus3.onap.org/#browse/search=keyword%3Dportal - how do we get the portal-BE there - 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://nexus3.onap.org/#browse/search=keyword%3Dportal - how do we get the portal-BE there - read
- https://wiki.onap.org/display/DW/OOM+NodePort+List for port info - create Jira ticket in OOM if you need a port; 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: - Have Manoop or Sunder check to see if there are any unnecessary ports
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. 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
- Try deploying Portal/AAI in local VM - Lorraine, let Dominik know - at a minimum you need to deploy Portal and AAF
- AAI changed role name, it needed to get into AAF - Leimeng will check
- Angular code coverage needs to be at 50%
- Robot framework is being set up by Deepansha and Sireesha
...
All portal high or highest bugs
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Release Planning:
...