1 #LyX 1.3 created this file. For more info see http://www.lyx.org/
\r
8 \paperfontsize default
\r
10 \papersize letterpaper
\r
15 \use_numerical_citations 0
\r
16 \paperorientation portrait
\r
19 \paragraph_separation skip
\r
21 \quotes_language english
\r
25 \paperpagestyle default
\r
35 lmc Lustre configuration maker.
\r
43 lmc [options] --add <objectype> [args]
\r
48 lmc [options] --remove <objecttype> [args] -- [NOT IMPLEMENTED]
\r
53 lmc [options] --convert [args] -- [NOT IMPLEMENTED]
\r
65 , when invoked, adds configuration data to the config file.
\r
72 will also be able to remove configuration data or convert its format.
\r
73 A Lustre cluster consists of several components - MDS's, mount-points,
\r
74 OSTs, LOVs and whatever those reference (e.g nets and profiles).
\r
75 A single configuration file would be generated for the complete cluster.
\r
82 command line interface, each of these components is associated with an
\r
95 refers to a collection of related configuration entities and can be one
\r
122 echo_client, or cobd.
\r
125 We describe the arguments required for the addition of each
\r
133 To generate configuration data associated with systems in a Lustre cluster:
\r
134 \layout Description
\r
141 node Adds a new node in the cluster configuration.
\r
146 The arguments required are:
\r
147 \layout Description
\r
149 --node\SpecialChar ~
\r
150 ''node_name'' This will create a new node with the given name if not
\r
152 \layout Description
\r
154 --timeout\SpecialChar ~
\r
155 <num> Timeout before going into recovery
\r
156 \layout Description
\r
158 --lustre_upcall\SpecialChar ~
\r
159 <path> Set the location of the Lustre upcall scripts used
\r
160 by the client for recovery
\r
161 \layout Description
\r
163 --portals_upcall\SpecialChar ~
\r
164 <path> Specify the location of the Portals upcall scripts
\r
165 used by the client for recovery
\r
166 \layout Description
\r
168 --upcall\SpecialChar ~
\r
169 <path> Specify the location of both (Lustre and Portals) upcall
\r
170 scripts used by the client for recovery
\r
171 \layout Description
\r
173 --ptldebug\SpecialChar ~
\r
174 <debug_level> Set the portals debug level.
\r
175 \layout Description
\r
177 --subsytem\SpecialChar ~
\r
178 <subsystem_name> Specify which Lustre subsystems have debug output
\r
179 recorded in the log.
\r
181 \layout Description
\r
188 net Adds a network device descriptor for the given node, with parameters
\r
193 The arguments required are:
\r
194 \layout Description
\r
196 --node\SpecialChar ~
\r
197 ''node_name'' This will create a new node with the given name if not
\r
199 This is also used to specify a specific node for other elements.
\r
200 \layout Description
\r
202 --nettype\SpecialChar ~
\r
203 <type> Specify the network type.This can be
\r
206 \layout Description
\r
208 --nid\SpecialChar ~
\r
214 ElanID or IP address as used by Portals.
\r
219 is '*', then the local address of the interface with specified
\r
223 is will be substituted when the node is configured with lconf.
\r
232 should be used only for the generic
\r
237 \layout Description
\r
239 --cluster_id\SpecialChar ~
\r
240 id Specify the cluster ID.
\r
241 \layout Description
\r
243 --hostaddr\SpecialChar ~
\r
244 addr Specify the host address.
\r
245 lconf will transfer it to the real host address.
\r
246 \layout Description
\r
248 --router Optional flag to mark this node as a router
\r
249 \layout Description
\r
251 --port\SpecialChar ~
\r
252 [port] Optional arguement to indicate the tcp port.
\r
253 The default is 988.
\r
255 \layout Description
\r
257 --tcpbuf\SpecialChar ~
\r
258 <size> Optional arguement.
\r
259 The default TCP buffer size is 1MB.
\r
260 \layout Description
\r
262 --irq_affinity\SpecialChar ~
\r
263 0|1 Optional arguement.
\r
265 \layout Description
\r
267 --nid_exchange\SpecialChar ~
\r
268 0|1 Optional arguement since some OSTs might not have the
\r
270 This is turned off by default, value of 1 will turn it ON.
\r
273 \layout Description
\r
275 --add\SpecialChar ~
\r
278 \layout Description
\r
280 --node\SpecialChar ~
\r
281 <node\SpecialChar ~
\r
282 name> Name of the node on which the MDS resides
\r
283 \layout Description
\r
285 --mds\SpecialChar ~
\r
286 <mds_name> Specify MDS name.
\r
287 \layout Description
\r
289 --mdsuuid\SpecialChar ~
\r
290 <uuid> Specify MDS uuid.
\r
291 \layout Description
\r
293 --failover Enable failover support on MDS.
\r
294 \layout Description
\r
296 --dev\SpecialChar ~
\r
297 <pathname> Path of device on local system.
\r
298 If the is a file, then a loop device is created and used as the block device.
\r
299 \layout Description
\r
301 --backdev\SpecialChar ~
\r
302 <pathname> Path of the device for backing storage on local system.
\r
303 \layout Description
\r
305 --size\SpecialChar ~
\r
306 <size> Optional argument indicating the size (in KB) of the device
\r
307 to be created (used typically for loop devices).
\r
308 \layout Description
\r
310 --node\SpecialChar ~
\r
311 <nodename> Adds an MDS to the specified node.
\r
316 argument, and it must not be a profile node.
\r
317 \layout Description
\r
319 --fstype\SpecialChar ~
\r
320 extN|ext3 Optional argument used to specify the file system type.
\r
322 \layout Description
\r
324 --backfstype\SpecialChar ~
\r
325 ext3|tmpfs Optional argument to specify the backing filesystem
\r
327 \layout Description
\r
329 --nspath Local mount point of server namespace.
\r
330 \layout Description
\r
332 --inode_size\SpecialChar ~
\r
333 <size> Specify new inode size for underlying ext3 file system.
\r
334 \layout Description
\r
336 --mkfsoptions\SpecialChar ~
\r
337 <options> Optional argument to mkfs.
\r
338 \layout Description
\r
340 --mountfsoptions\SpecialChar ~
\r
341 <options> Optional argument to mount fs.
\r
342 Mount options will be passed by this argument.
\r
343 For example, extents are to be enabled by adding ",extents" to the --mountfsopt
\r
346 \begin_inset Quotes eld
\r
350 \begin_inset Quotes erd
\r
354 \begin_inset Quotes eld
\r
358 \begin_inset Quotes erd
\r
361 can also be added to it.
\r
362 \layout Description
\r
364 --journal_size\SpecialChar ~
\r
365 <size> Optional arguement to specify the journal size for
\r
366 the ext2/ext3 file system.
\r
367 The size should be in the units expected by
\r
371 , so for ext3 it should be in MB.
\r
372 If this is option is not used, the ext2/ext3 filesystem will be configured
\r
373 with the default journal size.
\r
375 \layout Description
\r
377 --add\SpecialChar ~
\r
378 lov Creates an LOV with the specified parameters.
\r
383 must already exist in the descriptor.
\r
385 \layout Description
\r
387 --lov\SpecialChar ~
\r
388 <name> Specify LOV name.
\r
389 \layout Description
\r
391 --mds\SpecialChar ~
\r
392 <name> Specify the mds name.
\r
393 \layout Description
\r
395 --stripe_sz\SpecialChar ~
\r
396 <size> Specify the stripe size in bytes.
\r
397 \layout Description
\r
399 --stripe_cnt\SpecialChar ~
\r
400 <count> A value of 0 for this means to stripe on all available
\r
403 \layout Description
\r
405 --stripe_pattern\SpecialChar ~
\r
406 <pattern> Only Pattern 0 (RAID 0) is supported currently.
\r
408 \layout Description
\r
410 --add\SpecialChar ~
\r
411 ost Creates an OBD, OST, and OSC.
\r
412 The OST and OBD are created on the specified node.
\r
414 \layout Description
\r
416 --ost\SpecialChar ~
\r
417 <name> Assign a name to the OST device.
\r
418 \layout Description
\r
420 --node\SpecialChar ~
\r
421 <nodename> Node on which the OST service is run, can not be a profile
\r
423 \layout Description
\r
425 --failover Enable failover support on OST.
\r
426 \layout Description
\r
428 --dev\SpecialChar ~
\r
429 <pathname> Path of device on local system.
\r
430 If this is a file, then a loop device is created and used as the block
\r
432 \layout Description
\r
434 --backdev\SpecialChar ~
\r
435 <pathname> Path of the device for backing storage on local system.
\r
436 \layout Description
\r
438 --size\SpecialChar ~
\r
439 [size] Optional argument indicating the size (in KB) of the device
\r
440 to be created (used typically for loop devices).
\r
441 \layout Description
\r
443 --osdtype\SpecialChar ~
\r
444 obdfilter|obdecho Specify the type of OSD.
\r
445 \layout Description
\r
447 --lov\SpecialChar ~
\r
448 <name> Optional arguement.
\r
449 Name of LOV to which this OSC will be attached.
\r
451 \layout Description
\r
453 --ostuuid\SpecialChar ~
\r
454 UUID Specify the UUID of the OST device.
\r
456 \layout Description
\r
458 --fstype\SpecialChar ~
\r
459 extN|ext3 Optional arguement used to specify the file system type.
\r
461 \layout Description
\r
463 --backfstype\SpecialChar ~
\r
464 ext3|tmpfs Optional argument to specify the backing filesystem
\r
466 \layout Description
\r
468 --inode_size\SpecialChar ~
\r
469 <size> Specify new inode size for underlying ext3 file system.
\r
470 \layout Description
\r
472 --nspath Local mount point of server namespace.
\r
473 \layout Description
\r
475 --mkfsoptions\SpecialChar ~
\r
476 <options> Optional argument to mkfs.
\r
477 \layout Description
\r
479 --mountfsoptions\SpecialChar ~
\r
480 <options> Optional argument to mount fs.
\r
481 Mount options will be passed by this argument.
\r
482 For example, extents are to be enabled by adding ",extents" to the --mountfsopt
\r
485 \begin_inset Quotes eld
\r
489 \begin_inset Quotes erd
\r
493 \begin_inset Quotes eld
\r
497 \begin_inset Quotes erd
\r
500 can also be added to it.
\r
501 \layout Description
\r
503 --journal_size\SpecialChar ~
\r
504 <size> Optional arguement to specify the journal size for
\r
505 the ext2/ext3 file system.
\r
506 The size should be in the units expected by
\r
510 , so for ext3 it should be in MB.
\r
511 If this is option is not used, the ext2/ext3 filesystem will be configured
\r
512 with the default journal size.
\r
514 \layout Description
\r
516 --add\SpecialChar ~
\r
517 mtpt Creates a mount-point on the specified node.
\r
518 Either an LOV or OSC name can be used.
\r
520 \layout Description
\r
522 --node\SpecialChar ~
\r
523 node Node or profile node that will use the
\r
528 \layout Description
\r
530 --path\SpecialChar ~
\r
531 /mnt/path Specify the mountpoint for Lustre.
\r
532 \layout Description
\r
534 --mds\SpecialChar ~
\r
535 mds_name Specify the mds name, which will provide service for this
\r
537 \layout Description
\r
539 --ost\SpecialChar ~
\r
540 ost_name\SpecialChar ~
\r
542 --lov\SpecialChar ~
\r
543 lov_name Specify the ost or lov, which will provide service
\r
545 \layout Description
\r
547 --clientoptions Specify the options for Lustre, such as async.
\r
549 \layout Description
\r
551 --add\SpecialChar ~
\r
552 route Creates a static route through a gateway to a specific
\r
562 \layout Description
\r
564 --node\SpecialChar ~
\r
565 node Node to add the route to.
\r
566 \layout Description
\r
568 --router Optional flag to mark a node as router.
\r
569 \layout Description
\r
576 of the gateway (must be a local interface or a peer).
\r
577 \layout Description
\r
579 --gateway_cluster_id\SpecialChar ~
\r
580 id Specify the id of the cluster, to which the gateway
\r
582 \layout Description
\r
584 --target_cluster_id\SpecialChar ~
\r
585 id Specify the id of the cluster, to which the target
\r
586 of the route belongs.
\r
587 \layout Description
\r
590 nid For a range route, this is the lo value
\r
593 \layout Description
\r
596 nid For a range route, this is the hi value
\r
600 \layout Description
\r
602 --add\SpecialChar ~
\r
603 echo-client Used for testing purpose only.
\r
606 \layout Description
\r
608 --node\SpecialChar ~
\r
613 Node on which the echo-client resides.
\r
615 \layout Description
\r
617 --add\SpecialChar ~
\r
618 mgmt Management/monitoring service.
\r
620 \layout Description
\r
622 --node\SpecialChar ~
\r
627 Node on which the mgmt service resides.
\r
628 \layout Description
\r
630 --mgmt\SpecialChar ~
\r
631 <mgmt_service_name> Specify management/monitoring service name.
\r
634 \labelwidthstring 00.00.0000
\r
638 --add\SpecialChar ~
\r
641 Create the cobd on the specified node.
\r
643 \layout Description
\r
644 \noindent \align left
\r
645 --node\SpecialChar ~
\r
650 Node on which the cobd resides.
\r
651 \layout Description
\r
653 --cache_obd\SpecialChar ~
\r
654 obd_name Specify the cache device for the cache obd system.
\r
655 \layout Description
\r
657 --real_obd\SpecialChar ~
\r
662 Specify the real device for the cache obd system.
\r
665 \labelwidthstring 00.00.0000
\r
670 \layout Description
\r
672 --reference Print short reference for commands.
\r
673 \layout Description
\r
675 --verbose Print system commands as they are run.
\r
676 \layout Description
\r
678 --batch\SpecialChar ~
\r
679 filename Used to execute lmc commands in batch mode.
\r
680 \layout Description
\r
682 --output\SpecialChar ~
\r
683 filename Send output to the file.
\r
684 If the file exists, it will be overwritten.
\r
685 \layout Description
\r
687 --merge\SpecialChar ~
\r
692 Add the new element to an existing file.
\r
697 \layout Subsubsection
\r
704 lmc --node adev3 --add net --nid adev3 --cluster_id 0x1000 --nettype tcp
\r
705 --hostaddr adev3-eth0 --port 988
\r
710 lmc --node adev3 --add net --nid adev3 --cluster_id 0x2000 --nettype tcp
\r
711 --hostaddr adev3-eth1 --port 989
\r
717 Used to add a Lustre node to a specified Lustre cluster through a network
\r
719 In this example, Lustre node adev3 has been added to 2 Lustre clusters
\r
720 whose cluster_id are 0x1000 and 0x2000 separately through 2 network interface
\r
721 cards: adev3-eth0 and adev3-eth1.
\r
722 adev3 would listen in some specified port(s) to prepare for possible connection
\r
723 requests from nodes in these two clusters.
\r
724 \layout Subsubsection
\r
731 lmc --node adev3 --add route --nettype tcp --gw 5 --gateway_cluster_id 0x1000
\r
732 --target_cluster_id 0x1000 --lo 4 --hi 7
\r
735 Used to add a route entry for a Lustre node.
\r
736 Here Lustre node adev3 is told it has a new route entry that now it could
\r
737 send packets to Lustre nodes whose nids is from 4 to 7 with the help of
\r
738 Lustre gateway node whose nid is 5.
\r
739 Besides, Lustre gateway node is in cluster whose id is 0x1000 and target
\r
740 of the route belongs to cluster whose id is also 0x1000.
\r
741 The network in this route path is a tcp network.
\r