Re: [Linux-HA] Antw: Re: ocf:pacemaker:ping: dampen
>>> Andrew Beekhof schrieb am 02.05.2011 um 13:20 in >>> Nachricht : > On Mon, May 2, 2011 at 8:27 AM, Ulrich Windl > wrote: > Andrew Beekhof schrieb am 29.04.2011 um 09:31 in > Nachricht > > : > >> On Fri, Apr 29, 2011 at 9:27 AM, Dominik Klein > >> wrote: > >> > It waits $dampen before changes are pushed to the cib. So that > >> > eventually occuring icmp hickups do not produce an unintended failover. > >> > > >> > At least that's my understanding. > >> > >> correcto > > > > Hi! > > > > Strange: So the update is basically just delayed by that amount of time? I > see no advantage: If you put a bad value to the CIB immediately or after some > delay, the value won't get better by that. "Damping" siggests some filtering > to me, but you are saying your are not filtering the values, but just > delaying them. Right? > > Only the "current" value is written. > So the cluster will tolerate "minor" outages provided they last for > less than the dampen interval and the monitor frequency is high > enough. Hi! It seems I'll have to use the source to understand. Maybe then I can suggest how to properly describe it ;-) Thanks anyway, maybe I'm too stupid to understand. Regards, Ulrich ___ 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: ocf:pacemaker:ping: dampen
On Mon, May 2, 2011 at 5:29 PM, Lars Ellenberg wrote: > On Mon, May 02, 2011 at 04:04:56PM +0200, Andrew Beekhof wrote: >> > Still, we may get a spurious failover in this case: >> > >> > reachability: >> > +__ >> > Node A monitoring intervals: >> > + - + + + - - - - - >> > Node B monitoring intervals: >> > + + - + + - - - - - >> > "dampening" interval: |-| >> > >> > Note how the "dampening" helps to ignore the first network "glitch". >> > >> > But for the "permanent" network problem, we may get spurious failover: >> >> Then your dampen setting is too short or interval too long :-) > > No. > Regardless of dampen and interval setting. > > Unless both nodes notice the change at the exact same time, > expire their dampen at the exact same time, This is where you've diverged. Once dampen expires on one node, _all_ nodes write their current value. > and place their updated > values into the CIB at exactly the same time. > > If a "ping node" just dies, then one node will always notice it first. > And regardless of dampen and interval settings, > one will reach the CIB first, and therefor the PE will see the > connectivity change first for only one of the nodes, and only later for > the other (once it noticed, *and* expired its dampen interval, too). > > Show me how you can work around that using dampen or interval settings. > > -- > : Lars Ellenberg > : LINBIT | Your Way to High Availability > : DRBD/HA support and consulting http://www.linbit.com > ___ > 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] get haresources2cib.py
On Mon, May 2, 2011 at 9:33 PM, Vinay Nagrik wrote: > Thank you Andrew. > > Could you please tell me where to get the DTD for cib.xml and where from can > I download crm shell. Both get installed with the rest of pacemaker > > thanks in anticipation. > > With best regards. > > nagrik > > On Mon, May 2, 2011 at 12:56 AM, Andrew Beekhof wrote: > >> On Sun, May 1, 2011 at 9:26 PM, Vinay Nagrik wrote: >> > Dear Andrew, >> > >> > I read your document "clusters from scratch" and found it very detailed. >> It >> > gave lots of information, but I was looking for creating a cib.xml and >> could >> > not decipher the language as to the syntex and different fields to be put >> in >> > cib.xml. >> >> Don't look at the xml. Use the crm shell. >> >> > >> > I am still looking for the haresources2cib.py script. >> >> Don't. It only creates configurations conforming to the older and now >> unsupported syntax. >> >> > I searched the web >> > but could not find anywhere. >> > >> > I have 2 more questions. >> > >> > Do I have to create the cib.xml file on the nodes I am running heartbeat >> v.2 >> > software. >> > Does cib.xml has to reside in /var/lib/crm directory or can it reside >> > anywhere else. >> > >> > Kindly provide these answers. I will greatly appreciate your help. >> > >> > Have a nice day. >> > >> > Thanks. >> > >> > nagrik >> > >> > On Sat, Apr 30, 2011 at 1:32 AM, Andrew Beekhof >> wrote: >> > >> >> Forget the conversion. >> >> Use the crm shell to create one from scratch. >> >> >> >> And look for the "clusters from scratch" doc relevant to your version >> >> - its worth the read. >> >> >> >> On Sat, Apr 30, 2011 at 1:19 AM, Vinay Nagrik >> wrote: >> >> > Hello Group, >> >> > >> >> > Kindly tell me where can I download >> >> > >> >> > haresources2cib.py file >> >> > >> >> > from. >> >> > >> >> > Please also tell me can I convert haresources file on a node where I >> am >> >> not >> >> > running high availability service and then can I copy the converted >> ..xml >> >> > file in >> >> > >> >> > /var/lib/heartbeat >> >> > >> >> > directory on which I am running the high availability. >> >> > >> >> > Also does >> >> > >> >> > cib file >> >> > >> >> > must resiede under >> >> > >> >> > /var/lib/heartbeat >> >> > >> >> > directory or can it reside under any directory like under >> >> > >> >> > /etc. >> >> > >> >> > please let me know. I am just a beginner. >> >> > >> >> > Thanks in advance. >> >> > >> >> > -- >> >> > Thanks >> >> > >> >> > Nagrik >> >> > ___ >> >> > 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 >> >> >> > >> > >> > >> > -- >> > Thanks >> > >> > Nagrik >> > ___ >> > 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 >> > > > > -- > Thanks > > Nagrik > ___ > 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] get haresources2cib.py
Thank you Andrew. Could you please tell me where to get the DTD for cib.xml and where from can I download crm shell. thanks in anticipation. With best regards. nagrik On Mon, May 2, 2011 at 12:56 AM, Andrew Beekhof wrote: > On Sun, May 1, 2011 at 9:26 PM, Vinay Nagrik wrote: > > Dear Andrew, > > > > I read your document "clusters from scratch" and found it very detailed. > It > > gave lots of information, but I was looking for creating a cib.xml and > could > > not decipher the language as to the syntex and different fields to be put > in > > cib.xml. > > Don't look at the xml. Use the crm shell. > > > > > I am still looking for the haresources2cib.py script. > > Don't. It only creates configurations conforming to the older and now > unsupported syntax. > > > I searched the web > > but could not find anywhere. > > > > I have 2 more questions. > > > > Do I have to create the cib.xml file on the nodes I am running heartbeat > v.2 > > software. > > Does cib.xml has to reside in /var/lib/crm directory or can it reside > > anywhere else. > > > > Kindly provide these answers. I will greatly appreciate your help. > > > > Have a nice day. > > > > Thanks. > > > > nagrik > > > > On Sat, Apr 30, 2011 at 1:32 AM, Andrew Beekhof > wrote: > > > >> Forget the conversion. > >> Use the crm shell to create one from scratch. > >> > >> And look for the "clusters from scratch" doc relevant to your version > >> - its worth the read. > >> > >> On Sat, Apr 30, 2011 at 1:19 AM, Vinay Nagrik > wrote: > >> > Hello Group, > >> > > >> > Kindly tell me where can I download > >> > > >> > haresources2cib.py file > >> > > >> > from. > >> > > >> > Please also tell me can I convert haresources file on a node where I > am > >> not > >> > running high availability service and then can I copy the converted > ..xml > >> > file in > >> > > >> > /var/lib/heartbeat > >> > > >> > directory on which I am running the high availability. > >> > > >> > Also does > >> > > >> > cib file > >> > > >> > must resiede under > >> > > >> > /var/lib/heartbeat > >> > > >> > directory or can it reside under any directory like under > >> > > >> > /etc. > >> > > >> > please let me know. I am just a beginner. > >> > > >> > Thanks in advance. > >> > > >> > -- > >> > Thanks > >> > > >> > Nagrik > >> > ___ > >> > 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 > >> > > > > > > > > -- > > Thanks > > > > Nagrik > > ___ > > 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 > -- Thanks Nagrik ___ 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: ocf:pacemaker:ping: dampen
On Mon, May 02, 2011 at 04:04:56PM +0200, Andrew Beekhof wrote: > > Still, we may get a spurious failover in this case: > > > > reachability: > > +__ > > Node A monitoring intervals: > > + - + + + - - - - - > > Node B monitoring intervals: > > + + - + + - - - - - > > "dampening" interval: |-| > > > > Note how the "dampening" helps to ignore the first network "glitch". > > > > But for the "permanent" network problem, we may get spurious failover: > > Then your dampen setting is too short or interval too long :-) No. Regardless of dampen and interval setting. Unless both nodes notice the change at the exact same time, expire their dampen at the exact same time, and place their updated values into the CIB at exactly the same time. If a "ping node" just dies, then one node will always notice it first. And regardless of dampen and interval settings, one will reach the CIB first, and therefor the PE will see the connectivity change first for only one of the nodes, and only later for the other (once it noticed, *and* expired its dampen interval, too). Show me how you can work around that using dampen or interval settings. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com ___ 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] DRBD and HA-Linux
You are wanting port bonding (http://www.linuxhorizon.ro/bonding.html) This will bond two port together as a single port and IP. You then have twice the bandwidth and should a port die the other will traffic the load. For reliablity you want the two ports to be coming from different chips. Say, on on the mother board and another from a card. - Original Message - From: "Peter Butler" To: linux-ha@lists.linux-ha.org Sent: Friday, April 29, 2011 1:04:30 PM Subject: [Linux-HA] DRBD and HA-Linux Hello, I have two Linux systems (i.e. two SBCs in a single chassis) A and B that are connected to one another via two independent Ethernet fabrics: System A System B +--+ |--+ | | | | | eth0---+--+---eth0 | | | | | | | | | | | | | | | | | | eth1---+--+---eth1 | | | | | +--+ +--+ I am setting up DRBD between the two Systems, which is easy enough in itself, however I want to implement it with redundant IP connectivity. DRBD only allows for a single IP address to be listed for both the local and remote nodes (i.e. *either* the eth0 IP addresses *or* the eth1 addresses), but not both. As such I was hoping that maybe HA-Linux could help me in this regard. That is, is there a way to configure each system such that it presents a single IP address to the other system, such that HA-Linux manages which Ehternet fabric is used (should one of them fail)? i.e. System A System B +--+ |--+ | | | | | eth0---+ +---eth0 | | |\/| | | | \ / | | | | ethA--ethB | | | | / \ | | | |/\| | | eth1---+ +---eth1 | | | | | +--+ +--+ ___ 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: ocf:pacemaker:ping: dampen
On Mon, May 2, 2011 at 3:51 PM, Lars Ellenberg wrote: > On Mon, May 02, 2011 at 01:20:16PM +0200, Andrew Beekhof wrote: >> On Mon, May 2, 2011 at 8:27 AM, Ulrich Windl >> wrote: >> Andrew Beekhof schrieb am 29.04.2011 um 09:31 in >> Nachricht >> > : >> >> On Fri, Apr 29, 2011 at 9:27 AM, Dominik Klein >> >> wrote: >> >> > It waits $dampen before changes are pushed to the cib. So that >> >> > eventually occuring icmp hickups do not produce an unintended failover. >> >> > >> >> > At least that's my understanding. >> >> >> >> correcto >> > >> > Hi! >> > >> > Strange: So the update is basically just delayed by that amount of >> > time? I see no advantage: If you put a bad value to the CIB >> > immediately or after some delay, the value won't get better by that. >> > "Damping" siggests some filtering to me, but you are saying your are >> > not filtering the values, but just delaying them. Right? >> >> Only the "current" value is written. >> So the cluster will tolerate "minor" outages provided they last for >> less than the dampen interval and the monitor frequency is high >> enough. > > Still, we may get a spurious failover in this case: > > reachability: > +__ > Node A monitoring intervals: > + - + + + - - - - - > Node B monitoring intervals: > + + - + + - - - - - > "dampening" interval: |-| > > Note how the "dampening" helps to ignore the first network "glitch". > > But for the "permanent" network problem, we may get spurious failover: Then your dampen setting is too short or interval too long :-) > > One dampening interval after node B notices loss of reachability, > it will trigger a PE run, potentially moving things from B to > A, because on A, the reachability (in the CIB) is still ok. > > Shortly thereafter, the dampening interval on A also expires, and the > CIB will be updated with "A cannot reach out there either". > > Any resource migrations triggered by "B cannot reach out there" > are now recognized as spurious. > > Question is, how could we avoid them? > > "ipfail" used to "ask the peer", wait for the peer to notice the new > situation as well, and only then trigger actions. > > We could possibly store a short history of values, and actually do some > "filtering" arithmetic with them. Not sure if this should be done > inside or outside of the CIB. Probably outside. Yes, outside :-) One of these attrd needs a rewrite :-( ___ 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: ocf:pacemaker:ping: dampen
On Mon, May 02, 2011 at 01:20:16PM +0200, Andrew Beekhof wrote: > On Mon, May 2, 2011 at 8:27 AM, Ulrich Windl > wrote: > Andrew Beekhof schrieb am 29.04.2011 um 09:31 in > Nachricht > > : > >> On Fri, Apr 29, 2011 at 9:27 AM, Dominik Klein > >> wrote: > >> > It waits $dampen before changes are pushed to the cib. So that > >> > eventually occuring icmp hickups do not produce an unintended failover. > >> > > >> > At least that's my understanding. > >> > >> correcto > > > > Hi! > > > > Strange: So the update is basically just delayed by that amount of > > time? I see no advantage: If you put a bad value to the CIB > > immediately or after some delay, the value won't get better by that. > > "Damping" siggests some filtering to me, but you are saying your are > > not filtering the values, but just delaying them. Right? > > Only the "current" value is written. > So the cluster will tolerate "minor" outages provided they last for > less than the dampen interval and the monitor frequency is high > enough. Still, we may get a spurious failover in this case: reachability: +__ Node A monitoring intervals: +-+++----- Node B monitoring intervals: ++-++----- "dampening" interval: |-| Note how the "dampening" helps to ignore the first network "glitch". But for the "permanent" network problem, we may get spurious failover: One dampening interval after node B notices loss of reachability, it will trigger a PE run, potentially moving things from B to A, because on A, the reachability (in the CIB) is still ok. Shortly thereafter, the dampening interval on A also expires, and the CIB will be updated with "A cannot reach out there either". Any resource migrations triggered by "B cannot reach out there" are now recognized as spurious. Question is, how could we avoid them? "ipfail" used to "ask the peer", wait for the peer to notice the new situation as well, and only then trigger actions. We could possibly store a short history of values, and actually do some "filtering" arithmetic with them. Not sure if this should be done inside or outside of the CIB. Probably outside. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com ___ 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: ocf:pacemaker:ping: dampen
On Mon, May 2, 2011 at 8:27 AM, Ulrich Windl wrote: Andrew Beekhof schrieb am 29.04.2011 um 09:31 in Nachricht > : >> On Fri, Apr 29, 2011 at 9:27 AM, Dominik Klein wrote: >> > It waits $dampen before changes are pushed to the cib. So that >> > eventually occuring icmp hickups do not produce an unintended failover. >> > >> > At least that's my understanding. >> >> correcto > > Hi! > > Strange: So the update is basically just delayed by that amount of time? I > see no advantage: If you put a bad value to the CIB immediately or after some > delay, the value won't get better by that. "Damping" siggests some filtering > to me, but you are saying your are not filtering the values, but just > delaying them. Right? Only the "current" value is written. So the cluster will tolerate "minor" outages provided they last for less than the dampen interval and the monitor frequency is high enough. ___ 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] DRBD and HA-Linux
Hello, I have two Linux systems (i.e. two SBCs in a single chassis) A and B that are connected to one another via two independent Ethernet fabrics: System A System B +--+ |--+ | | | | | eth0---+--+---eth0 | | | | | | | | | | | | | | | | | | eth1---+--+---eth1 | | | | | +--+ +--+ I am setting up DRBD between the two Systems, which is easy enough in itself, however I want to implement it with redundant IP connectivity. DRBD only allows for a single IP address to be listed for both the local and remote nodes (i.e. *either* the eth0 IP addresses *or* the eth1 addresses), but not both. As such I was hoping that maybe HA-Linux could help me in this regard. That is, is there a way to configure each system such that it presents a single IP address to the other system, such that HA-Linux manages which Ehternet fabric is used (should one of them fail)? i.e. System A System B +--+ |--+ | | | | | eth0---+ +---eth0 | | |\/| | | | \ / | | | | ethA--ethB | | | | / \ | | | |/\| | | eth1---+ +---eth1 | | | | | +--+ +--+ ___ 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] [PATCH] Low: adding cluster-glue-extras subpackage
Hi Vadim,
On Sun, May 01, 2011 at 10:53:44AM -0400, Vadym Chepkov wrote:
> Hi,
>
> recent addition of vcenter external plugin generates dependency on exotic
> perl(VMware::VIRuntime) package, majority won't use.
The dependency is automatically generated by find-requires on RH
distributions. Whether the package is exotic or not, depends on
what you run. One could brand exotic just about any stonith
plugin.
> I propose to create a separate subpackage, cluster-glue-extras, for all
> optional components
That is a wrong place to fix this issue. We should not create an
extra package just because find-requires (actually perl.req)
cannot be told not to create a dependency on a module.
Thanks,
Dejan
> # HG changeset patch
> # User Vadym Chepkov
> # Date 1304261276 14400
> # Node ID f8122aff3cef64089d611682f1b77a7695102757
> # Parent b3ab6686445b5267a18a37d1a1404170693306db
> Low: adding cluster-glue-extras subpackage
>
> Adding cluster-glue-extras subpackage for optional components
>
> diff --git a/cluster-glue-fedora.spec b/cluster-glue-fedora.spec
> --- a/cluster-glue-fedora.spec
> +++ b/cluster-glue-fedora.spec
> @@ -139,6 +139,7 @@
> %{_libdir}/stonith/plugins/stonith2/*.so
> %{_libdir}/stonith/plugins/stonith2/*.py*
> %exclude %{_libdir}/stonith/plugins/external/ssh
> +%exclude %{_libdir}/stonith/plugins/external/vcenter
> %exclude %{_libdir}/stonith/plugins/stonith2/null.so
> %exclude %{_libdir}/stonith/plugins/stonith2/ssh.so
> %{_libdir}/stonith/plugins/xen0-ha-dom0-stonith-helper
> @@ -214,11 +215,23 @@
> %{_includedir}/pils
> %{_datadir}/%{name}/lrmtest
> %{_libdir}/heartbeat/plugins/test/test.so
> -%{_libdir}/stonith/plugins/external/ssh
> -%{_libdir}/stonith/plugins/stonith2/null.so
> -%{_libdir}/stonith/plugins/stonith2/ssh.so
> %doc AUTHORS
> %doc COPYING
> %doc COPYING.LIB
>
> +%package -n cluster-glue-extras
> +Summary: Additional cluster-glue components
> +Group: Application/System
> +Requires:cluster-glue-libs = %{version}-%{release}
> +
> +%description -n cluster-glue-extras
> +cluster-glue-extras includes optional components of cluster-glue framework
> +
> +%files -n cluster-glue-extras
> +%defattr(-,root,root)
> +%{_libdir}/stonith/plugins/external/ssh
> +%{_libdir}/stonith/plugins/external/vcenter
> +%{_libdir}/stonith/plugins/stonith2/null.so
> +%{_libdir}/stonith/plugins/stonith2/ssh.so
> +
> %changelog
>
> Cheers,
> Vadym
>
>
> ___
> 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] get haresources2cib.py
On Sun, May 1, 2011 at 9:26 PM, Vinay Nagrik wrote: > Dear Andrew, > > I read your document "clusters from scratch" and found it very detailed. It > gave lots of information, but I was looking for creating a cib.xml and could > not decipher the language as to the syntex and different fields to be put in > cib.xml. Don't look at the xml. Use the crm shell. > > I am still looking for the haresources2cib.py script. Don't. It only creates configurations conforming to the older and now unsupported syntax. > I searched the web > but could not find anywhere. > > I have 2 more questions. > > Do I have to create the cib.xml file on the nodes I am running heartbeat v.2 > software. > Does cib.xml has to reside in /var/lib/crm directory or can it reside > anywhere else. > > Kindly provide these answers. I will greatly appreciate your help. > > Have a nice day. > > Thanks. > > nagrik > > On Sat, Apr 30, 2011 at 1:32 AM, Andrew Beekhof wrote: > >> Forget the conversion. >> Use the crm shell to create one from scratch. >> >> And look for the "clusters from scratch" doc relevant to your version >> - its worth the read. >> >> On Sat, Apr 30, 2011 at 1:19 AM, Vinay Nagrik wrote: >> > Hello Group, >> > >> > Kindly tell me where can I download >> > >> > haresources2cib.py file >> > >> > from. >> > >> > Please also tell me can I convert haresources file on a node where I am >> not >> > running high availability service and then can I copy the converted ..xml >> > file in >> > >> > /var/lib/heartbeat >> > >> > directory on which I am running the high availability. >> > >> > Also does >> > >> > cib file >> > >> > must resiede under >> > >> > /var/lib/heartbeat >> > >> > directory or can it reside under any directory like under >> > >> > /etc. >> > >> > please let me know. I am just a beginner. >> > >> > Thanks in advance. >> > >> > -- >> > Thanks >> > >> > Nagrik >> > ___ >> > 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 >> > > > > -- > Thanks > > Nagrik > ___ > 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
