[ClusterLabs] Antw: Colocations and Orders Syntax Changed?
eric.robinson at psmnv.com
Fri Jan 20 06:56:51 EST 2017
Thanks for the input. I usually just do a 'crm config show > myfile.xml.date_time' and the read it back in if I need to.
> -----Original Message-----
> From: Ulrich Windl [mailto:Ulrich.Windl at rz.uni-regensburg.de]
> Sent: Thursday, January 19, 2017 12:04 AM
> To: users at clusterlabs.org
> Subject: [ClusterLabs] Antw: Colocations and Orders Syntax Changed?
> This might not help, but messing up your cluster is a part of life. I decided to
> track cluster changes automatically (more human-usable than the diffs
> logged in pacemaker's log). So if the current configuration stops to work, I
> look at the changes and try to undo them until things work again (hoping it's
> not the current pacemaker patch) ;-)
> So I have a script run by cron that saves the current configuration (readable
> and XML), then looks if it's different from the one saved last. If so, the new
> configuration is saved. For convenience I add a hash to the files, and link a
> timestamp to the hashed files (So if you cycle between configurations, you'll
> save some space ;-)) So I can diff between any of the configurations saved (a
> kind of time machine)...
> >>> Eric Robinson <eric.robinson at psmnv.com> schrieb am 19.01.2017 um
> >>> 05:08 in
> <DM5PR03MB2729B7480FDF490F0DA81AC0FA7E0 at DM5PR03MB2729.nampr
> > Greetings!
> > I have a lot of pacemaker clusters, each running multiple instances of
> > mysql. I configure it so that the mysql resources are all dependent
> > on an underlying stack of supporting resources which consists of a
> > virtual IP address (p_vip), a filesystem (p_fs), often an LVM resource
> > (p_lvm), and a drbd resource (p_drbd). If any resource in the
> > underlying stack resource moves, then all of them move together and the
> mysql resources follow.
> > However, each of the mysql resources can be stopped and started
> > independently without impacting any other resources. I accomplish that
> > with a configuration such as the following:
> > colocation c_clust10 inf: ( p_mysql_103 p_mysql_150 p_mysql_204
> > p_mysql_206
> > p_mysql_244 p_mysql_247 ) p_vip_clust10 p_fs_clust10 ms_drbd0:Master
> > order o_clust10 inf: ms_drbd0:promote p_fs_clust10 p_vip_clust10 ( p
> > p_mysql_103 p_mysql_150 p_mysql_204 p_mysql_206 p_mysql_244
> > p_mysql_247)
> > This has suddenly stopped working. On my newest cluster I have the
> > following. When I try to use the same approach, the configuration gets
> > rearranged on me automatically. The parentheses get moved. Often each
> > of the underlying resources is changed to the same thing with ":Master"
> > Sometimes the whole colocation stanza gets replaced with raw xml. I
> > have messed around with it, and the following is the best I can come
> > up with, but when I stop a mysql resource everything else stops!
> > colocation c_clust19 inf: ( p_mysql_057 p_mysql_092 p_mysql_187
> > p_mysql_213
> > p_vip_clust19 p_mysql_702 p_mysql_743 p_fs_clust19 p_lv_on_drbd0 ) (
> > ms_drbd0:Master ) order o_clust19 inf: ms_drbd0:promote (
> > p_lv_on_drbd0:start ) ( p_fs_clust19
> > p_vip_clust19 ) ( p_mysql_057 p_mysql_092 p_mysql_187 p_mysql_213
> > p_mysql_702
> > p_mysql_743 )
> > The old cluster is running Pacemaker 1.1.10. The new one is running 1.1.12.
> > What can I do to get it running right again? I want all the underlying
> > resources (vip, fs, lvm, drbd) to move together. I want the mysql
> > instances to be collocated with the underlying resources, but I want
> > them to be independent of each other so they can each be started and
> > stopped without hurting anything.
> > --
> > Eric Robinson
> Users mailing list: Users at clusterlabs.org
> Project Home: http://www.clusterlabs.org Getting started:
> Bugs: http://bugs.clusterlabs.org
More information about the Users