Page History

1. Testing in SB05 Lab Instance
2. Current testing is failing in SDNC. Checking on the logs for failure  

Robot Script integration with SDC for naming-policy update, nf role etc.. [Completed]

Robot Script integration with policy manager for storing the naming recipe as part of the onap instantiation. [InProgress]

Robot Script to update to pass the onap_private_subnet_id at the vnf level. [Completed]

protected_private_subnet_id

Still Issue with the current environment. Being worked.

SDC Distribution is failing. No Release docker that cant control the version. Blocking CDS testing. SDC Distribution has been patched and fixed. Yang is working on the distribution of the latest vFW csar package after the SB05 reinstall.

Do we want to resolve via input or env file.

• The only drawback for env file is that it has to be reworked for every onap instance that is created.
• Yang to follow up with Marco.
• Does the value have to be unique for ONAP instance.
• Casablanca focus the testing with SO starting point.
• Dublin release focus the testing with VID as the starting point.

Question:

Can the Macro instantiation use case be triggered with VID. Yuriy: Yes it should be covered. Yang to share the logs for the VID Failure.

• • Service Assign Passed 
  • VNF Assign Passed
  • Base Assign Passed
  • vFW Module Assign Passed
  • vPG Module Assign Passed
  • vSN Module Assign Passed

A&AI Capability for putting in updates for the generic vnf object and vf module objects. Pat is working on the issue and will submit by 10/12/18.

Alexis: Retest the use case for manual naming assignment.

NOTE:

In General all the capabilities are passing for naming-generation capability, netbox capability, all the MD-SAL and DD resource retrieval is passing.

3. Completed all the Assignment

4. Now SO is trigger the Create-Activate BB but its failing.

SO-1107  - Max Benjamin shall upstream the SO fix. [Completed]

11/16 - Latest SO JIRA:  

SDNC: SO failed b/c A&AI didn't have the self-links. SDNC didn't update the self links (A&AI ) as part of the assignment capability.

SO issue: the cloudOwner is being hardcode as att-aic. Steve S is looking into the fix.

SO is retrying the failed request over and over again in the loop. – Steve S has said a fix is ready and available.

SO Issue: Failing need to be check why. Latest issue.

Plan is to have Alexis start testing in SB05.  10/16.

October 23, 2018:

SO to OOF pairwise testing issue is blocking instantiation use cases progress.  Possible workaround is to use OOF emulator that needs to be integrated with SO. 

OOF implementation in GR-API maybe incomplete. Need meeting with SO team to make progress.

OOF implementation with the VNF-API is coupled to the vCPE use case.