From: Erich Focht [mailto:[EMAIL PROTECTED]
Sent: Wed 08/02/2006 01:25
To: Bernard Li
Cc: [email protected]
Subject: Re: [Oscar-devel] infrastructure overhaul merge
On Wednesday 08 February 2006 08:27, Bernard Li
wrote:
> BTW is there a reason why the naming convention for
/tftpboot/distro is different from /tftpboot/oscar?
Eg.:
>
> /tftpboot/distro/redhat-el-ws-4-i386/
>
/tftpboot/oscar/rhel-4-i386/
The reason is because
/tftpboot/distro/redhat-el-ws-4-i386/
/tftpboot/distro/redhat-el-as-4-i386/
/tftpboot/distro/redhat-el-es-4-i386/
/tftpboot/distro/centos-4-i386/
/tftpboot/distro/scientific_linux-4-i386/
are _all_ covered by just _one_
OSCAR directory:
/tftpboot/oscar/rhel-4-i386/
It
makes sense to have multiple distro subdirectories, e.g. you might have
AS
for the master and WS for the nodes, or paid RH on the master and free SL
on
the nodes.
As explained: OSCAR uses separate names on purpose, they
correspond to the
"compat_distro" hash key returned by OS_Detect. The name
used by OSCAR should
be short and should not contain dashes or other special
characters.
OSCAR only needs to know in 2 places which real distro is
really meant:
- in the prereqs (because clones might have more
functionality than the
original and might need to be resolved
differently). The original distro
name appears in
prereq.cfg.
- when looking for distro packages
(/tftpboot/distro/...).
Every other place must use the OSCAR compatible
distro names.
This way adding a clone becomes trivial. And the use of the
"wrong" distro
name is easy to
trace.
Regards,
Erich
