Page History

...

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

      .

   7. 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 ( 'ab208687-8cbf-4368-80e3-a6e9f17ccd1a', NULL, '19ec7776-50fe-4915-bc99-cda08306583a', '47056701-dc62-4f0d-840f-f93f31424b15', '1.0', NULL,NULL,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,'TunnelXConnect',NULL, 'TunnelXConnect');

11/2/2017

1. vCpeResCust custom workflow: 
   1. vcperescust service failed to distribute from SDC to SO for several reasons:
      1. For the vBRG EMU allotted resource, we first designed it using "Allotted Resource" subcategory, SO did not accept it. We then re-designed it using "Tunnel XConn" subcategory, SO accepted it. But it is not clear if this will cause problem later on.
      2. Each VF in the service is assigned a customizationUUID. That ID is not changed unless the VF is removed and recreated in SDC composition. SO throws an error if a service being redistributed includes a component with the same customizationUUID. Basically it checks the DB to see if the ID already exist, if yes then reports a duplicate customizationUUID error in /var/log/ecomp/MSO/ASDC.../msodebug.log. If we need to change and redistribute a service, the workaround is to delete each component and add back in.
      3. Solutions:
         1. We recreated the mso container and db container to start with empty DB tables. Note that only recreate the DB does not work as it will lack the camunda records, which are created when the mso container is initialized.
         2. To recreate, delete the mso container, change /opt/test_lab/deploy.sh to enable "--force-recreate mariadb". Remember to turn it back off afterwards.
         3. After new mso container is created, do the following.
            1. Run cpjars to copy the updated jar and war files into the docker. This is not needed if docker is updated.
            2. Restart the container to load the above files.
            3. Run cpproperties to copy the properties in mso.bpmn.urn.properties, mso.sdnc.properties. Note that this properties got reset each time the container is restarted. This is not needed once docker is updated. But to enable debug log for specific items, some of the flags in mso.bpmn.urn.properties are still needed.
   2. SNIRO is updated to meet the needs of the Homing query. Now the data to be loaded to SNIRO is this: sniro.json. Note that some of the contents needs to be updated, such as gmux uuid.
   3. TunnelXConn flow queried AAI using the vCpeResCust service instance uuid but got nothing. This was caused by racing condition: it was too soon to query after the service flow put the same uuid in AAI. The temp solution is to let the flow sleep for 30 seconds before performing query. It worked. Note that sleeping for 5 seconds was proven to be insufficient.

...