...

Note: The above captures the currently committed VNF providers, we are open to adding more VNF providers.

...

Note: The above captures the currently committed VIM providers, we are open to adding more VIM providers.

...

Note: The above captures the currently committed HW providers, we are open to adding more HW providers.

...

• Design
  
  
  
• 1.0: ONAP user uses SDC to import and design VoLTE E2E model/templates via Portal. The E2E models should include, vIMS + vEPC network services, SDN-WAN connection services, relevant auto-healing policy and alarm correlation rules, etc. All of these should be tied together as a E2E VoLTE model
  SDC/CLAMP should distribute all above models to related components in run time when use need to instantiate the E2E VoLTE service.
• 1.1 Distribute E2E model to  to SO.
• 1.2 Distribute vIMS+vEPC NS to VF-C, 
• 1.3 Distribute SDN-WAN connection service to SDN-C(need to update flow)
• 1.3 4 Distribute auto-healing policy to Policy engine
• 1.4 5 Distribute alarm correlation rules to Holmes engine.
• 1.5 6 Design and Distribute DCAE configuration from CLAMP

...

After the fault detected and its root correlated, ONAP should do the auto-healing action as specified by a given policy to make the system back to normal.

More details about the VoLTE use case control loop.

Configuration flows (Stretch goal)

...

• OOM
  Support to deploy and operate new added components into ONAP, such as VF-C/Holmes
  
  
• MSB
  Support to route requests to components correctly.
  
  
• Use Case UISupport UI
  Support VoLTE case lifecycle management actions, monitor service instances status, display FCAPS metrics data in real time.
  
  
• ESR
  Support to register 3rd Party VIMs, VNFMs, EMSs and SDN controllers to ONAP

Priorities:

1 means the highest priority.

...