On Fri, 2014-01-17 at 09:15 +1100, Andrew Beekhof wrote: > On 17 Jan 2014, at 9:05 am, Lars Marowsky-Bree <l...@suse.com> wrote: > > > On 2014-01-17T07:40:34, Andrew Beekhof <and...@beekhof.net> wrote: > > > >>> Well, unless RHT states that installing crmsh on top of their > >>> distribution invalidates support for the pacemaker back-end, you could > >>> just ship crmsh as part of your product on that platform. > >> Thats not how RHT operates I'm afraid. If something isn't at least > >> planned to be supported, they don't ship it. > > > > Right, and I very much understand that. > > > > The question was if installing crmsh on top of RHEL/RHCS (as he's doing > > now) would invalidate support for the rest of the system. And I can't > > answer that. > > If some behaviour specific to crmsh (or the mixing of the two) was > triggering a bug, that /may/ result in the fix being given lower > priority for inclusion.
> I can also imagine support wanting to ensure issues are reproducible > with pcs prior to accepting them. Fair enough. I would expect to submit issues that are reproducible with "pcs". This is how I arrived at the VirtualDomain issue that was submitted today. > But I'd not think using crmsh would completely invalidate support > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
