0800 PST not 0600 PST for this one https://lists.onap.org/g/onap-tsc/topic/updated_event_ptl_meeting/28631547?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,28631547
Duration 60 minutes
| Duration | Agenda Item | Requested by | Notes / Links |
|---|---|---|---|
| START RECORDING | |||
| Integration Testing Status | AI: Helen Chen to follow up with Use case owner and update wiki page. | ||
| Release Management Status | Gildas Lanilis Gmail | AI: Gildas Lanilis Gmail Follow up with Tao Shen on USECASEUI-174 - Getting issue details... STATUS AI: Gildas Lanilis Gmail follow up with non-present PTL on their confidence to meet the Nov 15 to release their latest Docker Images | |
| Kubernetes Version Governance | TSC-46 - Getting issue details... STATUS AI: Michael O'Brien to update community on new K8S version | ||
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 | |||
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 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 | |||
| Status on nexus-iq replacement - github now has a fully functional microsoft contributed vulnerability scan - the owner of github.com/onap should see them | |||
Notes:
- RC2 is rescheduled on Tuesday, Nov 27 at 6:00 am PST
- Sign-Off is rescheduled on Friday, Nov 30 at 6:00 am PST
- New Docker MUST be released by Nov 15, COB.
- After Nov 15, authorization is required from Integration Team
- Bugs Priority
- Focus FIRST on functional defects
- If time permitting (before COB Nov 15) include security, otherwise postpone Security bugs for Casablanca Maintenance
Special PTL Actions from the last TSC Call:
- Create their Casablanca branch not later than Nov 12th (if not yet done)
- Nov 15th, Provide the latest “Release” containers
- After Nov 15th, Soak period i.e. any new code change on the Casablanca branch must be reviewed/approved by the Integration Team
PTL presence to weekly PTL meeting:
While going around all projects to get a sense of confidence for releasing latest Docker Images by Nov 15, we came to realize that 11 PTLs were not attending the weekly PTL meeting (nor sending a proxy).
As a reminder, PTL's presence (or a delegate) is expected.
Action items
- Gildas Lanilis Gmail Follow up with Tao Shen on USECASEUI-174 - Getting issue details... STATUS
- Gildas Lanilis Gmail follow up with non-present PTL on their confidence to meet the Nov 15 to release their latest Docker Images
- Michael O'Brien to email community on new K8S version
- Helen Chen to follow up with Use case owner and update wiki page.
Zoom Chat Log
06:15:55 From Pamela Dragosh : Security issues aren’t bugs. It should be a task to remove them.
06:16:21 From Michael O'Brien : Some are blocking like INT-716 - I cannot release without that fix
06:16:41 From Keong Lim k00759777 : AAI-1880 comment says it's been fixed. case should be close
06:18:50 From Catherine Lefevre : Need an assessment from teh Security Subcommitee
06:18:59 From Helen Chen : https://jira.onap.org/browse/INT-716
06:19:03 From Catherine Lefevre : can be part of the maintenance release Jan 31ST?
06:20:00 From Brian : kind of scary to change oparent so late
06:20:14 From Pamela Dragosh : I will not upgrade to new parent. Too late.
06:22:57 From Brian : th e issue is when is "too late"
06:23:54 From Pamela Dragosh : PTL determines that. Some are trivial, some are not.
06:23:59 From James MacNider ( Amdocs ) : Can we tie that to a milestone?
06:24:46 From Taka Cho : Pam +1
06:27:27 From Keong Lim k00759777 : isn't the cut-off date the code freeze milestone?
06:28:46 From Michael O'Brien : logging/pomba has James Macnider and Prudence and the rest of the team to do all the log/pomba CLM team - should be OK by thu TSC
06:28:53 From Pamela Dragosh : Not for security issues. We fix as soon as reasonably possible. Right now we are closing in on a release, so it is up to the PTL to decide.
06:33:29 From Catherine Lefevre : Special PTL Actions from the last TSC Call: 1) Create their Casablanca branch not later than Nov 12th (if not yet done) 2) Nov 15th, Provide the latest “Release” containers 3) After Nov 15th, Soak period i.e. any new code change on the Casablanca branch must be reviewed/approved by the Integration Team
06:42:32 From Vijay Venkatesh Kumar : DCAE healthcheck is good on Integration-OOM-Daily tenant.. Ran the healthcheck robot report - that passed as well.
06:46:23 From Dan Timoney : FYI … takes about 2-3 days to do release builds for CCSDK and SDNC (CCSDK has to be first) … so if I start right after this call on the first CCSDK repos, I should be okay (didn’t want to take up time on the call saying all that)
06:49:54 From Michael O'Brien : I find watching the integration repos - auto triggers, watching critical wiki pages and watching rocket-chat also is good for PTL's to keep in contact with integration - especially changes by Gary in git
06:55:28 From Michael O'Brien : I have 3 failing master builds - but they are normal transient jenkins timimg issues and are fixed by a recheck
06:57:20 From Taka Cho : @Dan, APPC needs CCSDK to release first also.
07:06:31 From Keong Lim k00759777 : are CLM results sent as notifications or does it require PTL to poll the page for updates?
07:06:49 From Gildas Lanilis : PTL requires to lokk at clm report.
07:06:53 From Jimmy Forsyth (AT&T) : PTLs have to look at the reports per repo to get details
07:06:58 From Gildas Lanilis : every week.