PTL 2020-02-03

PTL 2020-02-03

Agenda

START RECORDING

Duration

Agenda Item

Requested by

Notes / Links

Duration

Agenda Item

Requested by

Notes / Links

30

El Alto retrospective

@David McBride

El-Alto Retrospective

30 min

Requirement Status M2/M3

 

  • The following requirements have open issues that must be resolved ASAP

    • https://lf-onap.atlassian.net/browse/REQ-140  status (Hampus Tjader, @Pawel Baniewski , @Benjamin Cheung ) - recommend approval (Pawel to send email to David with risk assessment)

    • https://lf-onap.atlassian.net/browse/REQ-136 status (@Pawel Baniewski ) - Pawel recommends de-scope

    • https://lf-onap.atlassian.net/browse/REQ-134 status (@Benjamin Cheung ) - Pawel recommends reduced scope (remove external certificate)

    • https://lf-onap.atlassian.net/browse/REQ-76 status (@Oskar Malm@Former user (Deleted)recommend approval@Oskar Malm

    • Documentation of allotted resource model / status of review (@Andy Mayer) - Andy recommends approval - review IS the work.  Review expected to be completed in two weeks. NOT blocking - no code impact.  Incorrectly labeled yellow.

    • SECCOM requirements (@Paweł Pawlak@Amy Zwarico)

      • Amy to share list of projects that have not yet responded

      • Amy to reply to projects that responded by email but did not create JIRA

  • Helm charts (@Mike Elliott)

    • Requirements should be identified and vetted as part of the release planning process (M0 - M1)

    • If this is not possible for some reason, projects should be notified as follows:

      • JIRA issue with affected PTLs added to the issue as watchers

      • Presentation in the relevant subcommittee

      • Presentation to the PTL meeting

      • Gerrit review including all affected PTLs as reviewers

Requirements Status M4

 

  • Any concern about Frankfurt M4 JIRA ticket content?

  • PTLs raised concerns that the code to support cases/requirements will be pushed too late, impacting their M4 commitments
to be discussed on Monday to understand what''s the deadline that PTLs will accept code changes.

LF IT Support

@Jessica Gonzalez

Testing Environment

 

Any concern short term about AAF certificates?


Testing Improvement

 

 

CSIT Review

 

 

ToolChain Improvement

 

 

Documentation

@Sofia Wallin

the TSC has approved the migration of the Doc repo away from using git submodules to uning  intersphinx linking instead 

Other Improvement suggestion

 

 

Subcommittee Updates for PTLs

@Amy Zwarico@Paweł Pawlak

  • SECCOM Review Calendar to progress on Security OSGI

  • requesting input on certifying the ONAP jdk version

Sharing Best Practices

 

 

IF TIME ALLOWS ....

15 mins

Release status

@David McBride

@Paweł Pawlak @Jason Hunt

@Alla.Goldner

@Stephen terrill

@Hui Deng  @Andy Mayer

@Pamela Dragosh

 

5 mins

Upcoming Events

@Kenny Paul (Deactivated)

  • Certified ONAP Professional (COP) Beta Deadline is Feb 15th - https://lists.onap.org/g/onap-tsc/message/5878

  • Open Networking & Edge Summit (ONES), NA, Los Angeles, April 20 - 21

    • CFP will be closed by Feb 3rd, 2020.

    • ONAP TSC is submitting the following abstract:: ONAP and Cloud Native – The Best of the Two Worlds

  • ONAP 2 day event after ONES North America - April 22nd-24th (TBC) - Los Angeles

  • LFN Developer and Testing Forum, Seoul, South Korea, June 1-4, 2020

  • ONAP 2 day event after ONS North Europe - Antwerp (TBC)

  • Survey coming from LFN for Dec OR Jan for steady-state full DDF meetings to all LFN communities & locations

10 mins

Remaining Action Items

@David McBride

PTL Weekly ONAP12, Mon UTC 13:00

Zoom Chat Log 

06:02:33 From Kenny Paul (LFN) : Just FYI- I have the SPC this AM so will be leaving PTL call @ 7am today.
06:56:04 From Kenny Paul (LFN) : need to drop for SPC call
07:38:28 From Amy Zwarico : dropping

Action Items 

@David McBridemock up proposed requirements issue for Guilin
@David McBride survey monkey for El Alto retrospective points
@Kenny Paul (Deactivated) follow up with IT regarding Rocket Chat
@David McBride talk to Req Subcommittee about identifying requirements at the start of each release period