Red Hat Bugzilla – Bug 280191
fencing agents should be broken out into sub-packages
Last modified: 2010-12-21 11:35:30 EST
Description of problem:
cman contains a lot of fencing agents, all of which have their own set of
dependencies, e.g. as discussed in Bug 189668 fence-ilo depends on
perl-Crypt-SSLeay. Chris Feist pointed out that adding all these dependencies to
the cman package isn't really viable since that would add a huge chain of
dependencies to satisfy all the agents while a typical installation only uses
one or two of those. It might be better (as suggested by Bryn) to break out each
fencing agent into it's own (sub)-package and give each sub-package it's own set
Version-Release number of selected component (if applicable):
[root@localhost ~]# /sbin/fence_ilo
Net::SSL.pm or Net::SSLeay::Handle.pm not found.
Please install the perl-Crypt-SSLeay package from RHN (http://rhn.redhat.com)
or Net::SSLeay from CPAN (http://www.cpan.org)
My only thought against this is that it complicates manual installation of a
cluster environment (need to know about and then install the correct agents).
Since the users will need to configure an appropriate agent anyway it's maybe
not that big a deal.
Although having full dependencies declared will easy life for those with highly
automated deploy environments that rely on yum/anaconda to pull in all needed
Also, shouldn't this be filed against the fence component rather than cman?
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.
If this bug still exists in rawhide, please change the version back to
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)
Thanks for your help and we apologize for the interruption.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
I guess there is no consensus on whether the fencing agents really should be
broken out or not but to answer the comment above, all of the agents still are
in cman-2.0.60-5 so I'm changing the version back to rawhide.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
i don't think it is wise to break fence agents in their own subpackages. I agree
that there a bunch of extra dependencies to install (not that many anymore) but
we have no easy way to tell our users what fence agents they will need to
install and it will make the installation and deployment one step more complicated.
I'd like to close this one as WONTFIX.
No comments in about 20 days. Closing as suggested (WONTFIX). Please reopen if
you want to discuss the issue further.
what about introducing meta-package which depends on all fence-agents subpackages and is installed by default? By groups mechanism f.e.
Also every fence-agent subpackage could introduce virtual "feature", on which cman could depend.
Require: fence-agent-1 fence-agent-2 fence-agent-3 ...
Provides: fence agent
Group(Cluster): cman, fence-agents
This way X drivers are packaged I assume.
(In reply to comment #9)
> what about introducing meta-package which depends on all fence-agents
> subpackages and is installed by default? By groups mechanism f.e.
> Also every fence-agent subpackage could introduce virtual "feature", on which
> cman could depend.
> I mean:
> fence-agents (meta)
> Require: fence-agent-1 fence-agent-2 fence-agent-3 ...
At the stage in which fence agents are now developed upstream, this is an overkill and useless process. It could have been (maybe) a gain few years back when this bug was initially discussed, but with today's code it is a pointless and very expensive operation.