[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Cluster-devel] skipping unused services, cman_tool join -A

On Thu, Jan 28, 2010 at 09:11:06AM +0000, Christine Caulfield wrote:
> So, let me get this straight. For a cman upgrade you want to load the 
> same services as before. But for a new full-featured RHEL6 cluster suite 
> you think we should load fewer services, thus removing features ?

Exactly, removing unnecessary features is one of the nicest features we
can add IMO!

> To me it seems like a pointless bit of added complication, for us and 
> users. If the service is still to be shipped then what do we gain by 
> simply making it more difficult to use? So far Perry's argument is that 
> we don't *ship* things we can't support, thus preventing people from 
> using them at all unless they compile it themselves. But this is 
> different in that we have to ship the openais modules anyway, so 
> disabling them is merely being wilfully obscure. It's a bit like 
> shipping a command-line tool that was in RHEL5, but on RHEL6 insists on 
> having the first parameter "PLEASE" before it will do anything.
> I'm not really passionately in favour of either way, I just don't see 
> any benefit to us, or (more importantly) to customers, from changing it.

We were trying to stick to technical issues and leave all the "support"
issues to higher-ups, but support is clearly part of it.  This came up
because we do not want to support these other services in any official
way, I've been told.  So, the step of not loading these services is a
first, small, necessary step toward not supporting them.  Next, others can
sort out whether a product should leave out the services, or include with
caveats, or something else...

I'm not passionately in favor of either way either, I was just trying to
help sort our the technical steps involved in unsupporting them.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]