You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »


STATUS: DRAFT

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

This flow will focus on instantiation of a Service (first bullet). SO automates the end-to-end service instance provisioning activities. The service instantiation procedure is obtained from the Service Design and Creation (SDC), where service models and designs are created and distributed for consumption by SO. Service instantiation is currently done with GR flows (Generic Resource flows). Also, SO is responsible for the instantiation and release, and subsequent migration and relocation of VNFs in support of overall end-to-end service instantiation, operations and management.

WHEN EXECUTED: After Design Time. After SDC Service CSAR Distribution. (See ARCHCOM: InfoFlow - SDC Service Distribution)

PURPOSE: To instantiate a service designed in Design-time and requested by an operator at the OSS, VID or external API.

Information Model: Main information being used and a reference to the information model. Service name. In the case of VNF-based services: also the Cloud Region (where the VNF has to be deployed if HAS [homing allocation service] is not used in the workflow)

ACTORS:

  • Operations Specialist
  • Deployment and Service Designer

<<Optional: Replace with figure illustrating the scope >> 

2. Pre-Conditions

The preconditions are:

  • (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

The following diagram shows the SO Service Instantiation Flow:
 SDC Service Distribution-1 VID VID SO SO AAI AAI OOF OOF SERVICE CREATION REQUEST SO/VID API Svc Model ID, Recipe ID 1Service Creation Request INVENTORY RECORD CREATION AAI API 2Inventory Record Creation Request 3Create Inventory Record INVENTORY RECORD 4Inventory Record Creation Response HOMING REQUEST xNF Resources, Service ID 5Homing Assignment Request Homing Assignment Allocations 6Homing Assignment 7Homing Assignment Response

  1. << what >> – Flow description according to numbering. Include interface (e.g. SDCE-6) and main information  (can have a link to the information link).


4. Post Condition

The post-conditions are:

  • Service has an A&AI Service Record Entry.
  • Resources associated with the Service have been successfully given network assignments.
  • Cloud resources have been successfully assigned necessary to support the service
  • Network assignments have been assigned for the service
  • Security assignments have been successfully performed (IAK, RV, CA root cert, CA URL)
  • VNF instantiations have been successfully performed
  • Configurations from Controller to xNFs have been successfully performed.


5. References


  • No labels