[SSI-devel] Re: [SSI-users] root failover
Brought to you by:
brucewalker,
rogertsang
Menu
▾
▴
[SSI-devel] Re: [SSI-users] root failover
|
From: Brian J. W. <Bri...@hp...> - 2005-11-04 21:06:23
|
Hi Karl, I'm taking this discussion online, because others might have input to off= er. Karl Merritts wrote: > Of the ones I listed earlier there are only four that I see that might=20 > be needed immediately: > cp -pr ../openssi-fc/initscripts . > cp -pr ../openssi-fc/chkconfig/ . My understanding is that SuSE has the aaa_base package, rather than the=20 two Fedora packages listed above. I remember a lot of conversation=20 between En Chiang and Bharata (IIRC) regarding this topic. > cp -pr ../openssi-fc/pam/ . This exists on my SuSE 9.1 installation. I recall that the OpenSSI=20 changes to it are very minor and only needed for certain cases. If you=20 like, you can postpone this port, but it should be done with the SuSE=20 pam source, not by copying over the Fedora pam source. > cp -pr ../openssi-fc/udev/ . This seems important, since devfs is no longer used with the 2.6 kernel.=20 John would probably have a better idea, since he did the udev work.=20 Again, and port should be done using SuSE udev source. Regards, Brian >=20 > What do you think? >=20 > -Karl >=20 > On 11/4/05, *Karl Merritts* <km...@gm... <mailto:km...@gm...>= >=20 > wrote: >=20 > Roger, > # ls > aaa_base COPYING.libcluster kernel NEWS =20 > README > aaa_base.more CVS kernel.configs nfs-utils = specs > AUTHORS docs kernel.debug nfs-utils.more=20 > strace > ChangeLog drbd kernel.patches openssi-tools = sudo > ChangeLog.0 e2fsprogs logrotate portmap =20 > sysvinit > configure.ac <http://configure.ac> install =20 > Makefile portmap.more util-linux > CONTENTS install.pm <http://install.pm> Makefile.am > <http://Makefile.am> procps > COPYING ipvsadm mkinitrd psmisc >=20 > Instead of going out and finding the am-utils, lustre etc for suse > and doing what is necessary for them to work right now, because > these packages are more features than absolutely necessary for the > to operate, do you think I should leave those changes out and come > back to them later?=20 >=20 > There should be more than enough merging to be done without those > changes. >=20 > -Karl >=20 >=20 > On 11/4/05, *Roger Tsang* < rog...@gm... > <mailto:rog...@gm...>> wrote: >=20 > Hi Karl, >=20 > These are for building the userspace RPM's against the original > Fedora userspace source RPMS for OpenSSI. Are you sure > OPENSSI-SU doesn't have any of these directories? Wouldn't SuS= E > have a different version of its userspace utilities that need t= o > be ported to OpenSSI? This means we might have to port your > SuSE RPMS into those directories instead of copying straight > from Fedora branch. >=20 > Roger >=20 >=20 >=20 > On 11/4/05, *Karl Merritts* < km...@gm... > <mailto:km...@gm...>> wrote: >=20 > Guys, > Here is what I copied in so far: > cp -pr ../openssi-fc/initscripts . > cp -pr ../openssi-fc/lustre . > cp -pr ../openssi-fc/am-utils/ . > cp -pr ../openssi-fc/chkconfig/ . > cp -pr ../openssi-fc/devfsd/ . > cp -pr ../openssi-fc/pam/ . > cp -pr ../openssi-fc/udev/ . >=20 > From what I can see for the merge they need to be in there= . >=20 > -Karl >=20 >=20 >=20 >=20 >=20 > On 11/4/05, *Karl Merritts* < km...@gm... > <mailto:km...@gm...>> wrote: >=20 > Brian and Roger, >=20 > When I did the merge none of the lustre patches files > are present. So running 'cvs > rm -f lustre' seems unnecessary. For the time being (a= t > least until I find out how to properly setup the aliase= s > mentioned below) I am going to copy the things in that = I > need from openssi-fc tree so that I can test the > Makefile etc.=20 >=20 > -Karl >=20 > On 11/3/05, *Karl Merritts* < km...@gm... > <mailto:km...@gm...>> wrote: >=20 > Brian, > The largest chunks of code seem to be in mount.c an= d > mkinitrd script.=20 >=20 > So I should just be able to do a: > # cd openssi > # cvs update >=20 > That should give me all of the updates that Roger > has checked for the kernel right? > I assume so but just want to make sure. >=20 > Please explain briefly how the aliasing that you > mention below works and should be implemented > because on that part I am a bit confused. >=20 > What would I need to do to have lustre properly > populated in the OPENSSI-SU if it is not checked > into the repository? >=20 > Thanks, > Karl >=20 >=20 >=20 >=20 >=20 >=20 > That should be all I need to do >=20 >=20 > On 10/27/05, *Brian J. Watson* < > Bri...@hp... > <mailto:Bri...@hp...>> wrote: >=20 > Hi Karl, >=20 > Just a simple update (no -j options) should be > all that is needed to get > the stuff in kernel.patches/common. The stuff i= n > there is identical > between development branches, so no real merge > is needed. >=20 > The stuff in openssi/lustre should also be > common files. The reason you > got it with your merge is because aliases have > not been created for > OPENSSI-SU, MERGE-SU-FC, and MERGE-FC-SU. What > you should do is run `cvs > rm -f lustre' in your merge sandbox for OpenSSI= , > so that you don't > checkin an identical but separate copy of > Lustre. Later, you or Roger > should create the three aliases that I listed > above, so that this > doesn't happend again. >=20 > Are there any other huge chunks of code that > were introduced by your merge? >=20 > Best, >=20 > Brian >=20 >=20 > Roger Tsang wrote: >> Actually no. I just finished adding the MERGE > tags for those files in >> kernel.patches/common. Run your cvs update > again and send me the >> output. Thanks. >> >> Roger >> >> On 10/27/05, *Karl Merritts* < > km...@gm... <mailto:km...@gm...> >> <mailto:km...@gm... > <mailto:km...@gm...>>> wrote: >> >> >> Roger, >> I went ahead and ran the cvs update -j > MERGE-SU-FC -j OPENSSI-FC. >> There were only 6 files that had > conflicts. Is there anyway to >> verify that this is all the needs to be > done? My plan was to build >> and make sure the things that were affected > work correctly before I >> tagged. With all of the packages and > patches that were added(lustre >> etc.) it would quite a bit of work to > verify everything on SuSE. So >> should I just focus on core > functionality? Any suggestions for >> testing would be greatly appreciated. >> >> On to the kernel issue. The way I have > understood it is that this >> is also one of the pieces that is shared > between all of the OpenSSI >> distros. So I should have also recieved > all of you kernel changes >> when I ran the update, right? >> Are kernel changes checked in the tarball > or applied as patches? >> From I have seen it looks like the latter. >> >> -Karl >> >> >> >> On 10/27/05, *Roger Tsang* < > rog...@gm... <mailto:roger.tsang@gmail= .com> >> <mailto: rog...@gm... > <mailto:rog...@gm...>>> wrote: >> >> Hi Karl, >> >> By the way what is there in the kernel > to merge to OPENSSI-SU >> branch? I thought Brian said all the > development branches share >> the same branch for the kernel sources > which means my OPENSSI-FC >> checkin's were done on the trunk and > OPENSSI-FC is just a tag >> for the openssi/kernel/ directory. >> >> -Roger >> >> >> >> On 10/27/05, *Karl Merritts* > <km...@gm... <mailto:km...@gm...> >> <mailto:km...@gm... > <mailto:km...@gm...>> > wrote: >> >> Stephan, >> I will announce it to you and the list. >> >> -Karl >> >> >> On 10/27/05, *Stephan B=EF=BF=BDni* < > bo...@bp... <mailto:bo...@bp...> >> <mailto: bo...@bp... > <mailto:bo...@bp...>>> wrote: >> >> Karl, >> >> Thanks. Could you send me a > mail, when it's ready? >> >> Stephan >> >> >> -----Urspr=EF=BF=BDngliche > Nachricht----- >> *Von:* Karl Merritts > [mailto:km...@gm... <mailto:kmerri@gmail.c= om> >> <mailto:km...@gm... > <mailto:km...@gm...>>] >> *Gesendet:* Donnerstag, 27. > Oktober 2005 17:45 >> *An:* Steven Van Acker >> *Cc:* Stephan B=EF=BF=BDni; >=20 >> =20 > ssi...@li... > <mailto:ssi...@li...> >> =20 > <mailto:ssi...@li... > <mailto:ssi...@li...>= > >> *Betreff:* Re: [SSI-users] > root failover >> >> Stephan, >> You may want to wait on > trying that right now. >> There are a bunch of > changes that I am merging in >> from the FC tree. One of > the major features that >> this enables is root failover. >> >> -Karl >> >> On 10/27/05, *Steven Van Acker* >> <dee...@ul... > <mailto:dee...@ul...> <mailto: > dee...@ul... <mailto:deepstar@ulyssis.o= rg>>> >> wrote: >> >> On Thu, Oct 27, 2005 at > 01:58:09PM +0200, >> Stephan B?ni wrote: >> > >> > I've installed now my first cluster node, >> but without root failover. >> > How can i create now the root failover. I >> think, that i have to use >> > the clusterfstab command, but i don't know >> to correct syntax to >> > configure it. What is a UUID? And where can >> i find the correct UUID? >> >> Hi, >> >> you may want to use the > ssi-chnode command for that >> >> greets, >> -- Steven >> >> >> =20 > -----------------------------------------------= -------- >> ThisSF.Net email is > sponsored by the JBoss Inc. >> Get Certified Today * > Register for a JBoss >> Training Course >> Free Certification Exam > for All Training >> Attendees Through End > of 2005 >> Visit >> =20 > http://www.jboss.com/services/certification >> =20 > <http://www.jboss.com/services/certification> >> for more information >> =20 > _______________________________________________ >> Ssic-linux-users > mailing list >> =20 > Ssi...@li... > <mailto:Ssi...@li...> >> =20 > <mailto:Ssi...@li... > <mailto:Ssi...@li...>= > >> =20 > https://lists.sourceforge.net/lists/listinfo/ss= ic-linux-users >> >> >> >> >> >> >=20 >=20 >=20 >=20 >=20 >=20 >=20 |