Description of problem:
The support of fenceSpmStorage on the vdsm side was left only for backward compatibility. It's time to discuss the removal on the engine side as well.
We must keep this call for older engines, so we gain nothing but uneeded complexity on the engine side by removing the call on the vdsm side.
And we loose the ability to do something useful when this call issue issued in future version.
(In reply to Nir Soffer from comment #2)
> We must keep this call for older engines, so we gain nothing but uneeded
> complexity on the engine side by removing the call on the vdsm side.
That's why this bug is filed on ovirt-engine-backend. This RFE is indeed intended to simplify the engine side, th current fenceSpmStorage is useless and should be removed.
> And we loose the ability to do something useful when this call issue issued
> in future version.
Currently in the fashion that it's used on the engine side and how it's implemented on the vdsm side is useless.
Whenever we'll decide to have this again we'll implement it properly on the vdsm side and we'll call it appropriately from engine side, now it's only pollution.
Verified on :
oVirt Engine Version: 3.5.0-0.0.master.20140804172041.git23b558e.el6
vdsm Version: vdsm-4.16.1-6.gita4a4614.el6.x86_64
The scenario I used to verify it was :
- a system up and running with 2 hosts.
- on the spm host , I've killed vdsms and supervdsd .
- on the GUI , I've clicked "confirm host was rebooted"
- on the engine.log, I saw that "FenceVdsManualyCommand" was triggered,
and "fenceSpmStorage" was not .
RHEV-M 3.5.0 has been released, closing this bug.