Reviewed the following requirements: 

1. NFV Testing Automatic Platform Requirements.pptx

2. E2E Network Slicing-Requirement SubC session V1.0.pptx

3. ONAP rel. G TIM requirements.pptx

4. Guilin ETSI-Alignmentv1.pdf

5. 5G Svc CPS POB CMPv2

6. Support xNF Software Upgrade in association to schema updates

7. Harmonization

Input from EUAG on Guilin priorities is needed

The 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

Great collaboration between the Subcommittees !

OOM Daily gating: https://gating-results.onap.eu/results/

Wiki link

•  Wiki, RTD, ONAPDocs - a lot of information about ONAP from different sources

#1 Request to the ONAP Community to review the different templates:

• Project Architectural Review Requirement and Process (draft)
• Guilin Reviews

#2 Define the scope/role of all the Documentation tools and potential synergy i.e. integrate this “ONAP directory” in readthedocs or www.onap.org, not as a separate landing site

#3 CNCF TUG (Lei Wang)

• Cloud Native Thinking for Telecommunications
• Deploying Cloud Native Network Functions in a telecom service provider ecosystem
• Cloud Native Principles gitbook
• CNF Conformance (github)
• Conformance Test Categories Documentation
• CNF Conformance (deck)
• Platform Conformance Test in alignment with CNTT RA2

#1 Get Helm Chart sample from ETSI

#2 Upload Lei Wang's presentation (done)

 Reviewed and discussed requirements for Control loop in G release :

Control Loop Sub Committee Guilin Release Planning

•  How will the plugin with its own HPA placement logic interact with the rest of ONAP which also uses placement controller (OOF)?

1. The overall requirements for E2E Network Slicing use case in Guilin release was presented. This covered:

• New slice lifecycle operations to be supported. eg: slice modification, slice termination
• Expansion in scope of E2E network slice to include RAN and Transport
• Realization of NSSMF (Core/RAN/Transport) within ONAP, ONAP should also support NF set up and NF configurations under this condition
• ONAP as NSMF connecting to external RAN NSSMF and Core NSSMF
• KPI Monitoring, Closed Loop and Intelligent Slicing
• Improvements to Frankfurt content

 2. User Operation Guidance for E2E Network Slicing Use case for Frankfurt release was presented. This covered:

(a)    ONAP components required for the use case, and the setup

(b)    How to create the associated design artifacts

(c)     UUI actions

 3. Questions asked:

• How is Core NSSMF intended to be realized within ONAP?
• How will a service be orchestrated by ONAP wherein part of the service only is within ONAP scope, whereas NSSMF within ONAP may be controlling the associated slice sub-net.
• Details of modeling aspects and enhancements.
• Are external domain controllers foreseen to be used for the domain-level actions?

Action Items

1. Elaborate the modeling requirements and take it to the Modeling Sub-committee.
2. Prepare further details, and illustrative flows showing interactions & APIs, including interaction with external domain controllers

• Introduction about OVP PH2
• Project Mapping & Relationship
• Discussion about Badging level 

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

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

•  Guilin Package Updates per component
• 20_04_23_ONAPPackageUpgradeStrategyGuilin_V2.pptx

• Project team resource constraints

#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)?

X-projects

• Maintain java11

• create python3.8 baseline 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

#1 Modify CSIT tests

#2 Provide use-case overrides

#3 Include new Gating for additional components: SO ? Requrse more resources

1. "RAN and Transport Slicing" proposal and scope for Guilin release was presented. This covered:

• Overview of RAN Slicing, scope and assumptions for Guilin release
• RAN NSSMF within ONAP, as well ONAP acting as NSSMF interacting with an external RAN NSSMF
• Overview of Transport Slicing, based on TSCi (IETF), scope for Guilin
• TSCi information modelz
• Interaction between RAN and Transport Slicing, different deployment scenarios

2. "KPI Monitoring, Intelligent Slicing and Closed loop" proposal and scope for Guilin release was presented. This covered:

• KPI monitoring by slice tenant/operator (via portal)
• Three SON scenarios for Closed Loop Automation and Intelligent Slicing namely:

1. Slice resource optimization: Guilin: simple close loop for single NSI scenario; Beyond Guilin: Cross- Slice Scenario
2. KPI adherence optimization (KPI Guarantee): (Guilin: simple close loop by introducing AI model. Beyond Guilin: cross-interaction with (1) also)
3. Service experience optimization (SLA Guarantee, QoE based) (Beyond Guilin)

3. Questions asked:

• Are the data models taken from IETF drafts? (Data model details are work-in-progress in IETF, we are closely tracking the developments)
• Will a new SO adaptor be developed for connecting to external TN NSSMF in future, or can existing adaptor be extended? (Intention is to reuse existing one, however, it is under discussion)
• Are we aligning to O-RAN? (Yes, we are having regular interactions with the O-RAN team, intention is to align with O-RAN as much as possible, starting with Guilin release itself).
• Are we considering data from all network segments? (Under discussion)

1. Elaborate the details of Guilin scope with respect to the modeling and interface aspects.
2. Prepare flows for RAN <-> Transport interaction, and details of alignment with O-RAN.
3. Elaborate details of data collection and analysis to be done.