On Mon, 9 Mar 2015 12:28:44 +0100 franz schaefer schae...@mond.at wrote:
the libqb0 version 0.17.0-2 compiled on jessie out of the box.
so that should be quick and easy. who is going to do it?
In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768922#35 Jonathan
Wiltshire (member of the release team) stated that migrating libqb isn't
an option. And the pacemaker reversion did not happen either. Lacking
direction, other people couldn't do anything about this either.
Ok. but what i do not understand: as it seems libqb is only used by
pacemaker and its daemons only anyway. so even if it is not as clean as one
would wish for: why cant we still have it? as i said: it compiled fine and
with that library all the pacemaker stuff seems to work well.
i would say it is better to have pacemaker then to not have it in the
distribution...
mond
--
~~
.Franz Schaefer GPG KeyID: CFA2F632
.. +43 699 106 14 590 +43 720502048 Fingerprint: 57C2 C0CC
... schae...@mond.at 6F0A 54C7 0D88 D37E
... http://www.mond.at/ C17C CB16 CFA2 F632
That cluster stack really doesn't actually work fine though, it just
starts up - but then nothing else works; and that's if it even starts
for you.
Firstly, let me help by providing these links (provided by digimer of
clusterlabs - and he did say to take it with a grain of salt):
https://alteeve.ca/w/AN!Cluster_Tutorial_2
https://alteeve.ca/w/History_of_HA_Clustering
The biggest issue is that the clusterlabs stack no longer uses cman (its
deprecated...or even worse than deprecated; abandoned much like
heartbeat). CLI tools include (but are not limited to) crmsh and pcs.
Pacemaker 1.10.x doesn't come with cman support, but libcorosync 1.4.6
and any of the other non-sid/experimental packages from Debian are meant
to work with cman, because prior to 2.x: Corosync didn't handle quorum
on its own. RHEL only used cman until the new configuration was ready
and they were able to migrate (upgrading breaks the cluster).
You can upgrade to libcorosync 2.3.3 from unstable or experimental, but
it was built with the improper dependencies for the modern stack
configuration - as evident by the massive errors you get by installing
all of the newest corosync libraries (cpg, cfg, cmap, totem, quorum,
etc) from Debian, and trying to run corosync and pacemaker (CMAP via
pacemaker complains about database API errors, other cmap errors,
connections refused errors, etc - I've been in the clusterlabs channel
for days now sorting this out).
Attempting to use libcorosync 2.3.3 with older dependency packages won't
work because those older packages expect cman or crmsh to be installed
and of course yields API errors (naturally).
There is no crmsh package or pcs/pcsd package to replace cman, in fact
you need to install cman to get crmsh on Debian at this time without
building from source. Yet for clarity, beekof (pacemaker author)
recommends pcs, and clusterlabs associates state crmsh is good too.
---
So what we really need are new packages across the board (and they
should be brand new packages):
1. libqb (latest from github)
2 libcorosync (latest from github --enable-systemd). And I think we
should keep all the libraries in the exact same package, rather than
all broken up (cfg, cpg, sam, etc - this will make it easier to
choose an older stack or the modern one. How often does anyone
use those libraries outside of pacemaker/corosync anyhow?)
3. pacemaker (latest from github --with-corosync --with-cs-quorum )
4. crmsh pcs/pcsd. I've gotten both to build on Debian and work with
no issue, they are what modern documentation is based on, and are
the recommended 'editors' to use with the modern stack.
Lastly, it wasn't just yesterday that clusterlabs updated the
stack...its been corosync 2.x and pacemaker 1.x for years now. Debian is
just extraordinarily out of date sticking with corosync 1.4.6 and
recommending backports to users.
I've offered to help, I can package any of the components, contribute to
code, etc. I've requested to join Debian-HA on alioth (Devrik-Guest).
I'll post pacemaker, corosync, libqb, and crmsh/pcs/pcsd to debian
mentors if I'm not allowed to join the team. Hopefully something can be
done.
Best,
--
Rik
signature.asc
Description: This is a digitally signed message part
