1 #LyX 1.2 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
240 --profile\SpecialChar ~
242 implemented] Optional flag to mark this node as a profile node.
243 This would be very useful to configure several client nodes in large clusters.
244 It will allow user to define
248 for the various client configurations, and then load the correct profile
249 on the client nodes using lconf.
254 [port] Optional arguement to indicate the tcp port.
259 --tcpbuf\SpecialChar ~
260 <size> Optional arguement.
261 The default TCP buffer size is 1MB.
264 --irq_affinity\SpecialChar ~
265 0|1 Optional arguement.
269 --nid_exchange\SpecialChar ~
270 0|1 Optional arguement since some OSTs might not have the
272 This is turned off by default, value of 1 will turn it ON.
284 name> Name of the node on which the MDS resides
292 <pathname> Path of device on local system.
293 If the is a file, then a loop device is created and used as the block device.
297 <size> Optional arguement indicating the size of the device to be
298 created (used typically for loop devices).
302 <nodename> Adds an MDS to the specified node.
307 argument, and it must not be a profile node.
310 --fstype\SpecialChar ~
311 extN|ext3 Optional arguement used to specify the file system type.
315 --journal_size\SpecialChar ~
316 <size> Optional arguement to specify the journal size for
317 the ext2/ext3 file system.
318 The size should be in the units expected by
322 , so for ext3 it should be in MB.
323 If this is option is not used, the ext2/ext3 filesystem will be configured
324 with the default journal size.
329 lov Creates an LOV with the specified parameters.
334 must already exist in the descriptor.
346 --stripe_sz\SpecialChar ~
350 --stripe_cnt\SpecialChar ~
351 <count> A value of 0 for this means to stripe on all available
356 --stripe_pattern\SpecialChar ~
357 <pattern> Only Pattern 0 (RAID 0) is supported currently.
362 ost Creates an OBD, OST, and OSC.
363 The OST and OBD are created on the specified node.
368 <name> Assign a name to the OST device.
372 <nodename> Node on which the OST service is run, can not be a profile
377 <pathname> Path of device on local system.
378 If this is a file, then a loop device is created and used as the block
386 --osdtype\SpecialChar ~
391 <name> Optional arguement.
392 Name of LOV to which this OSC will be attached.
396 --ostuuid\SpecialChar ~
397 UUID Specify the UUID of the OST device.
401 --fstype\SpecialChar ~
402 extN|ext3 Optional arguement used to specify the file system type.
406 --journal_size\SpecialChar ~
407 <size> Optional arguement to specify the journal size for
408 the ext2/ext3 file system.
409 The size should be in the units expected by
413 , so for ext3 it should be in MB.
414 If this is option is not used, the ext2/ext3 filesystem will be configured
415 with the default journal size.
420 mtpt Creates a mount-point on the specified node.
421 Either an LOV or OSC name can be used.
426 node Node or profile node that will use the
434 /mnt/path\SpecialChar ~
443 ost_name\SpecialChar ~
451 route Creates a static route through a gateway to a specific
464 node Node or profile node to add the route to.
472 of the gateway (must be a local interface or a peer).
476 nid For a specific route, this is the target
482 nid For a range route, this is the lo value
488 nid For a range route, this is the hi value
495 echo-client Used for testing purpose only.
510 \labelwidthstring 00.00.0000
517 --output\SpecialChar ~
518 filename Send output to the file.
519 If the file exists, it will be overwritten.
522 --merge\SpecialChar ~
527 Add the new element to an existing file.
534 Real life examples are given in the Lustre-conf manual page.