Pairwise Testing - Amsterdam
The purpose of this wiki page is to collect in one central location relevant information for various pairwise testing activities so that we don't need to solely depend on email.
APPC/MultiVIM/AAI Integration Testing
Environment: POD-25 (WindRiver lab)
Protocol for making lab requests: <Stephen Gooch, can you document how you want to manage this?>
Primary goal of testing: Validate OpenStack actions from APPC via MultiVIM Opentack Proxy to VNF
Minimum Configuration:
AAI
ESR
APPC/CDP-PAL
MultiVIM
reference VNFs, propose vFW or vDNS
Key points of Contact for Lab/component deployment:
Lab/Component | Name | Notes | |
|---|---|---|---|
POD-25 | Stephen Gooch Gil Hellmann | ||
AAI | Jimmy Forsyth | ||
ESR | Zi Li | ||
APPC | Aaron Hay Veer Rajasekhar | ||
CDP-PAL | Tyler Smith | 9/6/17: CDP-PAL is deployed as part of APPC. APPC team will pull in Tyler as needed. | |
Multi-VIM/Cloud | Bin Yang | ||
MSB | Zhao Huabing | ||
Reference VNF | Marco Plantania | 9/6/17: Need to confirm with Marco that he will be the contact/support point for this Confirmed. |
Component Specs:
Component | VM | vCPU/ Cores | RAM | Storage | Additional Details |
|---|---|---|---|---|---|
AAI | 2 | 8 | 16GB | 50GB | an additional volume of 50 GB |
ESR | 1 | 2 | 4GB | N/A | ESR uses AAI for storage |
APPC/CPD-PAL | 1 | 4 | 8GB | 80GB | |
Multi-VIM/Cloud | 3 | 12 | 24GB | 240GB | 3 components:Broker, Plugin for Openstack Newton, Plugin for VIO |
MSB | 1 | 2 | 8G | 40GB | |
VNF (vFW) | 3 | 6 | 12GB | 12-GB | 3VMs: 1 traffic generator (data source), 1 firewall, 1 destination |
Deployment order:
From a deployment sequence, we assume the following order:
AAI (and ESR - look to AAI for details on deployment dependencies between these AAI & ERS microservice)
APPC (checks for AAI availability, so needs to come after AAI)
MSB
MutlVIM
VNF
High Level Tests: To be also tracked in Integration project
APPC
No. | Description | JIRA |
|---|---|---|
1 | APPC ONAP -LCM API HEALTHCHECK | |
2 | APPC ONAP -LCM API VM RESTART | |
3 | APPC ONAP -LCM API VNF RESTART | |
4 | APPC ONAP -LCM API START | |
5 | APPC ONAP -LCM API STOP | |
6 | APPC ONAP -LCM API VM REBUILD |
Refer to APPC Testing Scope and Status for additional tests executed.
Timeline:
9/6/17:
Lab planning activities to start this week (9/7)- led by Gil Hellman, who will reach out to key contacts from above.
APPC and AAI should have code done by end of week (9/8), so dockers may need to be upgraded next week depending on deployment progress made this week.
We will checkpoint early next week to see if we are ready to start testing; lab deployments always take longer than anticipated due to various issues related to connectivity that come up.
Tracking Issues:
Team agrees to track activity and any reported issues in the Integration project. An Epic will be create for APPC-MutlVIM Integration and stories and bugs will be tracked under that Epic.
Integration Project Epic: INT-181
The component field will be used to identify to which component an a story or bug belongs to. The following components have been created <pending>:
APPC
AAI
CDP-PAL
ESR
MultiVIM
MSB
11/11/17 update: In the end, it didn't quit work out this way. Issues were opened in each project.
APPC/DMaaP Integration Testing
Environment: POD-25 (WindRiver lab)
Primary goal of testing: Validate receiving messages from and posting messages to DMaaP successfully
Minimum Configuration:
Same configuration listed in APPC/MultiVIM/AAI Integration Testing, plus the following:
Key points of Contact for Lab/component deployment:
Same contacts listed in APPC/MultiVIM/AAI Integration Testing, plus the following
Lab/Component | Name | Notes | |
|---|---|---|---|
DMaaP | Varun Gudisena | ||
Multi-VIM/Cloud | Bin Yang |
Component Specs:
Same components listed in APPC/MultiVIM/AAI Integration Testing, plus the following
Component | VM | vCPU/ Cores | RAM | Storage | Additional Details |
|---|---|---|---|---|---|
DMaaP-MR | 1 | 4 | 8GB | 256GB |
Deployment order:
Deploy DMaaP before APPC
High Level Tests: To be also tracked in Integration project
Refer to APPC Testing Scope and Status for details on the tests executed using DMaaP
Tracking Issues:
Team agrees to track activity and any reported issues in the Integration project. An Epic will be create for APPC-DMaaP Integration and stories and bugs will be tracked under that Epic.
The component field will be used to identify to which component an a story or bug belongs to.
11/11/17 update: In the end, it didn't quit work out this way. Issues were opened in each project.
APPC/DMaaP/Policy Integration Testing
Covered by Integration team as part of vCPE/VFW testing.
APPC/DMaaP/Policy/CLAMP Integration Testing
Covered by Integration team as part of vCPE testing.