Date   

Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC #appc

Marco Platania
 

Alexis,

 

I remember I had to make a few manual changes to work with OpenStack actions. I’m copying parts of an email that I sent to APPC Team a few months ago. This was tested with Casablanca.

 

“I was able to run Start/Stop VM using the APPC LCM APIs. The main issue is that, if we want to use APPC LCM APIs against VMs, we must add a VNFC element in AAI and relate it to a vServer. Sort of a pain, I need to see how this can be done with heatbridge.” à this is available now, remember to run heatbridge

 

“That step wasn’t enough though. I dug the APPC DGs, code and debug logs, and saw that queries against PROTOCOL_REFERENCE table were returning empty results. I might have messed up a little bit because I was trying multiple things, including deleting rows from PROTOCOL_REFERENCE and start over, but I guess that CDT sometimes doesn’t push records correctly to that table. It seems that the first time you set a VNF with CDT, PROTOCOL_REFERENCE is updated correctly, but if you try to update an existing VNF, PROTOCOL_REFERENCE doesn’t always get updated as expected. I saw this in the past for another test, not sure if you encountered this problem in your local deployments.”

 

“On a side note, CDT doesn’t allow to specify VNFCs and VMs when setting up VNFs that use OpenStack actions. I had to select “ConfigModify” to set up VNFC and VM info, then I switched to “OpenStack Actions” and APPC seemed to remember VNFC and VM info. I’m not sure whether this is really necessary though, my guess is that VNFC and VM info can be obtained from AAI, so I don’t need to do anything in CDT. I was following the documentation in read the docs, which is a little outdated, perhaps this is no longer required in Casablanca.”  à not sure this is needed, it may have been myself playing too much

 

Note the xml file attached. I think I had to use the nf-type in AAI instead of VM or VNF.

 

Marco

 

From: Alexis de Talhouët <adetalhouet89@...>
Date: Thursday, May 16, 2019 at 11:16 AM
To: onap-discuss <onap-discuss@...>, Alexis de Talhouët <adetalhouet89@...>

Cc: "PLATANIA, MARCO (MARCO)" <platania@...>, BRIAN FREEMAN <bf1936@...>, "alphonse.steve.siani.djissitchi@..." <alphonse.steve.siani.djissitchi@...>, "CHO, TAKAMUNE" <tc012c@...>
Subject: Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

Also, I don’t know if it’s normal, but we had to add this in the sdnctl DB of appc to make it work.

 

MariaDB [sdnctl]> select * from VNF_DG_MAPPING;

+-------------------+---------+-------------+----------+-------------+----------+------------+-----------+

| VNF_DG_MAPPING_ID | ACTION  | API_VERSION | VNF_TYPE | VNF_VERSION | DG_NAME  | DG_VERSION | DG_MODULE |

+-------------------+---------+-------------+----------+-------------+----------+------------+-----------+

|                 1 | Stop    | 2.00        | vm       |             | VM_Stop  | 2.0.0      | APPC      |

|                 2 | Start   | 2.00        | vm       |             | VM_Start | 2.0.0      | APPC      |

|                 3 | Restart | 2.00        | vm       |             | RebootVM | 4.0.0      | APPC      |

+-------------------+---------+-------------+----------+-------------+----------+------------+-----------+



On May 16, 2019, at 11:14 AM, Alexis de Talhouet via Lists.Onap.Org <adetalhouet89=gmail.com@...> wrote:

 

 



On May 16, 2019, at 11:09 AM, PLATANIA, MARCO (MARCO) <platania@...> wrote:

 

Are you using CDT? What is your setup? 

 

 

Yes, setup as follow in the screenshot. The payload is the following, which seems similar as yours:

 

{

   "input": {

       "common-header": {

           "timestamp": "2019-05-16T14:47:55.449Z",

           "api-ver": "2.00",

           "originator-id": "appc",

           "request-id": "873aacdf-1d85-4e07-8deb-7815776bbd35",

           "flags": {

               "mode": "NORMAL",

               "force": "FALSE"

           }

       },

       "action": "Start",

       "action-identifiers": {

           "vnf-id": "VNF_demo_steve",

           "vserver-id": "c82153dc-8d84-4e69-9673-5e0a60030779"

       },

    }

}

 

 

<Screen Shot 2019-05-16 at 11.13.10 AM.png>

 


Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC #appc

Alexis de Talhouet
 

Also, I don’t know if it’s normal, but we had to add this in the sdnctl DB of appc to make it work.

MariaDB [sdnctl]> select * from VNF_DG_MAPPING;
+-------------------+---------+-------------+----------+-------------+----------+------------+-----------+
| VNF_DG_MAPPING_ID | ACTION  | API_VERSION | VNF_TYPE | VNF_VERSION | DG_NAME  | DG_VERSION | DG_MODULE |
+-------------------+---------+-------------+----------+-------------+----------+------------+-----------+
|                 1 | Stop    | 2.00        | vm       |             | VM_Stop  | 2.0.0      | APPC      |
|                 2 | Start   | 2.00        | vm       |             | VM_Start | 2.0.0      | APPC      |
|                 3 | Restart | 2.00        | vm       |             | RebootVM | 4.0.0      | APPC      |
+-------------------+---------+-------------+----------+-------------+----------+------------+-----------+

On May 16, 2019, at 11:14 AM, Alexis de Talhouet via Lists.Onap.Org <adetalhouet89=gmail.com@...> wrote:



On May 16, 2019, at 11:09 AM, PLATANIA, MARCO (MARCO) <platania@...> wrote:

Are you using CDT? What is your setup? 


Yes, setup as follow in the screenshot. The payload is the following, which seems similar as yours:

{
   "input": {
       "common-header": {
           "timestamp": "2019-05-16T14:47:55.449Z",
           "api-ver": "2.00",
           "originator-id": "appc",
           "request-id": "873aacdf-1d85-4e07-8deb-7815776bbd35",
           "flags": {
               "mode": "NORMAL",
               "force": "FALSE"
           }
       },
       "action": "Start",
       "action-identifiers": {
           "vnf-id": "VNF_demo_steve",
           "vserver-id": "c82153dc-8d84-4e69-9673-5e0a60030779"
       },
    }
}


<Screen Shot 2019-05-16 at 11.13.10 AM.png>


Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC #appc

Alexis de Talhouet
 



On May 16, 2019, at 11:09 AM, PLATANIA, MARCO (MARCO) <platania@...> wrote:

Are you using CDT? What is your setup? 


Yes, setup as follow in the screenshot. The payload is the following, which seems similar as yours:

{
   "input": {
       "common-header": {
           "timestamp": "2019-05-16T14:47:55.449Z",
           "api-ver": "2.00",
           "originator-id": "appc",
           "request-id": "873aacdf-1d85-4e07-8deb-7815776bbd35",
           "flags": {
               "mode": "NORMAL",
               "force": "FALSE"
           }
       },
       "action": "Start",
       "action-identifiers": {
           "vnf-id": "VNF_demo_steve",
           "vserver-id": "c82153dc-8d84-4e69-9673-5e0a60030779"
       },
    }
}



Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC #appc

Marco Platania
 

Alexis,

 

Are you using CDT? What is your setup? I ran this fine in the past from Postman:

 

{

  "input": {

    "common-header": {

      "timestamp": "{{serverDate}}",

      "api-ver": "2.05",

      "originator-id": "{{orginatorId}}",

      "request-id": "Postman",

      "sub-request-id": "Postman",

      "flags": {

        "mode": "NORMAL",

        "force": "TRUE",

        "ttl": 36000

      }

    },

    "action": "Restart",

    "action-identifiers": {

      "vnf-id": "{{vnf-id}}",

      "vserver-id":"{{vserver-id}}"

    },

    "payload": "{\"vm-id\":\"{{vm-id}}\"}"

  }

}

 

I have a pre-request script like this:

 

// Get the current DateTime

var moment = require('moment');

var date = new Date().toISOString();

var newdate = moment(date).subtract(80, 'minutes').toISOString();

var serverDate = moment(newdate).format('YYYY-MM-DDTHH:mm:ss.SS');

pm.globals.set("serverDate", serverDate+'Z');

 

//Get UUID

var uuid = require('uuid');

var orginatorId = uuid.v4();

pm.globals.set("orginatorId",orginatorId);

 

//Set IDs and payload values

pm.globals.set("vm-id","http://x.y.z.com:8774/v2/3f2aaef74ecb4b19b35e26d0849fe9a2/servers/e7f1db09-ff78-44fc-b256-69095c5556fb");

pm.globals.set("vserver-id","e7f1db09-ff78-44fc-b256-69095c5556fb");

pm.globals.set("vnf-id","17044ef4-e7f3-46a1-af03-e2aa562f23ac");

 

Marco

 

From: <onap-discuss@...> on behalf of Alexis de Talhouet <adetalhouet89@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "adetalhouet89@..." <adetalhouet89@...>
Date: Thursday, May 16, 2019 at 11:03 AM
To: BRIAN FREEMAN <bf1936@...>
Cc: onap-discuss <onap-discuss@...>, "alphonse.steve.siani.djissitchi@..." <alphonse.steve.siani.djissitchi@...>, "CHO, TAKAMUNE" <tc012c@...>
Subject: Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

Yes, agreed. Using Casablanca 3.0.1-ONAP version of APPC



On May 16, 2019, at 11:01 AM, FREEMAN, BRIAN D <bf1936@...> wrote:

 

Alexis,

 

Agree you shouldnt have to tweak the DG. Seems like the decoding before calling the DG isnt firing quite right for some reason in your Casablanca instance.

 

Brian

 

 

From: Alexis de Talhouët <adetalhouet89@...> 
Sent: Thursday, May 16, 2019 10:59 AM
To: FREEMAN, BRIAN D <bf1936@...>
Cc: onap-discuss <onap-discuss@...>; alphonse.steve.siani.djissitchi@...; CHO, TAKAMUNE <tc012c@...>
Subject: Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

Taka, I understand you ran testing, I would need to look into that. Also, note, I’m using Casablanca.

 

Attribute (input.common-header.api-ver), value (2.00)

Attribute (input.action-identifiers.service-instance-id), value ()

Attribute (input.action-identifiers.vserver-id), value (c82153dc-8d84-4e69-9673-5e0a60030779)

Attribute (input.common-header.sub-request-id), value ()

Attribute (input.common-header.request-id), value (873aacdf-1d85-4e07-8deb-7815776bbd35)

Attribute (input.common-header.timestamp), value (2019-05-16T14:00:43.177Z)

Attribute (currentGraph), value (SvcLogicGraph [module=APPC, rpc=VM_Start, mode=sync, version=2.0.0, md5sum=1cd3041dc9487e5abf527ee778af1bdc])

Attribute (input.action-identifiers.vnf-id), value (VNF_demo_steve)

Attribute (input.action-identifiers.vnfc-name), value ()

Attribute (input.action), value (Start)

Attribute (input.action-identifiers.vf-module-id), value ()

Attribute (input.common-header.originator-id), value (appc)

Attribute (isBwcMode), value (false)

 

 

It looks like `input.payload`, which is a JSON, isn’t converted to SLI ctx. `vm-id` that is looked for

 

2019-05-16 14:00:45,820 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.instance.url = (atom<CONTEXT_VAR> (variable-term vm-id)) resolves to

 

 isn’t within the context at all. I tweaked the DG to run a jsonStringToCtx using `input.payload` and then it worked. I also had to change vm-id to the output of jsonStringToCtx.vm-id…

 

But if there is a recipe I missed, I’d love to hear about it.

 

Thanks,

Alexis

 


Re: #appc Unable to execute stop lcm operation from APPC #appc

Taka Cho
 

No that is for Dublin release. 1.5.0-SNAPSHOT

 

Taka

 

From: Steve Siani <alphonse.steve.siani.djissitchi@...>
Sent: Thursday, May 16, 2019 11:07 AM
To: CHO, TAKAMUNE <tc012c@...>; onap-discuss@...
Subject: Re: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

Hi Taka,

These tests in APPC was it on Casablanca release?

Regards,
Steve


Re: #appc Unable to execute stop lcm operation from APPC #appc

Steve Siani
 

Hi Taka,

These tests in APPC was it on Casablanca release?

Regards,
Steve


Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC #appc

Alexis de Talhouet
 

Yes, agreed. Using Casablanca 3.0.1-ONAP version of APPC

On May 16, 2019, at 11:01 AM, FREEMAN, BRIAN D <bf1936@...> wrote:

Alexis,
 
Agree you shouldnt have to tweak the DG. Seems like the decoding before calling the DG isnt firing quite right for some reason in your Casablanca instance.
 
