-
Task
-
Resolution: Done
-
Medium
-
None
-
None
-
OOF-Beijing-Sprint 4, OOF-Beijing-Sprint 5
As OOF developer, I would like to accommodate the vim-id definition proposed by MultiCloud in https://wiki.onap.org/download/attachments/25429038/HowToAddNewCloudRegionAndThoughts.pdf?version=2&modificationDate=1520214136000&api=v2
The format recommended is:
{vim-id}=
{cloud-owner}_
{cloud-region-id}However, this format is not the accepted/recognized unanimously across all projects. Especially, SO,VID,SDNC,Integration team prefer the decoupled keys, not the concatenated vim.
Since our homing candidates have both the cloud-owner and cloud-region-id information already, and it is fairly easy to add a new attribute to the candidate, I recommend that we add the vim-id as an attribute to support the MultiCloud capacity_check queries: https://gerrit.onap.org/r/#/c/29413/
- relates to
-
OPTFRA-188 Format response to SO based on vim-id
- Closed
-
MULTICLOUD-166 Add check_vim_capacity to broker
- Closed
-
OPTFRA-42 OOF-MultiCloud Interface plugin
- Closed