This is the tracking page for ONAP Functional Requirement of "Centralized Representation and Consistent ID of Cloud Regions"
Functional Requirement Name
Plan B, Phase 1: Centralized Representation of Cloud Regions
Plan B, Phase 2: Consistent ID of Cloud Regions
Development Status (Plan B, Phase 1: Centralized Representation of Cloud Regions)
| Project | PTL | JIRA Epic / User Story* | Requirements |
|---|---|---|---|
| SO | 1,Depreciate the usage of internal representation of cloud region. Use centralized representation of cloud region in AAI instead. | ||
| Integration | 1, Robot VM should depreciate the usage of internal representation of cloud region. Use centralized representation of cloud region in AAI instead. 2, Robot VM should allow users to specify the composite key of "{cloud-owner}, {cloud-region-id}" to execute scripts |
Development Status (Plan B, Phase 2: 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-940 | 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 | |
| MultiCloud | MULTICLOUD-259 | 1,Depreciate the usage of "vim-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region | |
| SDNC | 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
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
**This should be a summary level Sequence diagram done in Gliffy**
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
Test Cases and Status
| # | Test Case | Status | ||||||
|---|---|---|---|---|---|---|---|---|
| 1 | There should be a test case for each item in the sequence diagram |
| ||||||
| 2 | create additional requirements as needed for each discreet step |
| ||||||
| 3 | Test cases should cover entire Use Case |
| ||||||
| 4 | Test Cases should include enough detail for testing team to implement the test |
|