Overview

The Controller Design Studio (CDS) will be contributed to ONAP as part of Casablanca release. CDS extends the current capabilities of CDT (tool that allows to define a VNF template used by the controller later on for LCM operations), allowing a service designer to create both a VNF template (feature introduced in Beijing) and a configuration template that will be used to configure VF modules once they are created (this will be introduced in Casablanca). SDNC will support collection of resource instantiation artifacts modeled at design time using CDS. SDNC will leverage the NETBOX capability to automate IP assignment and a Naming microservice for policy-driven resource naming generation. Default name values can also be used, if preferred. When the automated capabilities are used, SDNC automatically creates and assigns a name to a resource (e.g. a VM, network, etc.), based on predefined resolution strategies indicated in the Data Dictionary (DD). DD allows service designers and users to define how the parameters defined in the instantiation model can be resolved (automated capability, static value, or default value) and where the to retrieve resolution information from (MSDAL or database). Thanks to model-driven automation, the service designer or users can choose not to preload SDNC with VF module specific configuration before instantiating a VF module, but to rely on a fully automated approach.

Marco Platania - how does this extend to Control Loops???