istaz (~olivier@77.222-242-81.adsl-dyn.isp.belgacom.be) joined #fai.
istaz_ (~olivier@250.106-65-87.adsl-dyn.isp.belgacom.be) left irc: Ping timeout: 480 seconds
pjustice (~pjustice@yagi.h-net.msu.edu) left irc: Ping timeout: 480 seconds
pjustice (~pjustice@yagi.h-net.msu.edu) joined #fai.
fai-guy (~fai-guy@p4FC23452.dip0.t-ipconnect.de) joined #fai.
siggg (~jean@dyn-83-156-145-242.ppp.tiscali.fr) joined #fai.
ErKa (keryell@m2.wifi.enstb.org) joined #fai.
siggg (jean@dyn-83-156-145-242.ppp.tiscali.fr) left #fai.
10:04 eartoasth01ger: im hpc-cluster verkraftet das netz alle 56 maschinen gleichzeitig
10:05 oz__ui...was für ein netz ist das?
10:05 oz__1GB ?
10:05 stockholmoz__: ein high performance nety
10:05 stockholmnetz
10:05 stockholmdaher der name hpc
Action: oz__ konnte maximal 10
10:05 eartoastim "normalen" netz, also arbeitsplatzrechner und server, sind nicht mehr 20 drin, ohne dass die user leiden ;)
10:05 oz__ab 15 wurde es...naja
10:06 oz__aber das war ein extrem verswitchtes netz...nicht wirklich gut
10:06 eartoastoz__: hpc: tcp/ip laeuft ueber 1gb
10:06 eartoastder mpi-traffic der neuen maschinen wird ueber IB geregelt
10:08 eartoastdie normalen maschinen sind teilweise ueber 1gb, teilweise ueber 100mbit angebunden. der erfahrungswert 20 stammt noch aus der 100mbit-only zeit ;)
10:08 oz__eartoast: das war auch mein wert aus Freiburg
10:08 oz__in Jena ging's auf 10-15 runter
10:09 stockholmwelcher dienst gibt denn zuerst auf?
10:09 stockholmnfs? oder svn?
10:11 h01gereartoast, hm, ich dachte eher von der gui. der screenshot sieht nicht so aus, als ob das für 56 oder 560 machinen scaliert
10:11 h01ger_das gui_
10:11 h01gerweil soviel nicht aufn bildschirm passt
10:15 eartoaststockholm: cvs vergibt read-locks, die rechner werden an der stelle zunaechst einmal ausgebremst
10:18 stockholmah, ich habt cvs. :-)
10:18 eartoastdie 20-rechner-gleichzeitig-grenze war eigentlich das, was die benutzer hier im netz noch toleriert haben... wenn 20 rechner gleichzeitig von nem 1gb-angebundenen server openoffice per nfs updaten, war im netz selbst nicht mehr viel luft (ok, da war auch mehrere switches kaskadiert)
10:18 eartoastmittlerweile haben wir das ganze flacher...
10:19 eartoastkeine ahnung, wie viel das jetzt verkraftet
10:19 eartoasth01ger: die spalten kann man skrollen
10:20 h01gerhmokay. gruppieren wäre noch schön, aber es ist ja noch nicht weihnachten :)
10:20 eartoastdas layout war aber das effizienteste, was man mit 80x25 machen konnte
10:20 h01gerja. jetzt versteh ich das layout auch besser. die in "success" sind ja quasi egal.. und da sollten die meisten sein :)
10:21 eartoastwenn man sehr viele rechner gleichzeitig im update-zustand sind, dauert das updaten des UI allerdings manchmal etwas
10:21 eartoastjo
ErKa (keryell@m2.wifi.enstb.org) left irc: Ping timeout: 480 seconds
b1gf1sh (~f1sh@193.16.163.152) joined #fai.
12:07 b1gf1shhey
12:07 b1gf1shI have a question concerning multiple network devices and FAI
12:08 b1gf1shthing is, we have HP DL380 servers here, which come with 2 network-cards with 2 ports each
12:09 b1gf1shand I need to have the FAI installation booted with eth2 (2nd nic, 1. port), but unfortunately, while booting via tftp it tries to boot from eth0 only (after dhcp on eth2 kicked in and started booting), so then the FAI installation stalls at the moment it would usually mount the live-system from server to client via nfs
12:10 b1gf1shobviously, since there is no connection between eth0 and the fai-server
ErKa (keryell@keryell.pck.nerim.net) joined #fai.
12:22 eartoastb1gf1sh: what kind of kernel are you using/
12:22 eartoastinitrd or monolithic?
12:23 b1gf1shim using 2.6.18-6 (debian etch default kernel)
12:23 b1gf1shinitrd
12:23 b1gf1shnetwork devices are both "bnx2" drivers
12:23 b1gf1shso thats pretty nasty, would have been easier to disable loading of one driver if the the nics were different brands
12:24 b1gf1shthere must be something I could add to the file "fai-chboot" creates for the specific server
12:24 b1gf1shsome kernel appened param
12:25 eartoastwell, you could try to unpack the initrd and modify it;
12:26 eartoastkernel command line options only work reliably if you are using the kernel-level autoconfig code
12:27 b1gf1shkernel-level autoconfig code? never heard of it? can you please explain?
12:27 b1gf1shi was thinking to add: insmod=bnx2 netdevice=eth2
12:27 b1gf1shto the append line
12:27 b1gf1shbut it didnt work
12:29 b1gf1shappend initrd=initrd.img-2.6.18-6-amd64 insmod=bnx2 netdevice=eth2 ip=dhcp  root=/dev/nfs nfsroot=/srv/fai/nfsroot boot=live  FAI_FLAGS=verbose,sshd,createvt,reboot FAI_ACTION=install
12:30 b1gf1shany hints?
12:32 eartoastwhat i meant with kernel-level autoconfig is the code within the kernel
12:33 eartoastwhich is used if you linked the network drivers statically into the kernel
12:33 eartoastand you don't have an initrd
12:33 b1gf1shah ok
12:33 eartoastthis code then parses the ip=$something line
12:34 b1gf1shmakes sense, what would be the easiest work around then?
12:34 eartoastwhat you could try is to set dhcp only for eth2 and disable eth{0,1} detection.
12:34 b1gf1shyeah, when i disable eth0/1 in bios
12:34 b1gf1shall works fine
12:34 b1gf1shas soon as i reenable it
12:35 b1gf1shit will stall again during fai installation
12:35 eartoasti did not speak about the bios... i spoke about the ip=$something part
12:35 eartoastin the kernel command line
12:35 b1gf1shhow would it look like then?
12:36 b1gf1shi have no idea how to disable eth0/1 in the command line while not disabling eth2/3 which are of same brand/same driver
12:36 eartoastdirty hack: unpack the initrd, and restrict the udhcpc-call to eth2
12:37 b1gf1shah alright
12:37 eartoastwithin the initrd, it is just a bunch of shell scripts which do the work
12:37 b1gf1sh;)
12:37 b1gf1shsounds cool
12:37 eartoastthen repack it and reboot.
12:38 eartoastthe initrd code is understandable, I remember doing a similar hack a year ago...
12:39 b1gf1shthanks a lot
12:40 b1gf1shyou dont remember the cmds to unpack the initrd and mount it?
12:40 b1gf1shmount -o loop initrd.img-2.6.18-6-amd64 /test/
12:40 b1gf1shmount: you must specify the filesystem type
12:41 b1gf1shah figred it out, nm
12:44 b1gf1shproblem is, the file called udhcpc-call is not in there? do I have to create it manually?
12:47 eartoastargh.
12:48 eartoastno. in some script, there is called the dhcp client
12:48 eartoastcall in the sense of call of external program
12:49 eartoasttry to do the shotgun-approach: user@host:~/unpacked-initrd> grep -ri 'dhcp' .
13:11 b1gf1shok
13:11 b1gf1shive tried to edit scripts/nfs
13:12 b1gf1shand changed DEVICE in the line: ipconfig -c ${IPOPTS} -d ${DEVICE} to
13:12 b1gf1shipconfig -c ${IPOPTS} -d eth2
13:16 b1gf1shno go unfortunately
13:16 b1gf1shanyway, thanks for help
13:16 b1gf1shi might be back tonight if I dont figure it out, cu
b1gf1sh (~f1sh@193.16.163.152) left irc: Quit: b1gf1sh
fai-guy_ (~fai-guy@p4FC23452.dip0.t-ipconnect.de) joined #fai.
fai-guy__ (~fai-guy@p4FC23452.dip0.t-ipconnect.de) joined #fai.
fai-guy__ (~fai-guy@p4FC23452.dip0.t-ipconnect.de) left irc: Read error: Connection reset by peer
fai-guy_ (~fai-guy@p4FC23452.dip0.t-ipconnect.de) left irc: Ping timeout: 480 seconds
fai-guy_ (~fai-guy@p4FC23452.dip0.t-ipconnect.de) joined #fai.
fai-guy_ (~fai-guy@p4FC23452.dip0.t-ipconnect.de) left irc: Read error: Connection reset by peer
juri_ (~juri@ip70-178-3-140.ks.ks.cox.net) left irc: Ping timeout: 480 seconds
juri_ (~juri@ip70-178-3-140.ks.ks.cox.net) joined #fai.
ErKa (keryell@keryell.pck.nerim.net) left irc: Ping timeout: 480 seconds
fai-guy_ (~fai-guy@p4FC23452.dip0.t-ipconnect.de) joined #fai.
siggg (~jean@dyn-83-156-145-242.ppp.tiscali.fr) joined #fai.
fai-guy (~fai-guy@p4FC23452.dip0.t-ipconnect.de) left irc: Quit: leaving
fai-guy_ (~fai-guy@p4FC23452.dip0.t-ipconnect.de) left irc: Quit: leaving
siggg (~jean@dyn-83-156-145-242.ppp.tiscali.fr) left irc: Remote host closed the connection
ErKa (~keryell@keryell.pck.nerim.net) joined #fai.
siggg (~jean@dyn-83-156-145-242.ppp.tiscali.fr) joined #fai.
siggg (~jean@dyn-83-156-145-242.ppp.tiscali.fr) left irc: Ping timeout: 480 seconds
allee (~ach@allee.mpe.mpg.de) left irc: Remote host closed the connection
juri_ (~juri@ip70-178-3-140.ks.ks.cox.net) left irc: Ping timeout: 480 seconds
siggg (~jean@tra78-5-88-172-128-32.fbx.proxad.net) joined #fai.
ErKa (~keryell@keryell.pck.nerim.net) left irc: Ping timeout: 480 seconds
ErKa (~keryell@keryell.pck.nerim.net) joined #fai.
ErKa (~keryell@keryell.pck.nerim.net) left irc: Remote host closed the connection
ErKa (keryell@keryell.pck.nerim.net) joined #fai.
siggg (~jean@tra78-5-88-172-128-32.fbx.proxad.net) left irc: Ping timeout: 480 seconds
ErKa (keryell@keryell.pck.nerim.net) left irc: Ping timeout: 480 seconds
--- Fri Jun 6 2008

Generated by irclog2html.pl 2.1_h01ger1 by Jeff Waugh - find it at freshmeat.net! Customized by Holger 'h01ger' Levsen