Am 29.10.2008 21:31 Uhr schrieb "Lars Marowsky-Bree" unter <[EMAIL PROTECTED]>:
> On 2008-10-29T17:59:03, Annette Jäkel <[EMAIL PROTECTED]> wrote: > >> Is there a possibility to set up a group of ressources and an additional >> ressource and configure an order "start additional ressource if ANY of the >> group members has started"? > > No, there currently is not, I'm pretty sure. > > What is the use case? > > > Regards, > Lars I'm running a redundant fileserver cluster with two nodes, SAN Raids and NFS. I'm still searching for the correct order setup for my NFS service. Heartbeat manages underlying md-devices, the volume groups, the filesystems, the nfsserver and the NFS-IP, last but not least quotad. I wrote orders from md-devices to volume groups to filesystems to nfsserver. It was my intuitive idea, that nfsserver should start after all filesystems it manages are mounted. There are also collocations in chronological order for the resources. But my problem is that specific order of the nfsserver resource after all filesystem resources. This works fine until one of the file system crashes. Then nfsserver stops and the whole system doesnt work. Thats not what I want. If a file system crashes, for example because physical device was broken, the remaining devices and file systems should work and exported to clients. So maybe the nfsserver should start without any order? But I'm not shure that this is a good idea. I also dont want to run NFS, if there is no device it can manage. Meanwhile I read within Michael Schwartzkopff's Linux-HA book. He presented an example NFS service with DRBD devices and if I understand all setup steps right, there is really no order from any resource to nfsserver. I dont understand this. Within this context I think about setting up a group of all filesystem resources, setting attribute "ordered" to "false" and define a single resource of nfsserver ordered after the group - but dont wait for the complete start of the group, but starts if any resource of the group is running. In another thread (HA-NFS strategic question) Xinwei Hu suggested not to manage nfs but the step of exporting the devices, but seems theres no RA for this specific task. Until now I write /etc/exports by hand and call "exportfs -a" from outside heartbeat, if I add or delete a filesystem. Maybe a RA for exportfs would be a solution. Maybe I should set up filesystem resource operations for start and monitor with an on_fail attribute setting to ignore or block. Maybe I have to work with scores? (Xinwei Hu also suggested to set the score of the order from a filesystem resource to nfsserver less than 0). Sorry for the long posting, I'm pressed for time to solve the problem and reconfigure my heartbeat scenario. Regards, Annette _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
