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
 Joint Session - Cloud Native OVP
 #1 Finalize OVP PH2 Roadmap by end of May 2020

Requirements subcommittee meeting continuation

Moderator: Alla Goldner

We reviewed the following remained submitted Guilin proposed requirements:

8. PM Control and A1 adapter extension

9. OOF SON requirements

10. ONAP - Multi-tenancy

 Input from EUAG on Guilin priorities is neededThe presented requirements are already endorsed by the Requirements subcommittee

We will review the remaining endorsed ones on Thursday and review new ones during our next meeting on Monday, April 27th

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 cross-project system integration
  • CI/CD

Image Added

X-

project

projects

maintain
  • Maintain java11

Security 
  • create

python 3
  • python3.8 baseline

Joint Session - Cloud Native OVPmaintain oparentRequirements subcommittee meeting continuationRepositoriesFinalize generalization of lintersCreate new repo (simu/use cases)reinsource build chain for javareinsource xtesting build chaintestsuiteadopt microservice approach
  • image

Repositories

  • Adopt the approach to create a repo for new use cases / simulators

  • Add linters to all the new repositories

  • Add new linters (tobot, bashate, rst)

  • How to get a consistent view on all the repositories, shall we tag all the repositories,..

  • update xtesting repo and put in place the build chain in ONAP (move from gitlab.com to ONAP)

  • update jave/python3.8 in ONAP (move from gitlab.com to ONAP)

Robot pod

  • Adopt micro-service approach introduced by Daniel (propto in F)

  • move the helm chart back to OOM

Use case support

  • Write an documentation 'Use case guideline"

  • Test creation of an override.yaml per use case to be able to deploy adhoc environment in windriver

Tests

  • update the tests

  • harden the simulators/emulators (no more in xfail lists)

  • clean? are all the tests still maintained?

  • archive CIST? => projects can bring back their tests in their repository but jenkins CSIT not needed anymore

  • move some of the CIST tests in Daily CI

  • introduction of python_sdk for new tests (deprecate onap-tests)

  • improve security tests (Integration and Built Tests For Releases)

  • How to measure the test coverage?

  • How to get better healthcheck tests and "force" project to update them when they provide a new version of their code

  • Support OOM on a use case for Core on F→ G migration

Labs

  • include endpoint supervizion page? (cachet?)

  • Ops guideline (Zabbix/Prometheus/...) ?

CI/CD

  • improve CI chains and CI testing gate

  • new smoke use case

    • vFW CL

    • CDS

    • ...

  • integration of Portal GUI tests

  • finalize windriver/gitlab.com pipelines

  • introduce a weekly CI chain including robustness tests


maintain java11

#1 What will be the oParent requirements for Guilin? Pawel PawlakAmy Zwarico
finalize python3 migrationMove OOM chart back to helmuse casecreate a starting guidecreate overide.yaml per use case / to dedicated automatic deploymenttestsupdate/maintenance of existing testscomponent coveragediscussions with projects to improve healthcheckupdate security tests - check versions of upstream componentsupdate security tests check java11/python3.8update security tests - check certificates validityupdate security tests - check limitsupdate existing security tests (review xfail list, cist,..)archive CIST?move CIST to E2E tests in CIdeprecate onap-tests / use python-onapsdkSupport OOM for a migrationstress testslong duration testsupdate integration web pageLabssupervision/monitoringCreate a ops guideline (with OOM?)infra gate (functest)?CI/CDIntegrate vFW Cl testIntegrate CDS testsIntegrate GUI testsCreate 5G xtesting dockers and integrate in CI?finalize windriver pipelinesintroduce a weekly pipleine (for long duration tests)