Versions Compared

Key

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

...

TrackKey PointsChallengesNext Steps / AIs
Guilin Planning


Guilin Planning  - Control loop sub committee - Guilin requirements


Moderator:

Pamela Dragosh

 Reviewed and discussed requirements for Control loop in G release :

Control Loop Sub Committee Guilin Release Planning



Security 


ETSI/CNF - ETSI NFV modeling and API 

Moderator: Hui Deng

#1 Latest ETSI NFV modeling and API progress Thinh Nguyenphu

#2 ETSI NFV model impact on R7 Xu Yang



Speaker: Bin Yang

  •  cFW - POC in progress based on ONAP MultiCloud project - Source code available here
  • What API is used in VID? VNF API or GR API? Does it make any difference? What about that override.yaml - is there an example available? VNF/VF API to instantiate the deploymen
  • No development yet related to fault and performance monitoring of the CNFs. Targeted for Guilin.
  •  Dummy heat template is temporary for now as we did not want to make any major changes to SDC and SO.  In R7, we intend to make Helm as first class citizen.  Until R6, Helm charts are hidden as artifacts under Dummy HEAT template.


Speaker: Fernando OliveiraByung-Woo Jun

  •  Discussions have started with SDC for ETSI alignment for the onboarding
  •  SVNFM/NFVO are coming from 3rd party vendors




ETSI/CNF - CNF Task Force -Review Multi Site Orchestration with ONAP4K8s (ONAP for K8s)

Moderators: Catherine LefevreSeshu Kumar Mudiganti

 Speaker: Srinivasa Addepalli

  • How to handle different VNF types i.e. Openstack based, Helm Chart based, Heat based etc? It should work based on the current ONAP4K8S
  •  How will the plugin with its own HPA placement logic interact with the rest of ONAP which also uses placement controller (OOF)?


#1 Upload Sandeep Sharma presentation

 Speaker: Rajendra Mishra


#1 Upload Sandeep Sharma presentation

 Joint Session


 Others



Day 3 - April 23, 2020

TrackKey PointsChallengesNext Steps / AIs

Security - Third party dependency upgrade strategy

Moderator: Krzysztof Opasiak



Guilin Planning - OOM Proposal

Moderator: Eric Debeau

Speaker: Sylvain Desbureaux

Review of OOM Guilin Release proposal 

Some proposals with help of projects:

  • All logs to STDOUT
  • Certificates
  • Crash well when Issue (and not "wait for I don't know" or exit with status 0)
  • AAF integration must be settable to off
  • MSB integration must be settable to off

Tentative / PoC

  • Make Ingress default deployment
  • Make Deployment with storage class default deployment
  • check storage asked for PVC is consistent with actual deployments
  • Service Mesh PoC continuation
  • All pods have requests/limits
  • request/limits bad values hunting: use only 10 vCPU while 92 vCPU are required, RAM may be divided by 3


#1 Assess the impact of upgrading to the version suggested by SECCOM? Does it require any architecture change or is it transparent for the component (only Helm Chart modifs)?


Guilin Planning - Integration priorities

Moderator: Eric Debeau

Speaker: Morgan Richomme

ONAP crossSecurity 
X-project
system integration
  • CI/CD
  • Image Removed

    #1 What will be the oParent requirements for Guilin? Pawel PawlakAmy Zwarico

    maintain java11


    Security 
    create python 3.8 baseline
    Joint Session - Cloud Native OVP

    #1 Finalize OVP PH2 Roadmap by end of May 2020

    Requirements subcommittee meeting continuation

    We reviewed the following remained submitted Guilin proposed requirements:

    8. PM Control and A1 adapter extension

    9. OOF SON requirements

    10. ONAP - Multi-tenancy


    maintain oparent
    Requirements subcommittee meeting continuationRepositoriesFinalize generalization of linters


    Create new repo (simu/use cases)


    reinsource build chain for java


    reinsource xtesting build chain

    testsuiteadopt microservice approach


    finalize python3 migration


    Move OOM chart back to helm

    use casecreate a starting guide


    create overide.yaml per use case / to dedicated automatic deployment

    testsupdate/maintenance of existing tests


    component coverage


    discussions with projects to improve healthcheck


    update security tests - check versions of upstream components


    update security tests check java11/python3.8


    update security tests - check certificates validity


    update security tests - check limits


    update existing security tests (review xfail list, cist,..)


    archive CIST?


    move CIST to E2E tests in CI


    deprecate onap-tests / use python-onapsdk


    Support OOM for a migration


    stress tests


    long duration tests


    update integration web page

    Labssupervision/monitoring


    Create a ops guideline (with OOM?)


    infra gate (functest)?

    CI/CDIntegrate vFW Cl test


    Integrate CDS tests


    Integrate GUI tests


    Create 5G xtesting dockers and integrate in CI?


    finalize windriver pipelines


    introduce a weekly pipleine (for long duration tests)
    Same as for the session on Day 1