STATUS: DRAFT

Remove: Please copy, change the title, and fill the contents.  Extra material can be added as attachments to the wiki page.

1. Scope

DESCRIPTION: Service Orchestrator performs orchestration for:
• Service activation requests or changes to an existing service
• Service scaling, optimization, or (migration)
• Controller instantiation
• Capacity management

...

• (Instantiation/Design Time) PNFD and VNFD have been mapped to ONAP platform data/information model. That is, the onboarded descriptor models (vendor provided) have been mapped onto ONAP platform data & information models that are useable and known to ONAP.
• SDC contains the verified service and resource descriptor (models). These resource descriptors are provided by the vendor (PNFD and VNFD).
• Associated resources (PNF, VNF, ANF) used by services have been properly onboarded.
• Services have been defined in design time, and associated templates, control loops, blueprints have been incorporated into the service CSAR package.
• SDC has composed the Service Design CSAR package ready for distribution.
• The Certification Studio has certified the Package ready for distribution
• The Deployment Studio operator has identified the Service Design CSAR package for distribution.
• Software images loaded in OpenStack installation, where instantiation will happen (since no S/W image repository). Need to be available in Target Cloud Instances.
• The User at OSS or VID has knowledge of the Service Model Identifier that they wish to create a service instance of. The Service is seen as available in the catalog.

3. Information Flow

<<Remove:  this is a plantUML macro to show the information flow.  Syntax can be found here: http://plantuml.com/sequence-diagram >>The following diagram shows the SO Service Instantiation Flow:

@startuml
participant VID
participant SO
participant OOF
participant Part1A&AI
participant NFV Orch
participant SDN-C
participant OpenStack
participant Part2Controller
autonumber 



Part1 -> Part2: example flow

note left: notes can be added 
Part2 --> Part1: Example response
note right: more notes can be added
@enduml

...