Table of Contents | ||||
---|---|---|---|---|
|
What is SDC?
Expand |
---|
SDC is the ONAP visual modeling and design tool. It creates internal metadata that describes assets used by all ONAP components, both at design time and run time. The SDC manages the content of a catalog, and logical assemblies of selected catalog items --as needed-- to completely define how and when VNFs are realized in a target environment. A complete virtual assembly of specific catalog items, together with selected workflows and instance configuration data, completely defines how the deployment, activation, and life-cycle management of VNFs are accomplished. Selected sub-assemblies may also be represented in the catalog and may be combined with other catalog items, including other sub-assemblies. In the context of a catalog containing TOSCA nodes that are assembled to form a TOSCA blueprint within the SDC, it is expected that such nodes convey (as properties) all of the workflows and/or workflow fragments) needed to realize the node in some specific target environment. In this way, any assembly of such nodes (defined in a blueprint) can be used to define the end-to-end workflow needed to realize the VNF associated with the TOSCA blueprint. SDC manages four levels of assets:
|
The key output of SDC is a set of models containing descriptions of asset capabilities and instructions to manage them. These models are stored in the SDC Master Reference Catalog for the entire enterprise to use. There are four major components of SDC: |
|
|
|
|
|
|
|
|
|
|
|
The definitions of assets include Information Artifacts and Deployment Artifacts. Information Artifacts are provided by the vendor of an asset such as a VNF; they describe characteristics of the asset. Some of these artifacts are supporting documents intended for human readers only, whereas others contain data that will be imported into the ONAP 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. The model includes not only the description of the asset but also references to ONAP functions needed for lifecycle management of the asset. The tested models will then be distributed to the ONAP execution environment as Deployment Artifacts. The Deployment Artifacts include the asset definition (a Resource or Service |
) with instructions to ONAP for creation and management of an instance of the asset in the network. 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, and certain vendor provided scripts. In the future, SDC may import BPMN/BPEL files for specifying business processes and their interconnections in a service-oriented architecture. |
SDC intro
Expand | ||||
---|---|---|---|---|
|
SDC in ONAP
SDC is a starting place for most ONAP use cases. Please see: Using ONAP
SubprojectsDocumentation
children SDC Documentation
page | Service Design and Creation (SDC) Portal |
---|
Architecture
API guide
AID
Developer Guide
Developer Onbording sessions
Releases
Contact us
- temp chat channel until a preferment solution is available.
http://52.168.69.155:3000/channel/sdc
http://onap-integration.eastus.cloudapp.azure.com:3000/channel/sdc
- onap discuss mailing list.
- wiki questions.
Documentation Site
Presentations
User interface
Tutorials
Child pages (Children Display) | ||
---|---|---|
|
Repositories
JIRA
Jenkins
Weekly Meeting
[sdc] Team ONAP4, Mon UTC 15:00 / China 23:00 / Eastern 10:00 / Pacific 07:00
Weekly Meeting Notes
Child pages (Children Display) | ||
---|---|---|
|
Presentations
Contact us
JIRA
Jenkins
Meeting
Weekly meetings
[sdc] Team ONAP3, Mon UTC 11:00 / China 19:00 / Eastern 06:00 / Pacific 03:00
Notes and agenda: Weekly meetings - agenda and minutes
SDC feature Deiscusions
SDC Release planing
Child pages (Children Display) | ||
---|---|---|
|
User interface
SDC and sub-projects roles and responsibilities
Expand | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||
|
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
Tutorials
Child pages (Children Display) | ||
---|---|---|
|