Logistics

• We passed our latest license scan.  We’re in pretty good shape.
• We no longer have any critical security issues, but there are a few “severe” ones.  We need to look at those and document our analysis on the vulnerability page to maintain our CII badge.
• Most of our repos are at 50% code coverage (or for python, can produce local evidence of 50+%). However, we have a few repos that are low.  We need to fix that.

M4 Code Freeze

Please plan to attend or have a delegate.  This is our last call before the code freeze (M4) and we need to clean up Jira and go through our checklist. For each person, we need to review:

1. Which tickets do you expect to close by next Thursday (really, Tuesday so that Gildas has a chance to review)?
2. Which tickets will you NOT close by M4?
3. Are all your unit tests and CSIT tests uploaded? Are they working?
4. Is code coverage >50% in Sonar?  For python, do we have local evidence for >50% (I know we’re having problems with Sonar)
5. Are all your Jenkins jobs working?  If not, do you have a plan to fix them, or are you running into any problems?
6. Are your builds and docker containers showing up in Nexus?
7. Do you foresee any blocking issues or other risks going into the code freeze?
8. We don’t need documentation by M4, but are any of you already working on docs?  Any gaps we need to fill?
9. What progress have you made towards S3P?  We need to fill out the S3P table on the wiki.
   

1. Alex: Building examples/guide, victor/shitao implemented them. Working on a webpage to illustrate HPA usage. Victor needs to make some additional changes for vCPE use case.
2. Andrei: Not present
3. Andy: Need to update JIRA issues status. Info model is ready but Data Models aren't there yet. This is a risk. Gap analysis between heat and tosca still underway.
4. Bruce: On travel
5. Avinash: Not present
6. Gokul: On track
7. Lianhao: We may have to do a maintenance release once VNFD is finalized.
8. Victor: Not present
9. Murali: SDC docker is not working

Chris reviewed the M4 checklist.

API documentation is now in Swagger. We need a consistent structure for the API documentation. How is API versioning handled?

ONS Sessions (ONAP Breakouts + Thursday session)

https://wiki.lfnetworking.org/display/LN/LFN+Developer+Forum+Schedule

https://wiki.lfnetworking.org/display/LN/ONAP+Project+Specific+Breakouts

Any new business?