Page History

...

1. vCpeResCust custom workflow: 

   1. Body 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-17", "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" : "b12d36da-459f-41be-aadc-7034568690eb", "modelName" : "vCpeResCust110301", "modelVersion" : "1.0", "modelInvariantId" : "ef89c526-70f3-410e-ab30-563bd20d364d" } } }

   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: activate.

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 ( 'ab208686-8cbf-4368-80e3-a6e9f17ccd1a', NULL, '19ec7776-50fe-4915-bc99-cda08306583a', '47056701-dc62-4f0d-840f-f93f31424b15', '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 ('9ad2424f-a18f-4f54-8ef7-f3326584c1da', NULL, '73f307f5-b9f5-4fd8-90d8-25d703d1cfad', '76c0f51c-4760-4212-99d0-9bbcb08fdc11', '1.0', NULL,NULL,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

...