Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

2018 PTL RecordingsZoom Chat Log

Duration 60 minutes

DurationAgenda ItemRequested byNotes / Links
START RECORDING

Release Management Status

Including:

  1. ONAP deployment: While doing the deployment of your Docker image, do you have to run  a “git clone” cmd or in other word is there “git clone” call in the Dockerfile?
  2. Sync up from Helm chart to Docker Manifest files
Gildas Lanilis GmailONAP Casablanca PTL Nov19Version1.pdf

Heat Installation removal in ReadTheDocs for Casablanca releaseGildas Lanilis GmailReadTheDocs

Integration Testing StatusHelen Chen

DocumentationSofia Wallin

Questions on CLM jobs going forward, PTL responsibilities.

(20181111 add oparent clm daily build - not weekly to keep CLM count at 0,0 for the root oparent pom) - https://lists.onap.org/g/onap-discuss/topic/oparent_spring_5_0_9_versions/28087317?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,28087317

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyTSC-50

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-716

Postponed to next week


Grant nexus-iq access to non-committer contributors seeking to fix CLM issues

While I understand the dual reasons why we protect clm content from non-committers - we are loosing the active contributors that fall out of the access scope.

The access is currently binary - because anyone can get a non-vetted LF account - it needs to be 3 part - in order to work and accelerate clm work

Committers, contributors, the rest of LF users.

1) to abide our license agreement
2) to not disclose out vulnerabilities beyond vetted committers

Proposal: allow for vetted contributors that can access nexus-iq and the security space. This could be done by providing a way for all contributors to be a committer on at least one project - or create a sandbox project we can vet committers to.

Gildas raised a good point - verify we are not overriding any oparent versions that already fix the dependencies

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyTSC-49

/wiki/spaces/SV/pages/16089838

Postponed to next week


Status on nexus-iq replacement - github now has a fully functional microsoft contributed vulnerability scan - the owner of github.com/onap should see them

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyTSC-32

Postponed to next week

Notes

Action items

  •  @LFHelpdesk: Ticket#63980. to address Jenkins, JIRA and Gerrit slowness. Over the week-end all systems were very slow.
  •  Dan Timoney close all SDNC and CCSDK Jira tickets and release Docker Image by COB Nov 19.
  •  Seshu Kumar Mudiganti to close
    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySO-1214
     and 
    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keySO-1235
     and release Docker Image by COB Nov 19.
  •  Michael Lando to provide logs for 
    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyDMAAP-885
  •  Mike Elliott to discuss further with Integration for closure of 
    Jira Legacy
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-1516
  •  Takamune Cho Release APPC docker image by COB Nov 19. 
  •  Michael O'Brien CLM license schema not friendly to open source community. Michael to summarize issue and bring it to TSC.
    •  will fill out more 
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyTSC-32
       and post to onap-discuss
  •  @All . Perform sanity check on Documentation and remove statement such as "In this first ONAP Release" or "In the Amsterdam Release".

Other Discussion

  •  "Git clone" on other repo than ONAP is OK. apt-get installs (and the likes) are ok 
  •   

...