when will the fence device fence_rhevm will be supported in rhev3.0 ?

Latest response

I want to create  a rhcs   HA  cluster  in rhev3.0 vm guest ,  Now there is no fence device I could select , except  manual fence , is the fence_rhevm supported in rhev 3.0 ?  and how  to configure rhcs to use the fence device ?

 

Does anyone test this fence device in rhev3.0 ?

w3
Log in to join the conversation

Responses

rh Red Hat Guru 1569 points
20 December 2011 3:55 PM

fence_rhevm is actually a cluster suite package it is a fencing agent which can be used with RHEV-M REST API to fence virtual machines.

 

 

The fencing configuration should be done in RHCS same as you configure other fence agents, and not in RHEV-Manager itself. The fencing devices list that you are seeing in RHEV Manager is for fencing hosts and not virtual machines that run RHCS. You will have to know your VM names in RHEV manager,  and the REST API admin password to provide during configuration.

 

As for the supported matrix ATM there are the following references, however it does not include RHEV3.0 as it's not GA yet:

https://access.redhat.com/kb/docs/DOC-30003

https://access.redhat.com/kb/docs/DOC-30004

w3 Active Contributor 250 points
29 June 2012 10:41 AM

use fence_rhevm    default  timeout value  failed to fence off  and fence on a vm 

 

 

Operation timed out after 3000 milliseconds with 0 bytes received
Connection timed out

 

using following parameters  success :

 

fence_rhevm -a 192.168.0.253 -l admin@internal -p redhat -z -4 -u 8443 -n node1 -o on --power-wait 5 --power-timeout 25  --shell-timeout 25 --retry-on 3 -v

 

192.168.0.253  rhevm  ip address  ,  vm name node1

 

[root@node2 ~]# fence_rhevm -a 192.168.0.253 -l admin@internal -p redhat -z -4 -u 8443 -n node1 -o off --power-wait 5 --power-timeout 25  --shell-timeout 25  -v

Success: Powered OFF

 

 

 

ssl is needed

fence without ssl  can not work :

[root@node2 ~]# fence_rhevm -a 192.168.0.253 -l admin@internal -p redhat  -4 -u 8080 -n node1 -o on -v
vms/?search=name%3Dnode1

Failed: Unable to obtain correct plug status or plug is not available

w3 Active Contributor 250 points
29 June 2012 10:41 AM

use fence_rhevm    default  timeout value  failed to fence off  and fence on a vm 

 

 

Operation timed out after 3000 milliseconds with 0 bytes received
Connection timed out

 

using following parameters  success :

 

fence_rhevm -a 192.168.0.253 -l admin@internal -p redhat -z -4 -u 8443 -n node1 -o on --power-wait 5 --power-timeout 25  --shell-timeout 25 --retry-on 3 -v

 

192.168.0.253  rhevm  ip address  ,  vm name node1

 

[root@node2 ~]# fence_rhevm -a 192.168.0.253 -l admin@internal -p redhat -z -4 -u 8443 -n node1 -o off --power-wait 5 --power-timeout 25  --shell-timeout 25  -v

Success: Powered OFF

 

 

 

ssl is needed

fence without ssl  can not work :

[root@node2 ~]# fence_rhevm -a 192.168.0.253 -l admin@internal -p redhat  -4 -u 8080 -n node1 -o on -v
vms/?search=name%3Dnode1

Failed: Unable to obtain correct plug status or plug is not available

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.