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


Overview

This is the page to track the realization of functional requirement of "Centralized Representation and Consistent Identification of Cloud Regions In ONAP" to facilitate the orchestration over multiple cloud regions .

The motivation of this functional requirement lies in the fact: with ONAP Amsterdam and Beijing Releases, there are 3 representation of a single cloud region in ONAP, and different ONAP components use different identification to refer to the same cloud region. This complicates the on-boarding process of a cloud region, also imposes unnecessary constraints of the choice of cloud regions,e.g. If there is 2 cloud region with the same cloud region id, only one of them can be on-boarded into ONAP.

The functional requirement is to centralize the representation of the cloud regions into AAI only by depreciating all other representations. All ONAP components should use the composite key of "{cloud-owner}, {cloud-region-id}" to refer to a cloud region.


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.


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
	...
	...




Projects Impacted

projectproposed changes
SO1, Depreciate the usage of internal representation of cloud region. Use centralized representation of cloud region in AAI instead. 

        2, Depreciate the usage of "cloud-region-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region

VIDDepreciate the usage of "cloud-region-id",   use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region
SDNCDepreciate the usage of "cloud-region-id",  use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region
OOFDepreciate the usage of "vim-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region
VFCDepreciate the usage of "vim-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region
MultiCloudDepreciate the usage of "vim-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region
UUIDepreciate the usage of "vim-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region
Integration1, Robot VM should depreciate the usage of internal representation of cloud region. Use centralized representation of cloud region in AAI instead.

                    2, Robot VM should allow users to specify the composite key of "{cloud-owner}, {cloud-region-id}" to execute scripts

DCAEmake sure dcaeLocation is derived from  a cloud region + tenant, and can be translate to {cloud-owner } + {cloud-region-id} + {tenant} for retrieving cloud region information from AAI
DMaaPmake sure dcaeLocation is derived from  a cloud region + tenant, and can be translate to {cloud-owner } + {cloud-region-id} + {tenant} for retrieving cloud region information from AAI

Projects that enables the "centralized representation and consistent identification of cloud regions in ONAP"



ProjectPTLCommitted for R3M1M2MVPJIRA
1SO

Seshu Kumar Mudiganti






2VID
Ofir Sonsino

Yes





3SDNC
Dan Timoney





4Integration
Helen Chen

Yes





5OOF
Sarat Puthenpura





6VFC
Yan Yang
Yes



7UUI
Tao Shen
Yes



8MultiCloud
Former user (Deleted)
Yes



9DCAE

Lusheng Ji






10DMaaPRamprasad Koya





  • No labels