Page History

...

1. vCpeResCust custom workflow: 

   1. Postman body to invoke SO updated

      Code Block
      language java title to invoke SO collapse true
      { "requestDetails" : { "requestInfo" : { "productFamilyId" : "a9a77d5a-123e-4ca2-9eb9-0b015d2ee0fb", "suppressRollback" : "false", "instanceName" : "vcperescust-1104-1719", "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" : "b12d36da2da136af-459f510d-41be457e-aadcb3dc-7034568690ebf1c3e6dab0c3", "modelName" : "vCpeResCust110301vCpeResCust110403", "modelVersion" : "1.0", "modelInvariantId" : "ef89c52635f93cd5-70f317a8-410e4735-ab309531-563bd20d364da63df867d776" } } }

   2. 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: activateway and commit to the repo. Passed TunnelXConn steps: assign, create. Wait to be tested: activate. Some of the problems are:
      1. Incorrect username/password for authentication;
      2. Correct username/password in configuration file, but they are referenced incorrectly in DG.
      3. DG does not obtain globalcustomerID and gmux service ID properly, and thus failed to query AAI.
      4. Use incorrect IP to config vGMUX.
      5. Restconf request to vGMUX has mal-formatted body.
      6. DG has error (use incorrect resource) when allocating IP addresses for vG.
   3. 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.

11/3/2017

1. vCpeResCust custom workflow: 

   1. Modified the vcperescust service and then redistribution to AAI failed. It looks like SDC has a problem handling update but it is not easy to pinpoint the problem. The workaround is to recreate the service from scratch. Distribution passed.

   2. Brian created the infrastructure including BNG BRG vGMUX, which are to be used for vcperescust flow.

   3. Found a bug in TunnelXConn flow where the content send to SDNC assign is incorrect. Fixed with code change onsite. Tracked by 

      Jira
      server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SO-302

   4. Found a few missing configurations and mistakes in mso.sdnc.properties, fixed onsite. The file being used now is mso.sdnc.properties.

   5. Found a problem in SDNC handling TunnelXConn create operation. Dan fixed it onsite. 

   6. TunnelXConn flow has a bug: the SDNC assign request misses some info: 

      Jira
      server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SO-304

   7. SDNC ueb cannot parse service template when distributed. Reopen this ticket: 

      Jira
      server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SDC-564

      .

   8. Manually inserted the following into table: ALLOTTED_RESOURCE_MODEL

      Code Block
      title Insert into sdnc db ALLOTTED_RESOURCE_MODEL collapse true
      INSERT INTO ALLOTTED_RESOURCE_MODEL (`customization_uuid`,`model_yaml`,`invariant_uuid`,`uuid`,`version`,`naming_policy`,`ecomp_generated_naming`,`depending_service`,`role`,`type`,`service_dependency`,`allotted_resource_type`) VALUES ( 'ab208686fc63c42e-8cbf6c52-43684d9b-80e3a6bc-a6e9f17ccd1abe8d1365b03a', NULL, '19ec7776b7752dfe-50fe8b52-491547e6-bc99a79f-cda08306583afe75ab286f8d', '470567010e03fd2d-dc62e8b7-4f0d4a86-840f9a60-f93f31424b15c7025756e48e', '1.0', NULL,'Y',NULL,NULL,'TunnelXConnect',NULL, 'tunnelxconnect'); INSERT INTO ALLOTTED_RESOURCE_MODEL (`customization_uuid`,`model_yaml`,`invariant_uuid`,`uuid`,`version`,`naming_policy`,`ecomp_generated_naming`,`depending_service`,`role`,`type`,`service_dependency`,`allotted_resource_type`) VALUES ('9ad2424fcda7b93c-a18ff742-4f54478e-8ef79262-f3326584c1daa457ed6c2844', NULL, '73f307f5ea4e0947-b9f52498-4fd84030-90d8bb7a-25d703d1cfad5a5294cccfd5', '76c0f51c110e8a6e-476087f9-42124133-99d0beab-9bbcb08fdc117ea5c36f0be8', '1.0', NULL,NULL'Y',NULL,NULL,'BRG',NULL, 'brg') ;

   9. A few other tickets: 

      Jira
      server ONAP JIRA columns key,summary,status maximumIssues 20 jqlQuery key in (SDNC-170,SDNC-169,SDNC-168,SDNC-167) serverId 425b2b0a-557c-3c0c-b515-579789cceedb

...