-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> > At the moment, LCFG works fine with a consistent list of rpms and
> > the rpms themselves. Does this mean that I can populate the
> > repositories with consistent sets of 7.1 or 7.2 and it will still
> > work, or is it much more subtle than this ?
Good question. There are unfortunately, a number of differences between
6.2 and 7.* that mean the current EDG (testbed) version of LCFG won't
actually work properly if you try this.
> I think the answer is that everything is now available for supporting
> 7.x but at a testing stage. Mike or Alex may be able to add something.
That's right. In fact, following some discussions with EDG folks this
week, I can clarify (as in, um, correct) some comments I made a week ago
at the HEP system managers meeting. Then I said that the new version of
LCFG will be part of the EDG testbed release scheduled for the end of
May, and that it will support Red Hat 7.1. In fact:
(1) The new stuff will only go to the WP8 integration team at the end of
May, so it won't appear as a proper release till some point,
hopefully not too long, after that. (Unless I've got confused.)
(2) The new LCFG code *does* support Red Hat 7.1, and we are using it
with 7.1 at Edinburgh now. However, the shortly-after-end-of-May
EDG release which first incorporates the new LCFG will still only
support testbeds running 6.2. The plan is to offer 6.2 and *7.2*
(not 7.1) in the next EDG testbed release after that (approx two
months later). In other words, although the underlying LCFG
software can now do at least 7.1, the official EDG releases won't
use it for anything other than 6.2 till after the end of July.
> > Also, do you know when the PXE version will be ready ?
>
> Exactly what is missing so that you can pxe is unclear, it may
> just be instructions. Though DHCP over bootp which is now present
> does make life more flexible in this area.
Both DHCP-rather-than-BOOTP and PXE support have been retrofitted by
others into the LCFG that is part of the current EDG release, and I've
not had a chance to look at that work. The new LCFG has support for
both of these (and should have some documentation, too). So, as above,
that will be available as part of the end-of-May EDG release.
Lex
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6
iD8DBQE8zyGDZVggDq4Uh5YRAkpnAJ9faOcIfAJCRmUArY4uMwAaTTwUlwCeKNHz
jeGkCbRPDXYj14oKHz/mGMo=
=gW8U
-----END PGP SIGNATURE-----
