Page History

...

APPC Testing Scope and Status

11/7/2017

new vgw yaml file: 

11/6/2017

1. vCpeResCust custom workflow:
   1. Test almost finished. Successfully created tunnel-x-connect, vG, and brg-allotted-resource. When SO finally queries SDC with the parent service instance id of brg-allotted-resource (which is the service instance id of vbrg service), SDNC failed to find it in its catalog. This will be fixed. Once this query passes, SO service flow will finish successfully.
   2. SO calling SDNC to create a vG instance failed. SDNC queried AAI to find the availability zone but such a zone did not exist. Brian fixed this by manually adding such a zone and a complex in AAI. Jerry will add this in demo.sh init. 

      1. Add an availability zone

         Code Block
         title Add availability zone collapse true
         https://aai1:8443/aai/v11/cloud-infrastructure/cloud-regions/cloud-region/CloudOwner/RegionOne/availability-zones/availability-zone/nova { "availability-zone-name": "nova", "hypervisor-type": "KVM", "operational-status": "Active" }

      2. Add an complex

         Code Block
         title Add a complex collapse true
         https://aai1:8443//aai/v11/cloud-infrastructure/complexes/complex/clli1 { "physical-location-id": "clli1", "data-center-code": "example-data-center-code-val-5556", "complex-name": "clli1", "identity-url": "example-identity-url-val-56898", "resource-version": "1509928831089", "physical-location-type": "example-physical-location-type-val-7608", "street1": "example-street1-val-34205", "street2": "example-street2-val-99210", "city": "example-city-val-27150", "state": "example-state-val-59487", "postal-code": "example-postal-code-val-68871", "country": "example-country-val-94173", "region": "example-region-val-13893", "latitude": "example-latitude-val-89101", "longitude": "example-longitude-val-66229", "elevation": "example-elevation-val-30253", "lata": "example-lata-val-46073" }

      3. Add relationship in CloudOwner to the above complex

         Code Block
         title Add relationship to the complex collapse true
         https://aai1:8443/aai/v11/cloud-infrastructure/cloud-regions/cloud-region/CloudOwner/RegionOne/ Do a GET of CloudOwner/RegionOne and add this relationship then do a PUT back to CloudOwner/RegionOne "relationship": [ { "related-to": "complex", "related-link": "/aai/v11/cloud-infrastructure/complexes/complex/clli1" } Example: { "cloud-owner": "CloudOwner", "cloud-region-id": "RegionOne", "cloud-type": "SharedNode", "owner-defined-type": "OwnerType", "cloud-region-version": "v1", "cloud-zone": "CloudZone", "sriov-automation": false, "resource-version": "1509931173816", "relationship-list": { "relationship": [ { "related-to": "complex", "related-link": "/aai/v11/cloud-infrastructure/complexes/complex/clli1" }, { "related-to": "l3-network", .... more data ...

   3. SO calling SDNC during vG instantiation used incorrect format for vG. What defined in Yang uses dash, e.g., vg-ip. SO used vg_ip. SO fixed this onsite.
   4. vG instantiation completed successfully. Currently the IP address facing vGMUX is using the one in HEAT. SO workflow should take the one allocated by SDNC. 
   5. SO: preProcessSDNCAssign workflow didn't include modelCustomizationUuid. This was fixed onsite.

   6. A routing entry needs to be added to the SDNC VM (not docker) to allow reaching BRG through BNG:

      Code Block
      ip route add 10.3.0.0/24 via 10.0.101.10 dev eth0

   7. SDNC assign of brg-allotted-resource failed. Note that unassign, activate, deactive all may have similar problems.
      1. The original DG had an error and was not loaded to SDNC. Fixed.
      2. The assign DG didn't set global-customer-id. Fixed.
      3. The assign DG didn't set service instance uuid. Fixed.
   8. The latest config for SO are: mso.sdnc.properties and mso.bpmn.urn.properties. Note that these config files are dynamically generated when SO docker container is started/restarted. After the latest fixes, there should be no need to use these files anymore.

...