Brian
 
 
From: Alexis de Talhouët <adetalhouet89@...> 
Sent: Thursday, May 16, 2019 10:59 AM
To: FREEMAN, BRIAN D <bf1936@...>
Cc: onap-discuss <onap-discuss@...>; alphonse.steve.siani.djissitchi@...; CHO, TAKAMUNE <tc012c@...>
Subject: Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC
 
Taka, I understand you ran testing, I would need to look into that. Also, note, I’m using Casablanca.
 
Attribute (input.common-header.api-ver), value (2.00)
Attribute (input.action-identifiers.service-instance-id), value ()
Attribute (input.action-identifiers.vserver-id), value (c82153dc-8d84-4e69-9673-5e0a60030779)
Attribute (input.common-header.sub-request-id), value ()
Attribute (input.common-header.request-id), value (873aacdf-1d85-4e07-8deb-7815776bbd35)
Attribute (input.common-header.timestamp), value (2019-05-16T14:00:43.177Z)
Attribute (currentGraph), value (SvcLogicGraph [module=APPC, rpc=VM_Start, mode=sync, version=2.0.0, md5sum=1cd3041dc9487e5abf527ee778af1bdc])
Attribute (input.action-identifiers.vnf-id), value (VNF_demo_steve)
Attribute (input.action-identifiers.vnfc-name), value ()
Attribute (input.action), value (Start)
Attribute (input.action-identifiers.vf-module-id), value ()
Attribute (input.common-header.originator-id), value (appc)
Attribute (isBwcMode), value (false)
 
 
It looks like `input.payload`, which is a JSON, isn’t converted to SLI ctx. `vm-id` that is looked for
 
2019-05-16 14:00:45,820 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.instance.url = (atom<CONTEXT_VAR> (variable-term vm-id)) resolves to
 
 isn’t within the context at all. I tweaked the DG to run a jsonStringToCtx using `input.payload` and then it worked. I also had to change vm-id to the output of jsonStringToCtx.vm-id…
 
But if there is a recipe I missed, I’d love to hear about it.
 
Thanks,
Alexis


Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC #appc

Brian Freeman
 

Alexis,

 

Agree you shouldnt have to tweak the DG. Seems like the decoding before calling the DG isnt firing quite right for some reason in your Casablanca instance.

 

Brian

 

 

From: Alexis de Talhouët <adetalhouet89@...>
Sent: Thursday, May 16, 2019 10:59 AM
To: FREEMAN, BRIAN D <bf1936@...>
Cc: onap-discuss <onap-discuss@...>; alphonse.steve.siani.djissitchi@...; CHO, TAKAMUNE <tc012c@...>
Subject: Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

Taka, I understand you ran testing, I would need to look into that. Also, note, I’m using Casablanca.

 

Attribute (input.common-header.api-ver), value (2.00)

Attribute (input.action-identifiers.service-instance-id), value ()

Attribute (input.action-identifiers.vserver-id), value (c82153dc-8d84-4e69-9673-5e0a60030779)

Attribute (input.common-header.sub-request-id), value ()

Attribute (input.common-header.request-id), value (873aacdf-1d85-4e07-8deb-7815776bbd35)

Attribute (input.common-header.timestamp), value (2019-05-16T14:00:43.177Z)

Attribute (currentGraph), value (SvcLogicGraph [module=APPC, rpc=VM_Start, mode=sync, version=2.0.0, md5sum=1cd3041dc9487e5abf527ee778af1bdc])

Attribute (input.action-identifiers.vnf-id), value (VNF_demo_steve)

Attribute (input.action-identifiers.vnfc-name), value ()

Attribute (input.action), value (Start)

Attribute (input.action-identifiers.vf-module-id), value ()

Attribute (input.common-header.originator-id), value (appc)

Attribute (isBwcMode), value (false)

 

 

It looks like `input.payload`, which is a JSON, isn’t converted to SLI ctx. `vm-id` that is looked for

 

2019-05-16 14:00:45,820 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.instance.url = (atom<CONTEXT_VAR> (variable-term vm-id)) resolves to

 

 isn’t within the context at all. I tweaked the DG to run a jsonStringToCtx using `input.payload` and then it worked. I also had to change vm-id to the output of jsonStringToCtx.vm-id…

 

But if there is a recipe I missed, I’d love to hear about it.

 

Thanks,

Alexis


Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC #appc

Taka Cho
 

It sounds like indentity-url is required… need to check the “secret” code

 

Taka

 

From: FREEMAN, BRIAN D
Sent: Thursday, May 16, 2019 10:37 AM
To: Alexis de Talhouët <adetalhouet89@...>; onap-discuss <onap-discuss@...>
Cc: alphonse.steve.siani.djissitchi@...; CHO, TAKAMUNE <tc012c@...>
Subject: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

It looks like its the encoding that is not quite right.

 

 

2019-05-16 14:00:45,830 | INFO  | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0057I APPC IAAS Adapter start server requested

2019-05-16 14:00:45,831 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.instance.url" =""

2019-05-16 14:00:45,831 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.provider.name" ="OpenStack"

2019-05-16 14:00:45,832 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.identity.url" =""

 

Can you try “\\””  (double slash encoding) ?

 

Taka – what is the secret ?

 

Brian

 

 

 

{

    "input": {

        "common-header": {

            "timestamp": "2017-10-31T15:02:04.244Z",

            "api-ver": "2.05",

            "originator-id": "SDNGP",

            "request-id": "Stop_VM-vFirewall_demo_app",

            "sub-request-id": "Stop_VM-vFirewall_demo_app",

            "flags": {

                "mode": "NORMAL",

                "force": "TRUE",

                "ttl": 36000

            }

        },

        "action": "Start",

        "action-identifiers": {

            "vnf-id": "vFirewall_demo_app",

            "vserver-id": "5b06cf36-40a0-4bcb-bde9-849aa4702d67"

        },

        "payload": "{\"vm-id\":\"http://10.12.25.2:8774/v2.1/466979b815b5415ba14ada713e6e1846/servers/5b06cf36-40a0-4bcb-bde9-849aa4702d67\", \"identity-url\": \"http://10.12.25.2:5000/v3\",\"skip-hypervisor-check\":\"true\"}"

    }

}

 

 

 

 

 

From: Alexis de Talhouët <adetalhouet89@...>
Sent: Thursday, May 16, 2019 10:03 AM
To: onap-discuss <onap-discuss@...>; FREEMAN, BRIAN D <bf1936@...>
Cc: alphonse.steve.siani.djissitchi@...
Subject: Re: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

Brian, Team,

 

We are following this example. Here is our payload

 

{

   "input": {

       "common-header": {

           "timestamp": {{timestamp}},

           "api-ver": "2.00",

           "originator-id": "appc",

           "request-id": "873aacdf-1d85-4e07-8deb-7815776bbd35",

           "flags": {

               "mode": "NORMAL",

               "force": "FALSE"

           }

       },

       "action": "Start",

       "action-identifiers": {

           "vnf-id": "VNF_demo_steve",

           "vserver-id": "c82153dc-8d84-4e69-9673-5e0a60030779"

       },

   }

}

 

And here are the DG logs in APPC:

 

2019-05-16 14:00:45,818 | INFO  | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute graph SvcLogicGraph [module=APPC, rpc=VM_Start, mode=sync, version=2.0.0, md5sum=1cd3041dc9487e5abf527ee778af1bdc]

2019-05-16 14:00:45,818 | INFO  | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 1 (execute)

2019-05-16 14:00:45,819 | DEBUG | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Executing node 1

2019-05-16 14:00:45,819 | DEBUG | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Executing node executor for node type execute - org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor

2019-05-16 14:00:45,819 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | execute node encountered - looking for plugin org.onap.appc.adapter.iaas.ProviderAdapter

2019-05-16 14:00:45,820 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.instance.url = (atom<CONTEXT_VAR> (variable-term vm-id)) resolves to

2019-05-16 14:00:45,826 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.provider.name = (atom<STRING> OpenStack) resolves to OpenStack

2019-05-16 14:00:45,829 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.identity.url = (atom<CONTEXT_VAR> (variable-term identity-url)) resolves to

2019-05-16 14:00:45,830 | INFO  | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0057I APPC IAAS Adapter start server requested

2019-05-16 14:00:45,831 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.instance.url" =""

2019-05-16 14:00:45,831 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.provider.name" ="OpenStack"

2019-05-16 14:00:45,832 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.identity.url" =""

2019-05-16 14:00:45,836 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | Service Logic Context: Status (success), Attribute count (14)

Attribute (input.common-header.api-ver), value (2.00)

Attribute (input.action-identifiers.service-instance-id), value ()

Attribute (input.action-identifiers.vserver-id), value (c82153dc-8d84-4e69-9673-5e0a60030779)

Attribute (input.common-header.sub-request-id), value ()

Attribute (input.common-header.request-id), value (873aacdf-1d85-4e07-8deb-7815776bbd35)

Attribute (input.common-header.timestamp), value (2019-05-16T14:00:43.177Z)

Attribute (currentGraph), value (SvcLogicGraph [module=APPC, rpc=VM_Start, mode=sync, version=2.0.0, md5sum=1cd3041dc9487e5abf527ee778af1bdc])

Attribute (input.action-identifiers.vnf-id), value (VNF_demo_steve)

Attribute (input.action-identifiers.vnfc-name), value ()

Attribute (input.action), value (Start)

Attribute (input.action-identifiers.vf-module-id), value ()

Attribute (input.common-header.originator-id), value (appc)

Attribute (isBwcMode), value (false)

 

For some reason, it’s not picking up the vm-id that is passed within the request, through the payload.

 

Are we missing something?

 

 

 

On May 15, 2019, at 4:44 PM, Brian <bf1936@...> wrote:

 

 

Hoepfully your payload is matching one of these examples

 

 

Brian

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of FREEMAN, BRIAN D
Sent: Wednesday, May 15, 2019 4:37 PM
To: onap-discuss@...; alphonse.steve.siani.djissitchi@...
Subject: Re: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

I’m not an expert at APPC but it looks like the input doesnt have the $vm-id (or its variation) defined (not sure which version of the Stop DG you are running).

You need to find the input variable to your REST call that matches the variable in the DG.

 

 

Brian

 

 

appc-directed-graph/appc-dgraph/provider/src/main/resources/json/APPC/APPC_VM_Stop.json:        "xml": "<execute plugin='org.onap.appc.adapter.iaas.ProviderAdapter' method='stopServer'>\n<parameter name=\"org.onap.appc.provider.name\" value=\"OpenStack\"/>\n<parameter name=\"org.onap.appc.instance.url\" value=\"`$vm-id`\" />\n<parameter name=\"org.onap.appc.identity.url\" value=\"`$identity-url`\

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Steve Siani
Sent: Wednesday, May 15, 2019 4:01 PM
To: FREEMAN, BRIAN D <bf1936@...>; onap-discuss@...
Subject: Re: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

Hi Brian,

you where somehow right because I found that the svcLogic was not able to resolv SDNC DB URL. In OOM APPC, the namespace is added in the name of SDNC container. So the result was appc-host.NAMESPACE. I removed the NAMESPACE and my test can go one step ahead.

But I still have some issue. Below is the log.

2019-05-15T19:54:00,891 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 76 (call)

2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute graph SvcLogicGraph [module=APPC, rpc=StopVM_VM, mode=sync, version=2.0.0, md5sum=08a100251d4498556a8896c9eac11918]

2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 1 (switch)

2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 34 (block)

2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 35 (set)

2019-05-15T19:54:00,916 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 36 (switch)

2019-05-15T19:54:00,916 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 37 (set)

2019-05-15T19:54:00,925 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 39 (for)

2019-05-15T19:54:00,926 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 40 (switch)

2019-05-15T19:54:00,926 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 41 (execute)

2019-05-15T19:54:00,926 | INFO  | appc-dispatcher-5 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0056I APPC IAAS Adapter stop server requested

2019-05-15T19:54:00,927 | ERROR | appc-dispatcher-5 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0045E One or more properties for [stopServer] are missing, null, or empty.  They are:

'org.onap.appc.instance.url'

2019-05-15T19:54:00,927 | ERROR | appc-dispatcher-5 | StopServer                       | 503 - appc-iaas-adapter - 1.4.4 | APPC0112E Server APPC (id n/a) failed to stop during n/a phase, reason Check Parameters:APPC0045E One or more properties for [stopServer] are missing, null, or empty.  They are:

'org.onap.appc.instance.url'

2019-05-15T19:54:00,927 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 42 (switch)

2019-05-15T19:54:00,928 | INFO  | appc-dispatcher-5 | SvcLogicExprListener             | 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.3 | Outcome ("") not found, keys are { (CONTEXT_NOT_FOUND) (SUCCESS) (ERROR)}

