Background
- For the ONAP Beijing release, the APPC project delivered the CDT design tool to support the APPC model driven design approach.
- For the next ONAP releases Casablanca, we are proposing to develop a common design tool to support both SDNC and Generic L4-7 NFs (APPC, VFC) Controller integrated with SDC.
- This common design tool, also called “Controller Design Studio”, will be built with associated data dictionary and an Ingredient Resource Resolution Microservice
- The common design tool models shall be backwards compatible to the current use cases supported in Amsterdam and Beijing release by Generic L4-7 NF (APP-C specific).
...
The Controller Design Studio is composed of two major components: the GUI (or frontend) and the Run Time (or backend). The GUI handles direct user input and allows for displaying both design time and run time activities. For design time, it allows for the creation of service models, from selecting the DGs to be included, to incorporating the artifact templates, to adding necessary components. For run time, it allows the user to direct the system to resolve the unresolved elements of the service model and download the resulting configuration into a VNF. At a more basic level, it allows for creation of data dictionaries, capabilities catalogs, and service models, the basic elements that are used to generate a configuration.The essential function of the Controller Design Studio is to create and populate a Service Model, create a configuration file from this Service Model, and download this configuration file (configlet) to a VNF/PNF.
Proposed Work Items
Design Time
| Feature | Description | JIRA | Owner AT&T SDN-C | |
|---|---|---|---|---|
Controller Design Studio GUI | AT&T Seed Code Contribution for Service Model Creation and Management including artifact model, component model, connectivity model, and dg modeling. | AT&T Brinda M/Kapil S | ||
AT&T Seed Code Contribution for Catalog Creation and Management | AT&T Brinda M/Kapil S | |||
AT&T Seed Code Contribution for Data Dictionary Creation and Management | AT&T Brinda M/Kapil S | |||
Enhance existing screen to support data dictionary panel layout and data dictionary reference model creation for existing APP-C Models. | AT&T APP-C | |||
Controller Design Time Studio app extension with SDC integration | SDC AT&T APP-C/SDN-C Tech M IBM Bell Canada |
Run Time
| Feature | Description | JIRA | Owner AT&T SDN-C | |
|---|---|---|---|---|
| Instantiation | Generic Resource API integration with netbox ip management capability for assign | Bell Canada | ||
| Generic Resource API integration with netbox ip management capability for unassign | Bell Canada | |||
| netbox ip management REST API support in ONAP | Bell Canada | |||
| AT&T Seed code contribution for policy driven naming mS in ONAP | AT&T Ajay Sing/Biju Thomas | |||
| AT&T Seed code contribution for Resource Resolution using data dictionary mS in ONAP | AT&T Ajay Sing/Biju Thomas | |||
| AT&T Seed code contribution for template meshing mS in ONAP | AT&T Brinda M/Kapil S | |||
| Controller Design Time Studio app extension with SDC integration | SDC AT&T APP-C/SDN-C Tech M IBM Bell Canada | |||
Post Instantiation | APP-C Integration with resource resolution REST API based on data dictionary. | AT&T SDN-C | ||
AT&T Seed Code Contribution for Configuration Generation, Preview and Deployment. | AT&T SDN-C | |||