Red Hat Bugzilla – Bug 1280348
Tracking Bug: Make clufter reflect new additions wrt. corosync's external quorum device
Last modified: 2018-03-02 11:30:34 EST
We will see if there is something we can do to accommodate qdisk users
in the old cluster stack in the conversion process to the new one if
it already contains quorum device discussed in the referred bug:
+++ This bug was initially created as a clone of Bug #614122 +++
Because qdevice (at least net model) is completely different from old cman qdisk I can see only two "convertible" sections:
- logging. Subsystem name is QDEVICE. Supported options are to_stderr, to_syslog, syslog_facility, syslog_priority, logfile_priority, debug, fileline, timestamp and function_name. to_logfile and logfile are not supported
- number of qdevice votes. stored in quorum.device.votes key
I would suggest to ether let this BZ open till we get disk model which in theory may be more "compatible" with old qdisk so more options may be "convertible" or we can open new one for 7.4.
Honzo, if I understand [comment 2] correctly, the two mentioned sections
are global (regardless of model) and are relatively stable.
Can you confirm, please?
Yes. These two sections are model independent and stable at least in RHEL 7.
As a matter of following the overall progress, clufter is currently
able to emit pcs commands based on corosync.conf to configure
(refined in 0.59:
I am pushing this bug to 7.4 to keep tabs on the further progress.
If there is eventually a "disk" model, also some advanced conversions
might be feasible.
Likewise, pushing further to 7.5.
Capacity asks for postponing for 7.6 consideration.
Actually what's new for 7.5, heuristics (see recently added Depends On
bugs), will get addressed as a matter of rebase [bug 1509381], this bug
then remains a sliding tracker of the progress in other components clufter
should respond to, till the corosync quorum device support gets settled
(expected after "disk" model is present?).