2019-05-15T19:54:00,928 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 86 (block)

2019-05-15T19:54:00,930 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 87 (block)

2019-05-15T19:54:00,937 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 88 (record)

2019-05-15T19:54:00,938 | ERROR | appc-dispatcher-5 | message-log                      | 223 - org.onap.ccsdk.sli.core.sli-recording - 0.3.3 |

2019-05-15T19:54:00,938 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 89 (execute)

2019-05-15T19:54:00,938 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 90 (execute)

2019-05-15T19:54:00,939 | INFO  | appc-dispatcher-5 | EventSenderDmaapImpl             | 458 - appc-common-bundle - 1.4.4 | Posting Message [873aacdf-1d85-4e07-8deb-7815776bbd35 - {"eventHeader":{"eventTime":"Wed May 15 19:54:00 UTC 2019","apiVer":"2.00","eventId":"873aacdf-1d85-4e07-8deb-7815776bbd35"},"eventStatus":{"code":501,"reason":"Check Parameters:APPC0045E One or more properties for [stopServer] are missing, null, or empty.  They are:"}}]

2019-05-15T19:54:00,939 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 91 (set)

2019-05-15T19:54:00,940 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 92 (return)

Any idea please?

Thanks!

 

 


Re: APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC #appc

Alexis de Talhouet
 

Taka, I understand you ran testing, I would need to look into that. Also, note, I’m using Casablanca.

Attribute (input.common-header.api-ver), value (2.00)
Attribute (input.action-identifiers.service-instance-id), value ()
Attribute (input.action-identifiers.vserver-id), value (c82153dc-8d84-4e69-9673-5e0a60030779)
Attribute (input.common-header.sub-request-id), value ()
Attribute (input.common-header.request-id), value (873aacdf-1d85-4e07-8deb-7815776bbd35)
Attribute (input.common-header.timestamp), value (2019-05-16T14:00:43.177Z)
Attribute (currentGraph), value (SvcLogicGraph [module=APPC, rpc=VM_Start, mode=sync, version=2.0.0, md5sum=1cd3041dc9487e5abf527ee778af1bdc])
Attribute (input.action-identifiers.vnf-id), value (VNF_demo_steve)
Attribute (input.action-identifiers.vnfc-name), value ()
Attribute (input.action), value (Start)
Attribute (input.action-identifiers.vf-module-id), value ()
Attribute (input.common-header.originator-id), value (appc)
Attribute (isBwcMode), value (false)


It looks like `input.payload`, which is a JSON, isn’t converted to SLI ctx. `vm-id` that is looked for

2019-05-16 14:00:45,820 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.instance.url = (atom<CONTEXT_VAR> (variable-term vm-id)) resolves to

 isn’t within the context at all. I tweaked the DG to run a jsonStringToCtx using `input.payload` and then it worked. I also had to change vm-id to the output of jsonStringToCtx.vm-id…

But if there is a recipe I missed, I’d love to hear about it.

Thanks,
Alexis


[so] SO staging image versions out-of-date

Gary Wu
 

Hi Seshu and SO team,
 
It has come to our attention that even though SO has released version 1.4.1 of docker images, the dublin staging builds are continuing to build 1.4.1-STAGING-latest which is out-of-date; they should be 1.4.2-STAGING-latest going forward.  Can you please bump your staging docker image versions?
 
Thanks,
Gary
 
 


Re: #appc Unable to execute stop lcm operation from APPC #appc

Taka Cho
 

Sorry, folks. I have been focusing on the bugs fix these days…

 

Alexis,

 

We ran 72 hours performance testing for APPC that contains “start” lcm in Windriver labs APPC tenant. Here is the payload sample for start lcm

 

{

    "version": "2.01",

    "rpc-name": "start",

    "correlation-id": "${request_id}",

    "type": "request",

    "body": {

        "input": {

            "common-header": {

                "timestamp": "${__time(yyyy-MM-dd&apos;T&apos;hh:mm:ss.SSS)}Z",

                "api-ver": "2.05",

                "originator-id": "${request_id}",

                "request-id": "${request_id}",

                "sub-request-id": "1",

                "flags": {

                    "force": "TRUE",

                    "ttl": 60000

                }

            },

            "action": "Start",

            "action-identifiers": {

                "vnf-id": "${vnf_id}",

                "vserver-id": "${vm_id}"

            },

            "payload": "{\"vm-id\":\"http://10.12.25.2:8774/v2.1/cf142fb96ce24770946c0f7117c0aeb3/servers/c0d9b8c7-9534-4a22-b464-d6aa2c930847\", \"identity-url\": \"http://10.12.25.2:5000/v2.0\",\"skip-hypervisor-check\":\"true\"}"

        }

    }

}

 

We used k8s-master oom env in APPC tenant for 72 hours performance testing. https://wiki.onap.org/display/DW/APPC+WindRiver+Lab

 

Hope that helps….

 

Taka

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Alexis de Talhouet
Sent: Thursday, May 16, 2019 10:03 AM
To: onap-discuss <onap-discuss@...>; FREEMAN, BRIAN D <bf1936@...>
Cc: alphonse.steve.siani.djissitchi@...
Subject: Re: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

Brian, Team,

 

We are following this example. Here is our payload

 

{

   "input": {

       "common-header": {

           "timestamp": {{timestamp}},

           "api-ver": "2.00",

           "originator-id": "appc",

           "request-id": "873aacdf-1d85-4e07-8deb-7815776bbd35",

           "flags": {

               "mode": "NORMAL",

               "force": "FALSE"

           }

       },

       "action": "Start",

       "action-identifiers": {

           "vnf-id": "VNF_demo_steve",

           "vserver-id": "c82153dc-8d84-4e69-9673-5e0a60030779"

       },

   }

}

 

And here are the DG logs in APPC:

 

2019-05-16 14:00:45,818 | INFO  | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute graph SvcLogicGraph [module=APPC, rpc=VM_Start, mode=sync, version=2.0.0, md5sum=1cd3041dc9487e5abf527ee778af1bdc]

2019-05-16 14:00:45,818 | INFO  | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 1 (execute)

2019-05-16 14:00:45,819 | DEBUG | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Executing node 1

2019-05-16 14:00:45,819 | DEBUG | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Executing node executor for node type execute - org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor

2019-05-16 14:00:45,819 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | execute node encountered - looking for plugin org.onap.appc.adapter.iaas.ProviderAdapter

2019-05-16 14:00:45,820 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.instance.url = (atom<CONTEXT_VAR> (variable-term vm-id)) resolves to

2019-05-16 14:00:45,826 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.provider.name = (atom<STRING> OpenStack) resolves to OpenStack

2019-05-16 14:00:45,829 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.identity.url = (atom<CONTEXT_VAR> (variable-term identity-url)) resolves to

2019-05-16 14:00:45,830 | INFO  | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0057I APPC IAAS Adapter start server requested

2019-05-16 14:00:45,831 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.instance.url" =""

2019-05-16 14:00:45,831 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.provider.name" ="OpenStack"

2019-05-16 14:00:45,832 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.identity.url" =""

2019-05-16 14:00:45,836 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | Service Logic Context: Status (success), Attribute count (14)

Attribute (input.common-header.api-ver), value (2.00)

Attribute (input.action-identifiers.service-instance-id), value ()

Attribute (input.action-identifiers.vserver-id), value (c82153dc-8d84-4e69-9673-5e0a60030779)

Attribute (input.common-header.sub-request-id), value ()

Attribute (input.common-header.request-id), value (873aacdf-1d85-4e07-8deb-7815776bbd35)

Attribute (input.common-header.timestamp), value (2019-05-16T14:00:43.177Z)

Attribute (currentGraph), value (SvcLogicGraph [module=APPC, rpc=VM_Start, mode=sync, version=2.0.0, md5sum=1cd3041dc9487e5abf527ee778af1bdc])

Attribute (input.action-identifiers.vnf-id), value (VNF_demo_steve)

Attribute (input.action-identifiers.vnfc-name), value ()

Attribute (input.action), value (Start)

Attribute (input.action-identifiers.vf-module-id), value ()

Attribute (input.common-header.originator-id), value (appc)

Attribute (isBwcMode), value (false)

 

For some reason, it’s not picking up the vm-id that is passed within the request, through the payload.

 

Are we missing something?

 

 



On May 15, 2019, at 4:44 PM, Brian <bf1936@...> wrote:

 

 

Hoepfully your payload is matching one of these examples

 

 

Brian

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of FREEMAN, BRIAN D
Sent: Wednesday, May 15, 2019 4:37 PM
To: onap-discuss@...; alphonse.steve.siani.djissitchi@...
Subject: Re: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

I’m not an expert at APPC but it looks like the input doesnt have the $vm-id (or its variation) defined (not sure which version of the Stop DG you are running).

You need to find the input variable to your REST call that matches the variable in the DG.

 

 

Brian

 

 

appc-directed-graph/appc-dgraph/provider/src/main/resources/json/APPC/APPC_VM_Stop.json:        "xml": "<execute plugin='org.onap.appc.adapter.iaas.ProviderAdapter' method='stopServer'>\n<parameter name=\"org.onap.appc.provider.name\" value=\"OpenStack\"/>\n<parameter name=\"org.onap.appc.instance.url\" value=\"`$vm-id`\" />\n<parameter name=\"org.onap.appc.identity.url\" value=\"`$identity-url`\

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Steve Siani
Sent: Wednesday, May 15, 2019 4:01 PM
To: FREEMAN, BRIAN D <bf1936@...>; onap-discuss@...
Subject: Re: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

Hi Brian,

you where somehow right because I found that the svcLogic was not able to resolv SDNC DB URL. In OOM APPC, the namespace is added in the name of SDNC container. So the result was appc-host.NAMESPACE. I removed the NAMESPACE and my test can go one step ahead.

But I still have some issue. Below is the log.

2019-05-15T19:54:00,891 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 76 (call)

2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute graph SvcLogicGraph [module=APPC, rpc=StopVM_VM, mode=sync, version=2.0.0, md5sum=08a100251d4498556a8896c9eac11918]

2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 1 (switch)

2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 34 (block)

2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 35 (set)

2019-05-15T19:54:00,916 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 36 (switch)

2019-05-15T19:54:00,916 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 37 (set)

2019-05-15T19:54:00,925 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 39 (for)

2019-05-15T19:54:00,926 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 40 (switch)

2019-05-15T19:54:00,926 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 41 (execute)

2019-05-15T19:54:00,926 | INFO  | appc-dispatcher-5 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0056I APPC IAAS Adapter stop server requested

2019-05-15T19:54:00,927 | ERROR | appc-dispatcher-5 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0045E One or more properties for [stopServer] are missing, null, or empty.  They are:

'org.onap.appc.instance.url'

2019-05-15T19:54:00,927 | ERROR | appc-dispatcher-5 | StopServer                       | 503 - appc-iaas-adapter - 1.4.4 | APPC0112E Server APPC (id n/a) failed to stop during n/a phase, reason Check Parameters:APPC0045E One or more properties for [stopServer] are missing, null, or empty.  They are:

'org.onap.appc.instance.url'

2019-05-15T19:54:00,927 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 42 (switch)

2019-05-15T19:54:00,928 | INFO  | appc-dispatcher-5 | SvcLogicExprListener             | 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.3 | Outcome ("") not found, keys are { (CONTEXT_NOT_FOUND) (SUCCESS) (ERROR)}

2019-05-15T19:54:00,928 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 86 (block)

2019-05-15T19:54:00,930 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 87 (block)

2019-05-15T19:54:00,937 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 88 (record)

2019-05-15T19:54:00,938 | ERROR | appc-dispatcher-5 | message-log                      | 223 - org.onap.ccsdk.sli.core.sli-recording - 0.3.3 |

2019-05-15T19:54:00,938 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 89 (execute)

2019-05-15T19:54:00,938 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 90 (execute)

2019-05-15T19:54:00,939 | INFO  | appc-dispatcher-5 | EventSenderDmaapImpl             | 458 - appc-common-bundle - 1.4.4 | Posting Message [873aacdf-1d85-4e07-8deb-7815776bbd35 - {"eventHeader":{"eventTime":"Wed May 15 19:54:00 UTC 2019","apiVer":"2.00","eventId":"873aacdf-1d85-4e07-8deb-7815776bbd35"},"eventStatus":{"code":501,"reason":"Check Parameters:APPC0045E One or more properties for [stopServer] are missing, null, or empty.  They are:"}}]

2019-05-15T19:54:00,939 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 91 (set)

2019-05-15T19:54:00,940 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 92 (return)

