...
The definitions of assets include Information Artifacts and Deployment Artifacts. Information Artifacts can be provided are provided by the vendor when of an asset such as a VNF is on-boarded to SDC. The artifacts describe the ; they describe characteristics of the asset and the companion supporting documents as to how it works, and how to manage it once it is deployed. Once VNFs . Some of these artifacts are supporting documents intended for human readers only, whereas others contain data that will be imported into the OpenECOMP environment when the asset is onboarded.
Once assets are on-boarded, the information provided by the vendor is translated into SDC internal resource models. The service provider will use SDC to further enrich the resource model to meet the provider’s environment, and additionally compose resources into service models and product models. The model includes not only the description of the asset but also references to OpenECOMP functions needed for lifecycle management of the asset. The tested models will then be distributed to the OpenECOMP execution environment as Deployment Artifacts.
The Deployment Artifacts include the asset definition (a Resource or Service or Product model) with instructions to OpenECOMP for creation and management of an instance of the asset in the network. SDC is evolving the support of various Deployment Artifacts – including Currently, SDC imports and retains information from Heat Templates for cloud infrastructure creation, YANG XML files for state data manipulated by the Network Configuration Protocol, TOSCA files for specifying cloud infrastructure, vendor and certain vendor provided scripts, or . In the future, SDC may import BPMN/BPEL files for specifying business processes and the their interconnections in a service-oriented architecture.
...