...
| Code Block |
|---|
<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/
...
31/2017
- vCpeResCust custom workflow:
- In SDNC ueb listener docker container, /opt/onap/sdnc/data/properties/ueb-listener.properties does not have the correct sdc address, fixed. But the user name and password to authenticate with SDC are incorrect. So it's not able to get service model distributed from SDC. This is blocking us.
10/30/2017
- vCpeResCust custom workflow:
- 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
- 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
. A new ticket is created.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
.Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SO-289
- Eric and team have the following update on VNFs:
- There should be vnf snapshot images in the Integration environment now. Note, that the vbng image Brian made today needs to be replaced with one Matt is in process of building.
- Per Kang’s question below, the last line of each vnf yaml file runs an install script – this is what sets up the interface addresses, per the env file. The snapshot images skip over need for time consuming compilation of the vpp/honeycomb code.
- We have tested manually configuring vxlan tunnels, etc. in the VCPE project and verified that the data path is working.
- we would like to remove and rebuild the vnfs in the vcpe project tomorrow morning.
- one item we’re in process of testing is control plane connectivity from sdnc to the vbrg
- A couple areas where there may be some unkowns that could come up during integration:
- interaction with the onap vdhcp vnf (different than what was tested in our local lab)
- interaction with the aaa vnf (did not have this in our local lab setup)
...