23.07.2014 Views

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

11.2.2.4 Specifying Security Flavors<br />

If you have not specified a security flavor, the CLIENT-MDT connection defaults to<br />

plain, and all other connections use null.<br />

Specifying Flavors by Mount Options<br />

When mounting OST or MDT devices, add the mount option (shown below) to<br />

specify the security flavor:<br />

# mount -t lustre -o sec=plain /dev/sda1 /mnt/mdt/<br />

This means all connections to this device will use the plain flavor. You can split this<br />

sec=flavor as:<br />

# mount -t lustre -o sec_mdt={flavor1},sec_cli={flavor1}/dev/sda \<br />

/mnt/mdt/<br />

This means connections from other MDTs to this device will use flavor1, and<br />

connections from all clients to this device will use flavor2.<br />

Specifying Flavors by On-Disk Parameters<br />

You can also specify the security flavors by specifying on-disk parameters on OST<br />

and MDT devices:<br />

# tune2fs -o security.rpc.mdt=flavor1 -o security.rpc.cli=flavor2 \<br />

device<br />

On-disk parameters are overridden by mount options.<br />

11.2.2.5 Mounting Clients<br />

Root on client node mounts <strong>Lustre</strong> without any special tricks.<br />

11-14 <strong>Lustre</strong> <strong>1.6</strong> <strong>Operations</strong> <strong>Manual</strong> • September 2008

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!