...
| Features/Capabilities | ONAP | Comments |
|---|---|---|
| Step #1 Containerization | ||
| Step #2 CI/CD | ||
CNF Deployment
#1 Workload Considerations - POD and Host Strategies
- Separate POD
- Shared POD
- Shared Host (with VNFs)
#2 HW Requirements
- Persistency
- Performance Optimization (Compute, Storage) - Generic or Special HW?
- Multi-Tenancy @Storage, Networking, Resource maangement
- Security - check with SECCOM
#3 Testing Considerations
- Canary Testing - Rolling upgrades
- Chaos Monkey Testing
Pre-requisite(s)
- Is there any available CNF that we could use to prototype/test with "ONAP CNCF"?
- Check this link about CNF Testbed-https://github.com/cncf/cnf-testbed
- Check with OPNFV - if any investigation in this area
...
- Feedback from OVP PH2 meeting: https://wiki.lfnetworking.org/display/LN/2020-03-09+OVP+2.0+Meeting+notes
- Review of our previous feedback concerning Compliance & Verification Program - https://wiki.lfnetworking.org/display/LN/OVP+2.0+Boot+Strap
- 2 presentations:
- CNCF Compliance (Bill Mulligan) (PDF version)
- OVP Workstream (Rabi Abdel)
- Review "Features/Capabilities - How We complement each other?"
- Is there any impact on ONAP depending on CNF Deployment (Separate POD, Shared POD and Shared Host)?
Action Items
- ONES CFP - Srinivasa Addepalli will work with Alla Goldner on the abstract - Key item - "the value that ONAP can bring"
- Kenny Paulset up doodle pole for meeting cadence and 2 or 3 per week
-
Sylvain Desbureaux - Start to work on our ONAP response to Dan (CNCF)
-
Try to identify where we are on the CNCF Trail Journey
-
Fill in the table - how we complement each other
-
Consolidation our message about ONAP Role - should be linked to our ONAP Respçonse to Dan (CNCF)
...