...
vCpeResCust custom workflow:
Postman body to invoke SO updated
Code Block language java title to invoke SO collapse true http://so:8080/ecomp/mso/infra/serviceInstances/v5 user/pass: InfraPortalClient:password1$ Content-Type and Accept are both: application/json { "requestDetails" : { "requestInfo" : { "productFamilyId" : "a9a77d5a-123e-4ca2-9eb9-0b015d2ee0fb", "suppressRollback" : "false", "instanceName" : "vcperescust-1104-19", "requestorId": "Kang", "source" : "Postman-Kang" }, "requestParameters" : { "subscriptionServiceType" : "vCPE", "userParams" : [{ "name":"BRG_WAN_MAC_Address", "value":"fa:16:3e:8f:ea:68" }], "aLaCarte" : "false" }, "subscriberInfo" : { "subscriberName" : "Kaneohe", "globalSubscriberId" : "SDN-ETHERNET-INTERNET" }, "cloudConfiguration" : { "lcpCloudRegionId" : "RegionOne", "tenantId" : "466979b815b5415ba14ada713e6e1846" }, "modelInfo" : { "modelType" : "service", "modelVersionId" : "2da136af-510d-457e-b3dc-f1c3e6dab0c3", "modelName" : "vCpeResCust110403", "modelVersion" : "1.0", "modelInvariantId" : "35f93cd5-17a8-4735-9531-a63df867d776" } } }
- Made much progress by modifying multiple DGs with temp fixes. Marcus is working to fix them the right way and commit to the repo. Passed TunnelXConn steps: assign, create. Wait to be tested: activate. Some of the problems are:
- Incorrect username/password for authentication;
- Correct username/password in configuration file, but they are referenced incorrectly in DG.
- DG does not obtain globalcustomerID and gmux service ID properly, and thus failed to query AAI.
- Use incorrect IP to config vGMUX.
- Restconf request to vGMUX has mal-formatted body.
- DG has error (use incorrect resource) when allocating IP addresses for vG.
- Created a new vCpeResCust110403 service. The difference is that now the vG model is based on the latest heat and env: vgw.zip. The heat and env have been validated using openstack stack create. Note that in order to correctly distribute to SO, all the components were created from scratch, including vG (from onboarding), tunnelXconn VF, vBRG Allotted Resource VF. After distribution, added service recipe in SO DB and allotted resources to SDNC DB. Verified that this service model can be executed through SO API.
...