Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

  • PTL Recordings
  • Antitrust Policy Notice

We start our meetings by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

Agenda

START RECORDING

Duration

Agenda Item

Requested byNotes / Links
30 mins

Cross-project discussion


CLM Jenkins jobs are failing


  • Byung-Woo Jun opened a ticket for LFN IT to remove Jenkins jobs for deprecated projects, https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26907
  • Need to provide a to-be-deprecated repo list to LF IT (Jessica) - WIP
  • Amy Zwarico created the following draft of repos to be removed from Jenkins (will be discussed this at ONAP SECCOM tomorrow):
    • Draft of repos to be removed from Jenkins:

      CLI

      • cli

      DMaaP Message Router

      • dmaap-messagerouter-dmaapclient
      • dmaap-messagerouter-messageservice

      ExtAPI

      • externalapi-nbi

      Holmes

      • holmes-common
      • holmes-engine-management
      • holmes-rule-management

      Modeling

      • modeling-etsicatalog
      • modeling-yang-kit

      MSB

      • msb-apigateway
      • msb-discovery
      • msb-java-sdk
      • msb-swagger-sdk

      NBI

      •  

      OOF

      • optf-has
      • optf-osdf

      VFC

      • vfc-gvnfm-vnflcm
      • vfc-gvnfm-vnfmgr
      • vfc-gvnfm-vnfres
      • vfc-nfvo-driver-svnfm-huawei
      • vfc-nfvo-driver-vnfm-gvnfm
      • vfc-nfvo-lcm

      VNFSDK

      • vnfsdk-dovetail-integration
      • vnfsdk-functest
      • vnfsdk-refrepo
      • vnfsdk-validation


New Delhi Release Status 


Oslo

For Oslo plan, 
  • Documentation on how to aggregate core ONAP functions for greater solutions, including deployment and trouble-shooting
  • a question around use of Github docs for project / code (e.g., readme.md)
    • collect PTL feedback

Project Maturity

Byung-Woo Jun 

ONAP component mature state, Mature State Projects

Now, we are handling ONAP component individually under ONAP Streamlining, exposing the components to users. CPS is the first case that TSC approved the mature state after ONAP Streamlining. Should we keep the projects under the list as "mature", or should we certify them again? Several components are deprecated.

According to TSC 2.0 doc, Mature state is "Project is fully functioning and stable, has achieved successful releases." Several projects in the list are deprecated/archived. To approach a broad audience, should we consider the "Core" state for some selected projects??

Gold badging is a separate process from the project maturity in LFN?

  • CPS got the gold badging
  • What other components do we want to get the gold badging? Policy is working on it.

LF IT Support


  • Ticket to be opened by Thomas Kulik - those repositories have no owners which blocks Documentation projects 

Pending tikect opened by Marek:

https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-25573

  • Kevin Sandi - a workaround solution will be tried;
  • Marek / Matthew - automatic building solution is needed; escalate this?
  • Kevin/Matt/Kevin - create a ticket and try a solution (maybe Github action helps? PoC??)
  • Some action plans and updates next week

Thomas Kulik - issues with Portal-NG and other documentation - 

IT-26899 Project is not created in RTD

Testing Environment


Testing Improvement



CSIT Review



ToolChain Improvement



Documentation

Other Improvement suggestion

Plan to migrate ONAP components to use RFC8040.

  • SDNC and SO decided to move it to Oslo.

----

As backup Dan is working on Biermann but not progressed. ODL is not supporting it. Restconf stack is based on RFC draft. 

  • Preferred approach is to move to RFC8040 (Alternative 1).
    • Originally proposed back in the Kohn release 
    • Plan for the New Delhi release
    • Andreas Geißler DT has someone working on the SO piece to try and port to RFC8040
    • ONAP components will be moved to RFC8040 in New Delhi
  • Alternative 2: keep maintaining Biermann interface.
    • may support either London or Montreal as a long term release
  • Alternative 3: rollback to version before Argon.
  • Alternative 4 (the most drastic): stay where we are for now and begin to work with moving off from ODL.  

As we have no solution, we can not move to ODL Potasium.


Subcommittee Updates for PTLs

  1. Recommended packages upgrades are available on the restricted Wiki. Jiras are created per project. 

    Need to check NG Portal status CLM jobs. Any update?

 - no solution for now:


Ticket opened by Fiete: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26527 (ticket is closed)

  • ongoing; Jessica and Fiete are discussing this.

We are missing NG Portal UI CLM job.

List of the ONAP components to be disabled prepared by Andreas: 

OOM New Delhi Release

On April 18th, TSC approved the list.


Sharing Best Practices




Others



IF TIME ALLOWS ....
15 minsRelease status






5 minsUpcoming Events


    • TBD
10 minsRemaining Action Items



Zoom Recordings


Zoom Chat Log



  • No labels