Difference between revisions of "Lustre intel: Setting up a Windows client"
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
*:In our case, networks 1 and 2 are the same (pxe). Here is an example of a CTDB Framework on Lustre: | *:In our case, networks 1 and 2 are the same (pxe). Here is an example of a CTDB Framework on Lustre: | ||
| − | [[File:Ctdb-nodes.png]] | + | [[File:Ctdb-nodes.png | 450px]] |
Revision as of 15:22, 10 April 2015
The following instructions are for one (or multiple) linux system(s), which will serve as the middle-layer cluster, which "translates" Lustre to Windows, using Samba.
There are two components that need to be installed:
- CTDB
- Samba
Pre-Requisites
- Lustre Client File System mounted with full cluster-coherent locking support on all CTDB nodes:
mkdir -m 0755 -p /mnt/lfs
mount -t lustre -oflock 172.28.50.2@tcp0:172.28.50.3@tcp0:/lfs1 /mnt/lfs/- Networking
- Each CTDB node will require three network interfaces on three separate networks inorder to operate correctly:
- a high performance data network interface, used to mount the Lustre client file system. This is typically an InfiniBand or 10Gb Ethernet fabric
- a private network interface over which all CTDB nodes communicate, sending heartbeats, exchanging data and cluster commands
- a public network interface over which clients will connect to the services running on the CTDB cluster, such as Samba
- In our case, networks 1 and 2 are the same (pxe). Here is an example of a CTDB Framework on Lustre:
Error creating thumbnail: File missing