-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey all!  I configured and maintain a heartbeat 1.2.3 cluster (load
balancer failover) and didn't really experience any problems.

Now I'm trying to get familiar and competent with 2.x and I'm running
into brick walls.  Reading the documentation, it seems to be very
straight forward, but I can't get it to do what I want.  To date, I've
only tried to configure it with the gui, but I'm happy to use the cli as
well.

Goal: an internal server on old crappy hardware locks on occassion.
Another internal server is running a copy of the same services, can
bring up the IP of the server that locked, and the services hobble along
until someone can reboot the locked machine.  I'm effectively doing an
IP address takeover, but the machine that I'm taking over the IP from is
NOT running heartbeat.

My thought process was that heartbeat would run in a single node
configuration and that I could define two resources:
1) pingd that would ping a secondary IP (192.168.100.6) on the machine that
occassionally locks
2) an ipaddr2 that does "if not pingd then ipaddr2 up" (192.168.100.9)

I can get the ipaddr2 resource to manually start and stop.  I have not
been able to get the pingd process to actually send out any pings.  I
have not been able to figure out how to tell ipaddr2 to only turn on if
pingd fails either.

Here is the generated cib.xml.

 <cib generated="true" admin_epoch="0" have_quorum="true" num_peers="1" 
cib_feature_revision="1.3" epoch="9" num_
updates="342" cib-last-written="Mon Aug 20 15:22:16 2007" ccm_transition="1" 
dc_uuid="53e4b339-8b6d-43fe-bf86-c9a
ef9f4ca61">
   <configuration>
     <crm_config>
       <cluster_property_set id="cib-bootstrap-options">
         <attributes>
           <nvpair name="last-lrm-refresh" 
id="cib-bootstrap-options-last-lrm-refresh" value="1187643852"/>
         </attributes>
       </cluster_property_set>
     </crm_config>
     <nodes>
       <node id="53e4b339-8b6d-43fe-bf86-c9aef9f4ca61" uname="space.ivenue.net" 
type="normal"/>
     </nodes>
     <resources>
       <primitive id="ldapip" class="ocf" type="IPaddr2" provider="heartbeat" 
is_managed="1">
         <instance_attributes id="ldapip_instance_attrs">
           <attributes>
             <nvpair id="3a403587-6ef7-44eb-8e4f-e82d82c28067" name="ip" 
value="192.168.100.6"/>
             <nvpair id="734742c4-92e5-4f59-b063-aeba8db1241e" name="nic" 
value="eth0:0"/>
             <nvpair id="1dbaadaf-fc6b-47a9-abed-0029765860c3" 
name="cidr_netmask" value="24"/>
           </attributes>
         </instance_attributes>
         <operations>
           <op id="a8449e20-6ee3-4bf0-9d8a-cb1d035f79c2" name="start" 
interval="2s" timeout="60s"/>
         </operations>
       </primitive>
       <primitive id="pingio" class="ocf" type="pingd" provider="heartbeat" 
is_managed="#default">
         <instance_attributes id="pingio_instance_attrs">
           <attributes>
             <nvpair id="162649da-ae5d-4a84-a3ae-744780d95606" name="host_list" 
value="192.168.100.9"/>
           </attributes>
         </instance_attributes>
         <operations>
           <op id="328518fa-24f4-4ae2-ad90-c458e77f7b18" name="monitor" 
interval="2s" timeout="10s"/>
         </operations>
       </primitive>
     </resources>
     <constraints>
       <rsc_colocation id="ioisup" from="pingio" to="ldapip" score="-INFINITY"/>
     </constraints>
   </configuration>
 </cib>

* Note: My first attempt at this, I actually installed heartbeat on both
machines and I created an ipaddr2 resource.  When I clicked the Play
button, it started the resource on both machines.  I never could figure
out how to make it only start on one.  I don't have a copy of that old
cib.xml.

I tend to think that something very basic is going over my head.  1.2.x
was a breeze to set up, 2.0.x is kicking my butt at the moment.

TIA!
- -- 
Regards...              Todd
Chris: grep 500 sendmail.mc 
undefine(`FAIL_MAIL_OVER_500_MILES')dnl
Chris: just in case ...
Linux kernel 2.6.17-6mdv   load average: 0.12, 0.12, 0.04
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFGyhW2Y2VBGxIDMLwRAmwsAJwNZbJ2eZFHChs3RsDLkFQcO9WeSACeO2lF
3mLFHPJMNc3ArtNekeHKPsg=
=ox1D
-----END PGP SIGNATURE-----
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to