Re: [ClusterLabs] how do I disable/negate resource option?

2017-01-20 Thread Ken Gaillot
On 01/19/2017 09:52 AM, lejeczek wrote:
> 
> 
> On 19/01/17 15:30, Ken Gaillot wrote:
>> On 01/19/2017 06:30 AM, lejeczek wrote:
>>> hi all
>>>
>>> how can it be done? Is it possible?
>>> many thanks,
>>> L.
>> Check the man page / documentation for whatever tool you're using (crm,
>> pcs, etc.). Each one has its own syntax.
> 
> I'd think this would be some built-in logic for a given tool, eg pcs
> which I'm using (as am on 7.x) but no. I don't think an RA option(s) can
> be ignored, or even better disabled.
> I'm looking at specific RA(s) descriptions and nothing like "disable"
> can I find there. Which is a shame, I really thought by design it'd be
> possible. Take CTDB, it's a mess, probably because of the version, in
> rhel.7.x must be newer, with which the CTDB has not kept up, it fails.
> I only started checking HA two days ago, and in my case it's a bit
> discouraging experience with that CTDB. Seems like the only road is to
> inside RA definition files. Is it really or I'm missing something
> fundamental, trivial?

Maybe I'm misunderstanding what you mean by "disable".

If you just want to change the value used for the option, you can do:

  pcs resource update RESOURCE_NAME OPTION_NAME=NEW_VALUE

If you mean that the resource agent is buggy, and you want it not to use
a particular option at all, then that can only be addressed within the
agent. If you're comfortable with shell scripting, you can copy it and
make any necessary changes yourself. Also feel free to open a bug at:

  https://github.com/ClusterLabs/resource-agents/issues

___
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


[ClusterLabs] Antw: Re: Antw: Colocations and Orders Syntax Changed?

2017-01-20 Thread Ulrich Windl
>>> Eric Robinson  schrieb am 20.01.2017 um 12:56 in
Nachricht


> 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. 

I guess 'crm configure show xml > myfile.xml.date_time', because here I get 
"ERROR: config: No such command" and no XML... ;-)

Acutally I'm using "cibadmin -Q -o configuration", because I think it's 
faster...

Regards,
Ulrich



___
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


Re: [ClusterLabs] Antw: Colocations and Orders Syntax Changed?

2017-01-20 Thread Eric Robinson
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. 

--
Eric Robinson
   

> -Original Message-
> From: Ulrich Windl [mailto:ulrich.wi...@rz.uni-regensburg.de]
> Sent: Thursday, January 19, 2017 12:04 AM
> To: users@clusterlabs.org
> Subject: [ClusterLabs] Antw: Colocations and Orders Syntax Changed?
> 
> Hi!
> 
> 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)...
> 
> Regards,
> Ulrich
> 
> >>> Eric Robinson  schrieb am 19.01.2017 um
> >>> 05:08 in
> Nachricht
>  d03.prod.outlook.com>
> 
> > 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"
> following.
> > 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@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

___
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