Closed nariai closed 8 years ago
Yep. That still OK?
Sure
You can change the BIOS to also not boot PXE.
OK. I show a 6.6 system!
I think I should have the "/" filesystem a little bigger.
As it includes /var. I propose 200GB. Its currently this:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg0-lv_root
50G 793M 46G 2% /
tmpfs 32G 0 32G 0% /dev/shm
/dev/sda1 477M 33M 419M 8% /boot
/dev/mapper/vg0-lv_scratch
837G 73M 794G 1% /scratch
That's right. Some software need temporary files on there.
10GB for / ?
Yeah. We don't have a ton of room, but lets take it up a bit.
OK. Made that change.
all new builds will get 200GB "/"
I would say start this one again and/or as many as you want. I feel it looks good.
OK, re-starting on cn2, cn1 then the others.
Nice!
Will I see the console?
The menu will appear, but the rest of the install goes to VNC. I can disable that if desired after cn1/cn2 to make sure they come up.
OK, doesn't have to be disabled.
Up to you....once we prove they rebuild clean I don't need to see the output. I also get a summary of where it is in the syslog.
I use the VNC when I am debugging a new node platform. As the install will stop and ask questions if I've not provided the proper KS values.
Formating partitions
I see, am starting cn1 too.
Cool!
In theory I suspect you can do about 5-10 at a time. Probably more.
Then later tonight I will do the Lustre, SGE and puppet.
I have one errand at 4:00PM my time (2:00PM your time)
OK, sounds great!
Hopefully this is a little easier ;)
Much easier for me.
And I will detail the config of the Kickstart items for folks once we get this done. It comes in very handy.
cn2 is loading software.
cn1 still doing disk partition formats but almost done.
cn2 rebooting.
working on cn3
yep.
I am switching the PXE default to the local disk so you don't have to play "find the console" as quickly ;)
New partitions give us a bit more breathing room.
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg0-lv_root
197G 801M 186G 1% /
tmpfs 32G 0 32G 0% /dev/shm
/dev/sda1 477M 33M 419M 8% /boot
/dev/mapper/vg0-lv_scratch
689G 69M 654G 1% /scratch
I would say "lets proceed"
cn3 is formatting filesystems cn1 is rebooting
I am actually going to do my errand but I will have my laptop as it involves another project. I show cn1 looking good as well. cn3 loading software
I have all the other nodes configured to accept kickstart. I will attempt to keep up with the menu change but you may find some of them waiting if you don't flip them back to BIOS boot off the local drive.
OK. cn5's on VNC. cn4 might have HDD issue, am checking.
cn4's on VNC
cn6's on VNC
cn8's on VNC. cn7 cannot boot up. We will have to discard it by hardware issue. I'm leaving for a lunch break, and will do the rest after coming back.
Sound good. Removed boot triggers for all but cn7
cn9's on VNC
cn10's on VNC
cn11's on VNC
cn12's on VNC
Noted!
Moved menu item aside for less than cn12
Paul,
As you can see, our current bottleneck is the number of nodes in the new cluster system, and hence we want to move a part of nodes in the old cluster to the new cluster as soon as possible (maybe eight nodes out of 16 nodes, as the first step).
Can you tell us what need to be done before migrating nodes?
Naoki