PTL 2019-08-05

zoom bridge: https://zoom.us/j/283628617

Duration 60 minutes

Duration

Agenda Item

Requested byNotes / Links
START RECORDING

Review agenda 

20 minsEl-Alto Release

Project Status in El-Alto Release

  • Today is the final due date to release your container Nexus3 repo (docker.release)
  • El Alto Staging situation - Brian Freeman reviewed the staging and master branches
  • Current High/Highest defects: Defect Status for El Alto
  • Test Coverage: Collecting Waiver request (Policy, AAF) - any other waiver
  • Platform Maturity (Jason): Feedback - El-Alto Release Platform Maturity
  • Security (Pawel):
    • Request PTLs to complete their CII Badging adjustment - time to practice!
    • OJSIs status update
  • M1 Planning
ModuleWithout jScriptWith jScript
ccsdk-dashboard66.618.4 - what can be achievable? 25%? Dan T. to confirm
aaf-authz4040 -> 50%?
sdc master48.348.4 → 55%?
ccsdk-sli-adaptors49.449.3 → 55%?
policy-engine57.749.7 → 55%?
portal72.9

21.6 → ?

Angular upgrade in Typescript code, so planning not to add JS tests in old code.

more details at El-Alto Risks

ccsdk-sli-northbound50.849.9 → 55%?
ccsdk-sli-core53.453.4 → 55%?
sdc-jtosca dublin53.753.7 → 55%?
sndc-northbound54.554.5 → 55%?

Others:

15minLF Infrastructure/Rel process
5 minsOOM StrategyWe are no more using the Manifest but the OOM strategy while releasing our container
5 mins

JIRA priority definitions

10 minsIssues with testing staging artifactsDan Timoney

The 'Staging Repositories' group in Nexus has a bug which causes it to always return the OLDEST instance of a staged maven artifact as opposed to the most recent. Thus, it is not practical to create docker artifacts based on 'staging' versions of maven artifacts. It is more reliable to use SNAPSHOTs, begging the question of whether it is useful to automatically create daily staging versions.

An alternative to consider would be to change our daily build process to build SNAPSHOT versions instead of staging versions, and then to only build the staging version when we are ready to create a release version.

5 minsCredentials in archived reposAmy ZwaricoA default password in in an archived ONAP repo resulted in an outside researcher submitting a report to the AT&T Bug Bounty program. We would like the PTLs to remove credentials from archived repos to avoid such submissions to ONAP or other vulnerability management programs. (move to 8/12)
10 minsRemaining Action ItemsPTL Weekly ONAP12, Mon UTC 13:00
5 mins

Incoming Events

Kenny Paul

Zoom Chat Log 

07:13:56 From Shankar Narayanan P N (AT&T) : we are working through the release jib changes as well. https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-17017
07:19:36 From Keong : instead of a staging branch, the charts could have a staging value and a release value. both values can be changed in the same commit and can be selectable at run-time
07:32:03 From Keong : ok
07:36:33 From Tony Hansen : can’t talk
07:36:53 From Brian : you are muted Tony ?
07:40:36 From Jimmy Forsyth (AT&T) : I’m getting can’t connect when trying to access https://bestpractices.coreinfrastructure.org/en
07:40:57 From Jimmy Forsyth (AT&T) : Anyone else able to access it?
07:41:37 From Kenny Paul (LFN) : @jimmy - link came right up for me.
07:49:16 From Brian : @Amy - we need to figure out what to do about integration since we are between PTLs
07:49:23 From Brian : wrt CII
07:49:43 From Amy Zwarico : @Jimmy, I was able to access it from the corp network
07:50:15 From Amy Zwarico : @Brian - sure. are you available later today?
07:53:23 From Jimmy Forsyth (AT&T) : @Amy, @Kenny, I can access through Firefox, Safari wouldn’t even give me option to accept the cert; maybe weirdness with corp proxy server
07:53:26 From Brian : yes - afternoon
07:57:29 From Kenny Paul (LFN) : dropping for finance committee meeting.

Action Items