On our cluster we are using the System installer method of installing
the nodes. We insert a common startup file that detects from a genders
database what type of node we currently are, then calls the correct
lconf options, mostly we just need to know if the node is a
server(MDS/OST) which calls lconf with no --node option, and otherwise
calls lconf with the --node client option, this way we only have one
profile for a client node. With the advent of newer interfaces that
allow just a mount option, the same init.d script could just call mount
if the node is a client, can do the lconf if it is a server node.
Evan
On Sat, 2004-02-14 at 16:32, Phil Schwan wrote:> Tim Harsch wrote:
> > I''m pondering the use of lustre on our cluster and want to
know: How
> > difficult is it to configure Lustre for a large number of nodes
> while using
> > imaging (RLX Control Tower, Rocks, Oscar, etc. ) as the installation
> > process? How could I configure nodes to play different roles in
> the file
> > system and achieve that by imaging out just one image?
> >
> > I want to be able to distribute one image and configure the nodes
> based on
> > node id: perhaps through a script or global identification file that
> says if
> > I am node X then I am an OST, or if I am node Y then I am an MDS,
> etc.
>
> I have never used any of those particular imaging tools, but your
> stated
> goal is not a problem.
>
> When you create your configuration file, you specify node names on the
> LMC command line, along the lines of:
>
> lmc -m config.xml --add net --node hostname --nid ...
>
> lconf will search for a configuration that matches that node''s
> hostname.
> You can override this with "--node foo", but it sounds like you
don''t
> want to.
>
> That will work well for MDS and OST nodes. For client nodes,
you''ll
> need another mechanism that knows to run "mount" only on those
nodes.
>
> -Phil
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss@lists.clusterfs.com
> https://lists.clusterfs.com/mailman/listinfo/lustre-discuss
--
-------------------------
Evan Felix
Administrator of Supercomputer #5 in Top 500, Nov 2003
Environmental Molecular Sciences Laboratory
Pacific Northwest National Laboratory
Operated for the U.S. DOE by Battelle