Any idea please?

Thanks!

 

 


APPC -> RE: [onap-discuss] #appc Unable to execute stop lcm operation from APPC #appc

Brian Freeman
 

It looks like its the encoding that is not quite right.

 

 

2019-05-16 14:00:45,830 | INFO  | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0057I APPC IAAS Adapter start server requested

2019-05-16 14:00:45,831 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.instance.url" =""

2019-05-16 14:00:45,831 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.provider.name" ="OpenStack"

2019-05-16 14:00:45,832 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.identity.url" =""

 

Can you try “\\””  (double slash encoding) ?

 

Taka – what is the secret ?

 

Brian

 

 

 

{

    "input": {

        "common-header": {

            "timestamp": "2017-10-31T15:02:04.244Z",

            "api-ver": "2.05",

            "originator-id": "SDNGP",

            "request-id": "Stop_VM-vFirewall_demo_app",

            "sub-request-id": "Stop_VM-vFirewall_demo_app",

            "flags": {

                "mode": "NORMAL",

                "force": "TRUE",

                "ttl": 36000

            }

        },

        "action": "Start",

        "action-identifiers": {

            "vnf-id": "vFirewall_demo_app",

            "vserver-id": "5b06cf36-40a0-4bcb-bde9-849aa4702d67"

        },

        "payload": "{\"vm-id\":\"http://10.12.25.2:8774/v2.1/466979b815b5415ba14ada713e6e1846/servers/5b06cf36-40a0-4bcb-bde9-849aa4702d67\", \"identity-url\": \"http://10.12.25.2:5000/v3\",\"skip-hypervisor-check\":\"true\"}"

    }

}

 

 

 

 

 

From: Alexis de Talhouët <adetalhouet89@...>
Sent: Thursday, May 16, 2019 10:03 AM
To: onap-discuss <onap-discuss@...>; FREEMAN, BRIAN D <bf1936@...>
Cc: alphonse.steve.siani.djissitchi@...
Subject: Re: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

Brian, Team,

 

We are following this example. Here is our payload

 

{

   "input": {

       "common-header": {

           "timestamp": {{timestamp}},

           "api-ver": "2.00",

           "originator-id": "appc",

           "request-id": "873aacdf-1d85-4e07-8deb-7815776bbd35",

           "flags": {

               "mode": "NORMAL",

               "force": "FALSE"

           }

       },

       "action": "Start",

       "action-identifiers": {

           "vnf-id": "VNF_demo_steve",

           "vserver-id": "c82153dc-8d84-4e69-9673-5e0a60030779"

       },

   }

}

 

And here are the DG logs in APPC:

 

2019-05-16 14:00:45,818 | INFO  | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute graph SvcLogicGraph [module=APPC, rpc=VM_Start, mode=sync, version=2.0.0, md5sum=1cd3041dc9487e5abf527ee778af1bdc]

2019-05-16 14:00:45,818 | INFO  | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 1 (execute)

2019-05-16 14:00:45,819 | DEBUG | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Executing node 1

2019-05-16 14:00:45,819 | DEBUG | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Executing node executor for node type execute - org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor

2019-05-16 14:00:45,819 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | execute node encountered - looking for plugin org.onap.appc.adapter.iaas.ProviderAdapter

2019-05-16 14:00:45,820 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.instance.url = (atom<CONTEXT_VAR> (variable-term vm-id)) resolves to

2019-05-16 14:00:45,826 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.provider.name = (atom<STRING> OpenStack) resolves to OpenStack

2019-05-16 14:00:45,829 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.identity.url = (atom<CONTEXT_VAR> (variable-term identity-url)) resolves to

2019-05-16 14:00:45,830 | INFO  | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0057I APPC IAAS Adapter start server requested

2019-05-16 14:00:45,831 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.instance.url" =""

2019-05-16 14:00:45,831 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.provider.name" ="OpenStack"

2019-05-16 14:00:45,832 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.identity.url" =""

2019-05-16 14:00:45,836 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | Service Logic Context: Status (success), Attribute count (14)

Attribute (input.common-header.api-ver), value (2.00)

Attribute (input.action-identifiers.service-instance-id), value ()

Attribute (input.action-identifiers.vserver-id), value (c82153dc-8d84-4e69-9673-5e0a60030779)

Attribute (input.common-header.sub-request-id), value ()

Attribute (input.common-header.request-id), value (873aacdf-1d85-4e07-8deb-7815776bbd35)

Attribute (input.common-header.timestamp), value (2019-05-16T14:00:43.177Z)

Attribute (currentGraph), value (SvcLogicGraph [module=APPC, rpc=VM_Start, mode=sync, version=2.0.0, md5sum=1cd3041dc9487e5abf527ee778af1bdc])

Attribute (input.action-identifiers.vnf-id), value (VNF_demo_steve)

Attribute (input.action-identifiers.vnfc-name), value ()

Attribute (input.action), value (Start)

Attribute (input.action-identifiers.vf-module-id), value ()

Attribute (input.common-header.originator-id), value (appc)

Attribute (isBwcMode), value (false)

 

For some reason, it’s not picking up the vm-id that is passed within the request, through the payload.

 

Are we missing something?

 

 



On May 15, 2019, at 4:44 PM, Brian <bf1936@...> wrote:

 

 

Hoepfully your payload is matching one of these examples

 

 

Brian

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of FREEMAN, BRIAN D
Sent: Wednesday, May 15, 2019 4:37 PM
To: onap-discuss@...; alphonse.steve.siani.djissitchi@...
Subject: Re: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

I’m not an expert at APPC but it looks like the input doesnt have the $vm-id (or its variation) defined (not sure which version of the Stop DG you are running).

You need to find the input variable to your REST call that matches the variable in the DG.

 

 

Brian

 

 

appc-directed-graph/appc-dgraph/provider/src/main/resources/json/APPC/APPC_VM_Stop.json:        "xml": "<execute plugin='org.onap.appc.adapter.iaas.ProviderAdapter' method='stopServer'>\n<parameter name=\"org.onap.appc.provider.name\" value=\"OpenStack\"/>\n<parameter name=\"org.onap.appc.instance.url\" value=\"`$vm-id`\" />\n<parameter name=\"org.onap.appc.identity.url\" value=\"`$identity-url`\

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Steve Siani
Sent: Wednesday, May 15, 2019 4:01 PM
To: FREEMAN, BRIAN D <bf1936@...>; onap-discuss@...
Subject: Re: [onap-discuss] #appc Unable to execute stop lcm operation from APPC

 

Hi Brian,

you where somehow right because I found that the svcLogic was not able to resolv SDNC DB URL. In OOM APPC, the namespace is added in the name of SDNC container. So the result was appc-host.NAMESPACE. I removed the NAMESPACE and my test can go one step ahead.

But I still have some issue. Below is the log.

2019-05-15T19:54:00,891 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 76 (call)

2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute graph SvcLogicGraph [module=APPC, rpc=StopVM_VM, mode=sync, version=2.0.0, md5sum=08a100251d4498556a8896c9eac11918]

2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 1 (switch)

2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 34 (block)

2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 35 (set)

2019-05-15T19:54:00,916 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 36 (switch)

2019-05-15T19:54:00,916 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 37 (set)

2019-05-15T19:54:00,925 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 39 (for)

2019-05-15T19:54:00,926 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 40 (switch)

2019-05-15T19:54:00,926 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 41 (execute)

2019-05-15T19:54:00,926 | INFO  | appc-dispatcher-5 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0056I APPC IAAS Adapter stop server requested

2019-05-15T19:54:00,927 | ERROR | appc-dispatcher-5 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0045E One or more properties for [stopServer] are missing, null, or empty.  They are:

'org.onap.appc.instance.url'

2019-05-15T19:54:00,927 | ERROR | appc-dispatcher-5 | StopServer                       | 503 - appc-iaas-adapter - 1.4.4 | APPC0112E Server APPC (id n/a) failed to stop during n/a phase, reason Check Parameters:APPC0045E One or more properties for [stopServer] are missing, null, or empty.  They are:

'org.onap.appc.instance.url'

2019-05-15T19:54:00,927 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 42 (switch)

2019-05-15T19:54:00,928 | INFO  | appc-dispatcher-5 | SvcLogicExprListener             | 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.3 | Outcome ("") not found, keys are { (CONTEXT_NOT_FOUND) (SUCCESS) (ERROR)}

2019-05-15T19:54:00,928 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 86 (block)

2019-05-15T19:54:00,930 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 87 (block)

2019-05-15T19:54:00,937 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 88 (record)

2019-05-15T19:54:00,938 | ERROR | appc-dispatcher-5 | message-log                      | 223 - org.onap.ccsdk.sli.core.sli-recording - 0.3.3 |

2019-05-15T19:54:00,938 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 89 (execute)

2019-05-15T19:54:00,938 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 90 (execute)

2019-05-15T19:54:00,939 | INFO  | appc-dispatcher-5 | EventSenderDmaapImpl             | 458 - appc-common-bundle - 1.4.4 | Posting Message [873aacdf-1d85-4e07-8deb-7815776bbd35 - {"eventHeader":{"eventTime":"Wed May 15 19:54:00 UTC 2019","apiVer":"2.00","eventId":"873aacdf-1d85-4e07-8deb-7815776bbd35"},"eventStatus":{"code":501,"reason":"Check Parameters:APPC0045E One or more properties for [stopServer] are missing, null, or empty.  They are:"}}]

2019-05-15T19:54:00,939 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 91 (set)

2019-05-15T19:54:00,940 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 92 (return)

Any idea please?

Thanks!

 

 


#ctrl-loop #integration Improvements to vFWCL regarding control loops #controlloop #integration

t.puha@...
 

Hi,

 

Referring to our discussion on this Wednesday’s control loop subcommittee meeting, it felt that we have quite a different view on what is actually included in current vFWCL case. To get some clarity to that, I checked what our guys had actually done with Casablanca vFWCL. See https://gerrit.onap.org/r/gitweb?p=oom/offline-installer.git;a=blob;f=docs/vFWCL-notes.rst;h=690b6dc9ec3c19cc225f6f495c8711b098f91008;hb=refs/heads/casablanca for details and it seems to fit my gut feeling of the scope.

 

Note that this is on Casablanca and other variants of vFWCL can and probably do exist, but as we are not aware of any other detailed (recent) description, this is what the analysis below is based on.

 

  1. Design time (SDC) is not included in any way except as a dumb catalogue. The starting point seems to be a pre-made service CSAR which is imported to SDC as such. In particular the building of a service including the control loop is not designed using any SDC mechanisms. Using a pre-based service CSAR is of course a fine scenario on its own, but leaves out the design time from demoing and testing, so the coverage will be less.
  2. On run time most of the control loop functionality does not seem to be used either. Simply put, the control loop model does not exist.
    1. On DCAE the flow uses the static bootstrapped instances of VES Collector and TCA and there is no sign of dynamic creation of DCAE service components or any other DCAE resources as part of the vFWCL
    2. Policies are created and manipulated directly using Policy APIs. It is not clear to me if the TCA policy is set dynamically at all or it just uses static configuration for vFWCL from bootstrap as it used to do before in previous releases.
    3. CLAMP is not used at all

 

AFAIK, this is much less than what Dublin control loops are capable of. I would like us to upgrade this demo case to contain the full supported set of components and models. To me this seems like a more fundamental part for https://wiki.onap.org/display/DW/vFirewall+Use+Case+Upgrade than the ones proposed there now. Although those target seem quite similar in spirit and I agree with those in general as well.

 

If a more complex vFWCL variant exists with some or all these features, please share a link to any material about it.

 

-Timo

 

  


Re: #appc Unable to execute stop lcm operation from APPC #appc

Alexis de Talhouet
 

Brian, Team,

We are following this example. Here is our payload

{
   "input": {
       "common-header": {
           "timestamp": {{timestamp}},
           "api-ver": "2.00",
           "originator-id": "appc",
           "request-id": "873aacdf-1d85-4e07-8deb-7815776bbd35",
           "flags": {
               "mode": "NORMAL",
               "force": "FALSE"
           }
       },
       "action": "Start",
       "action-identifiers": {
           "vnf-id": "VNF_demo_steve",
           "vserver-id": "c82153dc-8d84-4e69-9673-5e0a60030779"
       },
   }
}

And here are the DG logs in APPC:

