Marco,

The functionality works fine for us, by hardcoding the vm-id in the DG and 
adding the raw in the DB, I was able to start/stop/restart. 

The two main pain points are:
- (potentially fixed) inserting raw to the DB table. But that should be done 
automatically as Taka pointed out, so we’ll look at what happened during the 
table load.
- (ongoing) the vm-id isn’t being picked up by the DG, even though it’s 
provided in the payload. This one is still ongoing, we need to figure it out.

Thanks,
Alexis

> On May 16, 2019, at 11:24 AM, PLATANIA, MARCO (MARCO) 
> <[email protected]> wrote:
> 
> 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 <[email protected]>
> Date: Thursday, May 16, 2019 at 11:16 AM
> To: onap-discuss <[email protected]>, Alexis de Talhouët 
> <[email protected]>
> Cc: "PLATANIA, MARCO (MARCO)" <[email protected]>, BRIAN FREEMAN 
> <[email protected]>, "[email protected]" 
> <[email protected]>, "CHO, TAKAMUNE" <[email protected]>
> 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 
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__Lists.Onap.Org&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=9fu5mSsdAurCcvgfR9kNWVHyHeloXipPlswROe2F50Q&s=05zl3tyMa4MF-rCrv3sw1HyRtufecVDDe6Zs3TuRfqk&e=>
>>  <[email protected] 
>> <mailto:[email protected]>> wrote:
>>
>>
>> 
>> 
>>> On May 16, 2019, at 11:09 AM, PLATANIA, MARCO (MARCO) 
>>> <[email protected] <mailto:[email protected]>> 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"
>>        },
>>        "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_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=9fu5mSsdAurCcvgfR9kNWVHyHeloXipPlswROe2F50Q&s=7ovr4jbRzMlDvy_RQQcWcbO-DjsPJXcZHhAFxghhWZ4&e=>"}"
>>     }
>> }
>>
>>
>> <Screen Shot 2019-05-16 at 11.13.10 AM.png>
>> 
> 
>
> <vm_actions.xlsx>


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#17098): https://lists.onap.org/g/onap-discuss/message/17098
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]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to