...

Note: All detailed flows (with diagrams) are for R1. Flows planned for subsequent releases are tagged as "aspiration" and are only mentioned, details will be added later.

Onboarding of vCPE VNFs

...

Generic Run Time Flows

For "simple" Services which include only simple networks and VNFs (e.g., with no multi-data instances that map to different VF Modules), there exists an SO “Generic Service” flow (“top level flow”) that spawns Resource Level VNF and/or Network sub-flows that are themselves "Generic".  By "Generic" we mean that the SO flows were built with no particular Service, VNF, or Network in mind, but are rather implemented in such a way to support many different Service, VNF, and Network types.  The SDC model drives which particular sub-flows to spawn and of which type, as well as driving the specific behavior of the Service level and Resource level flows. 

For such "simple" Services, the SDNC functionality is also “generic” such that only modeling and configuration is needed to drive SDNC behavior for a specific VNF type.  For example, the SDNC generic VNF flow can automatically assign IP Addresses from a pool that has been pre-loaded into SDNC.  E.g., pre-load 25 vG instances with their assignments pre-populated.  SDNC keeps track of which instances have/have not been assigned. 

It is expected that these SO and SDNC assets will be leveraged for most of the Services and Resources needed for the vCPE use case, though some custom flows will also be needed as per the following table:

The run time functionality of these generic flows is as follows:

Generic Service Instantiation Flow

Image Added

Generic Resource Level flow for Networks

Image Added

Generic Resource Level Flow for VNFs

Image Added

...

• Customer ordering
  
  
  • New vG ordering, instantiation and activation
    Image Modified
    
  • Aspiration goal: Cut service
    
  • Aspiration goal: Per service activation ( connectivity to Internet, IMS VoIP, IPTV)
  • Aspiration goal: Wholesale access (future)
    
    
  • Self-service
  • Aspiration goal: Tiered bandwidth
  • Aspiration goal: Bandwidth on Demand
  • Aspiration goal: Change internet access bandwidth
    
    
  • Software management
  • Aspiration goal: Upgrade service
  • Aspiration goal: Upgrade a specific element (VNF) of the service
  • Aspiration goal: Delete service
    
    
  • Scaling
  • Aspiration goal: Storage (future)
    
    
• Auto-healing
  • Automatic reboot/restart
  • Image Modified
    
    
  • Aspiration goal: Rebuild
  • Aspiration goal: Migrate/evacuate to different CO Re-architected as DC (future)
  • Aspiration goal: Reconnect over an alternative path?

Project Impact:

• • • Modeling
      To be discussed
      
      
    • SDC
      Add logic to use the new modeling when designing the service, and then distribute the resulting artifacts.
      
      
    • CLAMP
      Framework for policy design and distribution 
      
      
    • SO
      Add logic to understand the new artifacts; orchestrate/manage changes according to it.
      
      
    • SDNC
      Add logic to create the chaining, configuration, healing, etc.
      
      
    • DCAE
      Support statistics collection and receipt of events as per the new model; monitor connectivity and livelihood of the BRG_Emulator.
      
      
    • APPC, VF-C, and DCAE
      Support more complex control loops.
      
      
    • A&AI
      Support the new data model.
      
      
    • Policy
      Support new policy related to the service + the connectivity to the BRG_Emulator.
      
      
    • VNF SDK
      Support the ONAP VNF guidelines (blend from ECOMP and OPEN-O)
      
      
    • Integration
      Integrate, produce test cases, run the tests, verify the use case with the selected VNFs

...