Thank you!
For reference, all I had to do was, on the oVirt hosted engine, run:
# yum install -y fence-agents-amt-ws
# engine-config -s CustomVdsFenceType="amt_ws"
# engine-config -s CustomVdsFenceOptionMapping="amt_ws:port=ipport"
# engine-config -s CustomFencePowerWaitParam="amt_ws=power_wait"
On Tue, May 15, 2018 at 6:50 PM, Shawn Southern wrote:
> Thanks for this!
>
> I’ve got fence_amt_ws working fine, however the document you linked
> mentions creating a script, and I’m not sure how I’m to pass the various
> parameters (host to fence, etc.) to this script. From the doc, I'm lookin
On Tue, May 15, 2018 at 11:20 AM, Martin Perina wrote:
>
>
> On Mon, May 14, 2018 at 8:13 PM, Shawn Southern <
> shawn.south...@entegrus.com> wrote:
>
>> I'm now using Intel AMT and the wsmancli package to reboot/power
>> off/power on my entry level systems... but now I want oVirt to use this for
Thanks for this!
I’ve got fence_amt_ws working fine, however the document you linked mentions
creating a script, and I’m not sure how I’m to pass the various parameters
(host to fence, etc.) to this script. From the doc, I'm looking at:
engine-config -s CustomVdsFenceType="amt"
engine-config -
On Mon, May 14, 2018 at 8:13 PM, Shawn Southern wrote:
> I'm now using Intel AMT and the wsmancli package to reboot/power off/power
> on my entry level systems... but now I want oVirt to use this for fencing.
>
> I created 3 xml files: powercycle.xml (uses PowerState 10), poweron.xml
> (uses Powe
5 matches
Mail list logo