Hello Steve,
Are you sure that Pacemaker is the right product for your project? Have you
checked Mesos/Marathon or Kubernates? Those are frameworks being developed
for managing containers.
On Sat Feb 07 2015 at 1:19:15 PM Steven Dake (stdake)
wrote:
> Hi,
>
> I am working on Containerizing Op
I solved the issue:
I had to configure resrouce-stickness option to 0 and now whatever hosts I
reboot the resources are back and stay like this:
ClusterVIP:0 (ocf::heartbeat:IPaddr2): Started haproxy01
ClusterVIP:1 (ocf::heartbeat:IPaddr2): Started haproxy02
Rega
On Fri, Feb 06, 2015 at 04:15:44PM +0100, Dejan Muhamedagic wrote:
> Hi,
>
> On Thu, Feb 05, 2015 at 09:18:50AM +0100, Digimer wrote:
> > That is the problem that makes geo-clustering very hard to nearly
> > impossible. You can look at the Booth option for pacemaker, but that
> > requires two (or
On Mon, Feb 09, 2015 at 10:53:00AM +, Jorge Lopes wrote:
> Hi Dejan,
> Thanks for the tip.
>
> Concerning the timeout values, what would be the ticket renewal typical
> values for a production environment?
We have two parameters: expire and renewal. The latter used to be
set to half of the fo
Hi Dejan,
Thanks for the tip.
Concerning the timeout values, what would be the ticket renewal typical
values for a production environment?
Thanks,
Jorge
>
>On Sun, Feb 08, 2015 at 07:06:13PM +, Jorge Lopes wrote:
>> Hi all,
>>
>> I'm performing a lab test were I have a geo cluster and an arb
Hi,
On Sun, Feb 08, 2015 at 07:06:13PM +, Jorge Lopes wrote:
> Hi all,
>
> I'm performing a lab test were I have a geo cluster and an arbitrator, in a
> configuration for disaster recovery with fail over. There are two main
> sites (primary and disaster recovery) and a third site for arbitrat
Hello,
I'd like to ask about following problem that troubles me for some time
and I wan't able to find solution for:
I've got cluster with quite a lot of resources, and when I try to do
multiple operations at time, I get a lot of resource failures (ie
failed starts)
The only related information
Hi Kristoffer,
Thank you for the help.
I will let you know if I see the same with the latest version.
On Feb 9, 2015 10:07 AM, "Kristoffer Grönlund" wrote:
> Hi,
>
> Kostiantyn Ponomarenko writes:
>
> > Hi guys,
> >
> > I saw this during applying the configuration using a script with crmsh
> >
Hi,
Kostiantyn Ponomarenko writes:
> Hi guys,
>
> I saw this during applying the configuration using a script with crmsh
> commands:
The CIB patching performed by crmsh has been a bit too sensitive to
CIB version mismatches which can cause errors like the one you are
seeing. This should be fix
