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'T'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: [email protected] <[email protected]> On Behalf Of
Alexis de Talhouet
Sent: Thursday, May 16, 2019 10:03 AM
To: onap-discuss <[email protected]>; FREEMAN, BRIAN D
<[email protected]>
Cc: [email protected]
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"
},
"payload": "{\"vm-id\":
\"http://10.195.194.213:8774/v2.1/7320ec4a5b9d4589ba7c4412ccfd290f/servers/c82153dc-8d84-4e69-9673-5e0a60030779\<https://urldefense.proofpoint.com/v2/url?u=http-3A__10.195.194.213-3A8774_v2.1_7320ec4a5b9d4589ba7c4412ccfd290f_servers_c82153dc-2D8d84-2D4e69-2D9673-2D5e0a60030779-255C&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=hTElw4KhmXvkYLsMZSEpVTUxYDRu2Qzr-D9LW1PMTz8&s=Cn1zUPVPY0ZL_uiYb7Vsi_GuLcN28P-h2YyZM8nbn7I&e=>"}"
}
}
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 (input.payload), value ({"vm-id":
"http://10.195.194.213:8774/v2.1/7320ec4a5b9d4589ba7c4412ccfd290f/servers/c82153dc-8d84-4e69-9673-5e0a60030779<https://urldefense.proofpoint.com/v2/url?u=http-3A__10.195.194.213-3A8774_v2.1_7320ec4a5b9d4589ba7c4412ccfd290f_servers_c82153dc-2D8d84-2D4e69-2D9673-2D5e0a60030779&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=hTElw4KhmXvkYLsMZSEpVTUxYDRu2Qzr-D9LW1PMTz8&s=f7UcOtaWM8fmR7_8M6uvtYs7g6nhEx_VSR7u7OyxQxk&e=>"})
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 <[email protected]<mailto:[email protected]>>
wrote:
Hoepfully your payload is matching one of these examples
https://wiki.onap.org/display/DW/APPC+ONAP+Testing+Requests<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_APPC-2BONAP-2BTesting-2BRequests&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=i5VHNTZ3SDPgIii87sudZA&m=hTElw4KhmXvkYLsMZSEpVTUxYDRu2Qzr-D9LW1PMTz8&s=vyMGm5_0shX05ncBnE7rbFs_IXH0fByanI3rs4iOSP4&e=>
Brian
From: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>> On Behalf Of
FREEMAN, BRIAN D
Sent: Wednesday, May 15, 2019 4:37 PM
To: [email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>
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: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>> On Behalf Of
Steve Siani
Sent: Wednesday, May 15, 2019 4:01 PM
To: FREEMAN, BRIAN D <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
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!
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17083): https://lists.onap.org/g/onap-discuss/message/17083
Mute This Topic: https://lists.onap.org/mt/31222663/21656
Mute #appc: https://lists.onap.org/mk?hashtag=appc&subid=2740164
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-