|Summary:||Tracking Bug: Make clufter reflect new additions wrt. corosync's external quorum device|
|Product:||Red Hat Enterprise Linux 7||Reporter:||Jan Pokorný [poki] <jpokorny>|
|Component:||clufter||Assignee:||Jan Pokorný [poki] <jpokorny>|
|Status:||NEW ---||QA Contact:||cluster-qe <cluster-qe>|
|Version:||7.0||CC:||ccaulfie, cfeist, cluster-maint, cluster-qe, djuran, jfriesse, jkortus, keypusher, mlisik, royoung, sdake, slevine, tojeline|
|Target Milestone:||rc||Keywords:||FutureFeature, Tracking|
|Fixed In Version:||Doc Type:||Enhancement|
|Doc Text:||Story Points:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:||1507087, 614122, 1389209, 1413573|
Description Jan Pokorný [poki] 2015-11-11 14:26:23 UTC
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 +++
Comment 2 Jan Friesse 2016-06-17 09:39:16 UTC
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.
Comment 4 Jan Pokorný [poki] 2016-06-17 15:37:58 UTC
Honzo, if I understand [comment 2] correctly, the two mentioned sections are global (regardless of model) and are relatively stable. Can you confirm, please?
Comment 5 Jan Friesse 2016-06-20 07:29:01 UTC
Yes. These two sections are model independent and stable at least in RHEL 7.
Comment 6 Jan Pokorný [poki] 2016-09-22 12:18:44 UTC
As a matter of following the overall progress, clufter is currently able to emit pcs commands based on corosync.conf to configure qdevice/qnet: 0.58: http://oss.clusterlabs.org/pipermail/users/2016-July/003513.html (refined in 0.59: http://oss.clusterlabs.org/pipermail/users/2016-July/003594.html) 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.
Comment 7 Jan Pokorný [poki] 2017-05-30 15:39:56 UTC
Likewise, pushing further to 7.5.
Comment 9 Jan Pokorný [poki] 2017-11-07 15:56:39 UTC
Capacity asks for postponing for 7.6 consideration.
Comment 10 Jan Pokorný [poki] 2017-11-07 17:41:15 UTC
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?).