2019-05-16 14:00:45,818 | INFO  | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute graph SvcLogicGraph [module=APPC, rpc=VM_Start, mode=sync, version=2.0.0, md5sum=1cd3041dc9487e5abf527ee778af1bdc]
2019-05-16 14:00:45,818 | INFO  | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 1 (execute)
2019-05-16 14:00:45,819 | DEBUG | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Executing node 1
2019-05-16 14:00:45,819 | DEBUG | ppc-dispatcher-6 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Executing node executor for node type execute - org.onap.ccsdk.sli.core.sli.provider.ExecuteNodeExecutor
2019-05-16 14:00:45,819 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | execute node encountered - looking for plugin org.onap.appc.adapter.iaas.ProviderAdapter
2019-05-16 14:00:45,820 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.instance.url = (atom<CONTEXT_VAR> (variable-term vm-id)) resolves to
2019-05-16 14:00:45,826 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.provider.name = (atom<STRING> OpenStack) resolves to OpenStack
2019-05-16 14:00:45,829 | DEBUG | ppc-dispatcher-6 | ExecuteNodeExecutor              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | Parameter org.onap.appc.identity.url = (atom<CONTEXT_VAR> (variable-term identity-url)) resolves to
2019-05-16 14:00:45,830 | INFO  | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0057I APPC IAAS Adapter start server requested
2019-05-16 14:00:45,831 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.instance.url" =""
2019-05-16 14:00:45,831 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.provider.name" ="OpenStack"
2019-05-16 14:00:45,832 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | PAL0004I Property "org.onap.appc.identity.url" =""
2019-05-16 14:00:45,836 | DEBUG | ppc-dispatcher-6 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | Service Logic Context: Status (success), Attribute count (14)
Attribute (input.common-header.api-ver), value (2.00)
Attribute (input.action-identifiers.service-instance-id), value ()
Attribute (input.action-identifiers.vserver-id), value (c82153dc-8d84-4e69-9673-5e0a60030779)
Attribute (input.common-header.sub-request-id), value ()
Attribute (input.common-header.request-id), value (873aacdf-1d85-4e07-8deb-7815776bbd35)
Attribute (input.common-header.timestamp), value (2019-05-16T14:00:43.177Z)
Attribute (currentGraph), value (SvcLogicGraph [module=APPC, rpc=VM_Start, mode=sync, version=2.0.0, md5sum=1cd3041dc9487e5abf527ee778af1bdc])
Attribute (input.action-identifiers.vnf-id), value (VNF_demo_steve)
Attribute (input.action-identifiers.vnfc-name), value ()
Attribute (input.action), value (Start)
Attribute (input.action-identifiers.vf-module-id), value ()
Attribute (input.common-header.originator-id), value (appc)
Attribute (isBwcMode), value (false)

For some reason, it’s not picking up the vm-id that is passed within the request, through the payload.

Are we missing something?



On May 15, 2019, at 4:44 PM, Brian <bf1936@...> wrote:

 
Hoepfully your payload is matching one of these examples
 
 
Brian
 
 
From: onap-discuss@... <onap-discuss@...> On Behalf Of FREEMAN, BRIAN D
Sent: Wednesday, May 15, 2019 4:37 PM
To: onap-discuss@...; alphonse.steve.siani.djissitchi@...
Subject: Re: [onap-discuss] #appc Unable to execute stop lcm operation from APPC
 

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

I’m not an expert at APPC but it looks like the input doesnt have the $vm-id (or its variation) defined (not sure which version of the Stop DG you are running).
You need to find the input variable to your REST call that matches the variable in the DG.
 
 
Brian
 
 
appc-directed-graph/appc-dgraph/provider/src/main/resources/json/APPC/APPC_VM_Stop.json:        "xml": "<execute plugin='org.onap.appc.adapter.iaas.ProviderAdapter' method='stopServer'>\n<parameter name=\"org.onap.appc.provider.name\" value=\"OpenStack\"/>\n<parameter name=\"org.onap.appc.instance.url\" value=\"`$vm-id`\" />\n<parameter name=\"org.onap.appc.identity.url\" value=\"`$identity-url`\
 
 
From: onap-discuss@... <onap-discuss@...> On Behalf Of Steve Siani
Sent: Wednesday, May 15, 2019 4:01 PM
To: FREEMAN, BRIAN D <bf1936@...>; onap-discuss@...
Subject: Re: [onap-discuss] #appc Unable to execute stop lcm operation from APPC
 
Hi Brian,

you where somehow right because I found that the svcLogic was not able to resolv SDNC DB URL. In OOM APPC, the namespace is added in the name of SDNC container. So the result was appc-host.NAMESPACE. I removed the NAMESPACE and my test can go one step ahead.

But I still have some issue. Below is the log.

2019-05-15T19:54:00,891 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 76 (call)
2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute graph SvcLogicGraph [module=APPC, rpc=StopVM_VM, mode=sync, version=2.0.0, md5sum=08a100251d4498556a8896c9eac11918]
2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 1 (switch)
2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 34 (block)
2019-05-15T19:54:00,915 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 35 (set)
2019-05-15T19:54:00,916 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 36 (switch)
2019-05-15T19:54:00,916 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 37 (set)
2019-05-15T19:54:00,925 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 39 (for)
2019-05-15T19:54:00,926 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 40 (switch)
2019-05-15T19:54:00,926 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 41 (execute)
2019-05-15T19:54:00,926 | INFO  | appc-dispatcher-5 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0056I APPC IAAS Adapter stop server requested
2019-05-15T19:54:00,927 | ERROR | appc-dispatcher-5 | ProviderOperation                | 503 - appc-iaas-adapter - 1.4.4 | APPC0045E One or more properties for [stopServer] are missing, null, or empty.  They are:
'org.onap.appc.instance.url'
2019-05-15T19:54:00,927 | ERROR | appc-dispatcher-5 | StopServer                       | 503 - appc-iaas-adapter - 1.4.4 | APPC0112E Server APPC (id n/a) failed to stop during n/a phase, reason Check Parameters:APPC0045E One or more properties for [stopServer] are missing, null, or empty.  They are:
'org.onap.appc.instance.url'
2019-05-15T19:54:00,927 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 42 (switch)
2019-05-15T19:54:00,928 | INFO  | appc-dispatcher-5 | SvcLogicExprListener             | 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.3 | Outcome ("") not found, keys are { (CONTEXT_NOT_FOUND) (SUCCESS) (ERROR)}
2019-05-15T19:54:00,928 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 86 (block)
2019-05-15T19:54:00,930 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 87 (block)
2019-05-15T19:54:00,937 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 88 (record)
2019-05-15T19:54:00,938 | ERROR | appc-dispatcher-5 | message-log                      | 223 - org.onap.ccsdk.sli.core.sli-recording - 0.3.3 |
2019-05-15T19:54:00,938 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 89 (execute)
2019-05-15T19:54:00,938 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 90 (execute)
2019-05-15T19:54:00,939 | INFO  | appc-dispatcher-5 | EventSenderDmaapImpl             | 458 - appc-common-bundle - 1.4.4 | Posting Message [873aacdf-1d85-4e07-8deb-7815776bbd35 - {"eventHeader":{"eventTime":"Wed May 15 19:54:00 UTC 2019","apiVer":"2.00","eventId":"873aacdf-1d85-4e07-8deb-7815776bbd35"},"eventStatus":{"code":501,"reason":"Check Parameters:APPC0045E One or more properties for [stopServer] are missing, null, or empty.  They are:"}}]
2019-05-15T19:54:00,939 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 91 (set)
2019-05-15T19:54:00,940 | INFO  | appc-dispatcher-5 | SvcLogicServiceImpl              | 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute node # 92 (return)

Any idea please?

Thanks!
 



logging pairwise RC1 results

Michael O'Brien <frank.obrien@...>
 

Pairwise complete – updated, a couple components either don’t ship logs, need a filebeat refactor or need more advanced use cases on my part.

https://wiki.onap.org/display/DW/Logging+Dublin+RC1+Deliverables+for+RC1+Milestone+Checklist

https://wiki.onap.org/display/DW/Logging+Pair+Wise+Testing+for+Dublin+Release

 

/michael

 

 

This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service


Re: Scale in working flow in ONAP

Scott Blandford
 

Hi Liu,

We were unable to do much with Scaling in the Dublin Release because of resource issues.  The only thing we did is make auto-scale out a little easier to use.  It looks like El Alto will be a maintenance release so we won’t be able to add new features.  However in Frankfurt, I would like to add Scale In as well as things like Pre and Post action capabilities, but we will need to find more people to work on it.  If Nokia is interested and would like to add some resource to the effort, please let me know.  We could really use the help.

 

Thanks,

Scott

 

From: Liu, Yongqiang (NSB - CN/Hangzhou) <yongqiang.liu@...>
Sent: Wednesday, May 15, 2019 11:32 PM
To: onap-discuss@...; BLANDFORD, SCOTT <cb1694@...>; Yongqiang Liu <yongqiangliu312@...>; LEWIS, LAUREN A <ll7851@...>; PINHO, ALBINO S <ap3929@...>; MAHIMKAR, AJAY <mahimkar@...>; Rajewski Lukasz - Korpo <lukasz.rajewski@...>
Cc: PLATANIA, MARCO <platania@...>
Subject: RE: [onap-discuss] Scale in working flow in ONAP

 

Hi, scott.

From prior talking about scaling work flow, what about such issue in Dublin release.

 

Also I agree that the Pre and Post actions need to be included in Scale Out.  We just have not gotten that far yet.  I will add them as work items for Dublin, but we will need to prioritize our Goals and Requirements since they are beginning to get quite large.

 

I have not seen that pre and post action included in the scale out Dublin workflow.

 

Best Regards

Yongqiang, Liu

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Scott Blandford
Sent: Monday, October 08, 2018 9:12 PM
To: Yongqiang Liu <yongqiangliu312@...>; onap-discuss@...; LEWIS, LAUREN A <ll7851@...>; PINHO, ALBINO S <ap3929@...>; MAHIMKAR, AJAY <mahimkar@...>; Rajewski Lukasz - Korpo <lukasz.rajewski@...>
Cc: PLATANIA, MARCO <platania@...>
Subject: Re: [onap-discuss] Scale in working flow in ONAP

 

Hi Liu,

We have not yet decided how the Pre and Post Actions will be implemented, but my early thoughts are that it will be as you say.  SO will call the Pre Action or Post Action API with a Scale In flag to APPC/SDNC and then APPC/SDNC will execute associated with Scale In.  As we have more meetings on this I will keep the team informed.

 

Scott

 

From: Yongqiang Liu <yongqiangliu312@...>
Sent: Saturday, October 06, 2018 5:01 AM
To: onap-discuss@...; LEWIS, LAUREN A <ll7851@...>; PINHO, ALBINO S <ap3929@...>; MAHIMKAR, AJAY <mahimkar@...>; Rajewski Lukasz - Korpo <lukasz.rajewski@...>; BLANDFORD, SCOTT <cb1694@...>
Cc: PLATANIA, MARCO <platania@...>
Subject: Re: [onap-discuss] Scale in working flow in ONAP

 

hi, thanks, scott, 

I think it's great news for our features to support ONAP.

 

Most of the examples you list below are things that are done by ONAP.  Can you give other actions that need to be done by your specific VNFs that are not needed by all other VNFs?

>> I'm sorry I thought I have not enough examples for this. our product still in continuous improving and developing, so I believe that  there are many new requirements continuously coming to us, if I have new such examples, I will provide to you in time. 

 

I believe that it's best and easiest way which provide Pre and Post actions to let many kinds of VNF supporting ONAP, it let them have enough flexibility to do their specific requirements.

 

“Pre Action” and a “Post Action” signal to the VNF and it will then wait for a response before continuing with the workflow.

>> it means that SO will trigger "Pre ation" and "Post ation" to APP-C, and then APP-C will invoke some specific playbooks which provided by VNFs to do such actions, Is my understanding accurate? 

 

 

 

Best Regards

Yongqiang, Liu

NSB MN ATF RD HZH CldFnd3

Tel: +86 13738187414

 

On Tuesday, October 2, 2018 4:31 AM, Scott Blandford <cb1694@...> wrote:

 

Liu,

We had a couple meetings late last week.  The outcome is that ONAP is going to provide both a “Pre Action” and a “Post Action” signal to the VNF and it will then wait for a response before continuing with the workflow.  This will be very good for many different types of VNFs.  However, it will be important for only VNF specific tasks to be done during these phases.

 

Any action that can be generalized across VNFs should be orchestrated by ONAP as part of the Scaling action.

 

