The "###" fields are missing from the MSO messae to SDNC.
{
"VNF-API:input": {
"VNF-API:request-information": {
"VNF-API:request-id": "Some request-id",
"VNF-API:notification-url": "Some notification-url",
###"VNF-API:ORDER-NUMBER": "SOME ORDER-NUMBER",
###"VNF-API:request-sub-action": "SUPP",
"VNF-API:request-action": "PreloadNetworkRequest",
"VNF-API:source": "Some source",
###"VNF-API:order-version": "Some order-version"
},
"VNF-API:service-information": {
"VNF-API:service-type": "Some service-type",
"VNF-API:service-id": "Some service-id",
"VNF-API:service-instance-id": "Some service-instance-id",
"VNF-API:subscriber-name": "Some subscriber-name"
},
"VNF-API:vnf-request-information": {
"VNF-API:use-preload": "Y",
"VNF-API:vnf-name": "Some vnf-name",
### "VNF-API:vnf-networks": [
{
"VNF-API:network-role": "Some network-role",
"VNF-API:subnet-name": "Some subnet-name",
"VNF-API:ipv6-subnet-id": "Some ipv6-subnet-id",
"VNF-API:contrail-network-fqdn": "Some contrail-network-fqdn",
"VNF-API:ipv6-subnet-name": "Some ipv6-subnet-name",
"VNF-API:neutron-id": "Some neutron-id",
"VNF-API:subnet-id": "Some subnet-id",
"VNF-API:network-id": "Some network-id",
"VNF-API:network-name": "Some network-name"
}
],
"VNF-API:aic-cloud-region": "Some aic-cloud-region",
"VNF-API:vnf-id": "Some vnf-id",
###"VNF-API:aic-clli": "Some aic-clli",
###"VNF-API:model-customization-uuid": "Some model-customization-uuid",
"VNF-API:generic-vnf-name": "Some generic-vnf-name",
###"VNF-API:vnf-request-version": "Some vnf-request-version",
"VNF-API:tenant": "Some tenant",
"VNF-API:vnf-type": "Some vnf-type",
"VNF-API:generic-vnf-id": "Some generic-vnf-id",
"VNF-API:generic-vnf-type": "Some generic-vnf-type"
},
"VNF-API:sdnc-request-header": {
###"VNF-API:svc-action": "reserve",
###"VNF-API:svc-notification-url": "Some svc-notification-url",
###"VNF-API:svc-request-id": "Some svc-request-id"
}
}
}
Also why is this not valid inptu to SDNC
<input>
<service-information>
<service-id>null</service-id>
<service-type>null</service-type>
<service-instance-id>79d015d1-29b5-434b-b5f5-d250a94d0204</service-instance-id>
<subscriber-name>notsurewecare</subscriber-name>
</service-information>
<request-information>
<request-id>6c6c03fd-0105-41af-adb2-01f2b71af208</request-id>
<request-action>VNFActivateRequest</request-action>
<source>VID</source>
<notification-url/>
<ORDER-NUMBER>00001</ORDER-NUMBER>
<request-sub-action>SUPP</request-sub-action>
<order-version>1.0</order-version>
</request-information>
<vnf-request-information>
<vnf-id>c3ca773d-999e-4855-a9fc-870eca756b02</vnf-id>
<vnf-type>2fe18e0c7a574409A761..base_vfw..module-0</vnf-type>
<vnf-name>demoVFWTEST06</vnf-name>
<generic-vnf-id>f8385ffe-3ce2-41cc-be95-87b06951e289</generic-vnf-id>
<generic-vnf-name>demoVFWTEST01</generic-vnf-name>
<generic-vnf-type>demoVFW/2fe18e0c-7a57-4409-a761 0</generic-vnf-type>
<aic-cloud-region>RegionOne</aic-cloud-region>
<tenant>466979b815b5415ba14ada713e6e1846</tenant>
<use-preload>Y</use-preload>
</vnf-request-information>
<sdnc-request-header>
<svc-action>assign</svc-action>
<svc-notification>som url</svc-notification>
<svc-request-id>0001</svc-request-id>
</sdnc-request-header>
</input>
-----Original Appointment-----
From: Yunxia Chen [mailto:[email protected]]
Sent: Monday, October 16, 2017 11:24 PM
To: Yunxia Chen; onap-discuss; Seshu m; DAUGHERTY, ROBERT E; FORSYTH, JAMES;
KAJUR, HARISH V
Subject: [onap-discuss] [integration][aai][so]VNF Instantiation for vFW / vDNS
When: Tuesday, October 17, 2017 8:00 AM-9:30 AM (UTC-08:00) Pacific Time (US &
Canada).
Where: https://zoom.us/j/4466668888
When: Tuesday, October 17, 2017 8:00 AM-9:30 AM. (UTC-08:00) Pacific Time (US &
Canada)
Where:
https://zoom.us/j/4466668888<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_4466668888&d=DwMFoQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=ncm7YoPo1Oe_Pz5OPz9GFPt2_5-LNdhoQBuK3Tlr3oE&s=q__4TrPOzOxEH3c1pA9JkVRWdSpXJtL1IpnB2VAlZ1c&e=>
*~*~*~*~*~*~*~*~*~*
Let's continue for the VNF Instantiation testing. And hope that SO issue has
been fixed at that time.
Helen Chen
<< File: ATT00001.txt >>
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
