Greetings,
In Fedora 11, the fencing agents (think power control) have been moved into a package called 'fence-agents'. This change also has moved the agents from /sbin to /usr/sbin.
Since cobbler should run on a Fedora 11 and earlier distros, I've changed the power templates to use relative paths instead of absolute? That seems the best approach, but just curious on other opinions?
Thanks, James
--- cobbler/action_check.py | 2 +- templates/power_apc_snmp.template | 2 +- templates/power_bladecenter.template | 2 +- templates/power_bullpap.template | 2 +- templates/power_drac.template | 2 +- templates/power_ilo.template | 2 +- templates/power_ipmilan.template | 2 +- templates/power_lpar.template | 2 +- templates/power_rsa.template | 2 +- templates/power_wti.template | 3 +-- 10 files changed, 10 insertions(+), 11 deletions(-)
diff --git a/cobbler/action_check.py b/cobbler/action_check.py index 717dd23..3085e6e 100644 --- a/cobbler/action_check.py +++ b/cobbler/action_check.py @@ -90,7 +90,7 @@ class BootCheck: def check_for_cman(self, status): # not doing rpm -q here to be cross-distro friendly if not os.path.exists("/sbin/fence_ilo") and not os.path.exists("/usr/sbin/fence_ilo"): - status.append("fencing tools were not found, and are required to use the (optional) power management features. install cman to use them") + status.append("fencing tools were not found, and are required to use the (optional) power management features. install fence-agents to use them") return True
def check_service(self, status, which, notes=""): diff --git a/templates/power_apc_snmp.template b/templates/power_apc_snmp.template index 002a45e..92053a8 100644 --- a/templates/power_apc_snmp.template +++ b/templates/power_apc_snmp.template @@ -1 +1 @@ -/usr/local/sbin/fence_apc_snmp -a $power_address -n $power_id -o $power_mode +fence_apc_snmp -a $power_address -n $power_id -o $power_mode diff --git a/templates/power_bladecenter.template b/templates/power_bladecenter.template index d350fa5..cae7673 100644 --- a/templates/power_bladecenter.template +++ b/templates/power_bladecenter.template @@ -1 +1 @@ -/sbin/fence_bladecenter -x -a $power_address -l $power_user -p $power_pass -n $power_id -o $power_mode +fence_bladecenter -x -a $power_address -l $power_user -p $power_pass -n $power_id -o $power_mode diff --git a/templates/power_bullpap.template b/templates/power_bullpap.template index 7de92a6..836a7a2 100644 --- a/templates/power_bullpap.template +++ b/templates/power_bullpap.template @@ -1 +1 @@ -/sbin/fence_bullpap -a $power_address -l $power_user -p $power_pass -d $power_id -o $power_mode +fence_bullpap -a $power_address -l $power_user -p $power_pass -d $power_id -o $power_mode diff --git a/templates/power_drac.template b/templates/power_drac.template index 6e6d8a7..979028c 100644 --- a/templates/power_drac.template +++ b/templates/power_drac.template @@ -1 +1 @@ -/sbin/fence_drac -a $power_address -l $power_user -p $power_pass -m $power_id -o $power_mode +fence_drac -a $power_address -l $power_user -p $power_pass -m $power_id -o $power_mode diff --git a/templates/power_ilo.template b/templates/power_ilo.template index c7ce6b4..a62d4a1 100644 --- a/templates/power_ilo.template +++ b/templates/power_ilo.template @@ -1,2 +1,2 @@ -/sbin/fence_ilo -a $power_address -l $power_user -p $power_pass -o $power_mode +fence_ilo -a $power_address -l $power_user -p $power_pass -o $power_mode
diff --git a/templates/power_ipmilan.template b/templates/power_ipmilan.template index ba92faf..410034c 100644 --- a/templates/power_ipmilan.template +++ b/templates/power_ipmilan.template @@ -1 +1 @@ -/sbin/fence_ipmilan -i $power_address -l $power_user -p $power_pass -o $power_mode +fence_ipmilan -i $power_address -l $power_user -p $power_pass -o $power_mode diff --git a/templates/power_lpar.template b/templates/power_lpar.template index e7ce89e..7915179 100644 --- a/templates/power_lpar.template +++ b/templates/power_lpar.template @@ -1,3 +1,3 @@ #set ($power_sys, $power_lpar) = $power_id.split(':')
-/sbin/fence_lpar -a $power_address -l $power_user -p $power_pass -x -s $power_sys -n $power_lpar -o $power_mode +fence_lpar -a $power_address -l $power_user -p $power_pass -x -s $power_sys -n $power_lpar -o $power_mode diff --git a/templates/power_rsa.template b/templates/power_rsa.template index 4fc4cc9..5344d74 100644 --- a/templates/power_rsa.template +++ b/templates/power_rsa.template @@ -1 +1 @@ -/sbin/fence_rsa -a $power_address -l $power_user -p $power_pass -o $power_mode +fence_rsa -a $power_address -l $power_user -p $power_pass -o $power_mode diff --git a/templates/power_wti.template b/templates/power_wti.template index ab819b0..c696d8d 100644 --- a/templates/power_wti.template +++ b/templates/power_wti.template @@ -1,2 +1 @@ -/sbin/fence_wti -a $power_address -n $power_id -p $power_pass -o $power_mode - +fence_wti -a $power_address -n $power_id -p $power_pass -o $power_mode
On 05/05/2009 07:05 PM, James Laska wrote:
status.append("fencing tools were not found, and are required to use the (optional) power management features. install cman to use them")
status.append("fencing tools were not found, and are required to use the (optional) power management features. install fence-agents to use them")
Will the fence-agents package land in other Fedora/EPEL repositories, or will EL5 for example still have to use cman?
-Jasper
Jasper Capel wrote:
On 05/05/2009 07:05 PM, James Laska wrote:
status.append("fencing tools were not found, and are required to use the (optional) power management features. install cman to use them")
status.append("fencing tools were not found, and are required to use the (optional) power management features. install fence-agents to use them")
Will the fence-agents package land in other Fedora/EPEL repositories, or will EL5 for example still have to use cman?
-Jasper _______________________________________________ cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
I'd expect they will still need cman, though we should ask if we can get those split out. I'll track down the package owner. --Michael
Michael DeHaan wrote:
Jasper Capel wrote:
On 05/05/2009 07:05 PM, James Laska wrote:
status.append("fencing tools were not found, and are required to use the (optional) power management features. install cman to use them")
status.append("fencing tools were not found, and are required to use the (optional) power management features. install fence-agents to use them")
Will the fence-agents package land in other Fedora/EPEL repositories, or will EL5 for example still have to use cman?
-Jasper _______________________________________________ cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
I'd expect they will still need cman, though we should ask if we can get those split out. I'll track down the package owner. --Michael
cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
Thinking about this further, I don't see them changing for a dot release.
On Tue, 2009-05-05 at 14:05 -0400, Michael DeHaan wrote:
Michael DeHaan wrote:
Jasper Capel wrote:
On 05/05/2009 07:05 PM, James Laska wrote:
status.append("fencing tools were not found, and are required to use the (optional) power management features. install cman to use them")
status.append("fencing tools were not found, and are required to use the (optional) power management features. install fence-agents to use them")
Will the fence-agents package land in other Fedora/EPEL repositories, or will EL5 for example still have to use cman?
-Jasper _______________________________________________ cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
I'd expect they will still need cman, though we should ask if we can get those split out. I'll track down the package owner. --Michael
cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
Thinking about this further, I don't see them changing for a dot release.
I was debating changing the message to include both 'fence-agents' and 'cman', but thought that might just be too confusing.
Thanks, James
James Laska wrote:
On Tue, 2009-05-05 at 14:05 -0400, Michael DeHaan wrote:
Michael DeHaan wrote:
Jasper Capel wrote:
On 05/05/2009 07:05 PM, James Laska wrote:
status.append("fencing tools were not found, and are required to use the (optional) power management features. install cman to use them")
status.append("fencing tools were not found, and are required to use the (optional) power management features. install fence-agents to use them")
Will the fence-agents package land in other Fedora/EPEL repositories, or will EL5 for example still have to use cman?
-Jasper _______________________________________________ cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
I'd expect they will still need cman, though we should ask if we can get those split out. I'll track down the package owner. --Michael
cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
Thinking about this further, I don't see them changing for a dot release.
I was debating changing the message to include both 'fence-agents' and 'cman', but thought that might just be too confusing.
Thanks, James
cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
If we require fence-agents when appropriate (which is what I just changed) I think we can have the warning message just mention about cman.
The only problem would be is if another non-Red Hat based distro didn't require fence-agents when appropriate also, which is why I held off doing that just now.
Is the package also "cman" for Debian and SuSE, for instance? I'd assume it is, though when/if that becomes fence-agents, not sure.
--Michael
James Laska wrote:
Greetings,
In Fedora 11, the fencing agents (think power control) have been moved into a package called 'fence-agents'. This change also has moved the agents from /sbin to /usr/sbin.
Since cobbler should run on a Fedora 11 and earlier distros, I've changed the power templates to use relative paths instead of absolute? That seems the best approach, but just curious on other opinions?
Thanks, James
Yes, seems like it.
I also seem to require a bug about check not knowing that they have moved, so it will have to look for both paths.
--Michael
Michael DeHaan wrote:
James Laska wrote:
Greetings,
In Fedora 11, the fencing agents (think power control) have been moved into a package called 'fence-agents'. This change also has moved the agents from /sbin to /usr/sbin.
Since cobbler should run on a Fedora 11 and earlier distros, I've changed the power templates to use relative paths instead of absolute? That seems the best approach, but just curious on other opinions?
Thanks, James
Yes, seems like it.
I also seem to require a bug about check not knowing that they have moved, so it will have to look for both paths.
--Michael _______________________________________________ cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
All merged in.
I also updated the cobbler spec so it will require fence-agents on F11, to save folks the trouble of dealing with that check msg. We can't require cman because it's not part of a standard channel on RHEL, you have to have Cluster Suite entitlements to get cman there.
I also tweaked the specfile to require yum-utils where we know it's available (i.e. RHEL 5 and later, any Fedora) so we can have reposync installed automagically in most places.
--Michael
cobbler-devel@lists.fedorahosted.org