Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


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)

ProjectPTLJIRA Epic / User Story*Requirements
 SOSO

SO Adapter to Multicloud Improvements

1,Depreciate the usage of "cloud-region-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region

 OOFOOF1,Depreciate the usage of "vim-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region
VFCVFC-94012091,Depreciate the usage of "vim-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region
UUIUSECASEUI-1311,Depreciate the usage of "vim-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region SDNC1,Depreciate the usage of "vim-id", use the composite key of "{cloud-owner}, {cloud-region-id}" to specify a cloud region
VID

VID-247

 VID

VID-246

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 "Centralized Representation CCVPN Use Case covering"Consistent ID of Cloud Region":

Prerequisites: SOUUI/VFC/Integration MultiCloud projects accomplish the functional requirement: "Plan B, Phase 12: Centralized Representation  Consistent ID of Cloud RegionRegions"

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: RegionTest.

Step 2, Tester Instantiates heat template based VF Module (vFWCL) to this cloud region with VID GUI Portal.

Step 3, Tester observes the vFWCL heat stacks are created onto the VIM instance.

Test Plan 2: for "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 cloud region with ESR GUI Portal, with VIM id: cloud-owner: Cloud_Owner1RegionOne}, and cloud region 2: {cloud-owner: CloudOwner2, 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 3: for 2: 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:  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

  1. Testing Blockers

  2. High visibility bugs
  3. Other issues for testing that should be seen at a summary level
  4. Where possible, always include JIRA links


End to End flow to be tested:

Follow Use Case vFWCL and vVoLTE respectively

Test Plan 1: for "Centralized Representation Consistent ID of Cloud Region"

Step 1: workflow for on-boarding a VIM instance, Make sure cloudowner is "CloudOwner1" cloud region 1: {cloud-owner: CloudOwner1, cloud-region-id: RegionOne}, and cloud region 2: {cloud-owner: CloudOwner2, cloud-region-id: RegionOne}

Gliffy Diagram
size600
nameSummary SeqDia Template
pagePin3

Step 2: Follow  the orchestration workflow of Use Case vFWCLof  Use Case vCPE with TOSCA VNF

Step 3: Login to OpenStack Horizon to verify the heat stacks VMs for vFWCL 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"

Step 2: Follow  the orchestration workflow of  Use Case vVoLTE

Step 3: Login to OpenStack Horizon to verify the heat stacks for vVoLTE VNFs are created as expected

Test Plan 3: for "Consistent ID of Cloud Region" (Will not be ready for testing in Casablanca Release):

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 CaseStatus
101

Using ESR VIM Registration Portal, ONAP user on-boards an OpenStack Instance as cloud region with following parameters:

Cloud Owner:CloudOwner1, Cloud Region Id: RegionTest

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

Status
colourGreen
title

Not yet tested

Done

102ONAP user
instantiates a VF Module of vFWCL to the cloud region {CloudOwner1/RegionTest}

Refer to "ONAP Amsterdam vFW Closed Loop Demo" for detail process.

elect Cloud Region on UUI: should be able to distinct 2 cloud regions with the same cloud region ID

Status
colourGreen
titleDone

103ONAP user could instantiate VNFs to both cloud regions
Note 1: This process can be done with existing Robot script (with enhancement to specify ID of cloud region?): ete.sh or ete-k8s.sh

Status
titleNOT YET TESTED

103
104ONAP user logins to OpenStack Horizon and observes the
HEAT
stack (representing the instantiated VF Module above) is launched.

Status
titleNOT YET TESTED




201Same as 101, except one parameter change
: Cloud Owner: "Cloud_Owner1"
: cloud region 1: {cloud-owner: CloudOwner1, cloud-region-id: RegionOne}, and cloud region 2: {cloud-owner: CloudOwner2, cloud-region-id: RegionOne}

Status
colourGreen
titleDone

  StatustitleNOT YET TESTED

202ONAP user
instantiate the VNF of VoLTE use case. Refer to "VoLTE Integration Test Cases"
elect Cloud Region on VID: should be able to distinct 2 cloud regions with the same cloud region ID

Status
colourRed
titleFailed

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-482

202

Same as 103

Status
titleNOT YET TESTED

203ONAP user logins to OpenStack Horizon and observes the vservers (representing the instantiated VF Module above) is launched.

Status
titleNOT YET TESTED

301Same as 101, except one parameter change: Cloud Owner: "Cloud_Owner1", Cloud Region Id: "RegionOne",Cloud Extra Info: ""

Status
titleNOT YET TESTED

302Same as 102

, except the selected cloud region is {Cloud_Owner1/RegionOne}


Status
titleNOT YET TESTED

303
204Same as
103
104

Status
titleNOT YET TESTED