Deploy vLB to Multiple Cloud Regions

1, I onboard 3 new cloud regions into AAI (in addition to the default one (CloudOwner/RegionOne) populated by robot init script) with the ESR registration portal: http://portal.api.simpledemo.onap.org:30280/iui/aai-esr-gui/extsys/vim/vimView.html

CloudOwner2/RegionOne

CloudOwner2/CloudRegion2

CloudOwner3/CloudRegion3

2, I hacked into SO to add them into catalogDB:

3, Instantiate a Service Instance of vLB service model: vLB2

This is can only be done with Test API of “VNF_API”, while fails always with Test AP of GR_API

4, Add vnf to vLB2 and select the CloudRegion2(CloudOwner2)

vLB2-VNF1

preload_vid_vlbbase.json

6, create VF Module: vLB2-VNF1-VFM1

Select CloudRegion2(CloudOwner2)

Upload the “preload_vid_vlbbase.json”, de-select SDNC preload

Then I got the dialog showing the progress and told me the result is failure:

"requestId": "eb45ded2-37dd-44a5-8708-45e2f1cc6aba",

"requestType": "createInstance",

"timestamp": "Wed, 29 May 2019 10:51:14",

"requestState": "FAILED",

"requestStatus": "STATUS: Received error from SDN-C: aic-cloud-region,CloudRegion2 not found in AAI",

"percent-progress": "100"

"requestId": "eb45ded2-37dd-44a5-8708-45e2f1cc6aba",

"requestType": "createInstance",

"timestamp": "Wed, 29 May 2019 10:51:13",

"requestState": "IN_PROGRESS",

"requestStatus": undefined,

"percent-progress": undefined

"requestId": "eb45ded2-37dd-44a5-8708-45e2f1cc6aba",

"requestType": "createInstance",

"timestamp": "Wed, 29 May 2019 10:51:12",

"requestState": "IN_PROGRESS",

"requestStatus": undefined,

"percent-progress": undefined

"requestId": "eb45ded2-37dd-44a5-8708-45e2f1cc6aba",

"requestType": "createInstance",

"timestamp": "Wed, 29 May 2019 10:51:10",

"requestState": "IN_PROGRESS",

"requestStatus": undefined,

"percent-progress": undefined

I think the critical issue is:

"requestStatus": "STATUS: Received error from SDN-C: aic-cloud-region,CloudRegion2 not found in AAI",

I am wondering why SDN-C is requesting (aic-cloud-region/CloudRegion2) other than (CloudOwner2/CloudRegion2) which specified via VID portal

Still investigating what's wrong or what the gap is

The following jira/patch might be relevant: