I've started my merging effort here
https://github.com/dmitryilyin/openstack-puppet-pacemaker
Can I change the interface of pcmk_resource?
You have pcmk_constraint but I have pcmk_location/colocation/order
separately. I can merge then into a single resource like you did
or I can keep them separat
Hello.
I'm the author of fuel-infra/puppet-pacemaker and I guess I would be able
to merge the code from "fuel-infra/puppet-pacemaker" to
"openstack/puppet-pacemaker"
We will be having a single set of pcmk_* types and two providers for the
each type: "pcs" and "xml", there is also a "noop" provider
Here is the implementation of the puppet "command" that outputs only stdout
and drops the stderr unless an error have happened.
https://github.com/dmitryilyin/puppet-neutron/commit/b55f36a8da62fc207a91b358c396c03c8c58981b
2015-10-22 17:59 GMT+03:00 Matt Fischer :
> On Thu, Oct 22, 2015 at 12:52 A
I have investigated this issue too.
Previously, Puppet "commands" had only stdout in their output value and
stderr was discarded unless the command have returned an error code and the
exception is raised with stderr as its message.
In the current Puppet versions BOTH stdout and stderr go into the
Speaking about the idea of running everything inside containers...
First, this idea is no the new one and have been around for a very long
time. People were running their services inside a simple chroot, then
OpenVZ and now LXC containers with variable success. Usually the ideas
behind this are fo
Hello, guy! I've just saw your thread and I have something to say about
your topic.
> What management tools are there?
The old time pacemaker users of course will name crm shell first (crmsh
package). It allows interacive configuration by enetering commands like
this:
> crm configure primitive t
