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:

Component Specs:

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

• 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:
  
  • DMaaP

Key points of Contact for Lab/component deployment:

• Same contacts listed in APPC/MultiVIM/AAI Integration Testing, plus the following

Component Specs:

• Same components listed in APPC/MultiVIM/AAI Integration Testing, plus the following

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.