Here are some examples of things that will be done by ONAP and therefore do not need to be done by the VNF during the Pre and Post phases:

  • Conflict avoidance:  ONAP will put a lock on the VNF while it is executing a Scale In or Out work flow, so that other actions will not produce conflicts.  It should also put a lock on the VNF when initiating other workflows that cannot tolerate conflicts.
  • Distribute Traffic: will tell the VNF to move new traffic to other instances of the VNFC
  • Quiesce Traffic: will tell ONAP when existing traffic on the VM has been drained
  • ConfigScaleIn: will tell the VNF it is time to make configuration changes to the VNF and remove the instance from the pool
  • Stop VM: will shutdown the VM
  • Terminate VM: will remove the VM from the cloud and return the resources.
  • Upgrade: is an ONAP action if needed
  • Rollback: is an ONAP Action if needed
  • Snapshot: is an ONAP action if needed.

 

I am sure there are many things a VNF needs to do in order to prepare for a scaling action as well as some cleanup items that need to be done after the action, but I am still looking for examples that may need to be done during these phases.

 

Most of the examples you list below are things that are done by ONAP.  Can you give other actions that need to be done by your specific VNFs that are not needed by all other VNFs?

 

Also I agree that the Pre and Post actions need to be included in Scale Out.  We just have not gotten that far yet.  I will add them as work items for Dublin, but we will need to prioritize our Goals and Requirements since they are beginning to get quite large.

 

Scott Blandford

 

 

 

From: Yongqiang Liu <yongqiangliu312@...>
Sent: Saturday, September 29, 2018 10:40 PM
To: onap-discuss@...; LEWIS, LAUREN A <ll7851@...>; PINHO, ALBINO S <ap3929@...>; MAHIMKAR, AJAY <mahimkar@...>; Rajewski Lukasz - Korpo <lukasz.rajewski@...>; BLANDFORD, SCOTT <cb1694@...>
Cc: PLATANIA, MARCO <platania@...>
Subject: Re: [onap-discuss] Scale in working flow in ONAP

 

hi, Scott and Lauren,

 

Is there any thing else need I to clarify, I have viewed your meeting result:

 

Prep and Post phases for Scale In

  • Scott will get back to Liu (Nokia) to explain what should be done by ONAP vs what should be done by the VNF.  once this is established we will need to determine if the VNF needs to be signaled for each phase and if a response is needed

so what's your explanation.

 

and I have another question that I think the pre-action is needed also for scaling out, I have not seen your talking about this.

 

 

 

Best Regards

Yongqiang, Liu

NSB MN ATF RD HZH CldFnd3

Tel: +86 13738187414

 

On Tuesday, September 25, 2018 2:12 AM, Scott Blandford <cb1694@...> wrote:

 

Let’s go through this in more detail during our weekly Scaling call Tuesday at 0900 US Eastern Time  (1300 UTC)

 

Scott Blandford

 

From: LEWIS, LAUREN A
Sent: Friday, September 21, 2018 10:40 AM
To: PINHO, ALBINO S <ap3929@...>; Yongqiang Liu <yongqiangliu312@...>; BLANDFORD, SCOTT <cb1694@...>; MAHIMKAR, AJAY <mahimkar@...>; Rajewski Lukasz - Korpo <lukasz.rajewski@...>; onap-discuss@...
Cc: PLATANIA, MARCO <platania@...>
Subject: RE: [onap-discuss] Scale in working flow in ONAP

 

Albino,

 

Good point about adding in the guidelines which operations require exclusive access.

 

Yongqiang: See some additional comments below.

 

From: PINHO, ALBINO S
Sent: Friday, September 21, 2018 8:51 AM
To: Yongqiang Liu <yongqiangliu312@...>; LEWIS, LAUREN A <ll7851@...>; BLANDFORD, SCOTT <cb1694@...>; MAHIMKAR, AJAY <mahimkar@...>; Rajewski Lukasz - Korpo <lukasz.rajewski@...>; onap-discuss@...
Cc: PLATANIA, MARCO <platania@...>
Subject: RE: [onap-discuss] Scale in working flow in ONAP

 

Lauren,

 

Looking at this thread reminds me, we need to document in the guidelines operations that require exclusive access to the VNF instance, blocking any other requests until they complete, examples, Configure, ConfigModify, StopApplication, StartApplication, ScaleOut, ScaleIn, etc. Multiple HealthCheck, UpgradePreCheck, UpgradePostCheck targeting a single VNF instance would be ok.

 

Thank you,

Albino Pinho

Office (732) 420-7035

 

From: Yongqiang Liu [mailto:yongqiangliu312@...]
Sent: Thursday, September 20, 2018 11:02 PM
To: LEWIS, LAUREN A <ll7851@...>; BLANDFORD, SCOTT <cb1694@...>; MAHIMKAR, AJAY <mahimkar@...>; Rajewski Lukasz - Korpo <lukasz.rajewski@...>; onap-discuss@...; LEWIS, LAUREN A <ll7851@...>; BLANDFORD, SCOTT <cb1694@...>; MAHIMKAR, AJAY <mahimkar@...>; Rajewski Lukasz - Korpo <lukasz.rajewski@...>; onap-discuss@...
Cc: PLATANIA, MARCO <platania@...>; PINHO, ALBINO S <ap3929@...>; PLATANIA, MARCO <platania@...>; PINHO, ALBINO S <ap3929@...>; PLATANIA, MARCO <platania@...>; PINHO, ALBINO S <ap3929@...>
Subject: Re: [onap-discuss] Scale in working flow in ONAP

 

hi, lauren,

 

the following conditions should be checked in preparation phase in our product: 

    >> [Lauren: If a VNF healthcheck is done in the preparation phase, this should detect if the VNF is not healthy and a failure message would be sent back to SO. At which point the     process should stop]

        yes, but I do believe that not all these conditions checking should be placed into HealthCheck action in ONAP, as I understand for healthcheck maybe only such things need to be            checked such as whether all key services are working well in VNF , or whether VM is running well.  [Lauren: I did some checking and it seems like there are cases where the playbook for healthcheck has been customized to check the DB Service. We can look into different ways in which we can accomplish what you are asking]

 

upgrade and rollback for both VNF and RAP; 

    >> [Lauren: Is this a check? What is the purpose of this during preparation phase]

        yes, we think that it's conflict operations between upgrading and scaling, if one of them is ongoing then another operation will be rejected in our product, I don't know if SO could         handle such conflict.[Lauren: I am not sure if SO has a way of managing that today. I am checking with SO. However, the Controller does have the Lock LCM actions that ensures exclusive rights during a series of critical LCM actions being performed. So the Controller (APPC/SDNC) would reject subsequent requests that did not have the same request ID. I think this would work for the most part, however, if the operation being executed came from another app, I am not sure APP-C would detect prior to sending the request. Again, I would think that once the request is sent, the VNF would reject the last request if another operation is being processed]

 

snapshot saving;

    >> [Lauren: Same question as above]

        also it's conflict operations between snapshot and scaling.[Lauren: Same as previous comment]

 

the mainly things are to delete VNFC/VM's configurations of different services running in VNF at post phase for scaling in, we do such things after VM resource deleted successfully from cloud, because we thought if VM delete failed from cloud (VM still could work), then the VNF could be recovered easily (configurations still exist).

    >>[Lauren: In the ScaleIn workflow, the plan is to have an action to delete the VNFC/VMs configurations.]

        it's certainly ok, but I still suggest you could add pre-phase and post-phase for scaling workflows from a common view, because maybe there are different requirements for different             VNF come from different vendors like us, they just need provide the ansible playbooks to do individual things according their specific requirement at these phases. [Lauren: I agree]

 

 

Best Regards

Yongqiang, Liu

NSB MN ATF RD HZH CldFnd3

Tel: +86 13738187414

 

 

 

On Thursday, September 20, 2018 10:07 PM, "LEWIS, LAUREN A" <ll7851@...> wrote:

 

Yongqiang,

 

Thanks for the clarification.

 

Please see my inline comments/questions below to your response.

 

Thanks,

 

Lauren Lewis

(AT&T)

 

From: Yongqiang Liu [mailto:yongqiangliu312@...]
Sent: Thursday, September 20, 2018 2:12 AM
To: BLANDFORD, SCOTT <cb1694@...>; MAHIMKAR, AJAY <mahimkar@...>; Rajewski Łukasz - Korpo <lukasz.rajewski@...>; onap-discuss@...
Cc: LEWIS, LAUREN A <ll7851@...>; PLATANIA, MARCO <platania@...>
Subject: Re: [onap-discuss] Scale in working flow in ONAP

 

hi, scott,

 

>>  Under what conditions is a preparation request likely to signal that the scaling operation should not be done, and how should it be handled by ONAP?

 

the following conditions should be checked in preparation phase in our product: [Lauren: If a VNF healthcheck is done in the preparation phase, this should detect if the VNF is not healthy and a failure message would be sent back to SO. At which point the process should stop]

upgrade and rollback for both VNF and RAP; [Lauren: Is this a check? What is the purpose of this during preparation phase]

snapshot saving;[Lauren: Same question as above]

another scaling operation ongoing; [Lauren: The Controller has a Lock LCM action that gives the controller exclusive access to the VNF, this is used to prevent future operations conflicting with the scaling operation. I am checking to see if Unlock checks to see if any ongoing process is running and what happens if there is ]

synchronization problems between VNFM and VNF database;[Current Scale Out/In does not have a VNFM]

DB service status;

 

I think if these preventive conditions checking is failed at preparation phase, then ONAP should end the current scaling operation.

 

 

>> What is done during the post phase?  I have not yet seen a solid need for this phase.  Does the Post phase need to be separate from the ConfigScaleOut/In?

for scaling out scenario, from your workflow I think ConfigScaleOut is already part of post phase, so separated post phase maybe not needed.

for scaling in scenario, I think ConfigScaleIn is part of preparation phase but not part of post phase, because ConfigScaleIn is triggered before the operation deleting VM from cloud (openstack), so seperated post phase is needed except HeathCheck after deleting VM resource from cloud.

 

the mainly things are to delete VNFC/VM's configurations of different services running in VNF at post phase for scaling in, we do such things after VM resource deleted successfully from cloud, because we thought if VM delete failed from cloud (VM still could work), then the VNF could be recovered easily (configurations still exist).[Lauren: In the ScaleIn workflow, the plan is to have an action to delete the VNFC/VMs configurations.]

 

Best Regards

Yongqiang, Liu

NSB MN ATF RD HZH CldFnd3

Tel: +86 13738187414

 

 

On Wednesday, September 19, 2018 4:39 AM, "BLANDFORD, SCOTT" <cb1694@...> wrote:

 

Liu,

At this point we are just considering the addition of a Preparation and Post phase for scaling.  Before it is officially added to the Use Case I really need to know more about what will be done during these phases.

  • Under what conditions is a preparation request likely to signal that the scaling operation should not be done, and how should it be handled by ONAP?
  • Configurations changes will be handled by the ConfigScaleOut and ConfigScaleIn commands along with their Ansible or Chef Playbooks.
  • What is done during the post phase?  I have not yet seen a solid need for this phase.  Does the Post phase need to be separate from the ConfigScaleOut/In?

 

I agree that there needs to be a response from the prep and post requests, I have not shown that in the diagram yet, but I will add it.

 

Scott Blandford

AT&T

 

 

From: Yongqiang Liu <yongqiangliu312@...>
Sent: Tuesday, September 18, 2018 5:40 AM
To: BLANDFORD, SCOTT <cb1694@...>; MAHIMKAR, AJAY <mahimkar@...>; Rajewski Łukasz - Korpo <lukasz.rajewski@...>; onap-discuss@...
Cc: LEWIS, LAUREN A <ll7851@...>; PLATANIA, MARCO <platania@...>
Subject: Re: [onap-discuss] Scale in working flow in ONAP

 

hi, scott,

it's great you could add preparation phase in scaling in workflow, but I think APPC /  SO should care about the result of preparation actions from VNF, so it should have a reply arrows from VNF to APPC.

 

what about the scaling out workflow,  preparation phase is also  needed for scaling out, the requirement  what I mentioned for DB VNFCs is needed for both of scaling out and scaling in.

 

What other actions need to be done during this phase?

>> as I understand currently we have a centralized cluster management component in our VNF, it played the role for management plane, so we need request it to do some validations or pre-condition checks at prepare phase  and add configurations(for scaling out ) or delete configurations ( for scaling in) at post phase, that means it not completely distributed for our VNF, such manager care about the VNFC status and  have right to reject or accept scaling request, that is mainly reason why pre-phase and post-phase is needed for us.

 

for scaling in, post phase is needed after vms deleted from VNF successfully before HealthCheck, there are some service need to delete configurations in our VNF.

 

 

Best Regards

Yongqiang, Liu

NSB MN ATF RD HZH CldFnd3

Tel: +86 13738187414

 

On Monday, September 17, 2018 8:10 PM, "BLANDFORD, SCOTT" <cb1694@...> wrote:

 

