I am very pleased to announce the 1.0.1 release of libqb
This is a bugfix release with mainly lots of small amendments.
Low: ipc_shm: fix superfluous NULL check
log: Don't overwrite valid tags
Low: further avoid magic in qblog.h by using named constants
Low: log: check for appropriate space when
Attribute dampening doesn't work for me also.
To test that I have a script:
attrd_updater -N node-0 -n my-attr --update false --delay 20
sleep 3
attrd_updater -N node-0 -n my-attr --update true
sleep 7
attrd_updater -N node-1 -n my-attr --update true
All my resources have this
We recently did an upgrade for our cluster nodes from Wheezy to Jessie.
To reduce possible problems with drbd we first updated the kernel to the
backport version, which is the same as the stable kernel in Jessie.
After that drbd versions matched while one node was on whezzy and one
node already
On 24/11/16 10:42 +, Christine Caulfield wrote:
> I am very pleased to announce the 1.0.1 release of libqb
For instant tryout on Fedora/EL-based distros, there is already
a habitual COPR build. But this time around, I'd like to introduce
some advancements in the process...
* * *
First, we n
On 2016-11-24 10:41, Toni Tschampke wrote:
We recently did an upgrade for our cluster nodes from Wheezy to Jessie.
IIRC it's the MIT CS joke that they have clusters whose uptime goes way
back past the manufacturing date of any/every piece of hardware they're
running on. They aren't linux-ha c
Hi all,
I want to ask what is the different between "pcs cluster standby node"
and "pcs resource move resource1 example-node2" commands that use to move the
resource
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailma
The only thing that comes to my mind is that "standby" prevents all
resources from running on a node, whereas you can achieve the same with
"move" but it needs to be used for each resources. Also with "move" you
specify a node where you want a resource to be moved to.
On Nov 24, 2016 10:18 PM, "Om
