From: Marc G. <gr...@at...> - 2007-10-10 14:03:11
|
On Wednesday 10 October 2007 15:45:37 Gordan Bobic wrote: > On Wed, 10 Oct 2007, Marc Grimme wrote: > > no the iscsid.conf should be created from cluster.conf. Because of the ip > > of the iscsi-source. It might be one server gets it root from on > > iscsi-device and another from another iscsi-device. > > Some customers have clusters with different roots for different nodes. > > Err - I thought this was about _shared_ roots, not unshared-roots. :-p Yes it still is. One cluster with root x and another with root y but still in the same cluster. ;-) > What makes iscsid.conf from cluster.conf, then? You. ;-) That has to be done. I don't remember how it looks like. I implemented it a long time ago. But wouldn't it do it to just copy a template /etc/iscsi.conf into the initrd and then add the lines for the device from the cluster.conf. You should get the value for the rootsource as described on my blog. > And what would configure the /var/lib/iscsi/*? Hmm. What is in there? > I've found I have to jump through a few hoops to get this working even > without the shared GFS. I have to set up connections to manual, and set > the username/password up in iscsid.conf, then do the iscsi discovery, then Uhh, username/password. Ahh rootsource="iscsi://username:password@iscsi-ip:port/" that sound not too bad. > just change the volume I want to mount to automatic. Then it correctly > mounts on the correct /dev/sd? device. Ok these commands should be added to iscsiLoad in boot-scripts/etc/iscsi-lib.sh. > > >> 3) Add iscsi and iscsid init scripts to the relevant run-level on OSR > >> initrd. > > > > there are no run-levels inside the initrd ;-( . So the starting has to be > > done manually within iscsi-lib and the iscsiLoad Function. > > Well, run-levels aren't what I meant as such. Are init scripts handled in > a similar way to the full setup? Even if it is a startup script invoking: > iscsid start > iscsi start This can easily be done why not. Cannot think of anything against it. > I have yet to get a single node booting off GFS as root. I'm some way off > having a whole cluster running at the moment. Need to get the iSCSI > working first. Yes. This takes some time. But is nice when it is running. > > > > > rootvolume has to be given always. It tells where to mount the rootfs > > from. rootsource is optional: I would use it for telling the cluster that > > the rootdevice itself is an iscsione and the ipadress is x.y.z. > > Right, OK. But before this can work, surely the iscsi daemons have to be > running first? If so start them before. > > com-expert: imediately starts a shell after initrd is loaded. > > Well, at the moment it fails with the message that it can't find root and > drops me to the initrd shell. What I need at that point is functioning > iscsi components. I think that is logically the next thing I need to add > to the initrd. exactly ;-) > > > > It is but RHEL5 has slightly different packages. > > Right - so in theory, once there are multiple machines running, they'll > all wait in initrd for enough machines to reach quorum, and then mount the > root and proceed from there? exactly. > > Gordan > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Open-sharedroot-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/open-sharedroot-devel Have fun and don't lose temper -- Gruss / Regards, Marc Grimme Phone: +49-89 452 3538-14 http://www.atix.de/ http://www.open-sharedroot.org/ ** Visit us at LinuxWorld Conference & Expo 31.10. - 01.11.2007 in Jaarbeurs Utrecht - The Netherlands ATIX stand: Hall 9 / B 005 ** ATIX Informationstechnologie und Consulting AG Einsteinstr. 10 85716 Unterschleissheim Deutschland/Germany |