Versions Compared

Version Old Version 4 New Version Current
Changes made by

Stephen terrill

Stephen terrill

Saved on

Key

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

STATUS: Draft

MC Multi-Cloud:

1 High Level Component Definition and Architecteral Relationships 

...

Drawio
bordertrue
viewerToolbartrue
fitWindowfalse
diagramNameMultiCloud System Context View
simpleViewerfalse
width
diagramWidth808870
revision412


The multi-cloud function provides mediation capabilities to connect to different infrastructure providers.

  • Connect Adapt ONAP to VM based infrastructure such as openstackContains container based Orchestration engine and infra structure levelLCM of VNFs for container based VNFs,Azure
  • Adapt ONAP to Container Orchestration Engine, such as K8S
  • Discovery and registration of resource information. 

MORE functional capabilities?

I was also unsure about the registration interface, whether MC was a provider and consumer there????

I didn't show redfish as its not functionally in dublin (or max a PoC)

  • Relay FCAPS data from infrastructure to DCAE


2. MultiCloud API definitions

Multi-Cloud provides the following interfaces:

Interface NameInterface Definition Interface Capabilities
MCE-2

Cloud FCAPS Resource Lifecycle Management Interface.

Provides the ability to obtain cloud FCAPS data. 

 What are the main capabilities here - is it VES?? MCE-3

Resource Lifecycle Management Interfacea course grain VNF level LCM interface in a template driven and cloud agnostic way

 Provides:

  • Infrastuture workload LCM (instantiate, query, Delete Infrastructure workloads)


MCE-3 

 N/A Place holder for SDN interconnect interface

Envisaged Future Capability

MCE-4 

Atomic Resource LCM

Provides a fine graned resource LCM interface at the VM level. This is an atomic resource level

 What are the main capabilities here?

xxxxx

MCE-4 

 SDN connect

Provides xxxxxxxxxxx

Is this in Dublin or should it be removed. 
MCE-5 

Atomic Resource LCM

Provides a course grain VNF level LCM interface 

What are the main capabilities here (instantiate, ....)? 
MCE-6 

workload LCM (specific to openstack resources)

Provides:

  • Image Management: (Create/Delete/Get Images)
  • Network Management (Create/Delete/Query connectivity)
  • Subnetwork Management ((Create/Delete/Query sub-networks)
  • Virtual Point Management (Create/Delete/Query Virtual endpoints)
  • Server Management (Create/Delete/Query Virtual Servers)
  • Heal Server
  • Flavour Management (Create/Delete/Query VM Flavors)
  • Volume Management (Create/Delete/Query Storage Volumes)
  • Tenant Management (Create/Delete/Query Infrastructure Tenants)


MCE-5 

Placement Optimization Interface

Provides xyz 

What are the main capabilities here 

real time available capacity information

Provides:

  • Query for real-time available capacity information
MCE-7 6 

Cloud VIM Registration interface 

What are the main capabilities 

Expose Interface to trigger MultiCloud plugin to discover the infrastructure resource and register them to AAI

Provides:

  • VIM Management (Update VIM info, unregister VIM info)

Note:   xxxI interface is a Component internal interface.  xxxxE interface is a component external interface

...

Interface NamePurpose Reason For Use
SDCE-6To recieve receive the cloud orchestration artifact from SDC
MCE-21

Consume the services from the cloud provider.

It is specific to each cloud type (by plugin approach)

DCAEE-X Supply Virtual Infrastructure FCAPS Events to DCAE 
AAIE-1Consume the services from AAI to access infrastructure resource inventory


3. Component Description:

...