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 4 Next »

Overview

This is the ongoing effort from Casablanca Release Centralized Representation and Consistent Identification of Cloud Regions In ONAP.

With this functional requirement proposal, ONAP should have centralized representation of cloud regions to facilitate the on-boarding/decommission of a cloud region into ONAP, and ONAP projects/components should adopt the same format of ID of a cloud region when referring to the same cloud region.

During Casablanca Release, part of functional requirement has been realized by several projects, including but may not limited to:

  • SO started the realization of Centralized Representation of Cloud Regions by integrating with MultiCloud
  • MultiCloud realized the support to Consistent ID of a Cloud Region

It is expected to continue the realization of this functional requirement in Dublin Release and future releases.

Dublin Goals

Consistent ID of a Cloud Region: Enforce that all related projects to adopt the same format of ID when referring to a cloud region: Use the composite keys:  {cloud-owner}, {cloud-region-id}

Depreciate the usage of {vim-id} or sole {cloud-region-id}


More Info about how AAI represent cloud regions in Beijing Release:

    AAI REST API Documentation - Beijing

    https://gerrit.onap.org/r/gitweb?p=aai/aai-common.git;a=blob;f=aai-schema/src/main/resources/aai_swagger_html/aai_swagger_v13.html;h=4100f41e007349b4c08517690da97a5b44e8865b;hb=HEAD

cloud-region Object from AAI schema v13
cloud-region: object  
	cloud-region designates an installation of a cloud cluster or region or instantiation
	...
	...
	cloud-owner: string  
		Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname

	cloud-region-id: string  
		Identifier used by the vendor for the region. Second part of composite key
	...
	...


Business Requirement


By enforcing this functional requirement, ONAP users will be able to onboard a cloud region by either issuing a single curl command to AAI service, or a single click over ESR VIM registration GUI portal. The consistent ID of a cloud region will make it is easy to correlate the operations on a cloud region across the all ONAP services.


Scope

Dublin will target to realize this functional requirement across all related projects


Presentations

ConsistentRepresentationAndIdentificationOfCloudRegionV2.pdf


Impacts

The impact projects includes VID, SO, SDNC, OOF, UUI, VFC

Project Commitments


  • No labels