> Here is the output of `pcs status` before powering off the primary:
>
> --
> Online: [ d-gp2-dbpg0-1 d-gp2-dbpg0-2 d-gp2-dbpg0-3 ]
>
> Full list of resources:
>
> vfencing (stonith:external/vcenter): Started d-gp2-dbpg0-1
> postgresql-master-vip
t; fence_sanbox2 - Fence agent for QLogic SANBox2 FC switches
> fence_sbd - Fence agent for sbd
> fence_scsi - Fence agent for SCSI persistentl reservation
> fence_tripplite_snmp - Fence agent for APC, Tripplite PDU over SNMP
> fence_vbox - Fence agent for VirtualBox
> fence_virsh - Fenc
n_timeout=60
> power_wait=3 op monitor interval=60s
>
> This results in the following error:
>
> Error: Unable to create resource 'stonith:fence_vmware_soap', it is
> not installed on this system (use --force to override)
>
> In the output of `pcs stonith list`, I see:
&g
ng its own fence
device (which would be almost pointless). There was a distant time when
such a constraint was a requirement for fencing to work, but now it's
just for monitoring.
I'm not familiar with VMware fencing, so I can't comment on the
specifics of the agents ...
>
> Thank you in adva
and appreciated.
Many thanks to all contributors of source code to this release,
including Gao,Yan, Hideo Yamauchi, Jan Pokorný, and Ken Gaillot.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterla
6
> Skype: georgemelikov
>
> С наилучшими пожеланиями,
> Георгий Меликов,
> m...@gmelikov.ru
> Моб: +7 9152783936
> Skype: georgemelikov
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterl
ck yet. I'm using Ubuntu 16
> so it may happen to just work better on your RHEL instances. If you
> have a different ESX version than 6.0, you may have better luck as
> well.
>
> Best wishes,
--
Ken Gaillot <kgail...@redhat.com>
___
; Thanks
> Niraj Singh
Hi Niraj,
There are no "official" ansible playbooks for pacemaker and corosync
that I'm aware of, but various users have made some available online.
It's an area I'd like to see more attention given to, but unfortunately
I per
> throttling is to keep Pacemaker from overloading the nodes such that
> actions might start timing out, causing unnecessary recovery.
>
>
> lkxjtu
> 邮箱：lkx...@163.com
> 签名由 网易邮箱大师 定制
>
>
>
--
Ken Gaillot <kgail...@redhat.com>
___
ht start timing out, causing unnecessary
recovery.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
G
h) the cluster
may choose to move the resource back to that node. That's one reason
failures aren't automatically cleaned after a successful start
elsewhere. Also, keeping the failure allows an administrator to notice
that something went wrong, and manually investigate before allowing the
node to host the r
7-3951 邮箱：xuxiao...@highgo.com
>
>
> 发件人： xuxiao...@highgo.com
> 发送时间： 2018-04-26 16:33
> 收件人： 范国腾; wangliang; shaodaming
> 主题： message+pglog
>
>
>
> 祝工作顺利！
> --
> 徐晓菲 产品检测部
> 瀚高基础软件股份有限公司
> 网址：www.highgo.com
> 地址：济南市高新区新泺大街2117号
, but pcmk_monitor_timeout would apply when the
fencing daemon needs to execute a monitor action on its own (which
probably doesn't happen often).
> Thanks
> Robert
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@cl
An exception is that stonith-action applies only to fencing initiated
by the cluster. If some external software (e.g. stonith_admin)
initiates a reboot explicitly, it will still be a reboot.
> The log is in the attachment.
> What prevents the stonith resource to be started if we only started
> part of
of the detail log is now
/var/log/pacemaker/pacemaker.log (not directly in /var/log or sharing a
log with corosync).
* Compare the Pacemaker-1.1.18 pacemaker.spec.in file with the new one
to look for any changes you might want to reproduce. There have been
improvements in Python 3 support, etc.
--
Ken
t cover all
possible use cases, so your feedback is important and appreciated.
Many thanks to all contributors of source code to this release,
including Andrew Beekhof, Gao,Yan, Hideo Yamauchi, Jan Pokorný, and Ken
Gaillot.
--
Ken Gaillot <kgail...@redhat.com>
__
best way is via a github pull request at:
https://github.com/ClusterLabs/pcs
If you are not familiar with github, or can't go that route for
whatever reason, let us know.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterla
; > minutes after the cluster starts.
> >
> > Why is there about 15 minutes delay every time?
>
> This was a bug in Pacemaker up to 1.1.17. I did a report about this
> last August and Ken Gaillot fixed it few days later in 1.1.18. See:
>
> https://lists.clusterlabs.or
t; useful
> > to check a basic sanity of the custom agents:
> > https://github.com/ClusterLabs/resource-agents/tree/master/tools/oc
> ft
>
>
> I did run ocf-tester and the result was passed. Here I carefully read
> the log. When this error was printed in the log, the late
ce/VIP stuff does, but you probably want
to write your own OCF resource agent (see IPaddr2 as an example) to
manage the IP, and let Pacemaker call it as needed.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs
it.
What log messages do you see from corosync and pacemaker indicating
that the node is down? Do you have fencing configured and tested?
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
https://lists.clus
l-ha pgsqld notify=true
> interleave=true;
>
>
> Sometimes it reports the following error, how to configure to avoid
> it?
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.o
On Wed, 2018-04-11 at 08:49 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot <kgail...@redhat.com> schrieb am 09.04.2018 um
> > > > 19:10 in Nachricht
>
> <1523293841.5734.7.ca...@redhat.com>:
> > Based on the list discussion and feedback I
e_state[@uname='xxx-a']/transient_attributes: OK (rc=0,
> origin=xxx-b/crmd/88, version=0.164.37)
>
> This the repeats forevermore ...
>
> Thanks for any hints,
>
> cheers,
>
> Stefan
--
Ken Gaillot <kgail...@redhat.com>
_
On Tue, 2018-04-10 at 08:50 +0200, Jehan-Guillaume de Rorthais wrote:
> On Tue, 10 Apr 2018 00:54:01 +0200
> Jan Pokorný <jpoko...@redhat.com> wrote:
>
> > On 09/04/18 12:10 -0500, Ken Gaillot wrote:
> > > Based on the list discussion and feedback I cou
On Tue, 2018-04-10 at 00:02 +0200, Jehan-Guillaume de Rorthais wrote:
> On Tue, 03 Apr 2018 17:35:43 -0500
> Ken Gaillot <kgail...@redhat.com> wrote:
>
> > On Tue, 2018-04-03 at 21:46 +0200, Klaus Wenninger wrote:
> > > On 04/03/2018 05:43 PM, Ken Gaillot wrote:
&g
er the convenient 15-character limit anyway.
On Wed, 2018-03-28 at 12:40 -0500, Ken Gaillot wrote:
> Hi all,
>
> Andrew Beekhof brought up a potential change to help with reading
> Pacemaker logs.
>
> Currently, pacemaker daemon names are not intuitive, making it
> difficult to
We do many regression tests and simulations, but we can't cover all
possible use cases, so your feedback is important and appreciated.
Many thanks to all contributors of source code to this release,
including Andrew Beekhof, Gao,Yan, Hideo Yamauchi, Jan Pokorný, and Ken
Gaillot. Thanks also to Fabio DiNitt
onf doesn't exist',
> last-rc-change='Fri Apr 6 13:16:39 2018', queued=0ms, exec=0ms
> ==
>
> We regard this behavior as a problem.
> Is there a way to avoid this behavior?
>
> Regards, Yusuke
Hi Yusuke,
One possibility would be to implement network fabric fencing a
On Tue, 2018-04-03 at 21:46 +0200, Klaus Wenninger wrote:
> On 04/03/2018 05:43 PM, Ken Gaillot wrote:
> > On Tue, 2018-04-03 at 07:36 +0200, Klaus Wenninger wrote:
> > > On 04/02/2018 04:02 PM, Ken Gaillot wrote:
> > > > On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guill
On Tue, 2018-04-03 at 21:33 +0200, Jehan-Guillaume de Rorthais wrote:
> On Mon, 02 Apr 2018 09:02:24 -0500
> Ken Gaillot <kgail...@redhat.com> wrote:
> > On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guillaume de Rorthais
> > wrote:
> > > On Sun, 1 Apr 2018 09:01:15 +03
On Tue, 2018-04-03 at 08:33 +0200, Kristoffer Grönlund wrote:
> Ken Gaillot <kgail...@redhat.com> writes:
>
> > > I
> > > would vote against PREFIX-configd as compared to other cluster
> > > software,
> > > I would expect that daem
mplify things but
> perhaps not.
Groups are easier to follow if you have simple colocation+order
sequences.
Sets can help with more complicated set-ups, but they are tricky to get
right and always difficult to read.
--
Ken Gaillot <kgail...@redhat.com>
e.
> --
> Sam Gardner
> Trustwave | SMART SECURITY ON DEMAND
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clu
On Tue, 2018-04-03 at 07:36 +0200, Klaus Wenninger wrote:
> On 04/02/2018 04:02 PM, Ken Gaillot wrote:
> > On Mon, 2018-04-02 at 10:54 +0200, Jehan-Guillaume de Rorthais
> > wrote:
> > > On Sun, 1 Apr 2018 09:01:15 +0300
> > > Andrei Borzenkov <arvidj...@gmail.c
> My questions are:
> > >
> > > 1. is it possible to cancel the fencing request
> > > 2. is it possible reset the node status to "online" ?
> >
> > Not that I'm aware of.
>
> Argh!
>
> ++
You could fix the problem with the sto
,
And show the world your uptime.
Keep serving all the things you can.
Standby your node.
Users list members will vote on all submissions, and the winner will
receive a COMPLETE SET of all available ClusterLabs swag!*
--
Ken Gaillot <kgail...@redhat.com>
* DISCLAIMERS: ClusterLabs current
On Thu, 2018-03-29 at 10:35 +0200, Kristoffer Grönlund wrote:
> Ken Gaillot <kgail...@redhat.com> writes:
>
> > Hi all,
> >
> > Andrew Beekhof brought up a potential change to help with reading
> > Pacemaker logs.
> >
> > Currently,
d, PREFIX-state
crmd: PREFIX-controld, PREFIX-clusterd, PREFIX-controller
lrmd: PREFIX-locald, PREFIX-resourced, PREFIX-runner
pengine: PREFIX-policyd, PREFIX-scheduler
stonithd: PREFIX-fenced, PREFIX-stonithd, PREFIX-executioner
pacemaker_remoted: PREFIX-remoted, PREFIX-remote
--
y to automatically calculate just a portion of the
score.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started
vinash Sharma
>
> On Fri, Feb 23, 2018 at 8:57 PM, Ken Gaillot <kgail...@redhat.com>
> wrote:
> > On Fri, 2018-02-23 at 16:15 +0530, avinash sharma wrote:
> > > Subject: Switchover of resource(MS) 'RoutingManager' and resource
> > > group 'floatingips',
raid that this could be the cause of my resources falling back
> to a node that has recovered from a fail over although I have a
> stickiness score of INFINITY.
>
> Thanks,
> George
> ___
> Users mailing list: Users@clusterlabs.org
>
(c1+c6). Before
starting the db, you want a resource that checks whether the original
config needs repair, and if so, copy it from the backup outside DRBD.
It sounds like you should make a copy of the oracle agent, and modify
its start action to do what you want.
> 2018-03-08 20:12 GMT+01:00 Ken Gaill
will be *probed* on every node (a one-time monitor
action to check whether they are already running there), but they
should only be *started* on allowed nodes.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
http
> be active on the same node. It means that in your case of
> >
> > > id="pcs_rsc_colocation_set_drbdfs_set_drbd.master_inside-interface-
> > sameip.master_outside-interface-sameip.master"
> > score="INFINITY">
> >
> >
&
score="-INFINITY">
>
>
>
The above constraints keep inside-interface on a node where eth1 is
good, and outside-interface on a node where eth2 is good.
I'm guessing you want to keep these two constraints, and start over
from scratch on
list sent by peer for local node
> Mar 20 10:55:45 [26932] pcmk3 pacemakerd: info:
> mcp_cpg_deliver: Ignoring process list sent by peer for local node
> Mar 20 10:55:45 [26932] pcmk3 pacemakerd: error:
> pcmk_child_exit: The crmd process (27037) exited: Key has expired
>
info/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.
> pdf
> Bugs: http://bugs.clusterlabs.org
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing li
into corosync :)
> > > >
> > > > > Regards,
> > > > > Honza
> > > > >
> > > > > >
> > > > > > help would be appreciated, much thanks!
> > > > > >
> > > > > > cheers,
> > > > > > Thomas
> &g
report.
> The question is: is there a sane way to run VMs under pacemaker's
> control? If yes, is it described somewhere?
>
>
> --
> Pavel
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.
r 9 10:10:21 rh74-test pacemakerd[17719]: notice: Respawning
> failed child process: pengine
> Mar 9 10:10:21 rh74-test pacemakerd[17719]: info: Using uid=990
> and group=984 for process pengine
> Mar 9 10:10:21 rh74-test pacemakerd[17719]: info: Forked child
> 1
nt for data integrity.
Native replication would avoid all that.
> 2018-03-07 10:20 GMT+01:00 Klaus Wenninger <kwenn...@redhat.com>:
> > On 03/07/2018 10:03 AM, Mevo Govo wrote:
> > > Thanks for advices, I will try!
> > > lados.
> > >
> >
ttp://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > Bugs: http://bugs.clusterlabs.org
> > ___
> > Users mailing list: Users@clusterlabs.org
> > https://lists.clusterlabs.org/mailman/listinfo/users
> >
> > Project H
发件人: Users [mailto:users-boun...@clusterlabs.org] 代表 Ken Gaillot
> 发送时间: 2018年2月23日 23:14
> 收件人: Cluster Labs - All topics related to open-source clustering
> welcomed <users@clusterlabs.org>
> 主题: Re: [ClusterLabs] 答复: 答复: How to configure to make each slave
> resource has one V
direct access to the original
file rather than a copy.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting
uot;**" \
> shutdown_method="immediate" \
> op monitor interval=30s
>
> pcs -f clust_ora_cfg_tmp constraint colocation add ora_db_xe with
> ora_listener INFINITY
> pcs -f clust_ora_cfg_tmp constraint order promote ora_listener then
> st
bytes received so far)
> [sender] ]
> Feb 21 21:37:40 [24021] IVM-1 lrmd: notice:
> operation_finished: stateful_consul_promote_0:864:stderr [
> rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.2]
> ]
--
Ken Gaillot <kgail...@redhat.com>
rlabs.org/mailman/listinfo/users
> >
> > Project Home: http://www.clusterlabs.org Getting started:
> > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > Bugs: http://bugs.clusterlabs.org
> > ___
> > Users mailing li
ocf:alteeve:server[3396]: 167;
> ocf:alteeve:server invoked.
> Feb 20 07:06:34 m3-a02n02.alteeve.com ocf:alteeve:server[3398]: 1360;
> Command line switch: [migrate_from] -> [#!SET!#]
> Feb 20 07:06:34 m3-a02n02.alteeve.com crmd[2394]: notice
no-quorum-policy=ignore \
> cluster-recheck-interval=30s \
> start-failure-is-fatal=false \
> stop-all-resources=false \
> have-watchdog=false \
> dc-version=1.1.16-94ff4df51a \
> cluster-infrastructure=corosync \
> clu
On Mon, 2018-02-19 at 10:23 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot <kgail...@redhat.com> schrieb am 16.02.2018 um
> > > > 22:06 in Nachricht
>
> <1518815166.31176.22.ca...@redhat.com>:
> [...]
> > It is recommended to run "cibadmi
On Fri, 2018-02-16 at 15:06 -0600, Ken Gaillot wrote:
> Source code for the first release candidate for Pacemaker version
> 2.0.0
> is now available at:
>
> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0
> .0
> -rc1
>
> The main goal of the c
any regression tests and simulations, but we can't cover all
possible use cases, so your feedback is important and appreciated.
Many thanks to all contributors of source code to this release,
including
--
Ken Gaillot <kgail...@redhat.com>
___
User
o. "Pacemaker Explained" applies
equally to all distros.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
onitoring the container itself).
Similarly, you could create a RHEL 6 VM and run it on RHEL 7 cluster
hosts. You can add the remote-node option to the VM resource, to be
able to launch and monitor the app inside it via its resource agent.
--
Ken Gaillot <kgail...@redhat.com>
_
compress_string: Compressed 233922 bytes into 11522
> (ratio 20:1) in 61ms
>
>
>
> ___
> Users mailing list: Users@clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Gettin
be called directly, but
are now named cts-cli, cts-lrmd, cts-pengine, and cts-stonithd.
That's probably all that will be done for 2.0.0. Eventually, I'd like
to make cts-regression the only front end (with an improved interface),
and have all the individual components as Python modules.
--
Ken Gaillot
ce_ec2 and external/ec2
agents, but I'm not familiar with how to get either working.
> - How to do that (sync two or more Amazon EC2s together)?
>
> Thanks in advance
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users
can
revisit the decision.
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.o
On Fri, 2018-01-26 at 09:07 +0100, Jehan-Guillaume de Rorthais wrote:
> On Thu, 25 Jan 2018 15:21:30 -0500
> Digimer <li...@alteeve.ca> wrote:
>
> > On 2018-01-25 01:28 PM, Ken Gaillot wrote:
> > > On Thu, 2018-01-25 at 13:06 -0500, Digimer wrote:
> > >
FYI, we will move the ClusterLabs mailing lists to an upgraded server
this weekend (most likely Sunday). If anyone has problems sending or
receiving mail from the lists next week, feel free to e-mail me
directly (address in signature below).
--
Ken Gaillot <kgail...@redhat.
On Thu, 2018-01-25 at 17:45 +0100, Jehan-Guillaume de Rorthais wrote:
> On Wed, 24 Jan 2018 17:42:56 -0600
> Ken Gaillot <kgail...@redhat.com> wrote:
>
> > On Fri, 2018-01-19 at 00:37 +0100, Jehan-Guillaume de Rorthais
> > wrote:
> > > On Thu, 18 Jan 2018 10:
On Thu, 2018-01-25 at 13:06 -0500, Digimer wrote:
> On 2018-01-25 11:11 AM, Ken Gaillot wrote:
> > On Wed, 2018-01-24 at 20:58 +0100, Jehan-Guillaume de Rorthais
> > wrote:
> > > On Wed, 24 Jan 2018 13:28:03 -0600
> > > Ken Gaillot <kgail...@redhat.com> wrote
On Wed, 2018-01-24 at 20:58 +0100, Jehan-Guillaume de Rorthais wrote:
> On Wed, 24 Jan 2018 13:28:03 -0600
> Ken Gaillot <kgail...@redhat.com> wrote:
>
> > I think there's enough sentiment for "promoted"/"started" as the
> > role
> > names, si
ng than "Slave" (and the other
> > way around).
Correct, "Started" is just the term used with non-master/slave
resources.
"Slave" is almost but not 100% identical to "Started" internally, but
those details can be
_
> Users mailing list: Users@clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.
> pdf
> Bugs: http://bugs.clusterlabs.org
--
yay, first umount, then demote...
>
> (tested with 1.1.15 and 1.1.16, not yet with more recent code base)
>
>
> Full good.xml and bad.xml are both attached.
>
> Manipulating constraint in live cib using cibadmin only:
> add: cibadmin -C -o constraints -X ' then="ms_dr
t@voipserver ~]# drbd-overview
> NOTE: drbd-overview will be deprecated soon.
> Please consider using drbdtop.
>
> 1:r0/0 WFConnection Primary/Unknown UpToDate/DUnknown /replica ext3
> 197G 720M 186G 1%
>
> Secondary
>
> [root@voipserver ~]# drbd-overview
> NOTE: drbd-overview will be deprecated soon.
> Pl
On Wed, 2018-01-17 at 19:19 -0600, Ken Gaillot wrote:
> On Thu, 2017-12-07 at 07:33 +0300, Andrei Borzenkov wrote:
> > 07.12.2017 00:28, Klaus Wenninger пишет:
> > > On 12/06/2017 08:03 PM, Ken Gaillot wrote:
> > > > On Sun, 2017-12-03 at 14:03 +0300, Andrei Borzen
d cluster status:
> Online: [ srv1 srv2 srv3 ]
>
> dummy1 (ocf::heartbeat:Dummy): Started srv2
>
>
>
> Thoughts?
>
> ___________
> Users mailing list: Users@clusterlabs.org
> http://lists.clusterlabs.org/mailman/listi
On Thu, 2018-01-18 at 08:22 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot <kgail...@redhat.com> schrieb am 17.01.2018 um
> > > > 17:04 in Nachricht
>
> <1516205099.5103.3.ca...@redhat.com>:
> > On Wed, 2018-01-17 at 08:32 +0100, Ulrich Windl wro
On Thu, 2017-12-07 at 07:33 +0300, Andrei Borzenkov wrote:
> 07.12.2017 00:28, Klaus Wenninger пишет:
> > On 12/06/2017 08:03 PM, Ken Gaillot wrote:
> > > On Sun, 2017-12-03 at 14:03 +0300, Andrei Borzenkov wrote:
> > > > I assumed that with corosync 2.x quorum is
On Wed, 2018-01-17 at 19:59 +0100, Kristoffer Grönlund wrote:
> Ken Gaillot <kgail...@redhat.com> writes:
>
> >
> > I can see the point, but I do like having separate.
> >
> > A clone with a single instance is not identical to a primitive.
> > Think
&g
On Wed, 2018-01-17 at 11:19 +0100, Kristoffer Grönlund wrote:
> Ken Gaillot <kgail...@redhat.com> writes:
>
> >
> > For Pacemaker 2, I'd like to replace the resource type
> > with
> > . (The old syntax would be transparently
> > upgraded to the new one.
ial 1.1 release.
> On Mon, Jan 15, 2018 at 6:10 PM, Ken Gaillot <kgail...@redhat.com>
> wrote:
> > On Mon, 2018-01-15 at 15:42 -0500, Doug Cahill wrote:
> > > Hello,
> > >
> > > I'm looking for some guidance on pacemaker RPM upgrades in a
> > &
On Wed, 2018-01-17 at 08:32 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot <kgail...@redhat.com> schrieb am 16.01.2018 um
> > > > 23:33 in Nachricht
>
> <1516142036.5604.3.ca...@redhat.com>:
> > As we look to release Pacemaker 2.0 and (separately)
t can operate in two modes, and
we don't care what those two modes do or what they are called natively
by the application. While some applications use master/slave, many have
moved away from those terms, and others have always used other terms,
so it makes sense for us to adopt
_283-0
> Two-node Cluster resources are configured for active/passive
> operation.
>
> Thanks,
> -Doug
On a side note, if you're building 1.1.18 packages yourself, it's a
good idea to use the latest upstream 1.1 branch, because it fixes an
important regression in 1.1.18.
On Mon, 2018-01-15 at 18:08 +0100, Klaus Wenninger wrote:
> On 01/15/2018 05:51 PM, Ken Gaillot wrote:
> > Currently, Pacemaker will use the same detail log as corosync if
> > one is
> > specified (as "logfile:" in the "logging {...}" section of
> > c
On Thu, 2018-01-11 at 10:24 -0600, Ken Gaillot wrote:
> On Thu, 2018-01-11 at 01:21 +0100, Jehan-Guillaume de Rorthais wrote:
> > On Wed, 10 Jan 2018 16:10:50 -0600
> > Ken Gaillot <kgail...@redhat.com> wrote:
> >
> > > Pacemaker 2.0 will be a major
sages in one logfile, or
would you prefer separate logfiles?
Note that this question only applies to the detail log; the syslog
would still get messages from everything (when configured).
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list:
> > > > Vladislav Bogdanov <bub...@hoster-ok.com> schrieb:
> > > > >
> > > > > 11.01.2018 18:39, Ken Gaillot wrote:
> > > > >
> > > > > [...]
> > > > > > > > I thought one option aired at the
s planned to be addressed later this year.
> May be crm_resource can be used for the same purpose, storing state
> data
> in resource attributes? Or here is any other solution?
>
--
Ken Gaillot <kgail...@redhat.com>
___
Users mailing list: U
On Thu, 2018-01-11 at 20:11 +0300, Andrei Borzenkov wrote:
> 11.01.2018 19:21, Ken Gaillot пишет:
> > On Thu, 2018-01-11 at 01:16 +0100, Jehan-Guillaume de Rorthais
> > wrote:
> > > On Wed, 10 Jan 2018 12:23:59 -0600
> > > Ken Gaillot <kgail...@redhat.com&g
lthough, looking at it now, it might be nice to reduce it to one
option:
--xml - standard input
--xml '' anything starting with '<' is literal
--xml fileanything else is a filename
--
Ken Gaillot <kgail...@redhat.com>
___
Users maili
On Thu, 2018-01-11 at 01:21 +0100, Jehan-Guillaume de Rorthais wrote:
> On Wed, 10 Jan 2018 16:10:50 -0600
> Ken Gaillot <kgail...@redhat.com> wrote:
>
> > Pacemaker 2.0 will be a major update whose main goal is to remove
> > support for deprecated, legacy syntax
On Thu, 2018-01-11 at 01:16 +0100, Jehan-Guillaume de Rorthais wrote:
> On Wed, 10 Jan 2018 12:23:59 -0600
> Ken Gaillot <kgail...@redhat.com> wrote:
> ...
> > My question is: has anyone used or tested this, or is anyone
> > interested
> > in this? We won't promot
eout higher than 10s during the test.
>
> -邮件原件-
> 发件人: Ken Gaillot [mailto:kgail...@redhat.com]
> 发送时间: 2018年1月11日 0:54
> 收件人: Cluster Labs - All topics related to open-source clustering
> welcomed <users@clusterlabs.org>
> 主题: Re: [ClusterLabs] pacemaker reports mo
cts takes more time. Still a good idea though.
> > > > Adam Spiers <aspi...@suse.com> schrieb am 11.01.2018 um 00:59
> > > > in Nachricht
>
> <20180110235939.fvwkormbruoqhwfb@pacific.linksys.moosehall>:
> > Ken Gaillot <kgail...@redhat.com> wrot
l list all possible exit statuses, and
> >
> > crm_error --exit 124
> >
> > will show a textual description of what exit status 124 means.
> >
> > This will mainly be of interest to users who script Pacemaker
> > commands
> > and check the return
901 - 1000 of 1689 matches
Mail list logo
