>>> Digimer <li...@alteeve.ca> schrieb am 26.11.2019 um 05:02 in Nachricht <37c840a6-9f63-28b9-0729-564d70330...@alteeve.ca>: > Congrats! > > Can I ask, when might fencing become required? Is that still in the > works, or has it been shelved?
Hi! It's a bit like freedom: Free people are allowed even to do stupid things. People are allowed tu run a cluster without fencing. Even if fencing were required, you could still implement fencing in a way that it does not work ;-) Regards, Ulrich > > digimer > > On 2019-11-25 9:32 p.m., Ken Gaillot wrote: >> Hi all, >> >> The final release of Pacemaker version 2.0.3 is now available at: >> >> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-2.0.3 >> >> Highlights include: >> >> * A dynamic cluster recheck interval (you don't have to care about >> changing cluster-recheck-interval when using failure-timeout or most >> rules) >> >> * Pacemaker Remote options for security hardening (listen address and >> TLS priorities) >> >> * crm_mon supports the --output-as/--output-to options, has some tweaks >> to text and HTML output that will hopefully make it easier to read, has >> a correct count of disabled and blocked resources, and supports an >> option to set a stylesheet for HTML output >> >> * A new fence-reaction cluster option controls whether the local node >> stops pacemaker or panics the local host when notified of its own >> fencing (which can happen with fabric fencing agents such as >> fence_scsi) >> >> * Documentation improvements include a new chapter about ACLs >> (replacing an outdated text file) in "Pacemaker Explained" and another >> one about the command-line tools in "Pacemaker Administration": >> >> > https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html-single/Pacemak > er_Explained/index.html#idm47160746093920 >> >> > https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html-single/Pacemak > er_Administration/index.html#idm47051359032720 >> >> As usual, there were bug fixes and log message improvements as well. >> Most significantly, a regression introduced in 2.0.2 that effectively >> disabled concurrent-fencing has been fixed, and an invalid transition >> (blocking all further resource actions) has been fixed when both a >> guest node or bundle and the host running it needs to be fenced, but >> can't (due to quorum loss, for example). >> >> For more details about changes in this release, see: >> >> https://github.com/ClusterLabs/pacemaker/blob/2.0/ChangeLog >> >> Many thanks to all contributors of source code to this release, >> including Aleksei Burlakov, Chris Lumens, Gao,Yan, Hideo Yamauchi, Jan >> Pokorný, John Eckersberg, Kazunori INOUE, Ken Gaillot, Klaus Wenninger, >> Konstantin Kharlamov, Munenari, Roger Zhou, S. Schuberth, Tomas >> Jelinek, and Yuusuke Iida. >> >> Version 1.1.22, with selected backports from this release, will also be >> released soon. >> > > > -- > Digimer > Papers and Projects: https://alteeve.com/w/ > "I am, somehow, less interested in the weight and convolutions of > Einstein’s brain than in the near certainty that people of equal talent > have lived and died in cotton fields and sweatshops." - Stephen Jay Gould > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/