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)
...
- Integration Project Epic: INT-181
The 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>:
APPCAAICDP-PALESRMultiVIMMSB
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)
...
- 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 | bin.yang@windriver.com |
...
- 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 APPCTBP
High Level Tests: To be also tracked in Integration project
- TBP
Timeline:
- TBPRefer 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.