Bug 595383

Simple example of using the REST API to stop a VM:

---
#!/bin/bash

VM_STOP_URI="vms/9/stop"

HOST="localhost"
PORT="8099"
BASE="/rhevm-api-mock/"
USER="Aladdin"
PASSWD="open sesame"

b64()
{
    u="$1"; shift
    p="$1"; shift
    t=$(mktemp)
    echo -n "$u:$p" > $t
    base64 $t
    rm -f $t
}

AUTH=$(b64 "$USER" "$PASSWD")

nc $HOST $PORT <<EOF
POST $BASE$VM_STOP_URI HTTP/1.1
Host: $HOST
Authorization: Basic $AUTH
Content-type: application/xml
Content-length: 9

<action/>
EOF
---

or if you use wget:

---
wget --header=Accept:application/xml --header=Content-Type:application/xml --http-user=$USER --http-password=$PASSWD --post-data="<action/>" http://$HOST:$PORT/$BASE$VM_STOP_URI
---

(In reply to comment #1)
> Simple example of using the REST API to stop a VM:

Fence agent needs to ensure machine is really down, would successful execution (200 response code I assume?) of this service guarantee that VM is really killed?

Fence agents are only as reliable/good as the devices they connect to.  We have the same issue for example with power fence devices.  i.e. you connect to a power fence device and tell it to shut down the host.  You have to trust that when the hardware device returns success that it told the truth.

Now that being said, we usually do a combination of 'device off' and then 'status' to verify that the device did turn off.  So we'll do the same for fence_rhev, calling 'power off vm' and waiting for status 200.  And then calling 'status vm' to double check that the vm turned off.

If the API lies to us... well, let's just make sure the API is functionally correct :)

qa_ack+

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The package has been updated to provide a fencing agent that is able to communicate with Red Hat Enterprise Virtualization Manager, allowing virtual machines to be fenced.

*** Bug 548595 has been marked as a duplicate of this bug. ***

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0745.html