FWIW, the "Exploring HASF" document does NOT use private containers. It uses shared containers, so you will need to adjust some things, in particular the type of CSM container (shared -> private), and use the evms_failover RA instead of the evmsSCC RA.
Yan Chris wrote: > Hi Andrew, > Thanks for your reply. > > Yes, I got that doc, however it goes through the integration of OCFS2 > and Heartbeat2 using the command line, while my test are with the > usage of reiserfs (or ext3) and the hb_gui. > > I mean, if the resource configuration in order to have the private > container resource to failover properly MUST be done using the command > line, for any valid reason, than I will of course go through that way, > otherwise I would really like to find the proper way of doing it using > the hb_gui. > > Anyway, I will go through the doc once again and I'll double check if > I can find some hints I eventually missed in the first read. > > Thanks, > Chris > > > > > On Nov 21, 2007 3:07 PM, Andrew Beekhof <[EMAIL PROTECTED]> wrote: >> On Nov 21, 2007, at 10:11 AM, Christian Zemella wrote: >> >>> Hi All, >>> Anybody out there managed to have EVMS container resources >>> properly failing over in a 2 node Heartbeat 2 cluster running on SLES >>> 10 SP1 ? >> I believe so... have you read the documentation below? >> http://wiki.novell.com/images/3/37/Exploring_HASF.pdf >> >>> >>> In my lab I can only start and stop the resource on the node that has >>> the container assigned within evms, while if I shut down that node, >>> the fail over does not occur as the evms_failover resource goes in >>> time out; as soon as the other nodes comes up again it takes the >>> resource back properly. >>> >>> In my environment I created the following: >>> >>> I'm working using 2 VMWare boxes sharing one 4GB plain disk that >>> works as SAN; >>> >>> EVMS: >>> >>> I created a private container (gwcont) on the shared disk using CSM >>> plug-in and in it an EVMS Volume (gwvol); >>> on the volume i make a reiserfs file system; >>> I verified that the HA plug-in was working and that the node assigned >>> to the container can manually mount it. >>> >>> HB_GUI: >>> >>> I created a group ordered and collocated; >>> Inside the group i created the following resources: >>> - evmsSCC --> no No attributes, No Parameters; >>> - evms_failover --> Parameter: 1 Value: gwcont (name of the EVMS >>> container ) >>> - Filesystem --> Parameter: fstype Value: reiserfs; Parameter: device >>> Value: /dev/evms/gwcont/gwvol; Parameter: directory Value: /gw; >>> - IPAddr --> Parameter ip Value: xxx.xxx.xxx.xxx >>> >>> I then created a Location constraint so to assign the value 100 for >>> the group to run on Node 1, and a second Location constraint so to >>> assign the value 50 for the group to run on Node2. >>> >>> ha.cf: >>> >>> *** >>> autojoin any >>> crm true >>> ucast eth1 xxx.xxx.xxx.xxx (ipaddress of eth1 on the other node) >>> auto_failback off >>> node CZVLabNode1 >>> node CZVLabNode2 >>> respawn hacluster /usr/lib/heartbeat/ccm >>> respawn root /sbin/evmsd >>> apiauth evms uid=hacluster,root >>> apiauth ccm uid=hacluster, root >>> apiauth crm uid=hacluster,root >>> *** >>> >>> On both nodes I issued: >>> >>> chkconfig boot.evms on >>> >>> My feeling is that I'm doing something wrong in the configuration, >>> anybody can point me to the error I'm eventually doing here ? >>> >>> TIA, >>> Chris >>> _______________________________________________ >>> Linux-HA mailing list >>> [email protected] >>> http://lists.linux-ha.org/mailman/listinfo/linux-ha >>> See also: http://linux-ha.org/ReportingProblems >> _______________________________________________ >> Linux-HA mailing list >> [email protected] >> http://lists.linux-ha.org/mailman/listinfo/linux-ha >> See also: http://linux-ha.org/ReportingProblems >> > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
