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)
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 | jf2512@att.com | |
ESR | Zi Li | li.zi30@zte.com.cn | |
APPC | Aaron Hay Veer Rajasekhar | ||
CDP-PAL | Tyler Smith | ts4124@att.com> | 9/6/17: CDP-PAL is deployed as part of APPC. APPC team will pull in Tyler as needed. |
MultiVIM | Bin Yang | Bin.Yang@windriver.com | |
Reference VNF | Marco Plantania | platania@research.att.com | 9/6/17: Need to confirm with Marco that he will be the contact/support point for this. |
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 | |
MultiVIM | ? | ? | ? | ? | |
VNF (vFW) |
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)
- MutlVIM
- VNF
High Level Tests: To be also tracked in Integration project
- Via apidoc explorer
- LCM Restart
- <TBP >
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.
The component field will be used to identify to which component an a story or bug belongs to.
APPC/DMaaP Integration Testing
TBD
APPC/DMaaP/Policy Integration Testing
TBD
APPC/DMaaP/Policy/CLAMP Integration Testing
TBD