You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

When an ONAP instance is deployed over a VIM/Cloud instance, the VIM/Cloud instance will be registered by default. However, it is somehow tricky to add additional VIM/Cloud instance to ONAP instance with Amsterdam Release. This page is trying to share the practice to do so and the goal is to allow users deploy VNF/VF-Modules to the additional VIM/Cloud instance.

There are 3 places to store information of a VIM/Cloud instance: A&AI, SO, Robot. And it is very important to associate the VIM/Cloud instance with subscriber's service subscription, otherwise you will not able to deploy the subscriber's VNF/VF-Modules to that VIM/Cloud instance 


Register VIM/Cloud instance into A&AI

Prerequisite: Complex object and Subscribe object are created in the AAI

     Complex object in A&AI represent the physical location of a VIM/Cloud instance, that is the one-to-many association between them, so creating the complex object is out of scope of this practice. But I can share the POST man script to do create complex named clli2:


Create a Complex Object 
PUT /aai/v11/cloud-infrastructure/complexes/complex/clli2 HTTP/1.1
Host: <AAI_VM1_IP>:8443
X-TransactionId: 9999
X-FromAppId: jimmy-postman
Real-Time: true
Authorization: Basic QUFJOkFBSQ==
Content-Type: application/json
Accept: application/json
Cache-Control: no-cache
Postman-Token: 734b5a2e-2a89-1cd3-596d-d69904bcda0a
 
        {
            "physical-location-id": "clli2",
            "data-center-code": "example-data-center-code-val-6667",
            "complex-name": "clli2",
            "identity-url": "example-identity-url-val-28399",
            "physical-location-type": "example-physical-location-type-val-28399",
            "street1": "example-street1-val-28399",
            "street2": "example-street2-val-28399",
            "city": "example-city-val-28399",
            "state": "example-state-val-28399",
            "postal-code": "example-postal-code-val-28399",
            "country": "example-country-val-28399",
            "region": "example-region-val-28399",
            "latitude": "example-latitude-val-28399",
            "longitude": "example-longitude-val-28399",
            "elevation": "example-elevation-val-28399",
            "lata": "example-lata-val-28399"
                
        }



The VIM/Cloud instance are represented as a cloud region object in A&AI. So registering a VIM/Cloud instance into A&AI basically refers to following actions:


action 1: create a cloud region object



action 2: create child object of cloud region object to represent the resources of that VIM/Cloud instance


action 3: associate this cloud region object with a complex object


action 4: associate this cloud region object with a subscriber's service subscription




Register VIM/Cloud instance into SO

Change Robot service to operate with the VIM/Cloud instance


The cloud-owner is "CloudOwner" and cloud-region-id is specified via the parameters "openstack_region" for deploying this ONAP instance.


  • No labels