Page History

...

<sdncadapterworkflow:SDNCAdapterWorkflowRequest xmlns:ns5="http://org.openecomp/mso/request/types/v1"
                                                                                                        xmlns:sdncadapterworkflow="http://org.openecomp/mso/workflow/schema/v1"
                                                                                                        xmlns:sdncadapter="http://org.openecomp/workflow/sdnc/adapter/schema/v1">
                                   <sdncadapter:RequestHeader>
                                                        <sdncadapter:RequestId>de7133cc-4ef1-4266-9cde-67d6c54d0561</sdncadapter:RequestId>
                                                        <sdncadapter:SvcInstanceId>1989b6bb-520c-4eb0-a7c2-5cc5b288d7c5</sdncadapter:SvcInstanceId>
                                                        <sdncadapter:SvcAction>assign</sdncadapter:SvcAction>
                                                        <sdncadapter:SvcOperation>service-topology-operation</sdncadapter:SvcOperation>
                                                        <sdncadapter:CallbackUrl>http://mso:8080/mso/SDNCAdapterCallbackService</sdncadapter:CallbackUrl>
                                                        <sdncadapter:MsoAction></sdncadapter:MsoAction>
                                        </sdncadapter:RequestHeader>
                                <sdncadapterworkflow:SDNCRequestData>
                                        <request-information>
                                                <request-id>dfac8680-d329-4beb-bd89-acb94da8098e</request-id>
                                                <source>MSO</source>
                                                <notification-url/>
                                                <order-number/>
                                                <order-version/>
                                                <request-action>CreateServiceInstance</request-action>
                                        </request-information>
                                        <service-information>
                                                <service-id>a9a77d5a-123e-4ca2-9eb9-0b015d2ee0fb</service-id>
                                                <subscription-service-type>123456789</subscription-service-type>
                                                <ecomp-model-information>
                                                 <model-invariant-uuid>1963dd8b-9375-4cab-aa59-0ee06e8333fa</model-invariant-uuid>
                                                 <model-uuid>d8784dc7-4ec8-4609-87bb-5e5bfc183613</model-uuid>
                                                 <model-version>1.0</model-version>
                                                 <model-name>vCpeResCust</model-name>
                                            </ecomp-model-information>
                                                <service-instance-id>1989b6bb-520c-4eb0-a7c2-5cc5b288d7c5</service-instance-id>
                                                <subscriber-name/>
                                                <global-customer-id>SDN-ETHERNET-INTERNET</global-customer-id>
                                        </service-information>
                                        <service-request-input>
                                                <service-instance-name>vcperescust-102404</service-instance-name>
                                                <service-input-parameters>      <param>
                                                        <name>BRG_WAN_MAC_Address</name>
                                                        <value>brgmac</value>
                                                        </param>
                                                        </service-input-parameters>
                                        </service-request-input>
                                </sdncadapterworkflow:SDNCRequestData>
                                </sdncadapterworkflow:SDNCAdapterWorkflowRequest>

10/28/2017

1. vCpeResCust custom workflow: 
   1. Identified configuration mistake in mso.bpmn.urn.properties: both hostname and url path needs to be corrected to provide correct callback url to SNIRO. The updated file is here: mso.bpmn.urn.properties
   2. Identified a bug. When SO service level flow requests SDNC for service instance assignment, the request does not have correct format and got rejected. Dan provides a sample and Yang model in 

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

      . A new ticket is created.
2. Passed: Get and decompose service template from catalog.

10/27/2017

1. vCpeResCust custom workflow: 

   1. Passed: Get and decompose service template from catalog.

   2. Passed: Query SNIRO emulator to get homing information. The current config files for SO after manual changes are:  mso.bpmn.urn.properties, mso-docker.json. They are supposed to be updated by SO so that no more manual changes are needed in the future. The callback URL provided by SO is incorrect, needs to be fixed (

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

      ). SNIRO emulator needs to be modified to use the callback URL from SO request (

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

      ). Currently we use the following hacking to send the required info to SO.

      Code Block
      title Manually send SNIRO results to SO collapse true
      curl -i -X POST -d @sniro.json -H Content-Type=application/json --user 'MSOClient:password1$' http://so:8080/workflows/messages/message/SNIROResponse/c39fe43a-8f31-4d70-957d-b1c11e161636 sniro.json is preloaded into SNIRO emulator and will be used to feed SO request. { "solutionInfo" : { "placement" : [ { "serviceResourceId" : "61d563e8-e714-4393-8f99-cc480144a05e", "resourceModuleName" : "TunnelXConn", "serviceInstanceId" : "GMuxInfra-UUID", "cloudRegionId" : "RegionOne", "inventoryType" : "service" }, { "resourceModuleName" : "vG", "serviceResourceId" : "91d563e8-e714-4393-8f99-cc480144a05e", "cloudRegionId" : "RegionOne", "serviceInstanceId" : "vG-service-instance-id", "inventoryType" : "cloud" }, { "inventoryType" : "service", "serviceInstanceId" : "BRG_EMU_UUID", "cloudRegionId" : "RegionOne", "resourceModuleName" : "BRG", "serviceResourceId" : "71d563e8-e714-4393-8f99-cc480144a05e" } ] }, "requestId" : "111-111-1111", "statusMessage" : "", "transactionId" : "111-111-1111", "requestState" : "complete" }

   3. Passed: SO queries AAI to get service and other info include globalCustomerID. We preload AAI with the following info. Note that the ASDC_TOSCA_UUID part is questionable. It seems not necessary. 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-279

      .

      Code Block
      title Preload AAI for vCpeResCust flow collapse true
      PUT /aai/v11 /business/customers/customer/SDN-ETHERNET-INTERNET { "global-customer-id": "SDN-ETHERNET-INTERNET", "subscriber-name": "SDN-ETHERNET-INTERNET", "subscriber-type": "INFRA", "service-subscriptions": { "service-subscription": [ { "service-type": "123456789", "service-instances": { "service-instance": [ { "service-instance-id": "fbe9ad27-7ddd-49a6-ab2f-8c08e31fe12c", "service-instance-name": "fbe9ad27-7ddd-49a6-ab2f-8c08e31fe12c", "service-type": "vcpe" } ] } } ] } } After the sdc models were loaded, I added this model into AAI: PUT /aai/v11 /service-design-and-creation/models/model/1963dd8b-9375-4cab-aa59-0ee06e8333fa/model-vers/model-ver/ASDC_TOSCA_UUID { "model-version-id": "ASDC_TOSCA_UUID", "model-name": "vCpeResCust", "model-version": "1.0", "model-description": "Some ASDC Tosca Model" }

   4. Passed: SO creates a service instance UUID and  put it in AAI. 
   5. Blocked: SO calls SDNC assign service (type=vCpeResCust, UUID), see 

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

      .
2. General Infrastructure
   
   1. Brian has successfully instantiated general infrastructure, hahahaha~~~~~~~~~~
3. Notes for upcoming test

   1. SO allows only one workflow to executive at a time. To clear the current one: 

      Code Block
      delete from mso_requests.infra_active_requests;

   2. To manually send event to DMaaP to invoke SDNC to create BRG record in AAI (this emulates the event from DHCP), do the following

      Code Block
      http://{{mr}}:3904/events/VCPE-DHCP-EVENT/group1/C1?timeout=5000 [ "{\"msg_name\":\"DHCPACK\",\"macaddr\":\"e2:91:8c:7a:1e:9d\",\"yiaddr\":\"10.3.0.2\"}" ]

...