[Linux-HA] resource-agents 3.9.6 released
Hello, We've tagged today (Jan 30) a new stable resource-agents release (3.9.6) in the upstream repository. Big thanks go to all contributors! Needless to say, without you this release would not be possible. It has been almost two years since the release v3.9.5, hence the number of changes is quite big. Still, every precaution has been taken not to introduce regressions. These are the most significant new features in the linux-ha set: - new resource agents: clvm dnsupdate docker galera iface-bridge iface-vlan kamailio nfsnotify sg_persist vsftpd zabbixserver - the drbd agent was removed (it has been deprecated since quite some time in favour of ocf:linbit:drbd) The full list of changes for the linux-ha RA set is available in ChangeLog (https://github.com/ClusterLabs/resource-agents/blob/v3.9.6/ChangeLog) Use the agents introduced with this release with due care: they probably haven't got a lot of field testing. Please upgrade at the earliest opportunity. Best, The resource-agents maintainers ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
[Linux-ha-dev] resource-agents 3.9.6 released
Hello, We've tagged today (Jan 30) a new stable resource-agents release (3.9.6) in the upstream repository. Big thanks go to all contributors! Needless to say, without you this release would not be possible. It has been almost two years since the release v3.9.5, hence the number of changes is quite big. Still, every precaution has been taken not to introduce regressions. These are the most significant new features in the linux-ha set: - new resource agents: clvm dnsupdate docker galera iface-bridge iface-vlan kamailio nfsnotify sg_persist vsftpd zabbixserver - the drbd agent was removed (it has been deprecated since quite some time in favour of ocf:linbit:drbd) The full list of changes for the linux-ha RA set is available in ChangeLog (https://github.com/ClusterLabs/resource-agents/blob/v3.9.6/ChangeLog) Use the agents introduced with this release with due care: they probably haven't got a lot of field testing. Please upgrade at the earliest opportunity. Best, The resource-agents maintainers ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-HA] Antw: Re: Antw: Re: Antw: Re: Antw: Re: SLES11 SP3: warning: crm_find_peer: Node 'h01' and 'h01' share the same cluster nodeid: 739512321
On 2015-01-30T14:57:29, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: # grep -i high /etc/corosync/corosync.conf clear_node_high_bit:new Could this cause our problem? This is an option that didn't exist prior to SP3. With there was no change meant: No administrator did change the file; if a package installation changed the file, I'm not aware of it. Hrm. It's definitely not an option that is meant to be changed automatically. Because it would break upgrades if it was. If you have logs that cover the upgrade process, I'm pretty sure someone would be willing to investigate. And yes, changing this option would cause exactly the issue you've seen. So it's this phrase from the manual page?: WARNING: The clusters behavior is undefined if this option is enabled on only a subset of the cluster (for example during a rolling upgrade). Among others, yes. Basically, it changes how the automated nodeid is computed. Clearly, that shouldn't be done unnecessarily. And also, pacemaker should cope with changing nodeids; I thought recent (I forgot when exactly) pacemaker updates fixed this. It can be a bit messy at times. BTW: The manual page does not says that nodeid has to be a positive 32-bit 2-complement; the page just says it's a 32-bit number... For corosync, it doesn't matter, this is a limitation actually coming from the DLM in-kernel. Isn't that nice. ;-) Regards, Lars -- Architect Storage/HA SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Experience is the name everyone gives to their mistakes. -- Oscar Wilde ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] [Planning] Organizing HA Summit 2015
On 30/01/15 08:34 AM, Dejan Muhamedagic wrote: Hi Digimer, On Tue, Jan 13, 2015 at 12:31:22AM -0500, Digimer wrote: Hi all, With Fabio away for now, I (and others) are working on the final preparations for the summit. This is your chance to speak up and influence the planning! Objections/suggestions? Speak now please. :) In particular, please raise topics you want to discuss. Either add them to the wiki directly or email me and I will update the wiki for you. (Note that registration is closed because of spammers, if you want an account just let me know and I'll open it back up). Sorry for being so late with the discussion proposal. I'd like to discuss Geo Clustering and booth. Cheers and see you in a few days, Dejan Added! -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
[Linux-HA] Antw: Re: Antw: Re: Antw: Re: Antw: Re: SLES11 SP3: warning: crm_find_peer: Node 'h01' and 'h01' share the same cluster nodeid: 739512321
Lars Marowsky-Bree l...@suse.com schrieb am 30.01.2015 um 14:38 in Nachricht 20150130133815.gf2...@suse.de: On 2015-01-30T08:23:14, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: Two of the three nodes were actually updated from SP1 via SP2 to SP3, and the third node was installed with SP3. AFAIR there was no configuration change since SP1. That must be incorrect, because: Was the corosync.conf option clear_node_high_bit changed? # grep -i high /etc/corosync/corosync.conf clear_node_high_bit:new Could this cause our problem? This is an option that didn't exist prior to SP3. With there was no change meant: No administrator did change the file; if a package installation changed the file, I'm not aware of it. And yes, changing this option would cause exactly the issue you've seen. So it's this phrase from the manual page?: WARNING: The clusters behavior is undefined if this option is enabled on only a subset of the cluster (for example during a rolling upgrade). BTW: The manual page does not says that nodeid has to be a positive 32-bit 2-complement; the page just says it's a 32-bit number... The old default behaviour was buggy, but since we couldn't fix it w/o this, we introduced new and defaulted new clusters to this; existing configuration files would remain on their old mode and thus remain compatible. Regards, Lars -- Architect Storage/HA SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Experience is the name everyone gives to their mistakes. -- Oscar Wilde ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Antw: Re: Antw: Re: Antw: Re: SLES11 SP3: warning: crm_find_peer: Node 'h01' and 'h01' share the same cluster nodeid: 739512321
On 2015-01-30T08:23:14, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: Two of the three nodes were actually updated from SP1 via SP2 to SP3, and the third node was installed with SP3. AFAIR there was no configuration change since SP1. That must be incorrect, because: Was the corosync.conf option clear_node_high_bit changed? # grep -i high /etc/corosync/corosync.conf clear_node_high_bit:new Could this cause our problem? This is an option that didn't exist prior to SP3. And yes, changing this option would cause exactly the issue you've seen. The old default behaviour was buggy, but since we couldn't fix it w/o this, we introduced new and defaulted new clusters to this; existing configuration files would remain on their old mode and thus remain compatible. Regards, Lars -- Architect Storage/HA SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Experience is the name everyone gives to their mistakes. -- Oscar Wilde ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] [Planning] Organizing HA Summit 2015
Hi Digimer, On Tue, Jan 13, 2015 at 12:31:22AM -0500, Digimer wrote: Hi all, With Fabio away for now, I (and others) are working on the final preparations for the summit. This is your chance to speak up and influence the planning! Objections/suggestions? Speak now please. :) In particular, please raise topics you want to discuss. Either add them to the wiki directly or email me and I will update the wiki for you. (Note that registration is closed because of spammers, if you want an account just let me know and I'll open it back up). Sorry for being so late with the discussion proposal. I'd like to discuss Geo Clustering and booth. Cheers and see you in a few days, Dejan The plan is; * Informal atmosphere with limited structure to make sure key topics are addressed. Two ways topics will be discussed; ** Someone will guide a given topic they want to raise for ~45 minutes, 15 minutes for QA ** Round-table style discussion with no one person leading (though it would be nice to have someone taking notes). People presenting are asked not to use slides. Hand-outs are fine and either a white-board or paper flip-board will be available for illustrating ideas and flushing out concepts. The summit will start at 9:00 and go until 17:00. We'll go for a semi-official summit dinner and drinks around 6pm on the 4th (location to be determined). Those staying in Brno are more than welcome to join an informal dinner and drinks (and possibly some sight-seeing, etc) the evening of the 5th. Any concerns/comments/suggestions, please speak up ASAP! -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
