Heatbridge inventories cloud resources (like VMs) in AAI. Find below the
payload that I used back in Casablanca and it worked.
{
"input": {
"common-header": {
"timestamp": "{{serverDate}}",
"api-ver": "2.00",
"originator-id": "{{orginatorId}}",
"request-id": "Postman",
"sub-request-id": "Postman",
"flags": {
"mode": "NORMAL",
"force": "TRUE",
"ttl": 36000
}
},
"action": "Stop",
"action-identifiers": {
"vnf-id": "{{vnf-id}}",
"vserver-id":"{{vserver-id}}"
},
"payload":
"{\"vm-id\":\"{{vm-id}}\",\"identity-url\":\"{{identity-url}}\",\"tenant-id\":\"{{tenant-id}}\"}"
}
}
This is how I set my Postman to resolve the parameters:
pm.globals.set("vnf-id","5fe35a12-cc39-49e6-9e68-44fd2f4c5045");
pm.globals.set("vserver-id","7a03d64f-c1fc-4373-b11c-15426b9724cc");
pm.globals.set("vm-id","7a03d64f-c1fc-4373-b11c-15426b9724cc");
pm.globals.set("identity-url","http://X.Y.Z.W:5000/v2.0<http://x.y.z.w:5000/v2.0>");
pm.globals.set("tenant-id","3f2aaef74ecb4b19b35e26d0849fe9a2");
Marco
On Jul 23, 2019, at 10:17 AM, Rajendra P Mishra (RP)
<[email protected]<mailto:[email protected]>> wrote:
Marco, Taka, thanks for the pointer.
I ran heatbridge and it PASSED all the tests. I still get the '450' error.
I was curious to know what exactly does heatbridge do ?
Do we really need vnfc for LCM stop ?
Here is my json file.
----------
{
"version": "2.00",
"rpc-name": "stop",
"correlation-id": "a20e2073-30b1-4357-893b-f5ed57b66ef0-10",
"type": "request",
"body": {
"input": {
"common-header": {
"timestamp": "2019-07-23T06:40:30.44Z",
"api-ver": "2.00",
"originator-id": "SDNGP",
"request-id": "OpenSTACK",
"sub-request-id": "stop10",
"flags": {
"force": "TRUE",
"ttl": 60000
}
},
"action": "Stop",
"action-identifiers": {
"vnf-id":
"097d2826-1949-4ad8-ab4f-dc2e27e94022",
"vserver-id":
"820b13c4-4649-475d-a421-28dfe6257c90"
},
"payload":
"{\"vm-id\":\"http://192.168.37.14:8774/v2.1/servers/820b13c4-4649-475d-a421-28dfe6257c90\<https://urldefense.proofpoint.com/v2/url?u=http-3A__192.168.37.14-3A8774_v2.1_servers_820b13c4-2D4649-2D475d-2Da421-2D28dfe6257c90-255C&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=XaA-67QK-cMW4zIh1CrFKV85SNiBgYhBaC9H7tj3DLU&s=wTYZN0PX_xqGiT5X0nxgXvkBqs1fnzeKZ_geXdYDCoc&e=>",
\"identity-url\":\"http://192.168.37.14:5000/v3\<https://urldefense.proofpoint.com/v2/url?u=http-3A__192.168.37.14-3A5000_v3-255C&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=XaA-67QK-cMW4zIh1CrFKV85SNiBgYhBaC9H7tj3DLU&s=11Zr5HRg_eeUGmgfqs1gHXw-PF76dPp74l1gb1qI11A&e=>",
\"tenant-id\": \"5a7c7f86fcaa418f83be664f921bf4ee\",
\"skip-hypervisor-check\":\"true\"}"
}
}
}
----------
I even tried the other version of payload
----
"payload":
"{\"vm-id\":\"http://192.168.37.14:8447/v2.1/5a7c7f86fcaa418f83be664f921bf4ee/servers/820b13c4-4649-475d-a421-28dfe6257c90\<https://urldefense.proofpoint.com/v2/url?u=http-3A__192.168.37.14-3A8447_v2.1_5a7c7f86fcaa418f83be664f921bf4ee_servers_820b13c4-2D4649-2D475d-2Da421-2D28dfe6257c90-255C&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=XaA-67QK-cMW4zIh1CrFKV85SNiBgYhBaC9H7tj3DLU&s=enm3FI8VrGXvVFXAjqblyLlppb-TB84z8DzQ4s_iuLg&e=>",
\"identity-url\":\"http://192.168.37.14:5000/v3\<https://urldefense.proofpoint.com/v2/url?u=http-3A__192.168.37.14-3A5000_v3-255C&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=XaA-67QK-cMW4zIh1CrFKV85SNiBgYhBaC9H7tj3DLU&s=11Zr5HRg_eeUGmgfqs1gHXw-PF76dPp74l1gb1qI11A&e=>",
\"tenant-id\": \"5a7c7f86fcaa418f83be664f921bf4ee\",
\"skip-hypervisor-check\":\"true\"}"
----
Log file is attached.
thanks,
-RP
On Tue, Jul 23, 2019 at 12:09 AM PLATANIA, MARCO (MARCO)
<[email protected]<mailto:[email protected]>> wrote:
Rajendra,
Please run heat bridge after you install the VNF, it seems that VNF-C aspects
aren’t found because not set in AAI.
Marco
On Jul 22, 2019, at 12:50 PM, Rajendra Prasad Mishra
<[email protected]<mailto:[email protected]>> wrote:
Hi Taka, Steve,
I am facing exactly the same problem as mentioned by Steve on Casablanca
release. While doing "stop" LCM operation I get the 450 error.
As I understood from the the email chain, the problem was due to
"capability-test" not passing.
I see in the email thread that the error was somehow resolved. Can you please
share the recipe for the fix.
I do not have a VNFC, hope that is not causing the problem. My vnf is the
simple vLB (load balancer with DNS).
Here is the snippet of the log .
---------------------------------
2019-07-22T12:26:38,994 | INFO | appc-dispatcher-4 | ConfigResourceNode
| 509 - appc-config-data-services - 1.4.4 | CONFIGTYPE=
2019-07-22T12:26:38,994 | INFO | appc-dispatcher-4 | ConfigResourceNode
| 509 - appc-config-data-services - 1.4.4 | tmp.vnfInfo.vm-count=3
2019-07-22T12:26:38,994 | INFO | appc-dispatcher-4 | ConfigResourceNode
| 509 - appc-config-data-services - 1.4.4 | skip-hypervisor-check=true
2019-07-22T12:26:38,994 | INFO | appc-dispatcher-4 | ConfigResourceNode
| 509 - appc-config-data-services - 1.4.4 | request-action=Stop
2019-07-22T12:26:38,995 | INFO | appc-dispatcher-4 | ConfigResourceNode
| 509 - appc-config-data-services - 1.4.4 | input.action=Stop
2019-07-22T12:26:38,995 | INFO | appc-dispatcher-4 | ConfigResourceNode
| 509 - appc-config-data-services - 1.4.4 |
tmp.vnfInfo.vnf.ipv4-oam-address=10.10.10.100
2019-07-22T12:26:38,995 | INFO | appc-dispatcher-4 | ConfigResourceNode
| 509 - appc-config-data-services - 1.4.4 | configuration-params=
2019-07-22T12:26:38,995 | INFO | appc-dispatcher-4 | ConfigResourceNode
| 509 - appc-config-data-services - 1.4.4 | VNFCNAME0=
2019-07-22T12:26:38,995 | INFO | appc-dispatcher-4 | ConfigResourceNode
| 509 - appc-config-data-services - 1.4.4 | template-name=
2019-07-22T12:26:38,995 | INFO | appc-dispatcher-4 | ConfigResourceNode
| 509 - appc-config-data-services - 1.4.4 |
tmp.vnfInfo.vm[1].tenant-id=5a7c7f86fcaa418f83be664f921bf4ee
2019-07-22T12:26:38,995 | INFO | appc-dispatcher-4 | ConfigResourceNode
| 509 - appc-config-data-services - 1.4.4 |
getVnfcFunctionCodeForVserver()::vnfcFunctionCode=null
20ppc-config-data-services - 1.4.4 | processCapabilitiesForVMLevel() ::
vnfcFunctionCode is not present in context!!!
| 509 - appc-config-data-services - 1.4.4 | getCapability Successful
19-07-22T12:26:38,996 | INFO | appc-dispatcher-4 | ConfigResourceNode
| 509 - appc-config-data-services - 1.4.4 |
processCapabilitiesForVMLevel() :: vnfcFunctionCode is not present in context!!!
2019-07-22T12:26:38,996 | INFO | appc-dispatcher-4 | ConfigResourceNode
| 509 - appc-config-data-services - 1.4.4 | getCapability Successful
.
.
.
2019-07-22T12:26:39,000 | INFO | appc-dispatcher-4 | SvcLogicServiceImpl
| 222 - org.onap.ccsdk.sli.core.sli-provider - 0.3.3 | About to execute
node # 47 (execute)
2019-07-22T12:26:39,011 | INFO | appc-dispatcher-4 | SvcLogicExprListener
| 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.3 | Outcome (success)
not found, keys are { (failure)}
2019-07-22T12:26:39,011 | INFO | appc-dispatcher-4 | SvcLogicExprListener
| 221 - org.onap.ccsdk.sli.core.sli-common - 0.3.3 | Outcome (Other) not
found, keys are { (failure)}
2019-07-22T12:26:39,036 | INFO | appc-dispatcher-4 | audit
| 458 - appc-common-bundle - 1.4.4 | APPC0090A Operation "Stop" for VNF
type "097d2826-1949-4ad8-ab4f-dc2e27e94022" from Source "SDNGP" with RequestID
"386d0f72-5495-4a50-b7fc-7e4003d8335c" was started at "2019-07-22T12:26:37Z"
and ended at "2019-07-22T12:26:39Z" with status code "450"
---------------------------------
thanks,
-RP
<appc14.log>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18260): https://lists.onap.org/g/onap-discuss/message/18260
Mute This Topic: https://lists.onap.org/mt/31641303/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]]
-=-=-=-=-=-=-=-=-=-=-=-
