[Rocks-Discuss] Installing Rocks not via optical media
Francis
I'm wondering if anybody here has tried or has any idea on how to install
Rocks and insert other existing rolls without using optical media like CDs
or DVDs? It's one of the questions I've been meaning to ask since
installation via USB is relatively much faster than via optical means,
especially with the sizes of USB thumb drives nowadays.
I wonder if I could go to a limited shell mode and mount the rolls one by
one during frontend installation i.e. behind Anaconda. Or is this not
possible?
Regards,
./francis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20100217/056b41cc/attachment.html
Mason J. Katz
Further everything Rocks frontend is also a "central server". So you
can build one Frontend with media, and then build as many others as
you want over the network.
mason katz
+1.240.724.6825
Francis
I wonder if I could do this for another OS other than Rocks itself or
CentOS? I was thinking of using Scientific Linux 5.4 instead.
Regards,
./francis
2010/2/17 Mason J. Katz <mason...@gmail.com>
Ian Kaufman
instead of the ROCKS OS rolls or CentOS/RHEL disks, it will
do what you want.
Ian
--
Ian Kaufman
Research Systems Administrator
UC San Diego, Jacobs School of Engineering ikaufman AT ucsd DOT edu
Francis
I was wondering if I could do a network install of Rocks wherein it will
also download the Scientific Linux ISOs so I won't have to resort to optical
media installation of Scientific Linux as well. Would you know how this
could be arranged? Do I just point Anaconda to the Scientific Linux ISO
mirror/url?
Regards,
./francis
2010/2/18 Ian Kaufman <ikau...@soe.ucsd.edu>
Philip Papadopoulos
Make sure you have lots of disk space then, on your rocks central server
# rocks create mirror
ftp://linux1.fnal.gov/linux/scientific/54/x86_64/SL/ rollname="SL"
version=5.4
# rocks create mirror
ftp://linux1.fnal.gov/linux/scientific/54/x86_64/updates/security/
rollname="SL5.4-Updates"
version=`date +%F`
Now add these two rolls to your distribution
# rocks add roll SL*iso
Build your new frontend using both the SL and SL5.4 updates. When doing that
your new system will be built with the updated RPMs.
-P
--
Philip Papadopoulos, PhD
University of California, San Diego
858-822-3628 (Ofc)
619-331-2990 (Fax)
-------------- next part --------------
An HTML attachment was scrubbed...
Francis
Thanks for the info. I wonder though, at which point in the Rocks frontend
installation do I enter/run the commands you gave? Because I'm trying to
install and run a hybrid setup: Rocks + Scientific Linux 5.4 as the OS,
instead of Rocks' own OS rolls.
Regards,
./francis
2010/2/19 Philip Papadopoulos <philip.pa...@gmail.com>
Philip Papadopoulos
> Hi Philip
>
> Thanks for the info. I wonder though, at which point in the Rocks frontend
> installation do I enter/run the commands you gave? Because I'm trying to
> install and run a hybrid setup: Rocks + Scientific Linux 5.4 as the OS,
> instead of Rocks' own OS rolls.
>
> You can't do that during the installation, you can do it on an installed
frontend and then
use that as a networked host. For what you want to do (I think) is point
to remote ISO image as "roll". We don't support that, unfortunately. If
you have a dvd on your frontend, you should be able to use the SL5 DVD
instead of Rocks OS rolls.
-P
Francis
So what do you suggest I do first to install my frontend? Use Rocks' default
OS rolls 1 and 2 and then after installation, run the commands you
previously mentioned to install SL 5.4?
Regards,
./francis
2010/2/19 Philip Papadopoulos <philip.pa...@gmail.com>
Philip Papadopoulos
> Thanks for the info Philip.
>
> So what do you suggest I do first to install my frontend? Use Rocks'
> default
> OS rolls 1 and 2 and then after installation, run the commands you
> previously mentioned to install SL 5.4?
>
No.
Download the SL5 DVD and burn it from your laptop.
Use this DVD -instead- of the Rocks OS rolls.
Without building a second machine, this is your only choice.
You will have an SL5 machine when done.
-P
Francis
first with SL, then create an SL mirror using that installation for my
succeeding frontend installations no? Or wasn't I able to follow your train
of thought?
Regards,
./francis
2010/2/19 Philip Papadopoulos <philip.pa...@gmail.com>
Ian Kaufman
Though, I thought it should be possible to install a frontend using
RHEL/CentOS/ROCKS
for the OS disks, and then add the SL ISOs to the inventory later. It
is definitely easier
to install a specific OS as the core, and use the installed OS as the
OS roll, but I
thought it was possible to place other rolls in the inventory. Perhaps I am
mistaken.
Ian
Francis
I think using any Redhat binary compatible Linux distribution should work as
an OS roll for Rocks.
But are you saying that, say I use Rocks or CentOS as OS rolls during
frontend installation, I can use the rest of the SL ISOs as OS rolls after
installation?
Regards,
./francis
2010/2/22 Ian Kaufman <ikau...@soe.ucsd.edu>
> >> > > > > ftp://linux1.fnal.gov/linux/scientific/54/x86_64/SL/rollname="SL"
Philip Papadopoulos
A. What happens when you build frontend from scratch?
--> The rolls inserted contain RPMs and (optionally) configuration graphs
--> All of the RPMS from All of the inserted rolls are copied to the
frontend
hard disk.
--> rocks create distro is then run to build a working distribution on the
frontend.
---> The RPMS -installed- are dependent on the what the final graph
indicates.
So, what does this mean.
If you build a frontend with CentOS only, the installed frontend will be
CentOS. If you build with SL5, it will be SL5. If you build with both, it
will be an indeterminate mixture of SL5 and CentOS.
B. What can you do after installation of a frontend end
--> every rocks frontend can be a central server. Edit iptables to allow
http access from other than local private and your local public LAN segment.
--> You can add rolls. In fact. you can build a CentOS frontend and add all
of the SL5 rpms as a "roll".
--- In this case, the frontend will serve out CentOS or SL5 to any
who ask for either/or/both.
--- Unless you "enable" the SL5 rolls, they will not be included in
the distro used to kickstart local nodes (distro serving and roll serving
are two
different things)
--- Simply adding a roll (via rocks add roll) does nothing to the
running
configuration of the frontend. If you add SL5 to a CentOS
machine, it
will still be CentOS.
So, if you want to build just one machine and have it be SL5, build it with
the SL5 DVD and leave out the CentOS (or Rocks OS rolls).
If you want to build two machines. You can build one as a central. You can
have it serve whatever rolls are on it. You could have CentOS, SL5, Updates,
and any other roll. For building multiple clusters we often have a roll
server
on the network.
-P
Francis
2010/2/23 Philip Papadopoulos <philip.pa...@gmail.com>
Joe Kaiser
I like mud so here is some more.
I used to work at Fermi and was required to use Scientific Linux.
It is faster, substantially, to build the frontend with the two CentOS
required rolls.
After completing the install, download SL5 iso to the frontend.
Add SL5 as a roll.
Enable SL5 roll.
Disable the two os rolls from CentOS.
Rebuild the distribution.
Your frontend isn't strictly SL5 in that instance, however.
Thanks,
Joe
Kevin
can install SL on all the nodes setup networking then install Oscar
then build the cluster?
That to me seems simpler for u
Sent from my iPod
Francis
Thanks for the info. So far what I plan to do is
Over the Internet installation of frontend with Rocks or CentOS as OS rolls
Then proceed to your suggestion.
And what do you exactly mean by the frontend not being a stricly SL5 one?
I wonder what is the official stand of the Rocks team with this (Joe's)
procedure/suggestion?
Regards,
./francis
2010/2/24 Joe Kaiser <jlka...@gmail.com>
Joe Kaiser
> Hi Joe
>
> Thanks for the info. So far what I plan to do is
>
> Over the Internet installation of frontend with Rocks or CentOS as OS rolls
> Then proceed to your suggestion.
> And what do you exactly mean by the frontend not being a stricly SL5 one?
>
>
So the installed rpms on the frontend are CentOS, not Scientific Linux.
They're mostly the same, all the trademarked stuff that was ripped out of
RHEL was probably replaced with CentOS and SL variants, so any of those
won't strictly be "the same."
In my experience, there was very little problem with this and I did it this
way for five years or so.
> I wonder what is the official stand of the Rocks team with this (Joe's)
> procedure/suggestion?
>
>
Oh, they think anything I do is just the most awesome stuff in the world and
are immediately ready to support it.
Wait, no, that's my wife.
Wait, no, that's my mother.
Thanks,
Joe
Francis
are immediately ready to support it.
Wait, no, that's my wife.
Wait, no, that's my mother.
Hehehe
So far so good guys. Now when I login I get:
Last login: Wed Mar 10 10:53:37 2010 from xxx.xxx.xxx.xxx
Rocks 5.3 (Rolled Tacos)
Profile built 06:47 26-Feb-2010
Kickstarted 15:16 26-Feb-2010
But if I do
$ cat /etc/issue
Scientific Linux SL release 5.4 (Boron)
Kernel \r on an \m
and
$ lsb_release -a
LSB Version:
:core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch
Distributor ID: ScientificSL
Description: Scientific Linux SL release 5.4 (Boron)
Release: 5.4
Codename: Boron
So is it fair to say now that I have a hybrid cluster setup?: Rock's easy
cluster setup + SL's binary compatibility with RHEL
:)
Regards,
./francis
2010/3/6 Joe Kaiser <jlka...@gmail.com>