You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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/ComponentNameEmail Notes
 POD-25

 Stephen Gooch

Gil Hellmann

 stephen.gooch@windriver.com>

gil.hellmann@windriver.com

 
AAIJimmy Forsythjf2512@att.com 
ESRZi Lili.zi30@zte.com.cn 
APPC

Aaron Hay

Veer Rajasekhar

ah415j@att.com

vr772b@att.com

 
CDP-PALTyler Smithts4124@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:

ComponentVM

vCPU/

Cores

 RAMStorageAdditional Details
AAI28 16GB50GBan additional volume of 50 GB
ESR12 ?N/AESR uses AAI for storage
APPC/CPD-PAL14 8GB80GB
MultiVIM? ? ??
VNF (vFW)

 


Timeline

9/7/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 

  • No labels