Page Comparison

Meeting Dates

...

04/11/18 - APPC Project Weekly Minutes

Participants:Randa Maher; Patrick Brady; Scott Seabolt; Aaron Hay; ry303t; Skip Wonnell; Ramya Balaji; Vidhya Nerella; Andrej Zan, Shubhada Vaze; Takamune Cho

Recording: APPC Weekly Poject Call 4-11-18.mp4

Actions from last meeting:

...

Patrick Brady to provide a knowledge share on the changes that upgrade to Nitrogen brings to APPC once he is done with the ODL upgrade.
Randa Maher setup call to discuss testing in WindRiver APPC dev lab after we get Beijing successfully deployed.
Update: 3/28/18: Discussions started, but until we have a working Beijing environment
Update: 4/11/18: In-Progress
Ramya to identify the minimum VNF AAI data that is needed to validate ScaleOut. The work around that was provided only addressed the template model name.
- Update: 4/11/2018: CLOSED.
  A&AI information needed for scaleout.
  We need vnf, vserver, vnfc information – this is similar to existing flows.
  In addition, for ScaleOut, we need vf module information and model information.

New Actions Items:

ry303t to investigate security vulnerabilty reported againt org.glassfish.grizzly, which is pulled in by CDP-PAL.

Agenda & Notes:

Status on outstanding items
ODL upgrade (Patrick)Code Coverage
DMaaP issue (Ryan)
AAF Integration (Ryan)
Resolved all the issues of bundles not coming up & other issues he ran into
Ran into a CCSDK issue, JIRA CCSDK-236 opened; Dan provided a fix today
Should be ready to merge today.
Next step: Determine what environment we want to deploy new docker in our WindRiver Dev Env.
DMaaP issue (Ryan)
We got our fixes in; needed a new build from DMaaP for the MR client,.
Currently working to verify in our WindRiver environment, working through environment issues, but Ryan did test successfully in his local.
AAF Integration (Ryan)
Looks like shiro.ini goes away in Nitrogen (suprise!); need to figure out how to configure autherization in Nitrogen.
Ryan believes it's still just configuration that needs to be figured out and no additional changes in by AAF team.
Code Coverage
Folks have been diligently been submitting junits and we hit 50% yesterday.
Continue submitting up to RC0
Security items from CLM report (Taka)
Stability retest on
Taka updated Security checklist with more details to address questions from Stephen terrill on the jackon items.
Taka also added all of the critical items currently showing on the CLM list, but we expect that many of those will go away with the ODL upgrade; however, the risk is that we don't know what "new" items will be introduced by Nitrogen.
The item related to org.glassfish.grizzly is pulled in by CDP-PAL. Ryan will look closer into this one,
Stability retest on Beijing (Scott)
Waiting on Beijing with Nitrogen to rerun the 72hour soak test
Resiliency (Aaron)
Flow that will be validated by Integration: https://wiki.onap.
Testing
Aaron has been working with OOM and running test on frequent basis with each OOM change to ensure nothing breaks for APPC.
Everything so far is looking good
Healthchecks in External Labs Jenkins show APPC is successful.
Aaron is working with OOM team and Dan Timonry on MD-SAL persistent storage. Work is being tracked under the OOM-779 ticket.
Aaron is also working on updating the wiki with details on the OOM installation.
Testing
Manual Scale Out Flow that will be validated by Integration (Marco): https://wiki.onap.org/display/DW/Manual+Scale+Out+Use+Case?preview=/25438344/28377562/image2018-3-21_16-36-18.png
Question from Marco: How do we know if Healthcheck and ConfigScaleOut request are successful?
Answer sent via email:
App C success message and success return code can be found in the Karaf.log; however, they are debug logs.
status":{"code":400,"message":"SUCCESS - request has been processed successfully"}}
If there is a problem with completing the request, the log will have a status of 401 with an error message. If there is a 401, looking further before in the log, will show the stack trace and where the exception occurred.
Progress on testing
in WindRiver Dev lab
in WindRiver Dev lab
Scott and Ryan working to get DMaaP working in the Beijing/Carbon singleton lab. Anticipate having this resolved today.
Need to decide where we deploy Beijing/Nitrogen - do we replace Beijing/Carbon, replace Amsterdam, or spin up a new APPC?
Vidhya still having issues with access to the various VMs in the lab. Patrick and team will work with her to get past the issues.
Once items above are resolved, need to focus on ScaleOut testing. Scott will start looking into the needed AAI data.
Can we provide a demo to Marco?
Upcoming milestone - RC0 on April 19.
APPC Beijing RC0 Checklist
Misc items
Casablanca dates
Release Planning#CasablancaRelease
M1 = June 28, 2018 (Dev Start)
Beijing branching
Date?
Work items in prep: Upgrade to support Karaf 4
Casablanca
Release theme: "Deployability"
Dependency Driver Driven work:
ODL upgrade to NitrogenOxygen
MariaDB plus Galera
Code Coverage
Upgrade to Karaf 4
anything else?
Allow support for multicloud integration beyond Generic_restart - move named query up to DGorchestrator - low priority; not likely to get into Casablanca.
Vacations
Patrick is out on Monday, 4/16
Ryan is out on Friday, 4/13
Taka is out from 4/12 through 4/17

App C success message and success return code can be found in the Karaf.log; however, they are debug logs.
status":{"code":400,"message":"SUCCESS - request has been processed successfully"}}
If there is a problem with completing the request, the log will have a status of 401 with an error message. If there is a 401, looking further before in the log, will show the stack trace and where the exception occurred.

Versions Compared

Old Version 122

New Version 123

Key

04/11/18 - APPC Project Weekly Minutes