...
- Resources, Vendors, & Service Agnostic: ONAP Platform must be PNF / VNF, Resources, and Service agnostic. Each service provider or integrator that uses ONAP can manage their specific environment (Resources, PNFs / VNFs, 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 PNF / VNFs and services.
- Pluggable Modules: The ONAP architecture should develop and promote PNF / 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.) from various vendors.
- Integrated & Centralized Design Studio: All meta-data / artifacts required by various ONAP components should be designed from a central ONAP design studio, catalogued and shared from central repository.
...