the time.
New development should go into the main branch. The main branch will be
pulled into the 3.0 branch for each 3.0.X-rc1, but otherwise, if a
change is needed for a release branch, a separate PR should backport
it.
--
Ken Gaillot
___
Manage your
>
> Any suggestions are appreciated!
> Dennis LaCroix
>
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/developers
>
> ClusterLabs home: https://www.clusterlabs.org/
--
Ken Gaillot
t; TEL: 995 32 225 05 90
> Mob: 995 593 14 00 37
> tso...@grena.ge
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
> Therefore, I think this is really just a documentation issue and I
> think it should be amended to state that "sid" should be the name of
> a (dedicated) tnsnames.ora entry for the service to tnsping.
>
> Cheers,
> Adrian.
>
>
> -Original Message-
&g
d in this
> paragraph are incorporated in England and Wales and share the same
> registered office at Grant Way, Isleworth, Middlesex TW7 5QD
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/developers
>
something
to play with and provides a framework for future additions.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
On Mon, 2023-01-09 at 09:37 -0600, Ken Gaillot wrote:
> Hi,
>
> I do think the idea is good. I've commented on the pull request with
> some technical issues. It would be an API compatibility break, but
> coincidentally I'm planning such a break for a release at the end of
t* data, struct set *array);
> > void init_array(struct set **array);
> > void insert_children(pe_resource_t * rsc, struct set *hashTable);
> >
> > Existing functions have also been changed: pcmk__unpack_constraints
> > (initialization
rictions so
that the agent can automatically detect when the node becomes healthy
again.
* We would have a framework for adding new types if the need arises.
Thoughts?
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinf
lusters from Scratch" document
linked on this page:
https://clusterlabs.org/pacemaker/doc/
By the way, the us...@clusterlabs.org list is better for this sort of
question. It's a lot more active than this one, which is just for
discussing software development.
--
Ken Gaillot
fork
called Phorge that is getting up and running, which we'll switch to
once it's stable.)
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
; # pcs constraint location nginx-lb prefers redis-lb2=50
>
> # pcs cluster stop --all
>
> # pcs cluster start --all
>
>
> Shall i have to provide the port number of Redis configuration(6379)
> that was setup in load balancers while creating
lly detect when the node becomes healthy again.
* We would have a model for adding new types when needed.
Thoughts?
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
> I am wondering if this change was intentional, or a bug introduced by
> some other change. I believe its a bug since crmadmin -h still exits
> with 0.
>
> Gerry Sommerville
> ___
> Manage your subscription:
> https
ee that this may seem too specific of a use case, but we think
> that
> such an option could be a benefit in some cases. Maybe there is even
> an
> application beyond all_squash NFS exports that we are not thinking
> of.
>
> Lars Ellenberg kindly volunteered to implement such a
is back online 100%.
> >
> > Fabio
> > ___
> > Manage your subscription:
> > https://lists.clusterlabs.org/mailman/listinfo/developers
> >
> > ClusterLabs home: https://www.clusterlabs.org/
> _
ast week of December.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
there anything I'm
forgetting or overlooking?
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
and implementing the
capability.
This will generally not matter to anyone, but if you want to run "make
check", as of the next release (2.1.2) you will have to install the
cmocka development files (libcmocka-devel in rpm world and libcmocka-
dev in deb world).
--
K
with each other.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
for the 2.1.0
release.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
be part of the original code. Any
> thoughts?
>
> Vladimir Yanakiev
> Unix Engineer, Hosting & Engineering Services – Solution Engineering
> Compute
> Phone: 703-833-3770 (direct) | 571-246-1946 (mobile)
I think it's a great enhan
).
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
On Tue, 2021-01-19 at 18:02 -0500, Digimer wrote:
> On 2021-01-19 4:34 p.m., Ken Gaillot wrote:
> > Hi all,
> >
> > Does anyone remember what ClusterLabs project is using Github's
> > Large
> > File Storage (https://git-lfs.github.com/)?
> >
> > The
.2.GB).
I vaguely remember someone wanting that capability, but I don't
remember the project(s). That project will need to either move away
from LFS, or cough up for a data plan.
If no one remembers, I can ask their support.
--
Ken Gaillot
___
M
and
regenerate them, e.g.:
rm -rf aclocal.m4 autom4te.cache config.guess config.log config.status \
config.sub configure depcomp install-sh libltdl libtool ltmain.sh \
missing py-compile test-driver
./autogen.sh
./configure
--
Ken Gaillot
> Sent from Mail for Windows 10
>
> From: Ken Gaillot
> Sent: 01 December 2020 03:01
> To: developers@clusterlabs.org
> Subject: Re: [ClusterLabs Developers] shutdown testing in pacemaker
> corosync cluster
>
> On Sun, 2020-11-29 at 14:21 +, Harishkumar Pathangay wrote:
ease let me know any further information required from my side.
>
> Thanks,
> Harish P
> YouTube.com/db2luwacademy
>
> Sent from Mail for Windows 10
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
.
--
Ken Gaillot
From 3d1a7dc0c545c1ffba216df5c82b5ee3e3c7b3bf Mon Sep 17 00:00:00 2001
From: Ken Gaillot
Date: Fri, 9 Oct 2020 09:56:03 -0500
Subject: [PATCH 1/7] Log: executor: show CRM_OP_REGISTER rc in debug message
Previously, process_lrmd_signon() would add the rc to the client reply
gt; > [CC+ cluster-devel]
> >
> > On 19/10/2020 23:59, Ken Gaillot wrote:
> > > On Mon, 2020-10-19 at 07:19 +0200, Fabio M. Di Nitto wrote:
> > > > Hi Ken,
> > > >
> > > > On 10/2/2020 8:02 PM, Digimer wrote:
>
g other nodes and resources up and running?
> 2. which config file crm_node command reads?
>
> Thanks,
>
> Jiaqi Tian
>
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/ma
On Mon, 2020-10-19 at 07:19 +0200, Fabio M. Di Nitto wrote:
> Hi Ken,
>
> On 10/2/2020 8:02 PM, Digimer wrote:
> > On 2020-10-02 1:12 p.m., Ken Gaillot wrote:
> > > Hi all,
> > >
> > > I sent a message to the us...@clusterlabs.org list about
>
g
it with 2.1.0 (since it has bigger changes than usual, and we can get
ahead of the curve) or waiting until the dust settles and future
conventions are clearer.
Opinions?
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
n relating to this
> issue.
> Thanks,
>
> - Hayden
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/developers
>
> ClusterLabs home: https://www.clusterlabs.org/
--
Ken Gaillot
_
ar Tummala
> Associate Consultant
> AWS Professional Services
> +91.998.950.9121 – mobile
> Thoughts on our interaction? Provide feedback here.
>
> ___________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/developers
>
of that
resource to ensure they can't run unless scsi access is available.
In a modern cluster, the first approach is preferred, and even if the
second approach is used, some sort of node-level fencing should be
configured as well (otherwise it relies on the cluster functioning
properly on a node that
curious
how Pacemaker 2.0.4 compares to 2.0.1 using your CIB -- there were some
improvements in that time.
> The version of Pacemaker we us is 2.0.1+20190417.13d370ca9 (release
> 3.6.1).
>
> Thanks a lot in advance!
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
On Thu, 2020-02-13 at 00:15 +0100, Jehan-Guillaume de Rorthais wrote:
> On Wed, 12 Feb 2020 15:17:01 -0600
> Ken Gaillot wrote:
>
> > On Wed, 2020-02-12 at 16:03 +0100, Jehan-Guillaume de Rorthais
> > wrote:
> > > Hello devs,
> > >
> >
On Thu, 2020-02-13 at 15:11 +0100, Jehan-Guillaume de Rorthais wrote:
> On Wed, 12 Feb 2020 15:11:41 -0600
> Ken Gaillot wrote:
> ...
> > > INT_MAX would set the working interval to ±2GB. Producing 2GB of
> > > worth of data
> > > in few seconds/minutes is p
in the futur? I'm not sure how I would be able to contribute to these
> features,
> at least with tests, maybe some code, but it really depend how hard
> it would be
> and how much time I can find to work on this.
>
> Regards,
--
Ken Gaillot
___
RA, we trigger an error in next expected
> action based
> on decision taken during the notify action.
>
> Thoughts?
>
> Regards,
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
e (which would be called before starting any
instances), and then on one instance selected to be promoted, another
new action (like "bootstrap") would be called to do some initial start-
up that all instances need, before the cluster started all the other
instances normally (whether
g it. Which we should do :)
There is some room for coming up with better option naming and meaning.
For example maybe the cluster-wide "maintenance-mode" should be
something like "force-maintenance" to make clear it takes precedence
over node and resource maintenance.
>
> Regards,
>Yan
>
> >
> > Please share your opinion about the issue, if we should leave it
> > working
> > as is or enforce the most specific rule in though the whole
> > cluster. And
> > give a priority to either one of the conflicting attributes (is-
> > managed
> > vs maintenance).
> >
> > Best regards,
> > Aleksei Burlakov
> > SUSE Senior Developer
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
Now that we're finished with the 2.0.3 release, new pacemaker pull
requests should be submitted against the master branch. Thanks,
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home
for the 2.0.3
release.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
and all of them should. Agents can get as
specific as they like with exit reasons.
- Agents can also log to the system log, or print error output which
pacemaker will log in its detail log. Many already provide good
information this way, but there's always room for improvement.
--
Ken Gaillot
__
Pokorný wrote:
> Neither bugs.c.o nor lists.c.o work for me ATM.
> Either it resolves by itself, or Ken will intervene, I believe.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLab
nces of
split brain depend on your workload. Something like a database or
cluster filesystem could become horribly corrupted.
>
>
> Thanks,
> Rohit
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/developers
ClusterLabs home: https://www.clusterlabs.org/
On Fri, 2019-06-14 at 23:57 +0200, Jan Pokorný wrote:
> On 14/06/19 14:56 -0500, Ken Gaillot wrote:
> > On Fri, 2019-06-14 at 20:13 +0200, Jan Pokorný wrote:
> > > > On Thu, 2019-06-06 at 10:12 -0500, Ken Gaillot wrote:
> > > >
> > > > Source cod
On Fri, 2019-06-14 at 20:13 +0200, Jan Pokorný wrote:
> > On Thu, 2019-06-06 at 10:12 -0500, Ken Gaillot wrote:
> >
> > Source code for the Pacemaker 2.0.2 and 1.1.21 releases is now
> > available:
> >
> >
https://github.com/ClusterLabs/pacemaker/releases
: improve CPG
membership messages
d0c12d98e01bc6228fc254456927d79a46554448 Fix: libcrmcommon: avoid use-of-NULL
when checking whether process is active
c0e1cf579f57922cbe872d23edf144dd2206156b Low: libcrmcommon: return proper code
if testing pid is denied
--
Ken Gaillot
ivecommons.org/licenses/by/4.0/
>
> Cheers,
> Kristoffer
>
> >
> > > On 09/21/2017 04:42 PM, Ken Gaillot wrote:
> > >
> > >> On Thu, 2017-09-21 at 11:56 +0200, Kai Dupke wrote:
> > >> - I would like to see the logo used by as many
&g
just mention them
here or to me directly.
On Wed, 2019-04-10 at 17:44 -0500, Ken Gaillot wrote:
> Hello all,
>
> Florian Haas and Kristoffer Grönlund noticed that the ClusterLabs
> organization on github currently carries over any app access that
> members have given to the
Since 2.0.2 is primarily a security release, all pull requests should
continue to be submitted against the master branch, with the exception
of fixes for regressions introduced in 2.0.2.
I'm hoping to minimize the number of release candidates and release the
final in about a month.
--
Ken
existing apps' access as
well as some individual contributors' ssh key access to the
repositories. If you are affected, you can simply re-upload your ssh
key and it will work again.
I'll wait a couple of weeks before implementing this change in case
anyone wants to raise concerns.
--
Ken Gaillot
On Fri, 2019-04-05 at 17:19 +0200, Lars Ellenberg wrote:
> On Fri, Apr 05, 2019 at 09:56:51AM -0500, Ken Gaillot wrote:
> > On Fri, 2019-04-05 at 09:44 -0500, Ken Gaillot wrote:
> > > On Fri, 2019-04-05 at 15:50 +0200, Lars Ellenberg wrote:
> > > > As mentioned in #cl
On Fri, 2019-04-05 at 09:44 -0500, Ken Gaillot wrote:
> On Fri, 2019-04-05 at 15:50 +0200, Lars Ellenberg wrote:
> > As mentioned in #clusterlabs,
> > but I think I post it here, so it won't get lost:
> >
> > pacemaker 1.1.19, in case that matters.
> >
> >
pgrade when some
nodes have the new capability and some don't).
It's certainly doable but a medium-sized project. If there are
volunteers I can give some pointers :) but there's quite a backlog of
projects at the moment.
> b) migration-theshold (and possibly other scores) should be properly
> parsed
it with Beekhof, so I'll update
files with his notice to the new format, and also contact other people
as needed for other files.
--
Ken Gaillot
___
Developers mailing list
Developers@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo
On Mon, 2019-02-11 at 17:01 -0600, Ken Gaillot wrote:
> On Mon, 2019-02-11 at 22:48 +0100, Jan Pokorný wrote:
> > On 20/01/19 12:44 +0100, Jan Pokorný wrote:
> > > On 18/01/19 20:32 +0100, Jan Pokorný wrote:
> > > > It was discovered that this release of glib pr
in
> crm_simulate),
> either pacemaker prior to 2.0.1 combined with glib pre- or equal-or-
> post-
> 2.59.0 need to be uniformly (reproducers need to follow the original)
> combined to get the same results, and with pacemaker 2.0.1+,
> identical
> results (but possibly differing against either of the former combos)
> will _likely_ be obtained regardless of particular run-time linked
> glib
> version, but strength of this "likely" will only be established with
> future experience, I suppose (but shall universally hold with the
> same
> glib class per stated division, so no change in this already positive
> regard).
>
> Just scratched the surface, so gladly be corrected.
--
Ken Gaillot
___
Developers mailing list
Developers@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/developers
On Tue, 2019-02-05 at 18:24 +0100, Gao,Yan wrote:
> On 2/5/19 7:50 AM, Kristoffer Grönlund wrote:
> > On Mon, 2019-02-04 at 18:43 -0600, Ken Gaillot wrote:
> > > Hi all,
> > >
> > > Anyone who works on the Pacemaker code base might be interested
> > >
make it easier to change the implementation
without breaking backward compatibility.
This is all just a proposal, and we can use the pull request and this
thread to discuss any suggested changes to the scheme.
--
Ken Gaillot
___
Developers mailing l
ps://github.com/ClusterLabs/pacemaker/tree/master/tools
>
> Thanks!
> Vinod
>
> On Mon, Feb 4, 2019 at 8:57 AM Ken Gaillot
> wrote:
> > On Sun, 2019-02-03 at 08:44 -0800, Vinod Chegu wrote:
> > > Hello,
> > >
> > > 'am new to this fo
instead, at the cost of creating an additional dependency for your
tool.
For alerts, you can have pacemaker call a Python script with
interesting info passed as environment variables. See:
http://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html-single/Pacemaker_Explained/index.html#i
On Fri, 2019-01-18 at 18:53 +0100, Lars Ellenberg wrote:
> On Thu, Jan 17, 2019 at 09:09:11AM +1100, Andrew Beekhof wrote:
> >
> >
> > > On 17 Jan 2019, at 2:59 am, Ken Gaillot
> > > wrote:
> > >
> > > I'm not familiar with the reasoning fo
abled them since they got really out of date and aren't actively
maintained. Our docs are updated more frequently than they used to be,
so any translators would have a nontrivial ongoing commitment. We could
use something like zanata.org to make contributing easi
tags_); \
> + } \
> + if (descriptor_pt && (descriptor_pt->targets || \
> + qb_bit_set(descriptor_pt->tags, \
> + QB_LOG_TAG_LIBQB_MSG_BIT))) \
> +
for the 2.0.1
release.
--
Ken Gaillot
___
Developers mailing list
Developers@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/developers
On Thu, 2018-11-01 at 16:41 -0500, Ken Gaillot wrote:
> This would affect most applications using libpe_status.
>
> I ran into a situation recently where a fix would require changing
> libpe_status's pe_working_set_t data type.
>
> For most data types in the Pacemaker API, w
example,
would reasonably be a package dependency that we wouldn't want to
require for all installations. So, maybe the resource-agents package
could separate into resource-agents-core (for all agents with minimal
dependencies), and separate resource-agents-X pack
, or has an opinion on the problem and solution here.
In case anyone's interested, the fix that inspired this has its own PR:
https://github.com/ClusterLabs/pacemaker/pull/1609
--
Ken Gaillot
___
Developers mailing list
Developers@clusterlabs.org
https
with respect to above.
>
>
> Thanks,
> Rohit
That's probably the best way available currently. You could copy the
source code of cibadmin and modify it to do the query in a loop until
successful, if you wanted to make it more convenient.
--
Ken Gaillot
__
Now that we're finished with the 2.0.0 / 1.1.19 release cycle, all
pacemaker pull requests should be submitted against the master branch.
--
Ken Gaillot
___
Developers mailing list
Developers@clusterlabs.org
https://lists.clusterlabs.org/mailman
should be sufficient for most applications, but as there
were API changes from 1.1.x to 2.0.0, some applications may need code
changes (typically simple search-and-replace). If compiling against the
new libraries fails, see:
https://wiki.clusterlabs.org/wiki/Pacemaker_2.0_API_Changes
--
Ken Gaillot
y open, so it's a question of "picking your poison" which
> doesn't
> make a strong "move" argument.
>
> I vote to just hang tight, say for 3~6 months, then start a new
> thread
> to discuss further.
+1
I'd wait until
"true". The old syntax will be supported for at least the lifetime of
the 2.0.x series, but if you create or modify clone syntax, you should
update it to handle the new syntax as soon as possible.
What has NOT changed with the daemon names: the public C API, including
library nam
bugs.linuxfoundation.org/buglist.cgi?product=Pacemaker
CLBZ - ClusterLabs bugzilla - https://bugs.clusterlabs.org/
RHBZ - Red Hat bugzilla - https://bugzilla.redhat.com/
BSC - SuSE bugzilla - https://bugzilla.suse.com/index.cgi
Sometimes you'll see bz without anything more spe
e who submit pull requests
and the developers who review them by necessity are primarily familiar
with their own use cases, and it really helps to have other users'
viewpoints.
--
Ken Gaillot <kgail...@redhat.com>
___
Developers mailing list
Developers@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/developers
er will look if they're confused about why there are two
agents.
If the new agent becomes the clear preference, we can eventually add a
"deprecated" notice to the old agent's description. (And if the
proposed OCF overhaul ever comes to fruition, there may be a form
r names or preferences? (Or
> reasons to keep the current LVM-activate name?).
>
> Thanks,
> Chris
--
Ken Gaillot <kgail...@redhat.com>
___
Developers mailing list
Developers@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/developers
> > > - galera: fix for MariaDB 10.1.21+
> > > > > > - mysql: set correct master score after maintenance mode
> > > > > > - ocf-shellfuncs: improve locking (ocf_take_lock())
> > > > > > - pgsql: add support for PostgreSQL 10
> > >
will be accepted only to backport
commits from 2.0 or master. This will mainly be of use to anyone who
wants to continue using heartbeat or corosync 1 as the cluster layer,
or anyone who wants to stay on the 1.1.18 version for a while longer,
but cherry-pick newer changes.
--
Ken Gaillot <kg
.
--
Ken Gaillot <kgail...@redhat.com>
___
Developers mailing list
Developers@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/developers
uot;false" to continue to allow
that.
I think the schema approach is still an option. We could do something
like:
--
Ken Gaillot <kgail...@redhat.com>
___
Developers mailing list
Developers@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/developers
On Tue, 2017-08-29 at 16:50 -0500, Ken Gaillot wrote:
> On Tue, 2017-08-29 at 22:55 +0200, Jehan-Guillaume de Rorthais wrote:
> > Hi all,
> >
> > We discussed this issue with Ken Gaillot and Lars Ellenberg today
> on IRC. This
> > is just a sum up of the problem.
&
On Tue, 2017-08-29 at 22:55 +0200, Jehan-Guillaume de Rorthais wrote:
> Hi all,
>
> We discussed this issue with Ken Gaillot and Lars Ellenberg today on IRC. This
> is just a sum up of the problem.
>
> Some users reported me that the PAF RA was not promoting the master after a
On Fri, 2017-07-28 at 09:04 +0200, Jan Pokorný wrote:
> On 27/07/17 17:40 -0500, Ken Gaillot wrote:
> > On Thu, 2017-07-27 at 23:26 +0200, Jan Pokorný wrote:
> >> On 24/07/17 17:59 +0200, Valentin Vidic wrote:
> >>> On Mon, Jul 24, 2017 at 09:57:01AM -0500, Ken Gail
On Thu, 2017-07-27 at 23:26 +0200, Jan Pokorný wrote:
> On 24/07/17 17:59 +0200, Valentin Vidic wrote:
> > On Mon, Jul 24, 2017 at 09:57:01AM -0500, Ken Gaillot wrote:
> >> Are you sure you have pacemaker 1.1.17 inside the container as well? The
> >> pi
d form any pacemaker_remoted
running on the underlying host when running ps.
--
Ken Gaillot <kgail...@redhat.com>
___
Developers mailing list
Developers@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/developers
On 07/19/2017 01:20 AM, Valentin Vidic wrote:
> Another issue with the rkt containers is the port-mapping. Each container
> defines exposed ports:
>
> "ports": [
> {
> "name": "http",
> "protocol": "tcp",
>
On 07/18/2017 03:36 PM, Valentin Vidic wrote:
> On Tue, Jul 18, 2017 at 10:22:40PM +0200, Valentin Vidic wrote:
>> And idea what could be the problem here?
>
> I also could not start multiple rkt containers either, but the problem
> seems to be duplicate id values. After fixing these it looks
On 07/17/2017 02:44 PM, Valentin Vidic wrote:
> Hello devs,
>
> Following the bundle release in 1.1.17, I've been working on a
> similar implementation for rkt. Resource agent based on docker
> is here:
>
> https://github.com/vvidic/resource-agents/blob/rkt/heartbeat/rkt
>
> That part should
On 07/07/2017 05:58 AM, Swati Smaranika Kar wrote:
> Hi Team,
>
>
>
> I am new to Pacemaker and Corosync. As a developer I was looking through
> the code of it.
>
>
>
> While configuring a resource on a node with CLI command : (pcs resource
> create Cluster_VIP11 ocf:heartbeat:IPadd)
>
>
FYI, now that we're done with the 1.1.17 release cycle, all Pacemaker
pull requests should be made against the master branch again.
--
Ken Gaillot <kgail...@redhat.com>
___
Developers mailing list
Developers@clusterlabs.org
http://lists.clusterla
On 02/14/2017 02:51 PM, Nils Carlson wrote:
> Hi,
>
> I'm working on implementing a MariaDB resource-agent based on the mysql
> one.
> The idea is to take advantage of new features in MariaDB, especially
> semi-synchronous replication and GTID.
>
> GTID (Global Transaction ID) means that there
On 11/03/2016 02:37 PM, Adam Spiers wrote:
> Hi again Ken,
>
> Sorry for the delayed reply, caused by Barcelona amongst other things ...
>
> Ken Gaillot <kgail...@redhat.com> wrote:
>> On 10/21/2016 07:40 PM, Adam Spiers wrote:
>>> Ken Gaillot <kgail...@r
On 11/09/2016 09:57 AM, Jehan-Guillaume de Rorthais wrote:
> Hi,
>
> It seems OCF_ERR_ARGS has different meanings according to documentations:
>
>
> http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-ocf-return-codes.html
> «The resource’s configuration is not valid
testing feedback in the next few weeks is greatly appreciated.
--
Ken Gaillot <kgail...@redhat.com>
___
Developers mailing list
Developers@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/developers
On 10/21/2016 07:40 PM, Adam Spiers wrote:
> Ken Gaillot <kgail...@redhat.com> wrote:
>> On 09/26/2016 09:15 AM, Adam Spiers wrote:
>>> [Sending this as a separate mail, since the last one was already (too)
>>> long and focused on specific details, whereas this o
1 - 100 of 120 matches
Mail list logo