Liu,

I understand that different types of VNFs might need to do different actions to prepare for a Scaling action.  I have been talking with several people about how to accommodate this need.  In many ways it might be better to do as you suggest: send a preparation signal to the VNF and have them take care of anything that needs to be done prior to scaling.  However, it is more in keeping with the ONAP/APPC strategy to have ONAP build these individual preparation actions into the orchestration flow and have APPC/SDNC call them directly through a playbook.

 

We are still looking into the best way to do this.  I have put a preparation phase into our Scaling workflow for now to trigger the conversation.  You can see where I have it currently positioned in the sequence diagram on this wiki page.

 

It would be very helpful to have more examples of the types of actions that are needed during the preparation phase.  You mentioned that there may need to be some synchronization done for DB VNFs before a Scale-In.  What other actions need to be done during this phase?

 

Thanks,

Scott

 

From: Yongqiang Liu <yongqiangliu312@...>
Sent: Monday, September 17, 2018 4:12 AM
To: MAHIMKAR, AJAY <mahimkar@...>; BLANDFORD, SCOTT <cb1694@...>; Rajewski Łukasz - Korpo <lukasz.rajewski@...>
Subject: Re: [onap-discuss] Scale in working flow in ONAP

 

hi, scott, do you have any comments for my last email.

if there is no preparation phase for ONAP scaling workflow, could you have any advice for us to adapt our VNF to ONAP,  preparation phase is needed for us from VNF side.

 

Best Regards

Yongqiang, Liu

NSB MN ATF RD HZH CldFnd3

Tel: +86 13738187414

 

On Tuesday, September 11, 2018 9:05 PM, "MAHIMKAR, AJAY (AJAY)" <mahimkar@...> wrote:

 

Joining in 10-15 mins. Sorry day care drop off for daughter.

 

 

On Tue, Sep 11, 2018 at 8:26 AM -0400, "BLANDFORD, SCOTT" <cb1694@...> wrote:

Yes.  1PM UTC

 

 

From: Rajewski Łukasz - Korpo <Lukasz.Rajewski@...>
Sent: Tuesday, September 11, 2018 3:21 AM
To: BLANDFORD, SCOTT <cb1694@...>; MAHIMKAR, AJAY <mahimkar@...>; Yongqiang Liu <yongqiangliu312@...>
Subject: RE: [onap-discuss] Scale in working flow in ONAP

 

Hi,

 

I can join Scale Out meeting today. Is it at 1 pm UTC?

 

Regards,

 

Logo Orange

Łukasz Rajewski, R&D Expert
Orange Labs Polska, Advancend Networking Systems Agency, Warsaw
Mobile: +48 519 310 854
Orange Polska, Obrzeżna 7, 02-691 Warszawa
www.orange.pl

 

 

From: BLANDFORD, SCOTT [mailto:cb1694@...]
Sent: Monday, September 10, 2018 10:50 PM
To: MAHIMKAR, AJAY; Rajewski Łukasz - Korpo; onap-discuss@...; Yongqiang Liu
Subject: RE: [onap-discuss] Scale in working flow in ONAP

 

Ajay and Lukasz,

We can talk about it on the Scale Out call tomorrow morning or I can join the CM call on Wednesday morning.

 

Scott

 

From: MAHIMKAR, AJAY
Sent: Monday, September 10, 2018 2:21 PM
To: Rajewski Łukasz - Korpo <Lukasz.Rajewski@...>; onap-discuss@...; BLANDFORD, SCOTT <cb1694@...>; Yongqiang Liu <yongqiangliu312@...>
Subject: RE: [onap-discuss] Scale in working flow in ONAP

 

Yes, there are synergies here. Let’s talk soon.

Lukasz – should we do it on the Scale Out call Tuesday 9AM Eastern?

 

From: Rajewski Łukasz - Korpo [mailto:Lukasz.Rajewski@...]
Sent: Friday, September 7, 2018 2:35 AM
To: onap-discuss@...; BLANDFORD, SCOTT <cb1694@...>; Yongqiang Liu <yongqiangliu312@...>
Cc: MAHIMKAR, AJAY (AJAY) <mahimkar@...>
Subject: RE: [onap-discuss] Scale in working flow in ONAP

 

Hi,

 

for Casablanca in Change Management projects we have started to work on Traffic Distribution mechanisms. It would be more mature for Dublin. It looks that the same mechanism is required for Scale IN operation. In fact in change management workflow that we analyze now Scale In of Old VNF instance is one of the steps and we need to move the traffic out from this instance to the one with new software version. I think it would we worth to discuss about synergy during the Wednesday’s Change Management weekly meeting. Ajay is a PTL.

 

Regards,

 

Logo Orange

Łukasz Rajewski, R&D Expert
Orange Labs Polska, Advancend Networking Systems Agency, Warsaw
Mobile: +48 519 310 854
Orange Polska, Obrzeżna 7, 02-691 Warszawa
www.orange.pl

 

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Scott Blandford
Sent: Thursday, September 6, 2018 6:19 PM
To: Yongqiang Liu; onap-discuss@...
Subject: Re: [onap-discuss] Scale in working flow in ONAP

 

Liu,

We do not have a preparation phase for scaling at this time.  I would like to know more about what needs to be done in this phase for Scale Out. 

 

For Scale In you mention the need to move traffic to other instances.  We are planning on moving traffic off the target instance as one of the steps taken by SO orchestration when we build the Scale In operation in the next release.  Is there anything else you see that needs to be done in the preparation phase for Scale In?

 

Thanks,

Scott Blandford (AT&T)

 

From: Yongqiang Liu <yongqiangliu312@...>
Sent: Monday, September 03, 2018 10:34 PM
To: onap-discuss@...; BLANDFORD, SCOTT <cb1694@...>; yongqiangliu312@...
Subject: Re: [onap-discuss] Scale in working flow in ONAP

 

hi, scott,

did you get my latest email? I want to know if it's possible to add the workflows for prepare phase except healthcheck for scaling out and scaling in in ONAP.

 

 

Best Regards

Yongqiang, Liu

NSB MN ATF RD HZH CldFnd3

Tel: +86 13738187414

 

On Thursday, August 30, 2018 6:25 PM, Yongqiang Liu via Lists.Onap.Org <yongqiangliu312=yahoo.com@...> wrote:

 

hi,  yes, indeed we uses our VNF manager to provide the life cycle management of the VNF, now if we want our VNF to support the ONAP, I think we should replace the role of our VNFM with ONAP, so ultimately we should scale VNFs with APPC not VF-C.

we provide the life cycle management framework as a service run in our VNF, we will tell other services or applications running in VNF to do scaling actions if we receive the scaling request, so we will request these services to do prepare action at preparation phase  and post action at scaling finished phase. for scaling out I don't know the detail about what's needed to be done in preparation phase for these services, but they indeed have requirement for this, for scaling in some services need bake-up data or stop their sub servers, and traffic applications need  transfer their business to standby node.

 

Best Regards

Yongqiang, Liu

NSB MN ATF RD HZH CldFnd3

Tel: +86 13738187414

 

On Wednesday, August 29, 2018 3:09 AM, Scott Blandford <cb1694@...> wrote:

 

Liu,

You ask some good questions and I may have confused you with my earlier responses.

 

I believe your VNF uses a VNF Manager that provides a lot of the life cycle management of the VNF.  If this is the case then you need to look at the work that was done in Beijing that used the VF-C.  China Mobile was the lead in effort and you can get in touch with either Zhao Peng or Lin Meng to get more information on how scaling works for VNFs using a VNFM.  (There is not much documentation on the wiki)

 

Most of the documentation on the wiki is showing how to scale VNFs using APPC or SDNC instead of a VNFM to support scaling functionality.  When using APPC or SDNC, ONAP should take care of all the preparation work.  Healthcheck is just one of these preparation steps.  If there are other steps that need to be executed then they will need to be orchestrated by SO.  I would like to understand more about what your VNF needs to do in a preparation phase of scaling to determine if appc/sdnc needs to add more functionality in our scaling work flow.

 

Thanks,

Scott Blandford (AT&T)

 

From: Yongqiang Liu <yongqiangliu312@...>
Sent: Monday, August 27, 2018 11:15 PM
To: onap-discuss@...; BLANDFORD, SCOTT <cb1694@...>
Subject: Re: [onap-discuss] Scale in working flow in ONAP

 

hi,  I have not found any description about 'VFC flow for Scaling',  do you have any references or documents?

 

recently I studied the ETSI standard "Network Functions Virtualisation (NFV) Management and Orchestration ",  I found that there is scaling phase "preparation work" for VNFM in the definition for scaling flow at the chapter B.4.3,  I have doubted that if there is no this phase in ONAP's work flow when I compared these two flows, I think it's important for our product to support ONAP because there are somethings need to be done in preparation stage, it would be hard for our product to support ONAP if lacked this stage.

 

so this is why I ask these questions on previous e-mail:

 

2, there were three scaling phase in our scaling working flow: validation, pre-action and post-action, we should do the scaling phases validation and pre-action before instantiation according this picture (attachment).

I thought the phase healthcheck could be as our pre-action scaling phase, but seems like the healthcheck is a common interface, it not just be used in scaling, so I have doubt that how should we do to

adapt ONAP for our scaling? Seems like there is no appropriate place to add these two scaling phases in ONAP scaling working flow, anyway they were necessary in our product.

 

FoxitReader_2018-08-28_10-30-17.png

 

 

Scale_Out_Workflow.png

 

 

 

 

 

 

On Tuesday, July 24, 2018 11:23 PM, Scott Blandford <cb1694@...> wrote:

 

The Casablanca version of Scale Out only supports APPC/SDNC as controllers it does not support VFC. APPC and SDNC do not support vendor provided VNFMs and therefore most of the work you mention below is done within ONAP.

 

For instance Policies can be set up to check if other processes are taking place on the VNF/C.  It can also check against Min and Max # of instances or to be sure there is some dead time between Scaling actions.

 

Healthcheck ensures that the VNF is healthy and ready to scale and APPC/SDNC are responsible for the VNFC configuration after instantiation.

 

If you are providing a VNFM with your VNF then you need to use the VFC flow for Scaling.  In Beijing a manual trigger was developed for scaling VNFs using VFC, but it is not being updated for Auto Scaling in Casablanca.

 

Scott Blandford

 

From: Yongqiang Liu <yongqiangliu312@...>
Sent: Tuesday, July 24, 2018 3:17 AM
To: onap-discuss@...; BLANDFORD, SCOTT <cb1694@...>
Subject: Re: [onap-discuss] Scale in working flow in ONAP

 

hi, thanks your reply. 

>>   I would like to know more about what you want to do during Validation, Pre-Action, and Post-Action phases.  As you have noticed we only do a VNF level Healthcheck prior to scaling actions.  This Healthcheck only verifies the health of the entire VNF.  It does not do anything specific for scaling.  What other actions do you envision for the phases you mention?

 

during validation phase when scaling happened in our product, it firstly check that if something like upgrading is ongoing, and then it will ask some key applications if scaling action is allowed by them, if upgrading was already ongoing or some applications rejected at validation, then hole scaling action will be rejected.  

during pre-action, it will also ask some key applications to do something to prepare for scaling (in / out).

about the post-action for scaling out,  it will add the VNFC instance configuration which scaled out to VNF,    for scaling in, it will delete the VNFC instance configuration which scaled in from VNF, and also it will ask key applications to do something after vnfc instance created or deleted during scaling.

 

we think that it is requirement for some key applications to care about the scaling action, at least for scaling in  scenario, before the vnfc instance deleted, applications should be notified to do something to avoid out of service, and also some time if some applications do not want to scale, they should have right to reject those scaling requests. this is the background why we divide these three scaling phases, at least pre-action phase is necessary for scaling in scenario.  

 

On Friday, July 20, 2018 9:03 PM, Scott Blandford <cb1694@...> wrote:

 

Liu,

Thanks for your interest in Scaling.  It would be great to have you join our working team that meets every Tuesday morning.  Yours would be the first commercial VNF that we have worked with in the scaling group.  You can get more information from our Casablanca Scale Out Wiki page.

 

Here are some comments to your questions:

  1. In Casablanca we are only implementing Scale Out.  Scale in is targeted for a future release (Hopefully Dublin).  There are many complications to scale in that we have not approached yet and we are hoping that some of the Change Management features will be helpful for Scale In.
  2. I would like to know more about what you want to do during Validation, Pre-Action, and Post-Action phases.  As you have noticed we only do a VNF level Healthcheck prior to scaling actions.  This Healthcheck only verifies the health of the entire VNF.  It does not do anything specific for scaling.  What other actions do you envision for the phases you mention?

 

