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 NOT IMPLEMENTED -- lmc [options] --remove <objecttype> [args]
53 NOT IMPLEMENTED -- lmc [options] --convert [args]
59 At present lmc when invoked adds configuration data to the config file.
60 lmc will also be able to remove configuration data or convert its forma.
61 One generates a single config file for the cluster at present including
62 at the minimum mds's, mtpt's and ost's and whatever those reference (e.g.
66 The objecttype refers to a collection of related configuration entities
69 net, mds, lov, ost, mtpt, route, oscref.
72 We describe the arguments required for the addition of each objecttype.
73 [NOT implemented] Lmc can also remove items from or convert the format
74 of configuration data.
77 to generate configuration data associated with systems in a Lustre cluster.
82 net Adds a network device descriptor for the given node, with parameters
87 The arguments required are
91 ''node_name'' If not present this will create a new node with the
93 This is also used to specify a specific node for other elements, and the
96 --nettype\SpecialChar ~
103 nid the network id, e.g.
104 ElanID or IP address as used by portals.
105 If host_name is '*', then the local address while be substituted when the
106 node is configured with lconf.
109 --router optional flag to mark this node as a router
112 --profile optional flag to mark this node as a profile node.
113 This is automatically true if the the --nid argument contains a '*'.
117 [port] optional argument to indicate the tcp port.
122 --tcpbuf\SpecialChar ~
123 <size> optional argument
137 <pathname> Path of device on local system.
138 If the is a file, then a loop device is created and used as the block device.
142 <size> optional argument indicating the size of the device to be created
143 (used typically for loop devices).
147 <nodename> Adds an MDS to the specified node.
148 This requires a --node argument, and it must not be a profile node.
153 lov Creates an LOV with the specified parameters.
154 The mds_name must already exist in the descriptor.
164 --stripe_sz\SpecialChar ~
168 --stripe_cnt\SpecialChar ~
172 --stripe_pattern\SpecialChar ~
173 <pattern> Pattern can be 0.
178 ost Creates an OBD, OST, and OSC.
179 The OST and OBD are created on the specified node.
184 <name> Assign a name to the OBD device.
188 <nodename> Node on which the OST service is run, can not be a profile
193 <pathname> Path of device on local system.
194 If the is a file, then a loop device is created and used as the block device.
202 <name> Name of LOV to which this OSC will be attached.
206 --obduuid\SpecialChar ~
207 UUID specify the UUID of the OBD device.
208 The default value is OBD_nodename_UUID.
213 mtpt Creates a mount point on the specified node.
214 Either an LOV or OSC name can be used.
219 node node or profile node that will use the mtpt
223 /mnt/path\SpecialChar ~
237 route Creates a static route through a gateway to a specific nid or
243 node node or profile node to add the route to
247 nid the nid of the gateway (must be a local interface or a peer)
251 nid for a specific route, this is the target nid
255 nid for a range route, this is the lo value nid
259 nid for a range route, this is the hi value nid
264 oscref Adds an OSC reference to a node.
265 This is only necessary when the the OSC will be used without a mountpoint.
270 node node or profile node to add the OSC ref to
274 osc_name Name of the OSC to add a reference to.
275 The --add ost command automatically creates the OSC, and the name will
276 be OSC_<node>, where node is the name of node the OST is on.
284 --output\SpecialChar ~
285 filename Sends output to the file.
286 If the file exists, it will be overwritten.
289 --merge\SpecialChar ~
290 filename Add the new element to an existing file.
298 Real life examples are given in the lustre-conf man page.
310 Cluster File Systems, Inc.