--=-ZSSNH5Vk79XmaAGpQVYN Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable A Qui, 2004-02-26 =C3=A0s 02:28, Phil Schwan escreveu:> > 2) What is the minimum part of the configuration file needed for an OST? > > The description of the OSTs in that node and the MDS is enough? (This > > would allow me to simplify a bit the config fetch part of the live CD) >=20 > You can fetch just the single XML file, which is enough to configure any > node. Or lconf can fetch your configuration from LDAP. >=20 > But maybe I don''t understand the question?I should have described the scenario a bit further. I''m working on a live CD that could be used for OSS. On being run on a OSS in setup mode it formats the harddisks and requests ost_uuids for each partition from a server (nowadays, that server is also in the MDS). On running mode the CD would do the following (this is one of the options): 1) Generate a configuration file with all local ost_uuids gathered from the volume label of the ext3 partitions. 2) Run lconf on the partial config file generated (which has the local OSTs and a pre-defined MDS and client configuration) 3) Send the configuration to the server which would: - add that information to the general config file - send an order to umount the filesystem on the clients - run lconf -d - run lconf - send an order to mount the filesystem on the clients Yes, I could just replace 2) by a another step after 3) that simply gets the full config file from the server and runs lconf on it. And it probably would be safer regarding changing client configs. Anyway, just wanted to know if it would work. --=20 Jo=C3=A3o Miguel Neves --=-ZSSNH5Vk79XmaAGpQVYN Content-Type: application/pgp-signature; name=signature.asc Content-Description: Esta =?ISO-8859-1?Q?=E9?= uma parte de mensagem assinada digitalmente -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAPdLuGFkMfesLN9wRAn3UAJ9/DjAeokPpUaxvrtZcwnbrTr4FRACfTyke uHt9HcjXK/LYbEnFxno7lrw=HLgC -----END PGP SIGNATURE----- --=-ZSSNH5Vk79XmaAGpQVYN--
João Miguel Neves wrote:> > After setting up the basics I wanted to know a couple of informations: > > 1) Is it possible to change the node of an OST as long as the OST''s name > remains the same?Yes, I believe so, as long as all nodes are aware of the new IP address. You can change the OST''s UUID, but unfortunately we do not make it very easy just yet. You would have to edit two binary files, but it is possible.> 2) What is the minimum part of the configuration file needed for an OST? > The description of the OSTs in that node and the MDS is enough? (This > would allow me to simplify a bit the config fetch part of the live CD)You can fetch just the single XML file, which is enough to configure any node. Or lconf can fetch your configuration from LDAP. But maybe I don''t understand the question? -Phil
--=-1zuzFU/B6iSV1NgaE5kT Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I''m preparing a lustre system where nodes with OSTs don''t have an installed operating system (they run from a live CD based on Morphix). Right know it''s not quite distributable, but if anyone wants to try out, tell me (if you use SCSI controller modules, please tell me which - I had to remove a couple for my purposes but can put back the one that interests you). After setting up the basics I wanted to know a couple of informations: 1) Is it possible to change the node of an OST as long as the OST''s name remains the same? 2) What is the minimum part of the configuration file needed for an OST? The description of the OSTs in that node and the MDS is enough? (This would allow me to simplify a bit the config fetch part of the live CD) Thanks for your great work, --=20 Jo=C3=A3o Miguel Neves --=-1zuzFU/B6iSV1NgaE5kT Content-Type: application/pgp-signature; name=signature.asc Content-Description: Esta =?ISO-8859-1?Q?=E9?= uma parte de mensagem assinada digitalmente -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAIg35GFkMfesLN9wRAjFYAJ9nCOpu1rajWMdTruywoWu/KldK2wCfbKff QIXRGfHoRucSExPynn2yyEs=qei1 -----END PGP SIGNATURE----- --=-1zuzFU/B6iSV1NgaE5kT--