...
To be determined by the people who will attend to this session
Minutes
FAQ
Q: What is the value-add of ONAP for CNF orchestration (CNFO)? What does it provide on top of K8S?
A: Lukasz Rajewski Konrad Bańka Byung-Woo Jun
- hybrid config and data operations can work on both K8s and PNFs
- Can manage helm charts
- Handling multi-cluster deployment on top of K8S
- ONAP works in the service level, not just the resource level
- Still need to address coordination across different clusters and SW upgrades
Q: What can end users do with ONAP Honolulu? What operations are supported (service design? Deployment? Day-0 configuration? Day 1/2 configuration? LCM?), and what will be supported in Istanbul?
A: Lukasz Rajewski For the "native helm" path - on-boarding, Helm enrichment with CDS, meaning modifying values in Helm templates. Day 2 operation config-assign/config-deploy - add/modify resources after the initial deployment, which may be used for upgrade. CNF status checking is supported in Honolulu, will be enhanced in Istanbul.
Q: What is the format of CNF packaging? Is it based on Helm? Does it follow ETSI-NFV specifications?
A:
Q: Where is the documentation for CNF on-boarding and deployment? How should end users report issues
A:
Q: Are there "CNF requirements" available in ONAP, similar to the "VNF Requirements"?
A:
Q: How could developers get involved? Where do you mostly need help? Are there open Jira tickets people can start working on?
A:
Q: What it is not supported today and is part of the roadmap?
A:
Q: What do we need to ask to CNF Vendors to be onboarded on the ONAP Platform?
A: