Versions Compared

Old Version 7

changes.mady.by.user Davide Cherubini

Saved on

compared with

New Version Current

changes.mady.by.user Davide Cherubini

Saved on

Key

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

The CCVPN E-LAN Service Use Case will impact each of the Projects listed on this page. Depending on the chosen implementation Option (listed here), impact will be different. Listed impacts refer to Option 2 for Service Creation and Option A for Service Modification

AAI

  1. Support Composite Services  Service Instances (also multi-operator)

DCAE

  •  Performance management - Stretched GOAL - POSTPONED TO R5

OOF 

(Not Pursing in R3)
  • OOF will process Homing and capacity placement request from MSO.

OOF will support additional Policies for Scale Out to check the following:

  • If there is enough capacity in the region or close to the region
  • For the VNF Instance, is the license sufficient to satisfy the configuration requested

Modeling (Not Required)

Need to add Controller type to the VNF Model in SDC 

  • TBC

SDN-C 

  • TBC

Modeling 

  • Need to support Composite Services

SDC

  1. Support Composite Services creation
  2. Must be able to model LCM operations/Interfaces and expose the modification capabilities through the Service Catalog

SDNC

  1. For L1-3 VNFs, process a HealthCheck action from SO via DMaaP
  2. Import Scaling changes from APPC so that all configuration changes may be done on VNFs controlled by SDNC
  3. Retrieve the IP addresses from A&AI for the ConfigScaleOut action  
    1. Obtain Configuration information for new instance from A&AI

SO

  • Create API for VID and Policy to call that will allow SO to scale a VNFC
  • Create work flow to get all needed information to Scale a VNFC
    • Call API for Homing and capacity checks (Moved to Dublin

    External API

    1. Implement TMF 641 for external BSS Portal (parameters passed as one composite/single orerItem)
    2. implement East-West cross-operator  External API-External API ("patch service" for service modification)

    SO

    1. Implement ability to "decompose" the End-to-End service (in collaboration with SDC). The same applies for the Service Change. 
    2. Implement Service Modification API and associated workflows to interact with other projects (SDN-C, A&AI & ExtAPI)