Thanks Brian.
Parvez, please update if the json Brian suggested works for you. I'll study 
this further in the meantime.

Brian, did you mean the root cause for this is SDNC-119 ?

Thanks,
Ofir

From: FREEMAN, BRIAN D
Sent: Thursday, October 12, 2017 5:35 PM
To: Parvez Basha Shaik <parvezbasha.sh...@amdocs.com>; 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: Eliyahu Noach <eliyahu.no...@amdocs.com>; GORENSHTEIN, STELLA 
<stel...@amdocs.com>; Netaji Surve <netaji.su...@amdocs.com>; Manoj Kapre 
<mano...@amdocs.com>
Subject: RE: BLOCKER - VID-82


The problem was the preload API changed from 1.0.

Try this as an example.

SDNC is working on a bug that is blocking : SDNC-119 but this payload passes 
validation against the Amsterdam yang model.


Brian



{

  "input":

  {

    "request-information":

    {

      "notification-url":"openecomp.org",

      "order-number":"1",

      "order-version":"1",

      "request-action":"PreloadVNFRequest",

      "request-id": "robot20"

    },

    "sdnc-request-header":

    {

      "svc-action": "reserve",

      "svc-notification-url": 
"http://openecomp.org:8080/adapters/rest/SDNCNotify";,

      "svc-request-id":"robot20"

    },

    "vnf-topology-information":

    {

      "vnf-assignments":

      {

        "availability-zones":[],

        "vnf-networks":[],

        "vnf-vms":[]

      },

      "vnf-parameters":

      [

        {"vnf-parameter-name":"public_net_id","vnf-parameter-value": 
"4d51376d-5c5a-4789-9253-b0740e815341"},

        {"vnf-parameter-name":"key_name","vnf-parameter-value":"ss"}

      ],

      "vnf-topology-identifier":

      {



                             "generic-vnf-name": "TESTPZ",

                             "generic-vnf-type": "devops1/devops1 0",

                             "vnf-name": "TESTPZ",

                             "vnf-type": "devops1..server..module-0",

                             "service-type": 
"8308f3c8-8d40-4d17-887a-9c9205569267"

      }

    }

  }

}


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Parvez Basha Shaik
Sent: Thursday, October 12, 2017 9:57 AM
To: SONSINO, OFIR <os0...@intl.att.com<mailto:os0...@intl.att.com>>; HEMLI, 
AMICHAI <ah0...@intl.att.com<mailto:ah0...@intl.att.com>>; onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; Yunxia Chen 
<helen.c...@huawei.com<mailto:helen.c...@huawei.com>>; Yang Xu (Yang, Fixed 
Network) <yang....@huawei.com<mailto:yang....@huawei.com>>
Cc: Eliyahu Noach <eliyahu.no...@amdocs.com<mailto:eliyahu.no...@amdocs.com>>; 
GORENSHTEIN, STELLA <stel...@amdocs.com<mailto:stel...@amdocs.com>>; Netaji 
Surve <netaji.su...@amdocs.com<mailto:netaji.su...@amdocs.com>>; Manoj Kapre 
<mano...@amdocs.com<mailto:mano...@amdocs.com>>
Subject: Re: [onap-discuss] BLOCKER - VID-82

Hi All,

Gentle reminder. If anyone from VID team needs to be added, please add them it 
will be of great help.

Thanks,
Parvez

From: Parvez Basha Shaik
Sent: Wednesday, October 11, 2017 8:36 PM
To: Sonsino, Ofir <os0...@intl.att.com<mailto:os0...@intl.att.com>>; Hemli, 
Amichai <ah0...@intl.att.com<mailto:ah0...@intl.att.com>>; onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; 'Yunxia 
Chen' <helen.c...@huawei.com<mailto:helen.c...@huawei.com>>; 'Yang Xu (Yang, 
Fixed Network)' <yang....@huawei.com<mailto:yang....@huawei.com>>
Cc: Tomer Oster <tomer.os...@amdocs.com<mailto:tomer.os...@amdocs.com>>; 
Michael O'Brien <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>; 
Netaji Surve <netaji.su...@amdocs.com<mailto:netaji.su...@amdocs.com>>; Manoj 
Kapre <mano...@amdocs.com<mailto:mano...@amdocs.com>>
Subject: 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=orfsxpZSKtLrsrS3P2OSmO05Hspc_hoCf2Z-gu4Fsa4&s=eYJ_eOqBzUW8finUjYSq9Nedr4h3pgEtjqMaVYhcLYM&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=orfsxpZSKtLrsrS3P2OSmO05Hspc_hoCf2Z-gu4Fsa4&s=LFBo4k3UCmba4pyjAHBUw3DbELOnanZz5SPGGpa2Ig4&e=>
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to