...
- a. Cloud Environment Support: All components in ONAP should be virtualized, preferably with support for both virtual machines and containers. All components should be software-based with no requirement on a specific hardware platform.
- b. Scalability: ONAP must be able to manage a small set of VNFs to highly distributed, very large network and service environment deployed across the globe.
- c. Availability & Resiliency: ONAP must support various deployment and configuration options to meet varying availability and resiliency needs of various service providers.
- d. Security: All ONAP components should keep security considerations at the fore-front of all architectural decisions. Security should be a pervasive underlying theme in all aspects of ONAP. The ONAP architecture should have a flexible security framework, allowing ONAP platform users to meet their security requirements.
Mind map diagram above maintained in ONAP Architecture Principles and Notes.xmind
See also Draft Architecture Principles