This is the tracking page for ONAP Functional Requirement of "Consistent ID of Cloud Regions"
Functional Requirement Name
Consistent ID of Cloud Regions
Development Status (Consistent ID of Cloud Regions)
| Project | PTL | JIRA Epic / User Story* | Requirements |
|---|---|---|---|
| SO | 1,Depreciate the usage of "cloud-region-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region | ||
| OOF | 1,Depreciate the usage of "vim-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region | ||
| VFC | VFC-9401209 | 1,Depreciate the usage of "vim-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region | |
| UUI | USECASEUI-131 | 1,Depreciate the usage of "vim-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region | |
| VID | 1,Depreciate the usage of "vim-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region |
*Each Requirement should be tracked by its own User Story in JIRA
Testing Plans
Test Plan 1: for CCVPN Use Case covering"Consistent ID of Cloud Region":
Prerequisites: UUI/VFC/MultiCloud projects accomplish the functional requirement: "Plan B, Phase 2: Consistent ID of Cloud Regions"
Step 1, Tester on-boards a VIM instance as a 2 cloud region regions with ESR GUI Portal, with VIM id: with cloud region 1: {cloud-owner: CloudOwner1, cloud-region-id: RegionOne}, and cloud region 2: {cloud-owner: Cloud_Owner1CloudOwner2, cloud-region-id: RegionTest,RegionOne}
Step 2, Tester instantiates VNFs (a vVoLTE VNF) with UUI GUI Portal to this these cloud regionregions
Step 3, Tester observes the VNFs are created onto the VIM instanceinstances
Test Plan 2: for vFW Use Case covering"Consistent ID of Cloud Region"
Prerequisites: VID/SO/SDNC projects accomplish the functional requirement: "Plan B, Phase 2: Consistent ID of Cloud Regions"
Step 1, Tester on-boards a VIM instance as a cloud region with ESR GUI Portal, with VIM id: cloud with cloud region 1: {cloud-owner: CloudOwner1, cloud-region-id: RegionOne}, and cloud region 2: {cloud-owner: Cloud_Owner1CloudOwner2, cloud-region-id: RegionOne,}
Step 2, Tester instantiates VNFs (vFWCL) with VID GUI Portal to this these cloud regionregions
Step 3, Tester observes the VNFs are created onto the VIM instanceinstances
Current Status
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
End to End flow to be tested:
Follow Use Case vFWCL and vVoLTE respectively
Test Plan 1: for "Consistent ID of Cloud Region"
Step 1: workflow for on-boarding a VIM instance, Make sure cloudowner is "Cloud_Owner1" cloud region 1: {cloud-owner: CloudOwner1, cloud-region-id: RegionOne}, and cloud region 2: {cloud-owner: CloudOwner2, cloud-region-id: RegionOne}
| Gliffy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Step 2: Follow the orchestration workflow of Use Case vCPE with TOSCA VNF
Step 3: Login to OpenStack Horizon to verify the VMs for vCPE TOSCA VNFs are created as expected
Test Plan 2: for "Consistent ID of Cloud Region":
Step 1: The same as Test plan 1, Step 1. Make sure cloudowner is "Cloud_Owner1", cloud region id is "RegionOne" cloud region 1: {cloud-owner: CloudOwner1, cloud-region-id: RegionOne}, and cloud region 2: {cloud-owner: CloudOwner2, cloud-region-id: RegionOne}
Step 2: Follow the orchestration workflow of Use Case vFWCL
Step 3: Login to OpenStack Horizon to verify the heat stacks for vFWCL VNFs are created as expected
Test Cases and Status
| # | Test Case | Status |
|---|---|---|
| 101 | Using ESR VIM Registration Portal, ONAP user on-boards an OpenStack Instance as cloud region with following parameters: |
cloud region 1: {cloud-owner: CloudOwner1, cloud-region-id: RegionOne}, and cloud region 2: {cloud-owner: CloudOwner2, cloud-region-id: RegionOne}, Cloud Type: openstack, Cloud Region Version: titanium_cloud, Cloud Extra Info: "{\"openstack-region-id\":\"RegionOne\"}" Note 1: The on-boarding process follows the steps described by "How-To: Register a VIM/Cloud Instance to ONAP" with one exception: The on-boarding process will not hack any SO configuration file which is depicted as "2, Register VIM/Cloud instance into SO". Note 2: This on-boarding process should be done with updated Robot script according to INT-541 |
|
| ||
| 102 | ONAP user |
| elect Cloud Region on UUI: should be able to distinct 2 cloud regions with the same cloud region ID |
| ||||||
| 103 | ONAP user could instantiate VNFs to both cloud regions |
|
| 104 | ONAP user logins to OpenStack Horizon and observes the |
| stack (representing the instantiated VF Module above) is launched. |
| ||||
| 201 | Same as 101, except one parameter change |
| : cloud region 1: {cloud-owner: CloudOwner1, cloud-region-id: RegionOne}, and cloud region 2: {cloud-owner: CloudOwner2, cloud-region-id: RegionOne} |
| |||||||||||||||||
| 202 | ONAP user elect Cloud Region on VID: should be able to distinct 2 cloud regions with the same cloud region ID |
| ||||||||||||||||
| 202 | Same as |
103, except the selected cloud region is {Cloud_Owner1/RegionOne} |
|
| 204 | Same as |
| 104 |
|