1 #LyX 1.3 created this file. For more info see http://www.lyx.org/
10 \papersize letterpaper
15 \use_numerical_citations 0
16 \paperorientation portrait
19 \paragraph_separation skip
21 \quotes_language english
25 \paperpagestyle default
35 lmc Lustre configuration maker.
43 lmc [options] --add <objectype> [args]
48 lmc [options] --remove <objecttype> [args] -- [NOT IMPLEMENTED]
53 lmc [options] --convert [args] -- [NOT IMPLEMENTED]
65 , when invoked, adds configuration data to the config file.
72 will also be able to remove configuration data or convert its format.
73 A Lustre cluster consists of several components - MDS's, mount-points,
74 OSTs, LOVs and whatever those reference (e.g nets and profiles).
75 A single configuration file would be generated for the complete cluster.
82 command line interface, each of these components is associated with an
95 refers to a collection of related configuration entities and can be one
129 We describe the arguments required for the addition of each
137 To generate configuration data associated with systems in a Lustre cluster:
145 node Adds a new node in the cluster configuration.
150 The arguments required are:
154 ''node_name'' This will create a new node with the given name if not
158 --timeout\SpecialChar ~
159 <num> Timeout before going into recovery
162 --lustre_upcall\SpecialChar ~
163 <path> Set the location of the Lustre upcall scripts used
164 by the client for recovery
167 --portals_upcall\SpecialChar ~
168 <path> Specify the location of the Portals upcall scripts
169 used by the client for recovery
172 --upcall\SpecialChar ~
173 <path> Specify the location of both (Lustre and Portals) upcall
174 scripts used by the client for recovery
183 net Adds a network device descriptor for the given node, with parameters
188 The arguments required are:
192 ''node_name'' This will create a new node with the given name if not
194 This is also used to specify a specific node for other elements.
197 --nettype\SpecialChar ~
200 tcp, elan, gm, scimac.
209 ElanID or IP address as used by Portals.
214 is '*', then the local address of the interface with specified
218 is will be substituted when the node is configured with lconf.
227 should be used only for the generic
237 --router Optional flag to mark this node as a router
241 [port] Optional arguement to indicate the tcp port.
246 --tcpbuf\SpecialChar ~
247 <size> Optional arguement.
248 The default TCP buffer size is 1MB.
251 --irq_affinity\SpecialChar ~
252 0|1 Optional arguement.
256 --nid_exchange\SpecialChar ~
257 0|1 Optional arguement since some OSTs might not have the
259 This is turned off by default, value of 1 will turn it ON.
271 name> Name of the node on which the MDS resides
279 <pathname> Path of device on local system.
280 If the is a file, then a loop device is created and used as the block device.
284 <size> Optional argument indicating the size (in KB) of the device
285 to be created (used typically for loop devices).
289 <nodename> Adds an MDS to the specified node.
294 argument, and it must not be a profile node.
297 --fstype\SpecialChar ~
298 extN|ext3 Optional argument used to specify the file system type.
302 --journal_size\SpecialChar ~
303 <size> Optional arguement to specify the journal size for
304 the ext2/ext3 file system.
305 The size should be in the units expected by
309 , so for ext3 it should be in MB.
310 If this is option is not used, the ext2/ext3 filesystem will be configured
311 with the default journal size.
316 lov Creates an LOV with the specified parameters.
321 must already exist in the descriptor.
333 --stripe_sz\SpecialChar ~
337 --stripe_cnt\SpecialChar ~
338 <count> A value of 0 for this means to stripe on all available
343 --stripe_pattern\SpecialChar ~
344 <pattern> Only Pattern 0 (RAID 0) is supported currently.
349 ost Creates an OBD, OST, and OSC.
350 The OST and OBD are created on the specified node.
355 <name> Assign a name to the OST device.
359 <nodename> Node on which the OST service is run, can not be a profile
364 <pathname> Path of device on local system.
365 If this is a file, then a loop device is created and used as the block
370 [size] Optional argument indicating the size (in KB) of the device
371 to be created (used typically for loop devices).
374 --obdtype\SpecialChar ~
379 <name> Optional arguement.
380 Name of LOV to which this OSC will be attached.
384 --ostuuid\SpecialChar ~
385 UUID Specify the UUID of the OST device.
389 --fstype\SpecialChar ~
390 extN|ext3 Optional arguement used to specify the file system type.
394 --journal_size\SpecialChar ~
395 <size> Optional arguement to specify the journal size for
396 the ext2/ext3 file system.
397 The size should be in the units expected by
401 , so for ext3 it should be in MB.
402 If this is option is not used, the ext2/ext3 filesystem will be configured
403 with the default journal size.
408 mtpt Creates a mount-point on the specified node.
409 Either an LOV or OSC name can be used.
414 node Node or profile node that will use the
422 /mnt/path\SpecialChar ~
431 ost_name\SpecialChar ~
439 route Creates a static route through a gateway to a specific
452 node Node to add the route to.
460 of the gateway (must be a local interface or a peer).
464 nid For a specific route, this is the target
470 nid For a range route, this is the lo value
476 nid For a range route, this is the hi value
483 echo-client Used for testing purpose only.
498 \labelwidthstring 00.00.0000
505 --output\SpecialChar ~
506 filename Send output to the file.
507 If the file exists, it will be overwritten.
510 --merge\SpecialChar ~
515 Add the new element to an existing file.
522 Real life examples are given in the Lustre-conf manual page.