ay 1 - April 21, 2020
| Track | Key Points | Challenges | Next Steps / AIs |
|---|---|---|---|
Guilin Planning - Requirements Moderator: Alla.Goldner | 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 6. Support xNF Software Upgrade in association to schema updates | 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 |
Guilin Planning - Architecture Moderator: Chaker Al-Hakim | Great collaboration between the Subcommittees ! OOM Daily gating: https://gating-results.onap.eu/results/ | #1 Request to the ONAP Community to review the different templates: #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 | |
ETSI/CNF - Container Modeling Moderators: Andy Mayer, Hui Deng | #1 ETSI NFV Container Architecture and ModelingUlrich Kleber VNF can use VM-s or containers. CNF is a _Cloud Native_ NF what is a VNF built with the Cloud Native principles in mind ETSI-based CNF support is compliant to IFA029&IFA040 (publication expected in May) Additional information shared by Thinh Nguyenphu : ONAP-ETSI Alignment Workshop (IFA040) #2 CNTT RA2 Tom Kivlin , Gergely Csatari Possibility to run NF on top of what it is defined in RA2 / K8S No conflict/overlap between what ETSI CNF defined and CNTT RA2 (K8S) CNTT Roadmap
#3 CNCF TUG (Lei Wang)
| #1 ETSI approach seems to generalize the capabilities of the container infrastructure layer and may limit the use of the full capabilities of Kubernetes - no recommendation in IFA029. #2 How to refer CNI in the descriptor? Normally no need to have CNI reference in the pod manifest - K8S should evolve to support it but there is currently no solution. #3 Different approaches for CNF Modeling - no conclusion yet from CNCF about the best approach
#4 How can we stay align between ETSI, CNTT, ONAP, CNCF, OVP PH2, etc? | #1 Get Helm Chart sample from ETSI #2 Upload Lei Wang's presentation (done) |
...
| Track | Key Points | Challenges | Next Steps / AIs |
|---|---|---|---|
| Guilin Planning | |||
Reviewed and discussed requirements for Control loop in G release : | |||
| 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 | ||
ETSI/CNF - CNF Orchestration over StarlingX 3.0 Demo Moderator: cl664y@att.com | Speaker: Bin Yang
| ||
ETSI/CNF - ETSI alignment on the SOL004 and SOL007 standard Moderator: Seshu Kumar Mudiganti | Speaker: Fernando Oliveira , Byung-Woo Jun
| ||
ETSI/CNF - CNF Task Force -Review Multi Site Orchestration with ONAP4K8s (ONAP for K8s) Moderators: cl664y@att.com , Seshu Kumar Mudiganti | Speaker: Srinivasa Addepalli
|
| |
ETSI/CNF - CNF Deployment on OpenShift Moderator: cl664y@att.com | #1 Upload Sandeep Sharma presentation | ||
Others - Learnings from OVP VNF Validation Moderator: cl664y@att.com | Speaker: Rajendra Mishra
| #1 Upload Sandeep Sharma presentation | |
| Joint Session | |||
| Others |
Day 3 - April 23, 2020
| Track | Key Points | Challenges | Next Steps / AIs |
|---|---|---|---|
Security - Third party dependency upgrade strategy Moderator: Krzysztof Opasiak | Speaker: Pawel Pawlak, Amy Zwarico | ||
Guilin Planning - OOM Proposal Moderator: Eric Debeau | Speaker: Sylvain Desbureaux Review of OOM Guilin Release proposal
Some proposals with help of projects:
Tentative / PoC
| #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| X-project |
#1 What will be the oParent requirements for Guilin? Pawel Pawlak , Amy Zwarico
maintain java11 | |||
| Security | create python 3.8 baseline | ||
| Joint Session - Cloud Native OVP |
- Introduction about OVP PH2
- Project Mapping & Relationship
- Discussion about Badging level
#1 Finalize OVP PH2 Roadmap by end of May 2020
We reviewed the following remained submitted Guilin proposed requirements:
| maintain oparent | |||
| Requirements subcommittee meeting continuation | Repositories | Finalize generalization of linters | |
| Create new repo (simu/use cases) | |||
| reinsource build chain for java | |||
| reinsource xtesting build chain | |||
| testsuite | adopt microservice approach | ||
| finalize python3 migration | |||
| Move OOM chart back to helm | |||
| use case | create a starting guide | ||
| create overide.yaml per use case / to dedicated automatic deployment | |||
| tests | update/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 | |||
| Labs | supervision/monitoring | ||
| Create a ops guideline (with OOM?) | |||
| infra gate (functest)? | |||
| CI/CD | Integrate 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) |