Thanks,

Scott Blandford

Lead Member Technical Staff

AT&T

 

From: Yongqiang Liu <yongqiangliu312@...>
Sent: Friday, July 20, 2018 5:08 AM
To: onap-discuss@...; BLANDFORD, SCOTT <cb1694@...>; yongqiangliu312@...
Subject: Scale in working flow in ONAP

 

hi, ONAP experts,

I came from Nokia, we want our VNF to support the ONAP platform, so we are studying ONAP, now I found some issues need to be clarified.

there were two issues:

1, from the ONAP documents, the scaling out working flow was supported for lifecycle management, but what about the scaling in working flow? I couldn't found any introductions for it.

2, there were three scaling phase in our scaling working flow: validation, pre-action and post-action, we should do the scaling phases validation and pre-action before instantiation according this picture (attachment).

I thought the phase healthcheck could be as our pre-action scaling phase, but seems like the healthcheck is a common interface, it not just be used in scaling, so I have doubt that how should we do to

adapt ONAP for our scaling? Seems like there is no appropriate place to add these two scaling phases in ONAP scaling working flow, anyway they were necessary in our product.

 

 Inline image

Best Regards

Yongqiang, Liu

NSB MN ATF RD HZH CldFnd3

Tel: +86 13738187414

 

 

 

 

 

 

 

 

 

 


Re: ONAP Dublin Highlights #dublin #dublin-release-intent

Srini
 

Hi Sriram,

 

Kubernetes based Cloud region support is not a POC.

 

Distributed Analytics as a service work is PoC in R4.

 

Thanks

Srini

 

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Sriram Rupanagunta
Sent: Wednesday, May 15, 2019 10:55 PM
To: onap-discuss@...
Subject: [onap-discuss] ONAP Dublin Highlights #dublin #dublin-release-intent

 

Dear Community members, 

As part of creating messaging for ONAP Dublin release for Linux Foundation, we have created the following Wiki page, and added the slides with details. All this material is based on the individual project Wiki pages, as well as few discussions with members. 

https://wiki.onap.org/display/DW/2019/05/16/Dublin+Release+Highlights

We would like to invite ONAP community to review and suggest if there are any factual errors/updates. Would appreciate if this could be done in a week's time (23 May). 

Thanks for your valuable time. 

-Sriram


Re: [aai] Standalone AAI UI

Chandra
 

The configmaps is not available it seems. I tried to list the cm but couldn’t get these configmaps.

 

 

[onap@rancher /]$ kubectl edit cm dev-aai-aai-sparky-be

Error from server (NotFound): configmaps "dev-aai-aai-sparky-be" not found

 

From: David.PerezCaparros@... [mailto:David.PerezCaparros@...]
Sent: 16 May 2019 17:55
To: onap-discuss@...; Chandrashekhar Thakare <CT00548828@...>
Cc: Francis.Paquette@...; Arul.Nambi@...
Subject: Re: [onap-discuss] [aai] Standalone AAI UI

 

Hi,

 

try editing the config map?

kubectl edit cm dev-aai-aai-sparky-be

 

Regards

David

--
David Pérez Caparrós
Senior Innovation Engineer
Swisscom (Switzerland)



On 16 May 2019, at 14:16, Chandra <CT00548828@...> wrote:

 

Thanks Francis. I am currently facing issue to edit this file it seems that it is in readonly-file system. Any known workaround to edit these rreadonly files in ONAP please?

 

From: Francis Paquette [mailto:Francis.Paquette@...] 
Sent: 16 May 2019 17:16
To: Chandrashekhar Thakare <CT00548828@...>; onap-discuss@...; Arul Nambi <Arul.Nambi@...>
Cc: Francis Paquette <Francis.Paquette@...>
Subject: RE: [onap-discuss] [aai] Standalone AAI UI

 

If you change the spring.profiles.active to

spring.profiles.active=camel,http,fe-prod,oxm-schema-prod,oxm-default,resources,sync

(and omit the portal from it) then you should be able to access AAI UI directly.

 

Francis

 

From: Chandrashekhar Thakare <CT00548828@...> 
Sent: Thursday, May 16, 2019 3:31 AM
To: Francis Paquette <Francis.Paquette@...>; onap-discuss@...; Arul Nambi <Arul.Nambi@...>
Subject: RE: [onap-discuss] [aai] Standalone AAI UI

 

Hi Francis,

Thanks for your reply.

We are using K8s Casablanca environment. Following are the contents of the application.properties file within the sparky-be pod. I could not see any option here to disable any redirection

 

spring.mvc.favicon.enabled=false

 

spring.profiles.active=camel,http,fe-prod,oxm-schema-prod,oxm-default,resources,sync,portal

 

searchservice.hostname=aai-search-data

searchservice.port=9509

searchservice.client-cert=client-cert-onap.p12

searchservice.client-cert-password=1y0q1uvc1uum1uvg1pil1pjl1uuq1uvk1uuu1y10

searchservice.truststore=tomcat_keystore

 

From: Francis Paquette [mailto:Francis.Paquette@...] 
Sent: 16 May 2019 01:28
To: onap-discuss@...; Chandrashekhar Thakare <CT00548828@...>; Arul Nambi <Arul.Nambi@...>
Cc: Francis Paquette <Francis.Paquette@...>
Subject: RE: [onap-discuss] [aai] Standalone AAI UI

 

Hi Chandra, if you disabled the portal as Arul specified, you can access the AAI UI using

https://aai.api.sparky.simpledemo.onap.org:30220/services/aai/webapp/index.html

(you can possibly replace aai.api.sparky.simpledemo.onap.org with one of the k8s node ip addresses)

 

Francis

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Chandra
Sent: Wednesday, May 15, 2019 1:59 PM
To: onap-discuss@...; Chandrashekhar Thakare <CT00548828@...>; Arul Nambi <Arul.Nambi@...>
Subject: Re: [onap-discuss] [aai] Standalone AAI UI

 

Hi Arul,

How can we access the standalone AAI UI  in K8S environment?

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Chandra
Sent: 28 February 2019 22:14
To: Arul Nambi <Arul.Nambi@...>; onap-discuss@...
Subject: Re: [onap-discuss] [aai] Standalone AAI UI

 

Hi Arul,

Is the standalone UI is available for AAI in Casablanca? Or it is still under development  for Dublin?

 

From: Arul Nambi [mailto:Arul.Nambi@...] 
Sent: 06 November 2018 19:47
To: Chandrashekhar Thakare <CT00548828@...>; onap-discuss@...
Subject: RE: [onap-discuss] [aai] Standalone AAI UI

 

Hi Chandra,

Yes you are right, you cannot use sparky without portal in Beijing L

Regards

Arul

 

From: Chandrashekhar Thakare [mailto:CT00548828@...] 
Sent: Tuesday, November 6, 2018 3:44 AM
To: onap-discuss@...; Arul Nambi <Arul.Nambi@...>
Subject: RE: [onap-discuss] [aai] Standalone AAI UI

 

Thanks Arul. 

Understood that the portal redirection can not be disabled  but does this mean that standalone AAI application UI cannot be accessed in Beijing and we will have to use Casablanca or Master for same?

 

 

 

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Arul Nambi
Sent: 05 November 2018 19:01
To: Chandrashekhar Thakare <CT00548828@...>; onap-discuss@...
Subject: Re: [onap-discuss] [aai] Standalone AAI UI

 

Hey Chandra,

Sorry unfortunately we were in the middle of configuration changes in Beijing and there is no way to disable portal in Beijing. Can you move to master/Casablanca? It is stable at this point in time.

Regards

Arul

 

From: Chandrashekhar Thakare [mailto:CT00548828@...] 
Sent: Monday, November 5, 2018 4:33 AM
To: Arul Nambi <
Arul.Nambi@...>; onap-discuss@...
Subject: RE: [aai] Standalone AAI UI

 

Hi Arul,

Thanks for information.

I am currently using the  following and using Beijing installation. Its heat based installation.

nexus3.onap.org:10001/onap/sparky-be             1.2.1

 

Where exactly I can locate this file ? Inside any specific docker ? I tried to search but could not get the portal profile related details inside aai-resources/aai-traversal.

 

From: Arul Nambi [mailto:Arul.Nambi@...] 
Sent: 02 November 2018 16:00
To: 
onap-discuss@...; Chandrashekhar Thakare <CT00548828@...>
Subject: RE: [aai] Standalone AAI UI

 

Hi Chandra,

Are you which version of sparky are you using? If you using the one from master, then you should be able to disable the portal profile from application.properties in backend. This will make sure that you are not redirected to portal for authentication.

Regards

Arul

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of Chandra
Sent: Friday, November 2, 2018 5:21 AM
To: 
onap-discuss@...
Subject: [onap-discuss] [aai] Standalone AAI UI

 

Hi,

I am trying to  access the standalone UI of AAI with below URL-

 

http://<AAI IP address>:9517/services/aai/webapp/index.html

 

However; it is pointing to 

 

 

Is there any way to disable this redirection?

============================================================================================================================

Disclaimer:  This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.

============================================================================================================================

“Amdocs’ email platform is based on a third-party, worldwide, cloud-based system. Any emails sent to Amdocs will be processed and stored using such system and are accessible by third party providers of such system on a limited basis. Your sending of emails to Amdocs evidences your consent to the use of such system and such processing, storing and access”.

“Amdocs’ email platform is based on a third-party, worldwide, cloud-based system. Any emails sent to Amdocs will be processed and stored using such system and are accessible by third party providers of such system on a limited basis. Your sending of emails to Amdocs evidences your consent to the use of such system and such processing, storing and access”.

“Amdocs’ email platform is based on a third-party, worldwide, cloud-based system. Any emails sent to Amdocs will be processed and stored using such system and are accessible by third party providers of such system on a limited basis. Your sending of emails to Amdocs evidences your consent to the use of such system and such processing, storing and access”.

This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service

This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service

 


[ONAP] [community] considerations on gerrit community practices

Morgan Richomme
 

Hi

I would like to share some personnal views on community practices.
I do not pretend that they are all applicable or even the best ones.
Moreover they may differ from one project to another depending on the
code activity, the number of committers and contributors.

Everything can be discussed however the following recommendations
could be useful if we want to stabilize a Master rolling release (i.e.
a Master branch always deployable).

This would save integration time and allow to spend more time on use
cases rather than systematically spending some weeks before the
release to simply get something usable:)

General Gerrit review
*********************
- the same person MUST NOT submit a patch/+2/Merge
- when possible, 2x +2 are required before merge (depends on the number
of committers)
- it is encouraged to have geographically distributed committers (Asia
/ Europe / North America)
- if people submit an incomplete patchset (especially for correction),
it is recommended to submit a new patchest on the existing patch rather
that create a new patch and abandon the initial patch
- abandoning a patch SHALL BE done by the patch owner, and if not
possible by the committer

OOM specific review
*******************
- +2/Merge shall give a chance to the gating...
It means that merge must not be done before the gating has been
finalized (it usually takes 60-90 minutes).
- Gating must be OK prior to merge on Master + onap-ci-windriver CI for
release.

With Dublin we may have the ambition to converge to a rolling release
on master. With gating, we MAY detect any regression if any change
breaks the gate.

Healthcheck tests
*****************
- each component shall provide at least 1 healthcheck robot test.

At the moment we have ~ 240 pods and 32 helm charts
[aaf, aai, appc, cassandra, clamp, cli, consul, contrib, dcae, dmaap,
esr, log, mariadb, msb, multicloud, nbi, oof, policy, pomba, portal,
robot, sdc, sdnc, so, uui, vfc, vid, vnfsdk, prometheus, weave scope]
on one side

and 61 healthcheck tests
[aaf (2), aai, appc, clamp, cli, dcae (3), dmaap (3), log (3),
modeling, msb, multicloud (8), nbi, oof (3), policy, pomba (9), sdc,
sdnc, so, uui, vfc (15), vid, vnfsdk]

When gating we check that the pods are Running (onap-k8s tests) then
the healthcheck robot tests..
Healthcheck SHALL indicate that the component is running as expected
(applicative verification).
Project MUST maintain these tests and ensure their evolutions if
needed (API evolution, HTTPS support, ...).

Misc
****
- more CSIT should be provided (it was asked by Catherine some weeks
ago) and integrated in Gating
- CIST MUST be to be executed on a k8s environemet (added to gating
chain)!
- components that are not involved directly on ONAP and not used by
any use cases SHOULD be considered as addons and not be part of the
release. Healthcheck SHOULD be run accordingly. It will lighten the
solution and limit the surface of attack.

Could be a topic for next DDF...

Morgan

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

5621 - 5640 of 22692