...
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: Catherine Lefevre | 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: Catherine Lefevre , Seshu Kumar Mudiganti | Speaker: Srinivasa Addepalli
|
| |
ETSI/CNF - CNF Deployment on OpenShift Moderator: Catherine Lefevre | #1 Upload Sandeep Sharma presentation | ||
Others - Learnings from OVP VNF Validation Moderator: Catherine Lefevre | 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 crossX-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) |