Re: [Pacemaker] Hawk error
Carlos Xavier writes: > Hi. > > I'm starting a new cluster on a OpenSuse 13.2, with the following packages > installed: Hi, I would recommend moving to Leap, the versions included in 13.2 are quite old at this point. > I verified the status of the program and got the messages below: > This is only the tail end of the error message. To get the full message, use journalctl: journalctl -u hawk Most likely, there is some dependency problem as Hawk depends on a number of rubygems and one of them may have been updated to an incompatible version. Cheers, Kristoffer > I have used Hawk on other cluster and never got those errors. > > Am I missing something? > Please, can you help me to fix this issue? > > Best Regards, > Carlos Xavier. > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] Hawk release 2.0
Hello everyone! It is my great pleasure to announce that Hawk 2.0.0 is released! Yes, technically the previous actual release was 0.7.2, but for various reasons I decided to bump the version number all the way up to 2. One of the reasons for doing so is the huge amount of changes that have gone into this version of Hawk. Not only does it look completely different, on the backend of things, everything has changed as well. First of all, Hawk now has a website! Visit http://hawk-ui.github.io/ and check out the new logo designed by Manuele Carlini. I have also started working on a User Guide for Hawk, here: http://hawk-guide.readthedocs.org/ . It's still early days for the Guide and it needs more work to be truly useful, but already it has one thing going for it: It's a cluster usage guide which doesn't ignore fencing. I know some of you will like that, at least. ## New Features * Redesigned Frontend The Hawk frontend has been modernised, and now uses Bootstrap 3. The layout and organization of the user interface has been rethought with usability in mind. * Updated Backend Hawk 2 is based on Ruby on Rails 4.2 running on the Puma web server. By using Puma, we can make Hawk as unintrusive as possible on the cluster nodes without compromising performance. In fact, thanks to the use of asset precompilation Hawk 2 should perform better than the Hawk 1 interface despite the updated visual style. * Wizards In Hawk 1, the wizards were implemented as a custom solution. For Hawk 2, the wizards have been moved into the crm shell, making them available from the command line as well. In addition to this move, the wizards have been greatly improved. They now feature optional steps and multi-step configuration (for example, in case resources in an earlier step need to be started before configuring the next set of resources). Wizards are also able to perform complex actions like installing and configuring necessary software packages. * Integrated Dashboard The multi-cluster dashboard has been integrated into the main interface. Now you can monitor multiple clusters directly from the regular Hawk UI. * New Pacemaker Features We support many of the features that have been added recently to Pacemaker: - Location constraints can apply to several resources at once. - Tags - Remote nodes are shown separate from regular nodes in the Dashboard * Configuration view and Command Log To make the transition between command line usage and the web interface easier, we've added the ability to view the current cluster configuration in the command line format, complete with syntax highlighting. Also, the command log provides a list of recent commands executed on the cluster from the web interface. This can serve as a basic audit log, as well as helping new users learn the command line interface directly by performing operations on the cluster. * History Explorer and Simulator Together with the general improvements to the interface, the History Explorer has been redesigned to be easier to use and more powerful. Now you can see more details for each transition, as well as easily navigate forward and backward in time through a report. The History Explorer now also shows a summary of important events directly when opening the report, to make it easy to find the relevant events in the log. The report generation, download and upload functions are all now accessible from a single location. Similarly, the Simulator has been updated to not only be prettier (if you ever used the old version, you'll know what I mean) but also easier to use. ## Downloading Source downloads for the release are available here: https://github.com/ClusterLabs/hawk/releases/tag/hawk-2.0.0 openSUSE Tumbleweed has a version of Hawk 2 (package name hawk2) which is very close to the actual release version, and the release will be there soon. Another way to try Hawk is to use the Vagrant configuration which comes with the User Guide. It configures a 1 - 3 node cluster with Hawk already installed and running. Thank you! Credit for the release goes to Tim Serong (for the original Hawk version), Thomas Boerger, Manuele Carlini and Thomas Hutterer. And also me. Cheers, Kristoffer -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Multiple live cib in one pacemaker
Adam Błaszczykowski writes: > Hello, > I am using Pacemaker 1.1.12 together with Corosync 2.4.3 in my cluster > environment. I have two nodes in cluster that are in different LAN > locations. It may be situation that nodes will not be able to connect with > each other because of network failure. In that situation split brain can > occur if we add new configuration on both nodes but that configuration will > be different on each node. Running a single cluster across different LANs with an unreliable network connection doesn't seem like a situation supported by Pacemaker. You probably need to look at something like booth [1] to get this to work reliably. Booth allows resources to migrate between different clusters, using tickets and an arbiter in a third location. [1]: https://github.com/ClusterLabs/booth -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Call cib_apply_diff failed (-205): Update was older than existing configuration
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 fixed in the latest released version of crmsh (2.1.2), and I would recommend upgrading to that version if you can. If this problem still occurs with 2.1.2, please let me know [1]. Thanks! [1]: http://github.com/crmsh/crmsh/issues > > + crm configure primitive STONITH_node-1 stonith:fence_avid_sbb_hw > + crm configure primitive STONITH_node-0 stonith:fence_avid_sbb_hw params > delay=10 > + crm configure location dont_run_STONITH_node-1_on_node-1 STONITH_node-1 > -inf: node-1 > + crm configure location dont_run_STONITH_node-0_on_node-0 STONITH_node-0 > -inf: node-0 > Call cib_apply_diff failed (-205): Update was older than existing > configuration > ERROR: could not patch cib (rc=205) > INFO: offending xml diff: > > > > > > > > > >num_updates="3" admin_epoch="0" cib-last-written="Thu Feb 5 14:56:09 2015" > have-quorum="1" dc-uuid="1"/> > > >position="1"> > rsc="STONITH_node-0" score="-INFINITY" node="node-0"/> > > > > After that pacemaker stopped on the node on which the script was run. > > Thank you, > Kostya > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] Announcing crmsh release 2.1.2
Today we are proud to announce the release of `crmsh` version 2.1.2! This version primarily fixes all known issues found since the release of `crmsh` 2.1.1 in October. We recommend that all users of crmsh upgrade to this version, especially if using Pacemaker 1.1.12 or newer. A massive thank you to everyone who has helped out with bug fixes, comments and contributions for this release! For a complete list of changes since the previous version, please refer to the changelog: * https://github.com/crmsh/crmsh/blob/2.1.2/ChangeLog Packages for several popular Linux distributions can be downloaded from the Stable repository at the OBS: * http://download.opensuse.org/repositories/network:/ha-clustering:/Stable/ Archives of the tagged release: * https://github.com/crmsh/crmsh/archive/2.1.2.tar.gz * https://github.com/crmsh/crmsh/archive/2.1.2.zip Changes since the previous release: - medium: ui_resource: Set probe interval 0 if not set (bnc#905050) - doc: Document probe op in resource trace (bnc#905050) - high: config: Fix path to system-wide crm.conf (#67) - medium: config: Fall back to /etc/crm/crmsh.conf (#67) - low: cliformat: Colorize id: as identifier (boo#905338) - medium: cibconfig: Don't bump epoch if stripping version - medium: ui_context: Lazily import readline - medium: config: Add core.ignore_missing_metadata (#68) (boo#905910) - medium: cibconfig: Strip digest from v1 diffs (bnc#914098) - medium: cibconfig: Detect v1 format and don't patch container changes (bnc#914098) - high: xmlutil: Treat node type=member as normal (boo#904698) - medium: xmlutil: Use idmgmt when creating new elements (bnc#901543) - low: ui_resource: --reprobe and --refresh are deprecated (bnc#905092) - doc: Document deprecation of refresh and reprobe (bnc#905092) - medium: parse: Support resource-discovery in location constraints - medium: Allow removing groups even if is_running (boo#905271) - medium: cibconfig: Delete containers first in edits (boo#905268) - medium: ui_history: Fix crash using empty object set - Low: term: get rid of annying ^O in piped-to-less-R output - medium: parse: Allow nvpair with no value using name= syntax (#71) - medium: parse: Enable name[=value] for nvpair (#71) - medium: utils: Check if path basename is less (#74) - medium: utils: crm_daemon_dir is added to PATH in envsetup (#67) - medium: cmd_status: Show pending if available, enable extra options - high: utils: Locate binaries across sudo boundary (bnc#912483) - Medium: history: match error/crit messages of pcmk 1.1.12 - low: ui_options: Add underscore aliases for legacy options - medium: constants: Fix transition start detection - medium: constants: Update transition regex (#77) - medium: orderedset: Add OrderedSet type - medium: cibconfig: Use orderedset to avoid reordering bugs (#79) - low: xmlutil: logic bug in sanity_check_nvpairs - medium: util: Don't fall back to current time - medium: report: Fall back to end_ts = start_ts Thank you, -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Colocating with unmanaged resource
Andrew Beekhof writes: >>> you'll want a recurring monitor with role=Stopped >>> >> >> How is it done? > > I don't know the crmsh syntax. Sorry > >> >> I've tried on 1.1.12 with: >> primitive Nginx lsb:nginx \ >> op monitor interval=2s \ >> op monitor interval=3s role=Stopped >> >> This produces warning that monitor_stopped may be unsupported by RA. > To clarify, the above is indeed the correct crmsh syntax for a monitor op with role=Stopped. -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [crmsh][Question] The order of resources is changed.
Hello, renayama19661...@ybb.ne.jp writes: > Hi All, > > We confirmed a function of crmsh by the next combination. > * corosync-2.3.4 > * pacemaker-Pacemaker-1.1.12 > * crmsh-2.1.0 > > By new crmsh, does "options sort-elements no" not work? > Is there the option which does not change order elsewhere? It is possible that there is a bug in crmsh, I will investigate. Could you file an issue for this problem at http://github.com/crmsh/crmsh/issues ? This would help me track the problem. Thank you! -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] pacemaker-remote debian wheezy
Thomas Manninger writes: > Hi, > I compiled the latest libqb, corosync and pacemaker from source. > Now there is no crm command available? Is there another standard > shell? > Should i use crmadmin? > Thanks! > Regards > Thomas You can get crmsh and build from source at crmsh.github.io, or try the .rpm packages for various distributions here: https://build.opensuse.org/package/show/network:ha-clustering:Stable/crmsh Best regards, Kristoffer -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [ha-wg-technical] [ha-wg] [Cluster-devel] [Linux-HA] [RFC] Organizing HA Summit 2015
>> On 27 Nov 2014, at 2:41 am, Lars Marowsky-Bree wrote: >> >> On 2014-11-25T16:46:01, David Vossel wrote: >> >> Okay, okay, apparently we have got enough topics to discuss. I'll >> grumble a bit more about Brno, but let's get the organisation of that >> thing on track ... Sigh. Always so much work! >> Will Chris Feist be at the summit? I would be happy to have a roundtable discussion or something similar about clients, exchange ideas and so on. I don't necessarily think that there is an urgent need to unify the efforts code-wise, but I think there is a lot we could do together on the level of idea exchange without giving up our independence, so to speak ;) Of course I would be happy to talk about such things with anyone else who is interested as well. -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Hawk and runtime environment
"Grüninger, Andreas (LGL Extern)" writes: > I managed to get Hawk running on Solaris. > I use as prefix /opt and not /usr. > > The last problem seems to be the runtime environment of the ruby application. > > For testing purposes I started lighthhtpd in a shell in the foreground. > In this shell crm works without any problem. > If in hawk a function is used which uses crm the error message occurs when > PYTHONPATH is not defined. > Crmsh is located in /opt/lib/python2.6/site-packages/. > When I define links into /usr/lib/python2.6/site-packages hawk can us crm. > > A similar problem exists with hb_report. > I checked hb_report in a shell and it works with some minor problems. > > Used in hawk I get error messages that egrep can’t be used. > Hb_report started over hawk uses /usr/bin/grep and that is the wrong version. > It should use /usr/gnu/bin which is defined in the PATH before /usr/bin. > The error may also stem from a process using the output of hb_report. > > Hawk or ruby seems to ignore the environment of the starting process. > > Does anyone have an idea how to solve the problem? This may be due to which user hawk is being run as. I think by default hawk runs as the hacluster user, so the PATH would need to be correct for that user. > > Andreas > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] Announcing crmsh release 2.1.1
Today we are proud to announce the release of `crmsh` version 2.1.1! This version primarily fixes all known issues found since the release of `crmsh` 2.1 in June. We recommend that all users of crmsh upgrade to this version, especially if using Pacemaker 1.1.12 or newer. A massive thank you to everyone who has helped out with bug fixes, comments and contributions for this release! For a complete list of changes since the previous version, please refer to the changelog: * https://github.com/crmsh/crmsh/blob/2.1.1/ChangeLog Packages for several popular Linux distributions can be downloaded from the Stable repository at the OBS: * http://download.opensuse.org/repositories/network:/ha-clustering:/Stable/ Archives of the tagged release: * https://github.com/crmsh/crmsh/archive/2.1.1.tar.gz * https://github.com/crmsh/crmsh/archive/2.1.1.zip Changes since the previous release: - cibconfig: Clean up output from crm_verify (bnc#893138) - high: constants: Add acl_target and acl_group to cib_cli_map (bnc#894041) - high: parse: split shortcuts into valid rules - medium: Handle broken CIB in find_objects - high: scripts: Handle corosync.conf without nodelist in add-node (bnc#862577) - medium: config: Assign default path in all cases - high: cibconfig: Generate valid CLI syntax for attribute lists (bnc#897462) - high: cibconfig: Add tag: to get all resources in tag - doc: Documentation for show tag: - low: report: Sort list of nodes - high: parse: Allow empty attribute values in nvpairs (bnc#898625) - high: cibconfig: Delay reinitialization after commit - low: cibconfig: Improve wording of commit prompt - low: cibconfig: Fix vim modeline - high: report: Find nodes for any log type (boo#900654) - high: hb_report: Collect logs from journald (boo#900654) - high: cibconfig: Don't crash if given an invalid pattern (bnc#901714) - high: xmlutil: Filter list of referenced resources (bnc#901714) - medium: ui_resource: Only act on resources (#64) - medium: ui_resource: Flatten, then filter (#64) - high: ui_resource: Use correct name for error function (bnc#901453) - high: ui_resource: resource trace failed if operation existed (bnc#901453) - Improved test suite Thank you, -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker with Xen 4.3 problem
On Wed, 9 Jul 2014 08:39:09 +0200 Tobias Reineck wrote: > Hello, > > do you mean the "Xen" script in /usr/lib/ocf/resource.d/heartbeat/ ? > I also tried this to replace all "xm" with "xl" with no success. > Is it possible that you can show me you RA resource for Xen ? > > Best regards > T. Reineck > I have been working on an updated Xen RA which supports both xl and xm. The pull request is here: https://github.com/ClusterLabs/resource-agents/pull/440 -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] Announcing crmsh release 2.1
Today we are proud to announce the release of `crmsh` version 2.1! This version primarily fixes all known issues found since the release of `crmsh` 2.0 in April, but also has some major new features. A massive thank you to everyone who has helped out with bug fixes, comments and contributions for this release! For a complete list of changes since the previous version, please refer to the changelog: * https://github.com/crmsh/crmsh/blob/2.1.0/ChangeLog Packages for several popular Linux distributions can be downloaded from the Stable repository at the OBS: * http://download.opensuse.org/repositories/network:/ha-clustering:/Stable/ (Will be updated soon) Archives of the tagged release: * https://github.com/crmsh/crmsh/archive/2.1.0.tar.gz * https://github.com/crmsh/crmsh/archive/2.1.0.zip Here are some of the highlights of this release: == Rule expressions in attribute lists One of the biggest features in this release is full support for rule expressions wherever the XML syntax allows them. Here is an example of using rule expressions in an attribute list in order to set the virtual IP of an IPAddr2 resource to a different value on a specific node. primitive vip-on-node1 IPAddr2 \ rule 10: #uname eq node1 ip=10.0.0.5 \ rule 1: ip=10.0.0.6 == Tags in the CIB A new feature added to Pacemaker recently is tags. This is a way to refer to multiple resources at once without creating any colocation or ordering relationship between them. For example, you could add all resources related to the database to a db tag, and then stop or start them all with a single command. tag db drbd:Master fs sql-db It is also possible to refer to tags in constraints. == Wildcards in show/edit The configure show and edit commands can now use glob-style wildcards to refer to multiple resources: configure edit db-* == Nvpair references Sometimes, different resources name the same parameters with different names. For example, an IPAddr2 may have an ip parameter that should be the same as a web servers server_ip parameter. By using nvpair references, it is possible to configure the ip in a single location. Note that this is a new feature in Pacemaker 1.1.12 and up. primitive vip IPAddr2 params $my-ip:ip=192.168.0.1 primitive www apache params @my-ip:server_ip == New ACL syntax The support for Access Control Lists has been revised in Pacemaker 1.1.12, and this release of crmsh supports the new syntax. Two new commands have been added: `acl_target` and `acl_group`. For more details, see the documentation. Thank you, Kristoffer -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] crmd does abort if a stopped node is specified
On Thu, 8 May 2014 09:58:41 +1000 Andrew Beekhof wrote: > > node $id=131 vm01 > > node $id=132 vm02 > > (snip) > > > > Is the method of setting up ID of the node which has not > > participated in a cluster using a corosync stack like this? > > I don;t know how crmsh works, sorry $id= maps directly to the id attribute in the XML. The name maps to the uname attribute. So those examples would generate the XML Not sure if that answers the original question. -- // Kristoffer Grönlund // kgronl...@suse.com signature.asc Description: PGP signature ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] list default options in crm shell as "pcs property list --all" does
On Mon, 7 Apr 2014 12:36:47 +0200 emmanuel segura wrote: > Hello, > > Sorry if this has been asked, but i would like to know how do that, > using the crm shell. > > Thanks There is no single equivalent command in crmsh, but the following give some (all) of the same information: crm ra meta crmd crm ra meta pengine crm ra meta cib crm ra meta stonithd -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] collocating a set of resources with crmsh
On Mon, 24 Mar 2014 20:01:25 +0100 Alexandre wrote: > Hi, > > I am configuring a cluster on nodes that doesn't have pcs installed > (pacemaker 1.1.7 with crmsh). > I would like to configure collocated sets of resources (as show > here:http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-single/Pacemaker_Explained/#s-resource-sets-collocation) > in that cluster but can't find the proper way to do it with crm. > I have tried the command bellow but it just failed: > > sudo crm configure xml " score="INFINITY"/> sequential="true"> id="pri_iscsi"/>" > > ERROR: not well-formed (invalid token): line 1, column 32 > > What is the way to proceed with crm? Well, that statement doesn't work because it doesn't parse in bash (you are quoting a string containing quotes). This should work: sudo crm configure colocation coloc-1 inf: \ \( pri_apache2 pri_iscsi sequential=true \) The parenthesis need to be quoted so bash doesn't eat them. > > Regards. > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: > http://bugs.clusterlabs.org > -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] How to avoid dual fencing ?
On Mon, 24 Mar 2014 19:41:16 +0800 邓尧 wrote: > I'm configuring a 2-node cluster on CentOS 6 with corosync + > pacemaker + cman. Everything works well except fencing. > > I'm using IPMI as the fencing device, I know it's not the best fencing > device, but this is the only option I have. > Manual fencing a node (pcs stonith fence ) works well: peer > node goes offline, resources migrate as expected. However, if network > traffic between the two nodes is blocked by iptables, both nodes will > try to fence each other, and both would success, which result in both > nodes offline. > > How to avoid such problem ? You'll need to have one node take priority, by setting different delays on the two nodes so that one of them will fence before the other (see the "delay" parameter). -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] pcs available on debian wheezy?
On Wed, 19 Mar 2014 16:13:13 +0100 Vladimir wrote: > Actually I have no concrete reasons to switch to pcs. I had no > problems with crmsh and was pretty happy with it. I'm just curious > how it will continue with crmsh under debian. pcs seems to become a > little more common, at least on clusterlabs documentation. Sometimes > also customers ask for it because they think pcs is crmsh's successor. Yeah, that seems to be a common misconception. To be fair, on Red Hat-based platforms that is the case (at least if you want support from RH). On the clusterlabs web site there's documentation using both pcs and crmsh, and if there's anything missing in the crmsh documentation there I'll try to get it fixed. I don't know exactly what the state of things are on Debian right now, but last time I checked crmsh was still the shell of choice there. crmsh is still alive! :) -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] pcs available on debian wheezy?
On Wed, 19 Mar 2014 15:17:21 +0100 Vladimir wrote: > Hey everyone, > > does anybody know if there is pcs already available on debian wheezy? > > I first tried to ask on debian-ha-maintainers (subject: crmsh and pcs > on wheezy) but maybe that's not the right list to address this > question. > > I asked myself if it makes sense to already switch to pcs on wheezy > (if possible at all). > May I ask why you want to switch from crmsh to pcs? Since I'm still developing crmsh, I'd be interested in knowing if there's anything major missing in crmsh that pcs has, so I could fix it ;) > Is it possible to first use crmsh and later to switch to pcs? Is the > actual cib the same and crmsh and pcs are only different frontends > (like cibadmin)? > Yes, the CIB is the same, crmsh and pcs are different client-side only frontends. There have been some possible problems reported with mixing use of crmsh and pcs in the same cluster, such as enabling a resource with one and disabling it with the other. I haven't been able to reproduce that so far, but it is something to keep in mind. In general, mixing the two should work just fine. > Thanks in advance. > > Kind regards > Vladimir > -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] What is the reason which the node in which failure has not occurred carries out "lost"?
On Fri, 07 Mar 2014 10:30:13 +0300 Vladislav Bogdanov wrote: > >> Andrew, current git master (ee094a2) almost works, the only issue > >> is that crm_diff calculates incorrect diff digest. If I replace > >> digest in diff by hands with what cib calculates as "expected". it > >> applies correctly. Otherwise - -206. > > > > More details? > > Hmmm... > seems to be crmsh-specific, > Cannot reproduce with pure-XML editing. > Kristoffer, does > http://hg.savannah.gnu.org/hgweb/crmsh/rev/c42d9361a310 address this? No, that commit fixes an issue when importing the CIB into crmsh, the diff calculation happens when going the other way. It seems strange that crmsh should be causing such a problem, all it does is call crm_diff to generate the actual diff so any problem with an incorrect digest should be coming from crm_diff. I don't think this is an issue that is known to me, it doesn't sound like it is the same problem I have been investigating. Could you file a bug at https://savannah.nongnu.org/bugs/?group=crmsh with some more details? Thank you, -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] What is the reason which the node in which failure has not occurred carries out "lost"?
On Thu, 06 Mar 2014 14:39:46 +0300 Vladislav Bogdanov wrote: > > Probably best to poke the corosync guys about this. > > > > However, <= .11 is known to cause significant CPU usage with that > > many nodes. I can easily imagine this staving corosync of resources > > and causing breakage. > > > > I would _highly_ recommend retesting with the current git master of > > pacemaker. I merged the new cib code last week which is faster by > > _two_ orders of magnitude and uses significantly less CPU. > > Andrew, current git master (ee094a2) almost works, the only issue is > that crm_diff calculates incorrect diff digest. If I replace digest in > diff by hands with what cib calculates as "expected". it applies > correctly. Otherwise - -206. Ah! This sounds like the same issue that I am seeing with crmsh. -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] possible regex error in "pcs resource enable/disable"
On Fri, 21 Feb 2014 08:51:58 +0100 Lars Marowsky-Bree wrote: > On 2014-02-20T16:03:36, Bob Haxo wrote: > > > Sooo, seems that we need to kick this over the fence to the crmsh > > folks ... or the SUSE folks, if they are maintaining crmsh. > > Yes, please file a bug. This shouldn't happen (I thought we had > exorcized this class of bugs.) > > https://savannah.nongnu.org/bugs/?group=crmsh I'll look over the meta_attributes handling in crmsh, sounds like it's not being a good citizen. No need to file an issue, but if you do create one I'll make sure to update it with status information once I've pushed a fix. -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] About the difference in handling of "sequential".
On Wed, 19 Feb 2014 11:57:29 +1100 Andrew Beekhof wrote: > It appears Yan did this on purpose. > The reason would likely be that this set is for use in a location > constraint (not ordering or colocation). And in particular, it is > creating a fake set for resources using the same template - so there > is no reason to think they should be ordered. > > So: > 1. sequential should _always_ default to true > 2. please report it to me if you find somewhere that does not > 3. since template_to_set() is creating (copying) a fake set, there is > no conflict with 1. Thanks, that's exactly the information I needed. :) -- // Kristoffer Grönlund // kgronl...@suse.com signature.asc Description: PGP signature ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] About the difference in handling of "sequential".
Hi everyone,
On Mon, 17 Feb 2014 10:54:29 +0900 (JST)
renayama19661...@ybb.ne.jp wrote:
> Hi Andrew,
>
> I found your correction.
>
> https://github.com/beekhof/pacemaker/commit/37ff51a0edba208e6240e812936717fffc941a41
>
> Many Thanks!
> Hideo Yamauchi.
>
> --- On Wed, 2014/2/12, renayama19661...@ybb.ne.jp
> wrote:
>
> > Hi All,
> >
> > There is difference in two between handling of "sequential" of
> > "resouce_set" of colocation.
> >
I suspect that sequential for resource sets is still broken. I have
been trying to figure out what the expected value of sequential is if
not explicitly set on a resource_set. It seems like the answer is "it
depends".
In pengine/constraints.c, unpack_order_set, sequential defaults to true
if not set, via the following logic:
/* line 1368 */
const char *sequential_s = crm_element_value(set, "sequential");
/* line 1384 */
if (sequential_s == NULL) {
sequential_s = "1";
}
sequential = crm_is_true(sequential_s);
However, in pengine/constraints.c(450), template_to_set, sequential
defaults to false:
/* line 495 */
/* Set sequential="false" for the resource_set */
crm_xml_add(*rsc_set, "sequential", XML_BOOLEAN_FALSE);
Am I reading this wrong, or is this on purpose?
--
// Kristoffer Grönlund
// kgronl...@suse.com
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [Question:crmsh] About a setting method of seuquential=true in crmsh.
On Thu, 13 Feb 2014 09:56:56 +0900 (JST) renayama19661...@ybb.ne.jp wrote: > But the next information appeared when I put crm. > Does this last message not have any problem? > > --- > [root@srv01 ~]# crm configure load update > db2-resource_set_0207.crm WARNING: pgsql: action monitor not > advertised in meta-data, it may not be supported by the RA WARNING: > pgsql: action notify not advertised in meta-data, it may not be > supported by the RA WARNING: pgsql: action demote not advertised in > meta-data, it may not be supported by the RA WARNING: pgsql: action > promote not advertised in meta-data, it may not be supported by the > RA INFO: object rsc_colocation-master cannot be represented in the > CLI notation --- It seems that there is some problem parsing the pgsql RA, which I suspect is the underlying cause that makes crmsh display the constraint as XML. Which version of resource-agents is installed? On my test system, I have version resource-agents-3.9.5-70.2.x86_64. However, the version installed by centOS 6.5 seems to be a very old version, resource-agents-3.9.2-40.el6_5.6.x86_64. It would be very helpful if you could file an issue for this problem at https://savannah.nongnu.org/bugs/?group=crmsh and also attach your configuration and an hb_report or crm_report, thank you. I have also implemented a fix for the problem discovered by Mr. Inoue. His original email was unfortunately missed at the time. The fix is in changeset 71841e4559cf. Thank you, -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [Question:crmsh] About a setting method of seuquential=true in crmsh.
On Wed, 12 Feb 2014 17:29:20 +0900 (JST) renayama19661...@ybb.ne.jp wrote: > Hi Kristoffer, > > Thank you for comments. > > > Could you try with the latest changeset 337654e0cdc4? > > However, the problem seems to still occur. > Hello, I have now verified that the fix in changeset 7f620e736895 works in CentOS 6.5, sorry for the false fixes previously. Please test again with this updated version. Thank you, -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [Question:crmsh] About a setting method of seuquential=true in crmsh.
On Wed, 12 Feb 2014 09:12:08 +0900 (JST) renayama19661...@ybb.ne.jp wrote: > Hi Kristoffer, > > Thank you for comments. > > I tested it. > However, the problem seems to still occur. > Hello, Could you try with the latest changeset 337654e0cdc4? Thank you, -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [Question:crmsh] About a setting method of seuquential=true in crmsh.
On Fri, 7 Feb 2014 09:21:12 +0900 (JST) renayama19661...@ybb.ne.jp wrote: > Hi Kristoffer, > > In RHEL6.4, crmsh-c8f214020b2c gives the next error and cannot > install it. > > Does a procedure of any installation have a problem? Hello, It seems that docbook validation is stricter on RHEL 6.4 than on other systems I use to test. I have pushed a fix for this problem, please test again with changeset 8d984b138fc4. Thank you, -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [Question:crmsh] About a setting method of seuquential=true in crmsh.
On Wed, 5 Feb 2014 23:17:36 +0900 (JST) renayama19661...@ybb.ne.jp wrote: > Hi Kristoffer. > > Thank you for comments. > We wait for a correction. > > Many Thanks! > Hideo Yamauchi. > Hello, A fix for this issue has now been committed as changeset c8f214020b2c, please let me know if it solves the problem for you. This construction should now generate the correct XML: colocation rsc_colocation-grpPg-clnPing INFINITY: \ [ msPostgresql:Master sequential=true ] \ [ vip-master vip-rep sequential=true ] Thank you, -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [Question:crmsh] About a setting method of seuquential=true in crmsh.
On Wed, 5 Feb 2014 15:55:42 +0900 (JST) renayama19661...@ybb.ne.jp wrote: > Hi All, > > We tried to set sequential attribute of resource_set of colocation in > true in crmsh. > > We tried the next method, but true was not able to set it well. > > [snipped] > > How can true set sequantial attribute if I operate it in crmsh? > Hello, Unfortunately, the parsing of resource sets in crmsh is incorrect in this case. crmsh will never explicitly set sequential to true, only to false. This is a bug in both the 2.0 development branch and in all previous versions. A fix is on the way. Thank you, Kristoffer > Best Regards, > Hideo Yamauchi. > > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: > http://bugs.clusterlabs.org > -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Reg. trigger when node failure occurs
On Wed, 8 Jan 2014 13:33:28 +1100 Andrew Beekhof wrote: > > # crm configure primitive ClusterMon ocf:pacemaker:ClusterMon > > params user="root" update="10" extra_options="-E /root/monitor.sh > > -e 192.168.100.188" op monitor on-fail="restart" interval="60" > > > > Entity: line 24: element nvpair: Relax-NG validity error : Type ID > > doesn't allow value > > 'ClusterMon-instance_attributes-/root/monitor.sh' > > Looks like crmsh is having trouble parsing your command line. More recent versions of crmsh have a configurable option 'add_quotes' which, when enabled (and should be enabled by default), works around bash de-quoting arguments with spaces in them. With this option enabled, the given command ought to parse correctly. I'd recommend upgrading to crmsh 1.2.6. It can be downloaded from OBS: https://build.opensuse.org/package/show/network:ha-clustering:Stable/crmsh Another option is to circumvent bash completely: crm configure < signature.asc Description: PGP signature ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] constraint colocation or resource group
On Thu, 2 Jan 2014 09:49:40 -0500 Luc Paulin wrote: > I am trying figure out in which case I should be using a constraint > colocation or the resource group. At the end it look that both will > result in the same result, the resource will be running on the same > host. > > As an example I am currently configuring a two node firewall. > Therefore the only resource that will need to be running are VIP, > BGP/Routing service, Firewall, IPSec/VPN. > > So which of the 2 commands is preferred to be use to have all service > running on the same server. Hi, I think the appropriate constraint in this case is a colocation. A group implies other constraints on the resources as well, for example if one of the resources fails, other resources appearing after it in the group will also be stopped. A colocation constraints only says that the resources should be placed on a particular node. However, if, for example, the Firewall depends on the VIP being started before it starts, you will need either an order constraint as well, or to use a group. > > Thanx! > > > -- > ! >( o o ) > --oOO(_)OOo-- >Luc Paulin >email: paulinster(at)gmail.com >Skype: paulinster -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] dc-version and cluster-infrastructure cluster options may be lost when editing
On Tue, 24 Dec 2013 14:41:20 +0300 Vladislav Bogdanov wrote: > I would expect that only one option is modified, but crmsh intend to > remove all others. > > May be it is possible to fix it by one-line crmsh patch? > > Kristoffer, Dejan? > > Best, > Vladislav > > Hi, This was indeed a bug in crmsh. An updated version which fixes this is now available from network:ha-clustering:Stable, or in the 1.2.6 branch of the crmsh repository. Thank you, -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] dc-version and cluster-infrastructure cluster options may be lost when editing
On Tue, 24 Dec 2013 14:41:20 +0300 Vladislav Bogdanov wrote: > I would expect that only one option is modified, but crmsh intend to > remove all others. > > May be it is possible to fix it by one-line crmsh patch? > > Kristoffer, Dejan? Hi, Yes, the intended behavior is for crmsh to preserve the unrelated properties when performing an update, so this does look like a bug in crmsh. It would be helpful if you could show me the property line in the configuration before applying the update, thank you. -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] crmsh: New syntax for location constraints, suggestions / comments
On Wed, 18 Dec 2013 21:21:32 +0100 (CET) "Rainer Brestan" wrote: > What i really miss in crmsh is the possibility to specify resource > parameters which are different on different nodes, so the parameter > is node dependant. In XML syntax this is existing, Andrew gave me the > hint as answer to an discussion how to deal with different node > parameters. But, if specified in XML syntax, crmsh cannot interpret > it any more and print the resource in XML syntax. Therefore, this is > not usable with crmsh, as there is no single syntax display with "crm > configure show". This is definitely something we should support. I'll look into adding support for node specific resource parameters. Thank you! -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] crmsh: New syntax for location constraints, suggestions / comments
On Fri, 13 Dec 2013 10:55:32 +0100 Michael Schwartzkopff wrote: > Order for colocations and order constraints: Please don't do it. > Everybody got use to the ordering as it is now. It also makes sense. > Please remember the irritations we had moving from heartbeat 2.0 > (with XML, shudder) to the new pacemaker/crm syntax and constraint > orders. I don't want to have that again. This worries me as well, however the current syntax for constraints is confusing and error-prone. It would be great to be able to do something to make this easier to use, but exactly what it would be is hard to say. Making a change that would silently invert the functionality of existing configurations is, I agree, not a good idea. However, maybe it would be acceptable if a "version: 2" header is required in the document to enable the new syntax? Yet another option is to come up with some entirely new construct to supplement colocation and order which does what I think most people intuitively expects by default, which is enforces both colocation and ordering, so that 'foo depends on bar' means foo will start after bar, and only where bar is running. -- // Kristoffer Grönlund // kgronl...@suse.com signature.asc Description: PGP signature ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] parametr "kind" in "order"
On Fri, 13 Dec 2013 13:57:59 +0400 Andrey Groshev wrote: > Hi All, > I see in PCMK Expl. > Explein > http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html#_mandatory_ordering > > What the parameter "kind"? Written "since 1.1.2" > This unrealized plans or something I do not understand? > Hi, >From the crmsh documentation [1]: Three strings are reserved to specify a kind of order constraint: Mandatory, Optional, and Serialize. It is preferred to use one of these settings instead of score. Previous versions mapped scores 0 and inf to keywords advisory and mandatory. That is still valid but deprecated. [1]: http://crmsh.nongnu.org/crm.8.html#cmdhelp_configure_order -- // Kristoffer Grönlund // kgronl...@suse.com ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] crmsh: New syntax for location constraints, suggestions / comments
Hi everyone,
As some of you may know, I have started developing crmsh together with
Dejan, and have been working on new features for an eventual
2.0-release some time next year.
Location constraints have gotten some new capabilities in recent
versions of Pacemaker, and I have some suggested syntax for support in
crmsh. I'd love to get your comments and feedback on these suggestions,
please let me know what you think!
Location constraints are now applicable to resource sets, and the
proposed syntax for this is as follows, using pseudo-syntax:
location { } [:] / rules...
So, an example would be:
location foo { A B ( C D ) } inf: node-1
The reason I added the { and } around the resource set is to make the
parser at least somewhat unambiguous in this case, otherwise there is no
good way of telling when the resource definitions end and the rest of
the location constraint definition continues. I know there is syntax in
crmsh that already violates this, but my preference is to keep things
unambiguous if possible.
Lars (lmb) suggested that we might switch to using the { } - brackets
around resource sets everywhere for consistency. My only concern with
that would be that it would be a breaking change to the previous crmsh
syntax. Maybe that is okay when going from 1.x to 2.0, but it also
makes me a bit nervous. :)
The second new syntax is for resource patterns / regexes. Here my
suggested syntax is as follows:
location // [:] / rules...
Example:
location prefer-node-1 /*/ 100: node-1
The // is a kind of vim-style / perl-style inspired syntax, which at
least to me seems pretty intuitive. Another option would be to try to
automatically detect patterns and generate rsc= or rsc-pattern= in the
XML appropriately, like so:
location prefer-node-1 * 100: node-1
...but I think I prefer a more explicit syntax.
I'd especially be curious to know what Chris thinks about this, if
there is already support for these types of constraints in pcs or if
there is some other syntax that might make more sense. Consistency is
always good. :)
--
// Kristoffer Grönlund
// kgronl...@suse.com
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
