Versions Compared

Old Version 8

changes.mady.by.user Unknown User (fay)

Saved on

compared with

New Version 9

changes.mady.by.user Unknown User (fay)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

SDC is the OpenECOMP visual modeling and design tool. It creates internal metadata that describes assets used by all OpenECOMP

...

components, both at design time and run time.

SDC manages four

...

levels of assets:

  • Anchor
    Resource
    Resource
    Resource: a fundamental capability, either hardware or software. There are three kinds of Resource:
    • Infrastructure (the Cloud resources, e.g., Compute, Storage) << more specific example??>>
    • Network (network connectivity functions & elements) Example: a Virtual Network Function (VNF)
    • Application (features and capabilities of a software application)<< example?>>
  • Anchor
    Service
    Service
    Service: a well formed object with comprising one or more Resources. Service Designers create Services from Resources, and include all of the information about the Service needed to instantiate, update, delete, and
    manage the Service << example? >>
  • Anchor
    Product
    Product
    Product: includes one or more Services packaged with commercialization attributes for customer ordering and billing of the underlying Service(s), billing, and issue resolution. Products are created by Product Managers. << example? >>
  • Anchor
    Offer
    Offer
    Offer: bundling of Products with specific Marketing configurations for selling to customers << example? >>

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 Catalog is the repository for assets at the Resource, Service and Product levels. Assets are added to the Catalog using the Design Studio.
  • The Design Studio is used to create, modify and add Resource, Service and Product definitions into the Catalog.
  • The Certification Studio, available in 2017, is used to test new assets at all levels. It will be used for sandbox experimentation.
  • The Distribution Studio is used to deploy certified assets. From the Distribution studio, new service artifacts including their underlying resources and products are deployed into lab environments for testing purposes, and into production after certification is complete.

Resources are the fundamental building blocks in the ASDC Catalog. Each Resource is a combination of a single Virtual Function Component (VFC), along with all the information necessary to instantiate, update, delete, and manage it. A Resource also includes license-related information.

<<Are some Resources "built-in", i.e. they don't have a VFC?>>

<<Can VFC's directly be incorporated into a Service, without being wrapped in a Resource? If so, the description of VFC's and Resources needs to be reorganized.>>

SDC can read asset descriptions using Yang, HEAT, TOSCA, YAML, BPMN/BPEL.