Per Scale Out testing:

 

From: "JAMKHEDKAR, PRAMOD A (PRAMOD A)" <pramod@research.att.com>
Date: Thursday, June 13, 2019 at 7:21 PM
To: "PLATANIA, MARCO (MARCO)" <platania@research.att.com>, "HERNANDEZ-HERRERO, JORGE" <jh1730@att.com>, "VENKATESH KUMAR, VIJAY" <vv770d@att.com>, "DRAGOSH, PAMELA L (PAM)" <pdragosh@research.att.com>, "DETERME, SEBASTIEN" <sebastien.determe@intl.att.com>, "NGUEKO, GERVAIS-MARTIAL" <gervais-martial.ngueko@intl.att.com>, "BLANDFORD, SCOTT" <cb1694@att.com>, "MALAKOV, YURIY" <ym9479@att.com>, "HAHN III, JIM" <jh7358@att.com>
Cc: BRIAN FREEMAN <bf1936@att.com>
Subject: Re: CL for scale out

 

Hi Marco,

I have a resolution for all the three issues you mentioned here:

 

1. Missing “ModelType”: This part of the code is developed by TechMahindra. They don’t set this parameter. I can make that change if it is okay.
2. Regarding null value for modelCustomizationName: The value is null because that’s what is returned from A&AI. See below. The code puts the string that is after the “/”. This is in line with what was done previously (during named queries). I just used the same code.
3. Regarding incorrect version: This happened because of a typo from my side. I used ServiceInstance instead of VNF in the code.

 

Once you help with Point 2 (It is just doing what it was supposed to right now), and if Pam is okay with me changing the code written by TechMahindra, I can make these changes and push the code.

Thanks,

Pramod

 

"generic-vnf":

{                 "vnf-id": "9d33cf2d-d6aa-4b9e-a311-460a6be5a7de",                 "vnf-name": "RegionOne_ONAP-NF_20190613T023006695Z",                 "vnf-type": "vDNSLoadBalancerService_CDS/null",                 "service-id": "a9a77d5a-123e-4ca2-9eb9-0b015d2ee0fb",                 "prov-status": "ACTIVE",                 "operational-status": "out-of-service-path",                 "orchestration-status": "Active",                 "ipv4-oam-address": "10.0.101.62",                 "in-maint": false,                 "is-closed-loop-disabled": false,                 "resource-version": "1560426586432",                 "model-invariant-id": "7cc46834-962b-463a-93b8-8c88d45c4fb1",                 "model-version-id": "94cb4ca9-7084-4236-869f-9ba114245e41",                 "model-customization-id": "69a4ebc7-0200-435b-930a-3cb247d7a3fd",                 "nf-type": "LOADBALANCER",                 "nf-function": "vlb",                 "nf-role": "vLB",                 "nf-naming-code": "ONAP-LOADBALANCER",                 "selflink": "restconf/config/GENERIC-RESOURCE-API:services/service/7d3ca782-c486-44b3-9fe5-39f322d8ee80/service-data/vnfs/vnf/9d33cf2d-d6aa-4b9e-a311-460a6be5a7de/vnf-data/vnf-topology/",             }

 

From: "PLATANIA, MARCO (MARCO)" <platania@research.att.com>
Date: Thursday, June 13, 2019 at 6:30 PM
To: "HERNANDEZ-HERRERO, JORGE" <jh1730@att.com>, "VENKATESH KUMAR, VIJAY" <vv770d@att.com>, PAMELA DRAGOSH <pdragosh@research.att.com>, "DETERME, SEBASTIEN" <sebastien.determe@intl.att.com>, "NGUEKO, GERVAIS-MARTIAL" <gervais-martial.ngueko@intl.att.com>, "BLANDFORD, SCOTT" <cb1694@att.com>, "MALAKOV, YURIY" <ym9479@att.com>, "JAMKHEDKAR, PRAMOD A (PRAMOD A)" <pramod@research.att.com>, "HAHN III, JIM" <jh7358@att.com>
Cc: "FREEMAN, BRIAN D" <bf1936@att.com>
Subject: Re: CL for scale out

 

Jorge,

 

SO is rejecting the input from Policy because there’s a missing parameter in the JSON object. In the VF module section, Policy doesn’t include the modelType. Please compare the 2 attachments, one from policy and one from Postman.

 

From Postman:

{

    "requestDetails": {

        "modelInfo":

{             "modelCustomizationName": "VdnsloadbalancerCds..vdns..module-3",             "modelCustomizationId": "ec2f6466-a786-41f9-98f3-86506ceb57aa",             "modelInvariantId": "8e134fbd-d6fe-4b0a-b4da-286c69dfed2f",            "modelVersionId": "297c4829-a412-4db2-bcf4-8f8ab8890772",             "modelName": "VdnsloadbalancerCds..vdns..module-3",             "modelType": "vfModule",             "modelVersion": "1"         }

,

 

From Policy:

{

   "requestDetails":{

      "modelInfo":

{          "modelInvariantId":"8e134fbd-d6fe-4b0a-b4da-286c69dfed2f",          "modelVersionId":"297c4829-a412-4db2-bcf4-8f8ab8890772",          "modelName":"VdnsloadbalancerCds..vdns..module-3",          "modelVersion":"1",          "modelCustomizationId":"ec2f6466-a786-41f9-98f3-86506ceb57aa"       }

,

 

As you can see, the modelType in the VF module section is missing. Another thing that seems wrong is "modelCustomizationName":"null", in the relatedInstanceList for "modelType":"vnf". The modelCustomizationName cannot be null. If it’s not in the object returned by AAI (as I suppose), you can assume that modelCustomizationName = modelName.

 

One last thing: still in the same section (relatedInstanceList for "modelType":"vnf") there’s "modelVersion":"2.0" while in reality the correct modelVersion under that model invariant ID is 3.0, according to the AAI custom query.

 

 

            "model": {

                "model-invariant-id": "7cc46834-962b-463a-93b8-8c88d45c4fb1",

                "model-type": "resource",

                "resource-version": "1560250852852",

                "model-vers": {

                    "model-ver": [

                        {

                            "model-version-id": "94cb4ca9-7084-4236-869f-9ba114245e41",

                            "model-name": "vDNSLOADBALANCER_CDS",

                            "model-version": "3.0",

 

Marco