If you use the apidoc/explorer/index.html and navigate to the particular operation you can click on the model schema and get an example input to the RPC.
Many of these parametes are optional so I think we just need to remove sectiosn of the 1.0 preloads that don’t match the 1.1 api . I’m debugging a problem in my environment but hope to get a valid preload for your example soon. Brian post<http://wn-sdnc:8282/apidoc/explorer/index.html#%21/VNF-API%282015-07-20%29/preload_vnf_topology_operation_post_466> /operations/VNF-API:preload-vnf-topology-operation<http://wn-sdnc:8282/apidoc/explorer/index.html#%21/VNF-API%282015-07-20%29/preload_vnf_topology_operation_post_466> { "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: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" }, "VNF-API:vnf-topology-information": { "VNF-API:vnf-topology-identifier": { "VNF-API:generic-vnf-name": "Some generic-vnf-name", "VNF-API:service-type": "Some service-type", "VNF-API:service-id": "Some service-id", "VNF-API:vnf-name": "Some vnf-name", "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:vnf-parameters": [ { "VNF-API:vnf-parameter-name": "Some vnf-parameter-name", "VNF-API:vnf-parameter-value": "Some vnf-parameter-value" } ], "VNF-API:vnf-assignments": { "VNF-API:vnf-status": "Some vnf-status", "VNF-API:vnf-vms": [ { "VNF-API:vm-type": "Some vm-type", "VNF-API:vm-names": [ { "VNF-API:vm-name": "Some vm-name" } ], "VNF-API:vm-networks": [ { "VNF-API:use-dhcp": "Y", "VNF-API:floating-ip-v6": "DabF:%LpN", "VNF-API:network-role": "Some network-role", "VNF-API:network-macs": [ { "VNF-API:mac-address": "Some mac-address" } ], "VNF-API:floating-ip": "52.9.0.9%{LpL", "VNF-API:network-ips": [ { "VNF-API:ip-address": "2.8.0.75%Lpp{" } ], "VNF-API:network-ips-v6": [ { "VNF-API:ip-address-ipv6": ":%{L}LL}" } ], "VNF-API:interface-route-prefixes": [ { "VNF-API:interface-route-prefix": "1.6.0.0%N", "VNF-API:interface-route-prefix-cidr": "Some interface-route-prefix-cidr" } ], "VNF-API:ip-count": "0" } ], "VNF-API:vm-count": "0" } ], "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:sriov-vlan-filter-list": [ { "VNF-API:sriov-vlan-filter": "Some sriov-vlan-filter" } ] } ], "VNF-API:availability-zones": [ { "VNF-API:availability-zone": "Some availability-zone" } ] } } } } From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Parvez Basha Shaik Sent: Wednesday, October 11, 2017 11:06 AM To: SONSINO, OFIR <os0...@intl.att.com>; HEMLI, AMICHAI <ah0...@intl.att.com>; onap-discuss <onap-discuss@lists.onap.org>; Yunxia Chen <helen.c...@huawei.com>; Yang Xu (Yang, Fixed Network) <yang....@huawei.com> Cc: Manoj Kapre <mano...@amdocs.com>; Netaji Surve <netaji.su...@amdocs.com> Subject: [onap-discuss] BLOCKER - VID-82 Importance: High Hi All, 1. This is about VID-82<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_VID-2D82&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=KdsUpEUIo85Q7T_O4NkPH2yiWnLu98B0q3rPGhyyf34&s=jUc-il_4T2lScjhSjpoEjc84zi5mgO8t992Zrz1O2Qo&e=> We are trying to create vFW stack. During the process, we are in the need of a valid Supplementary file/SDNC pre-load data to upload and create VF module. We had 1.0 preload file but we don’t have file compatible with 1.1. So, we used the same file to process the request. And below is the error response we’ve got on VID UI. 10/11/17 15:18:39 HTTP Status: Bad Request (400) { "serviceException": { "messageId": "SVC0002", "text": "Mapping of request to JSON object failed. Can not deserialize instance of java.util.ArrayList out of START_OBJECT token\n at [Source: java.io.StringReader@698a8dec<mailto:java.io.StringReader@698a8dec>; line: 1, column: 469] (through reference chain: org.openecomp.mso.apihandlerinfra.serviceinstancebeans.ServiceInstancesRequest[\"requestDetails\"]>org.openecomp.mso.apihandlerinfra.serviceinstancebeans.RequestParameters[\"userParams\"])" } } Can you please provide us the valid JSON file for SDNC pre-load. For now, we are using attached JSON files as supplementary files which are failing. Thanks, Parvez Ph: +91 9985300392 This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=KdsUpEUIo85Q7T_O4NkPH2yiWnLu98B0q3rPGhyyf34&s=9qJxmMZ6M_Nm5aqbfVkQFIvZjvzgPdD8QBv_haY31NI&e=>
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
