[opensuse] Any experienced heartbeat active/active config HA2 (cib.xml) administrator here?
Hi all, I am busy configuring an active/active HA2 (cib.xml) web server with SLES 10 SP2. I started manually with configuring a very basic with the YaST GUI and then manually checked ha.conf; thereafter I used hb_gui. For a manual config, I find the http://www.linux-ha.org website documentation a little difficult to follow between HA versions 1 & 2. They do not have a setup only for Version 2; you have to read all V1 and then find the V2 differences like using the cib.xml in stead of the haresources config files. I think I managed to get the basic heartbeat running as far as configuring the ha.conf file manually (and with Yast & hb_gui). I have set up a failover with a common IP and switched with hb_gui, and checked with ssh that the server actually switched. I then addad a Webserver on the common IP, which also works with a manual switching in hb_gui; actually stopping it on one server and starting on the other. Automatic failover does not seem to work. I found a more systematic description at http://www.novell.com/documentation/sles10/heartbeat/index.html?page=/docume... for heartbeat. I can find no actual description of setting up an active-active system which runs a web server on each node separately, that fails over to the other when a node fails. It means that at fail over, the one node should run both web servers, switching back to the default server as soon as it comes up again. I created a group which first switches the IP and then the web server. It works with a manual switch over, but not automatically. This is only switching from a resource on one node to another, i.e. another web server. I will create a NFS common data share for both on the same DRBD HA data cluster as a htdocs directory, then the content will be the same source. This is the one web server. Another web server has to host an ERP II (Web 2.0) system with its own database (also on a DRBD HA cluster) on the other node. Whenever one node fails, the other should take over and host both web servers. What I need then, are two web servers running each on its own node, and the takeover of the failing web server by the other node, which then runs both web servers till the default preferred server for the failed website comes back on. Any indicators as where to look for such a setup is highly appreciated. TIA :-) Al -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Try the documentation at http://clusterlabs.org/wiki/Documentation instead The section on clones might be of particular interest given that you want an active-active apache install. On Fri, Mar 6, 2009 at 17:23, LLLActive@GMX.Net <LLLActive@gmx.net> wrote:
Hi all,
I am busy configuring an active/active HA2 (cib.xml) web server with SLES 10 SP2. I started manually with configuring a very basic with the YaST GUI and then manually checked ha.conf; thereafter I used hb_gui.
For a manual config, I find the http://www.linux-ha.org website documentation a little difficult to follow between HA versions 1 & 2. They do not have a setup only for Version 2; you have to read all V1 and then find the V2 differences like using the cib.xml in stead of the haresources config files. I think I managed to get the basic heartbeat running as far as configuring the ha.conf file manually (and with Yast & hb_gui). I have set up a failover with a common IP and switched with hb_gui, and checked with ssh that the server actually switched. I then addad a Webserver on the common IP, which also works with a manual switching in hb_gui; actually stopping it on one server and starting on the other. Automatic failover does not seem to work.
I found a more systematic description at http://www.novell.com/documentation/sles10/heartbeat/index.html?page=/docume... for heartbeat.
I can find no actual description of setting up an active-active system which runs a web server on each node separately, that fails over to the other when a node fails. It means that at fail over, the one node should run both web servers, switching back to the default server as soon as it comes up again. I created a group which first switches the IP and then the web server. It works with a manual switch over, but not automatically. This is only switching from a resource on one node to another, i.e. another web server. I will create a NFS common data share for both on the same DRBD HA data cluster as a htdocs directory, then the content will be the same source. This is the one web server. Another web server has to host an ERP II (Web 2.0) system with its own database (also on a DRBD HA cluster) on the other node. Whenever one node fails, the other should take over and host both web servers.
What I need then, are two web servers running each on its own node, and the takeover of the failing web server by the other node, which then runs both web servers till the default preferred server for the failed website comes back on.
Any indicators as where to look for such a setup is highly appreciated.
TIA
:-) Al -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Andrew Beekhof wrote:
Try the documentation at http://clusterlabs.org/wiki/Documentation instead
The section on clones might be of particular interest given that you want an active-active apache install.
On Fri, Mar 6, 2009 at 17:23, LLLActive@GMX.Net <LLLActive@gmx.net> wrote:
Hi all,
I am busy configuring an active/active HA2 (cib.xml) web server with SLES 10 SP2. I started manually with configuring a very basic with the YaST GUI and then manually checked ha.conf; thereafter I used hb_gui.
For a manual config, I find the http://www.linux-ha.org website documentation a little difficult to follow between HA versions 1 & 2. They do not have a setup only for Version 2; you have to read all V1 and then find the V2 differences like using the cib.xml in stead of the haresources config files. I think I managed to get the basic heartbeat running as far as configuring the ha.conf file manually (and with Yast & hb_gui). I have set up a failover with a common IP and switched with hb_gui, and checked with ssh that the server actually switched. I then addad a Webserver on the common IP, which also works with a manual switching in hb_gui; actually stopping it on one server and starting on the other. Automatic failover does not seem to work.
I found a more systematic description at http://www.novell.com/documentation/sles10/heartbeat/index.html?page=/docume... for heartbeat.
I can find no actual description of setting up an active-active system which runs a web server on each node separately, that fails over to the other when a node fails. It means that at fail over, the one node should run both web servers, switching back to the default server as soon as it comes up again. I created a group which first switches the IP and then the web server. It works with a manual switch over, but not automatically. This is only switching from a resource on one node to another, i.e. another web server. I will create a NFS common data share for both on the same DRBD HA data cluster as a htdocs directory, then the content will be the same source. This is the one web server. Another web server has to host an ERP II (Web 2.0) system with its own database (also on a DRBD HA cluster) on the other node. Whenever one node fails, the other should take over and host both web servers.
What I need then, are two web servers running each on its own node, and the takeover of the failing web server by the other node, which then runs both web servers till the default preferred server for the failed website comes back on.
Any indicators as where to look for such a setup is highly appreciated.
TIA
:-) Al -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Andrew, Your documentation (very well presented) and product seems worth a try. I would like to try it, due to the reason of the "paying customers support only" that you mention. I do need a bit of clarification to install Pacemaker. Your description on http://clusterlabs.org/wiki/Install: (I do not want to be over critical or nitpicking, but the language is sometimes a little unclear) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ It seems the thing to do these days is attempt to install Pacemaker with Heartbeat 2.1.4 ##### Are you saying: "It seems many attempt to install Pacemaker together with Heartbeat 2.1.4" ##### /*PLEASE DO NOT ATTEMPT THIS*/ ##### Are you saying: "Please, do not install Pacemaker 0.6.6 (and later) together with Heartbeat 2.1.4" ##### Since Pacemaker was originally part of Heartbeat, it naturally includes many of the files contained in Heartbeat 2.1.x Most package managers including YUM, RPM and DEB will complain extremely loudly if you try this. For versions of Pacemaker prior to 0.6.6, it was possible to build Heartbeat with /--disable-crm/ and this would make the package managers happy. This is what happened for the 2.1.3 packages from the OpenSUSE Build Service. The problem now is that Pacemaker also includes the STONITH daemon from Heartbeat 2.1 and there is no clean way to disable it. So please use Heartbeat 2.99.0 or higher. ##### Your reasons are: ##### Package managers recognise the pacemaker files as not compatible with Heartbeat 2.1.x, because they only have the same names but do not conform to the dependencies. ##### STONITH is included in Pacemaker 0.6.6 and Heartbeat 2.1.4, but the Pacemaker installation cannot disable the Heartbeat version. ##### Heartbeat 2.99.0 or higher should be used instead. * Do it because its the same code as 2.1.4 but without the CRM and STONITH daemon. * Do it because it keeps the package managers happy. * Do it because thats what 0.6.6 was tested with. * Or just do it because the CRM in 2.1.4 is not and will never be supported except for /paying/ SLES10 customers. ##### The code of Heartbeat 2.99.0 is the same as that of Heartbeat 2.1.4, but without CRM and STONITH daemons. ##### Package managers accept Heartbeat 2.99.x ##### Pacemaker 0.6.6 was tested with Heartbeat 2.99.x ##### CRM 2.1.4 is only supported for paying customers ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I first have to de-install Heartbeat 1.2.4 in SLES 10 SP2 x86_64. I should install for SLES 10 SP2 x86_64: 1. Pacemaker (current) [ ] libpacemaker3-1.0.2-13.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/libpacemaker3-1.0.2-13.1.x86_64.rpm> 02-Mar-2009 14:26 279K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/libpacemaker3-1.0.2-13.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/libpacemaker3-1.0.2-13.1.x86_64.rpm.metalink> (NEW ?) [ ] pacemaker-1.0.2-13.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-1.0.2-13.1.x86_64.rpm> 02-Mar-2009 14:26 454K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-1.0.2-13.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-1.0.2-13.1.x86_64.rpm.metalink> <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-debuginfo-1.0.2-13.1.x86_64.rpm.metalink> (NEW ?) [ ] pacemaker-pygui-1.4-12.11.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-pygui-1.4-12.11.x86_64.rpm> 02-Mar-2009 15:05 166K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-pygui-1.4-12.11.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-pygui-1.4-12.11.x86_64.rpm.metalink> 2. Heartbeat (current): [ ] heartbeat-2.99.2-6.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-2.99.2-6.1.x86_64.rpm> 20-Nov-2008 15:58 405K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-2.99.2-6.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-2.99.2-6.1.x86_64.rpm.metalink> [ ] heartbeat-common-2.99.2-6.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-common-2.99.2-6.1.x86_64.rpm> 20-Nov-2008 15:58 274K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-common-2.99.2-6.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-common-2.99.2-6.1.x86_64.rpm.metalink> [ ] heartbeat-ldirectord-2.99.2-6.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-ldirectord-2.99.2-6.1.x86_64.rpm> 20-Nov-2008 15:58 127K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-ldirectord-2.99.2-6.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-ldirectord-2.99.2-6.1.x86_64.rpm.metalink> [ ] heartbeat-resources-2.99.2-6.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-resources-2.99.2-6.1.x86_64.rpm> 20-Nov-2008 15:58 192K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-resources-2.99.2-6.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-resources-2.99.2-6.1.x86_64.rpm.metalink> [ ] libheartbeat2-2.99.2-6.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libheartbeat2-2.99.2-6.1.x86_64.rpm> 20-Nov-2008 15:58 187K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libheartbeat2-2.99.2-6.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libheartbeat2-2.99.2-6.1.x86_64.rpm.metalink> [ ] libopenais2-0.80.3-12.2.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libopenais2-0.80.3-12.2.x86_64.rpm> 19-Nov-2008 18:12 113K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libopenais2-0.80.3-12.2.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libopenais2-0.80.3-12.2.x86_64.rpm.metalink> [ ] libpacemaker3-1.0.2-11.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libpacemaker3-1.0.2-11.1.x86_64.rpm> 02-Mar-2009 14:28 281K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libpacemaker3-1.0.2-11.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libpacemaker3-1.0.2-11.1.x86_64.rpm.metalink> (OLD ?) [ ] openais-0.80.3-12.2.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/openais-0.80.3-12.2.x86_64.rpm> 19-Nov-2008 18:12 224K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/openais-0.80.3-12.2.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/openais-0.80.3-12.2.x86_64.rpm.metalink> [ ] pacemaker-1.0.2-11.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-1.0.2-11.1.x86_64.rpm> 02-Mar-2009 14:28 464K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-1.0.2-11.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-1.0.2-11.1.x86_64.rpm.metalink> (OLD ?) [ ] pacemaker-mgmt-1.99.0-2.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-mgmt-1.99.0-2.1.x86_64.rpm> 02-Mar-2009 18:20 70K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-mgmt-1.99.0-2.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-mgmt-1.99.0-2.1.x86_64.rpm.metalink> [ ] pacemaker-mgmt-client-1.99.0-2.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-mgmt-client-1.99.0-2.1.x86_64.rpm> 02-Mar-2009 18:20 110K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-mgmt-client-1.99.0-2.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-mgmt-client-1.99.0-2.1.x86_64.rpm.metalink> Am I correct with my assumptions of the packages that have to be installed? TIA :-) Al -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Heartbeat / linux-ha has its own list. I think this is too detailed to discuss here. Greg On 3/7/09, LLLActive@GMX.Net <LLLActive@gmx.net> wrote:
Andrew Beekhof wrote:
Try the documentation at http://clusterlabs.org/wiki/Documentation instead
The section on clones might be of particular interest given that you want an active-active apache install.
On Fri, Mar 6, 2009 at 17:23, LLLActive@GMX.Net <LLLActive@gmx.net> wrote:
Hi all,
I am busy configuring an active/active HA2 (cib.xml) web server with SLES 10 SP2. I started manually with configuring a very basic with the YaST GUI and then manually checked ha.conf; thereafter I used hb_gui.
For a manual config, I find the http://www.linux-ha.org website documentation a little difficult to follow between HA versions 1 & 2. They do not have a setup only for Version 2; you have to read all V1 and then find the V2 differences like using the cib.xml in stead of the haresources config files. I think I managed to get the basic heartbeat running as far as configuring the ha.conf file manually (and with Yast & hb_gui). I have set up a failover with a common IP and switched with hb_gui, and checked with ssh that the server actually switched. I then addad a Webserver on the common IP, which also works with a manual switching in hb_gui; actually stopping it on one server and starting on the other. Automatic failover does not seem to work.
I found a more systematic description at http://www.novell.com/documentation/sles10/heartbeat/index.html?page=/docume... for heartbeat.
I can find no actual description of setting up an active-active system which runs a web server on each node separately, that fails over to the other when a node fails. It means that at fail over, the one node should run both web servers, switching back to the default server as soon as it comes up again. I created a group which first switches the IP and then the web server. It works with a manual switch over, but not automatically. This is only switching from a resource on one node to another, i.e. another web server. I will create a NFS common data share for both on the same DRBD HA data cluster as a htdocs directory, then the content will be the same source. This is the one web server. Another web server has to host an ERP II (Web 2.0) system with its own database (also on a DRBD HA cluster) on the other node. Whenever one node fails, the other should take over and host both web servers.
What I need then, are two web servers running each on its own node, and the takeover of the failing web server by the other node, which then runs both web servers till the default preferred server for the failed website comes back on.
Any indicators as where to look for such a setup is highly appreciated.
TIA
:-) Al -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Andrew,
Your documentation (very well presented) and product seems worth a try. I would like to try it, due to the reason of the "paying customers support only" that you mention. I do need a bit of clarification to install Pacemaker.
Your description on http://clusterlabs.org/wiki/Install: (I do not want to be over critical or nitpicking, but the language is sometimes a little unclear)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ It seems the thing to do these days is attempt to install Pacemaker with Heartbeat 2.1.4
##### Are you saying: "It seems many attempt to install Pacemaker together with Heartbeat 2.1.4" #####
/*PLEASE DO NOT ATTEMPT THIS*/ ##### Are you saying: "Please, do not install Pacemaker 0.6.6 (and later) together with Heartbeat 2.1.4" #####
Since Pacemaker was originally part of Heartbeat, it naturally includes many of the files contained in Heartbeat 2.1.x Most package managers including YUM, RPM and DEB will complain extremely loudly if you try this.
For versions of Pacemaker prior to 0.6.6, it was possible to build Heartbeat with /--disable-crm/ and this would make the package managers happy. This is what happened for the 2.1.3 packages from the OpenSUSE Build Service.
The problem now is that Pacemaker also includes the STONITH daemon from Heartbeat 2.1 and there is no clean way to disable it.
So please use Heartbeat 2.99.0 or higher.
##### Your reasons are: ##### Package managers recognise the pacemaker files as not compatible with Heartbeat 2.1.x, because they only have the same names but do not conform to the dependencies. ##### STONITH is included in Pacemaker 0.6.6 and Heartbeat 2.1.4, but the Pacemaker installation cannot disable the Heartbeat version. ##### Heartbeat 2.99.0 or higher should be used instead.
* Do it because its the same code as 2.1.4 but without the CRM and STONITH daemon. * Do it because it keeps the package managers happy. * Do it because thats what 0.6.6 was tested with. * Or just do it because the CRM in 2.1.4 is not and will never be supported except for /paying/ SLES10 customers.
##### The code of Heartbeat 2.99.0 is the same as that of Heartbeat 2.1.4, but without CRM and STONITH daemons. ##### Package managers accept Heartbeat 2.99.x ##### Pacemaker 0.6.6 was tested with Heartbeat 2.99.x ##### CRM 2.1.4 is only supported for paying customers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I first have to de-install Heartbeat 1.2.4 in SLES 10 SP2 x86_64.
I should install for SLES 10 SP2 x86_64:
1. Pacemaker (current)
[ ] libpacemaker3-1.0.2-13.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/libpacemaker3-1.0.2-13.1.x86_64.rpm> 02-Mar-2009 14:26 279K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/libpacemaker3-1.0.2-13.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/libpacemaker3-1.0.2-13.1.x86_64.rpm.metalink> (NEW ?) [ ] pacemaker-1.0.2-13.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-1.0.2-13.1.x86_64.rpm> 02-Mar-2009 14:26 454K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-1.0.2-13.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-1.0.2-13.1.x86_64.rpm.metalink> <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-debuginfo-1.0.2-13.1.x86_64.rpm.metalink> (NEW ?) [ ] pacemaker-pygui-1.4-12.11.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-pygui-1.4-12.11.x86_64.rpm> 02-Mar-2009 15:05 166K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-pygui-1.4-12.11.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering:/AISONLY/SLES_10/x86_64/pacemaker-pygui-1.4-12.11.x86_64.rpm.metalink>
2. Heartbeat (current):
[ ] heartbeat-2.99.2-6.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-2.99.2-6.1.x86_64.rpm> 20-Nov-2008 15:58 405K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-2.99.2-6.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-2.99.2-6.1.x86_64.rpm.metalink> [ ] heartbeat-common-2.99.2-6.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-common-2.99.2-6.1.x86_64.rpm> 20-Nov-2008 15:58 274K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-common-2.99.2-6.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-common-2.99.2-6.1.x86_64.rpm.metalink> [ ] heartbeat-ldirectord-2.99.2-6.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-ldirectord-2.99.2-6.1.x86_64.rpm> 20-Nov-2008 15:58 127K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-ldirectord-2.99.2-6.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-ldirectord-2.99.2-6.1.x86_64.rpm.metalink> [ ] heartbeat-resources-2.99.2-6.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-resources-2.99.2-6.1.x86_64.rpm> 20-Nov-2008 15:58 192K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-resources-2.99.2-6.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/heartbeat-resources-2.99.2-6.1.x86_64.rpm.metalink> [ ] libheartbeat2-2.99.2-6.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libheartbeat2-2.99.2-6.1.x86_64.rpm> 20-Nov-2008 15:58 187K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libheartbeat2-2.99.2-6.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libheartbeat2-2.99.2-6.1.x86_64.rpm.metalink> [ ] libopenais2-0.80.3-12.2.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libopenais2-0.80.3-12.2.x86_64.rpm> 19-Nov-2008 18:12 113K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libopenais2-0.80.3-12.2.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libopenais2-0.80.3-12.2.x86_64.rpm.metalink> [ ] libpacemaker3-1.0.2-11.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libpacemaker3-1.0.2-11.1.x86_64.rpm> 02-Mar-2009 14:28 281K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libpacemaker3-1.0.2-11.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/libpacemaker3-1.0.2-11.1.x86_64.rpm.metalink> (OLD ?) [ ] openais-0.80.3-12.2.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/openais-0.80.3-12.2.x86_64.rpm> 19-Nov-2008 18:12 224K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/openais-0.80.3-12.2.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/openais-0.80.3-12.2.x86_64.rpm.metalink> [ ] pacemaker-1.0.2-11.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-1.0.2-11.1.x86_64.rpm> 02-Mar-2009 14:28 464K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-1.0.2-11.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-1.0.2-11.1.x86_64.rpm.metalink> (OLD ?) [ ] pacemaker-mgmt-1.99.0-2.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-mgmt-1.99.0-2.1.x86_64.rpm> 02-Mar-2009 18:20 70K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-mgmt-1.99.0-2.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-mgmt-1.99.0-2.1.x86_64.rpm.metalink> [ ] pacemaker-mgmt-client-1.99.0-2.1.x86_64.rpm <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-mgmt-client-1.99.0-2.1.x86_64.rpm> 02-Mar-2009 18:20 110K Mirrors <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-mgmt-client-1.99.0-2.1.x86_64.rpm?mirrorlist> Metalink <http://download.opensuse.org/repositories/server:/ha-clustering/SLES_10/x86_64/pacemaker-mgmt-client-1.99.0-2.1.x86_64.rpm.metalink>
Am I correct with my assumptions of the packages that have to be installed?
TIA
:-) Al
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- Sent from my mobile device Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Andrew Beekhof -
Greg Freemyer -
LLLActive＠GMX.Net