...
Architectural principles provide guidelines when making architecture decisions. The principles are not requirements (functional or non-functional), nor should they specify the design of the system.
1. ONAP Scope:
- Lifecycle Support: ONAP must support a complete life cycle management of software-defined network functions / services: from VNF On-Boarding, Service Definition, VNF/Service Instantiation, Monitoring, Upgrade, to retirement
- Standardization: ONAP must support a common approach to manage various network functions from different vendors
- Standard templates for instantiations
- Standard language for configuration
- Standard telemetry for monitoring and management
- Vendor & Service Agnostic: ONAP Platform must be VNF, Resources, Products, and Service agnostic. Each service provider or integrator that uses ONAP can manage their specific environment (Resources, VNFs, Products, and services) by creating necessary meta-data / artifacts using Design Studio to support their needs / environment.
- Common Information Model approach: ONAP should define a standardized common information model for all vendors to follow. This will allow ONAP users to quickly onboard and support new VNFs.
- Pluggable Modules: The ONAP architecture should develop and promote VNF standards to allow delivery of Lego block-like pluggable modules, with standard interfaces for all aspects of lifecycle management (e.g. instantiation, configuration, telemetry collection, etc.).
- Integrated & Centralized Design Studio: All artifacts required for ONAP components should be able to be designed from a central ONAP design studio.
...
- 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.
