Hi Eswar, The link http://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/Multicloud-Fake_Cloud-Guide.html is to onboarding a fake VMware fake cloud, you need change some parameters to register a OpenStack instance.
I had shared some insight of VIM registration for ONAP A release in another thread, I paste it here for your reference, by the way, (to echo your another email ) you need use VID to instantiate the vFWCL demo. First of all, with ONAP in Amsterdam release, the VIM registration is not centralized in one place, as far as I know , there are two places to store VIM registration information which concerning service/VNF instantiation: SO and AAI. This is very important context for anyone who wants to add or modify VIM registration information. Several facts you need to know to register a new VIM instance to ONAP for orchestration: 1. To put VIM registration information into AAI, there are various way to do that, the most user-friend one is to leverage the ESR portal, which will trigger multicloud to discover VIM/cloud resources automatically. Please refer to docs at http://onap.readthedocs.io/en/latest/submodules/aai/esr-server.git/docs/platform/installation.html MultiCloud is using this VIM registration information to mediate API calls from SO/APPC/DCAEgen2/VFC/etc. to underlying VIMs 2. To put VIM registration information into SO, you need login SO VM and attach to the container, then you can change the config file. Here is the hint on wiki: https://wiki.onap.org/display/DW/vFWCL+instantiation%2C+testing%2C+and+debuging?focusedCommentId=22252150#comment-22252150 I guess VID is using this VIM registration information. 3. The registration procedures above are loosely coupled Let me give you several examples: Case 1: SO instantiate a VF modules without MultiCloud In this case, VIM registration information refers to directly identity services of underlying VIMs (those VIM exposes OpenStack keystone V2.0 API ), so the identity_url looks like: "identity_url": "http://10.12.25.2:5000/v2.0";, Case 2: SO instantiate a VF modules via MultiCloud In this case, VIM registration information refers to MultiCloud endpoints which is a proxy to underlying VIMs, so the identity_url looks like: "identity_url": " http://10.0.14.1:80/api/multicloud-titanium_cloud/v0/pod25_RegionOne/identity/v2.0";, For simplicity , I suggest that you just put VIM registration information into SO, and follow the Case 1 to instantiate the vFWCL. When you have more experiences and know how to compose the multicloud endpoints for your VIM instance, you can do your test following the Case 2 . Best Regards, Bin Yang, Solution Readiness Team, Wind River Direct +86,10,84777126 Mobile +86,13811391682 Fax +86,10,64398189 Skype: yangbincs993 From: [email protected] [mailto:[email protected]] On Behalf Of ESWAR RAO Sent: Wednesday, January 17, 2018 8:12 PM To: [email protected] Subject: [onap-discuss] Registered VIMs in ONAP Portal Hi All, I have installed ONAP Amsterdam release. I have registered a VIM following: http://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/Multicloud-Fake_Cloud-Guide.html # curl -X PUT -H X-TransactionId:get_aai_subr -H X-FromAppId:AAI -H Accept:application/json -H Content-Type:application/json -H 'Authorization:Basic QUFJO kFBSQ==' https://192.168.21.211:8443/aai/v11/cloud-infrastructure/cloud-regions/cloud-region/onap/bglr --insecure -d '{ "cloud-owner": "onap", "cloud-region-id": "bglr", "cloud-type": "openstack", "cloud-region-version": "4.0", "identity-url": "http://192.168.21.212:80/api/multicloud-ocata/v0/onap_bglr/identity/v3";, "cloud-zone": "bglr", "complex-name": "bglr-demo", "esr-system-info-list": { "esr-system-info": [ { "esr-system-info-id":"bglr-cloud", "system-name": "bglr-cloud", "type": "vim", "service-url": "http://192.168.21.31:5000/v3";, "user-name": "admin", "password": "36cee2491a7440e5", "system-type": "VIM", "ssl-insecure": "true", "cloud-domain": "Default", "default-tenant": "admin" } ] } } I am able to exercise all the APIs (list/create servers/heat-stacks) using below: http://192.168.21.212:80/api/multicloud-ocata/v0/onap_bglr/identity/projects http://192.168.21.212:80/api/multicloud-ocata/v0/onap_bglr/orchestration/v1/<tenant_id>/stacks I am unable to see registered VIM in ONAP portal. http://portal.api.simpledemo.onap.org:8989/ONAPPORTAL/login.htm Please let me know how can I see it ?? I can view registered VIMs in http://<onap-multi-service>/iui/aai-esr-gui/extsys/vim/vimView.html<http://%3conap-multi-service%3e/iui/aai-esr-gui/extsys/vim/vimView.html> Am I missing something in this flow ??? Thanks Eswar Rao
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
