Page History

...

1. vCpeResCust custom workflow: 
   1. The config changes for sniro end point should be visible at : docker-config\volumes\mso\chef-config\mso-docker.json. We should look at "sniroEndpoint".
   2. SNIRO emulator config tested. The related wiki page is here: SNIRO Emulator

   3. Add the following to ./etc/mso/config.d/mso.bpmn.urn.properties to enable debug

      Code Block
      title Debug mode linenumbers true
      log.debug.CreateVcpeResCustService=true log.debug.DeleteVcpeResCustService=true log.debug.DoCreateAllottedResourceBRG=true log.debug.DoCreateAllottedResourceBRGRollback=true log.debug.DoCreateAllottedResourceTXC=true log.debug.DoCreateAllottedResourceTXCRollback=true log.debug.DoDeleteAllottedResourceBRG=true log.debug.DoDeleteAllottedResourceTXC=true log.debug.Homing=true

10/25/2017

1. vCpeResCust custom workflow: 

   1. Re-created SO maria DB to reflect the latest change to the DB tables. This done by adding a line to /opt/test_lab/deploy.sh: "$DOCKER_COMPOSE_CMD up -d --force-recreate mariadb".

   2. The workflow successfully obtained service template from the catalog and decomposed it.

   3. A problem was observed when the workflow tried to call the homing service. It is 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-268

      .
2. Genera Infrastructure:
   

   1. Brian modified the neutron heat template and parameters in SO DB, pre-loaded SDNC, and successfully created virtual networks. (The scripts and template on 10/24 notes have been updated accordingly.) SDNC preload data for CPE_SIGNAL is below.

      Code Block
      title SDNC Preload for CPE_SIGNAL collapse true
      { "VNF-API:input": { "VNF-API:request-information": { "VNF-API:request-id": "robot0012", "VNF-API:notification-url": "http://so.onap.org", "VNF-API:order-number": "robot0012", "VNF-API:request-sub-action": "SUPP", "VNF-API:request-action": "PreloadNetworkRequest", "VNF-API:source": "robot", "VNF-API:order-version": "1.0" }, "VNF-API:network-topology-information": { "VNF-API:network-topology-identifier": { "VNF-API:network-role": "cpe-public", "VNF-API:network-technology": "neutron", "VNF-API:service-type": "vCPE", "VNF-API:network-name": "vCPEInfraCPEPUBLICL1025BDF01", "VNF-API:network-type": "Generic NeutronNet" }, "VNF-API:provider-network-information": { "VNF-API:is-external-network": "true", "VNF-API:physical-network-name": "vCPEInfraCPEPUBLIC1025BDF01", "VNF-API:is-provider-network": "true", "VNF-API:is-shared-network": "true" }, "VNF-API:subnets": [ { "VNF-API:start-address": "10.2.0.2", "VNF-API:cidr-mask": "24", "VNF-API:subnet-name": "vCPEInfraCPEPUBLIC1025BDF01", "VNF-API:ip-version": "4", "VNF-API:dhcp-enabled": "N", "VNF-API:gateway-address": "10.2.0.1" } ] }, "VNF-API:sdnc-request-header": { "VNF-API:svc-action": "reserve", "VNF-API:svc-notification-url": "http://so.onap.org", "VNF-API:svc-request-id": "reobot0012" } } }

   2. During VNF instantiation, a bug was discovered. The content of DB table vnf_component_recipe is incorrect. It is 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-267

      .
   3. Brian found a few bugs related to SDNC: 

      Jira
      server ONAP JIRA columns key,summary,status maximumIssues 10 jqlQuery key in (SDNC-148,SDNC-147,SDNC-145) serverId 425b2b0a-557c-3c0c-b515-579789cceedb

...