Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 7 Next »

Till Casablanca release, SO acts as both Orchestrator and OSS/BSS System in some usecases. In the role of OSS/BSS System, SO sends the request to VF-C for Network Services LCM. In the Dublin release, VF-C introduces SOL005 

SO has to align the VF-C adapter to call those APIs using the new endpoints and also support the existing APIs as is.

What SOL005 APIs are supported in VF-C?

As of Dublin release, VFC is planning to implement the following APIs:

  • NS LCM 
    • Create NS
    • Delete NS
    • Get NS
    • Instantiate NS
    • terminate NS
  • NSD Package management
    • Subscribe
    • Query Subscribe Information
    • Terminate Subscription
    • Notify
  • VNFD Package Management
    • Fetch VNF Package artifacts
    • Subscribe
    • Query Subscription information
    • Terminate Subscription

What SOL005 APIs that will be consumed by SO?

Till Casablanca release, SO supports NS LCM API and scaling of NS. We are not going to add any new APIs in this release. But we will modify existing NS LCM APIs alone to make compatible with SOL 005.

API ActionMethodURIDescription
Create NSPOST/ns_instancesTo create a Network Service
Instantiate NSPOST/ns_instances/{nsInstanceId}/instantiateTo instantiate Network service
Get NS DetailsGET/ns_instances/{nsInstanceId}To query the status of the Network Service
Terminate NSPOST/ns_instances/{nsInstanceId}/terminateTo Delete Network Service Instance


Architecture for the NS Orchestration using SOL 005:


Flow of the NS Orchestration Diagram:



What usecase to be tested with SOL 005 Flow:

As of the Dublin release, SOL 005 flow will be tested against vFW usecase with SOL004 CSAR.

What other components will be affected SOL 005 Flow:

  • UUI: Two new dropdowns will be introduced to select SOL 005  and orchestrator details.
  • AAI: New entity in ESR will be introduced to accept NFVO registrations.
  • SDC: We tested with vCPE CSARs to check artifacts distributed to SO and there is no change needed in vCPE usecase. Other usecases has to be tested.
  • SDNC: ????

Known Scope:

  • The scope of work is limited to NS LCM APIs, so Service Orchestrator (SO) won’t deal with CSAR package onboarding to VFC.
  • As all the attributes that SOL005 instantiate request expects are not provided from Usecase UI, so scope of this work is limited to such requests.






  • No labels