Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Software Environment: CentOS 7.3 (updated to the latest release), CentOS repositories available, Lustre 2.9 Client RPM's (anything >= 2.6 should be fine)

https://github.com/intel-hpddwhamcloud/lemur.git 

https://downloads.hpddwhamcloud.intel.com/public/lustre

Building & Installing Lemur/Lustre Client

...

Code Block
languagebash
[root@copy01 ~]# wget https://downloads.hpdd.intel.com/public/lustre/lustre-2.9.0/el7.3.1611/client/SRPMS/lustre-2.9.0-1.src.rpm

...

Code Block
languagebash
[root@copy01 ~]# rpmbuild --rebuild --without servers lustre-2.9.0-1.src.rpm
. 
. 
Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.TwezEa
+ umask 022
+ cd /root/rpmbuild/BUILD
+ rm -rf lustre-2.9.0
+ exit 0

 


  • Install the Lustre client RPM's and setup the Lustre network

...

Code Block
languagebash
[root@copy01 ~]# cat /etc/modprobe.d/lustre.conf
options lnet networks="o2ib0(ib0)" 

 


Download and Install Lemur

...

Setting up the POSIX component of Lemur, this configuration file is required before the copy tool will start correctly. 


 /etc/lhsmd/lhsm-plugin-posix

Code Block
languagebash
linenumberstrue
# Representative number of threads compared to the type of system it is running on
# Divisible by 8 usually makes sense to easily calculate scalability 
num_threads = 16 
 
# Archive name, this can be whatever you like
archive  "posix-test" {
    id = 1                          # Must be unique to this endpoint, we set this up earlier if you recall
    root = "/mnt/hsm2/HSMPATH"      # The base directory of the archive, local archive mount point, you need to mount this
 }

...


#######################################################

...

Setting up the basic Configuration Files

Placeholder text

 


#######################################################

...

  1. Open 4 shell sessions:
    1. One to the Lustre MDS
      1. tail -f /var/log/messages  
    2. Threeto the Data mover "copy01" in my case 
      1. tail -f /var/log/messages  
      2. Working shell for copy tool launch
      3. Testing shell
  2. In the working shell we will be starting the data mover with the debug flag.
    1. Be sure to monitor the logs on both servers and the debug output from the lhsmd command for any errors.  


Tip

The "lhsmd" command will not terminate in this instance, expect some very verbose output on the screen and then for it to suddenly stop, by this point check using "lfs df -h" to see if the frontend filesystem has been mounted. If you wish to terminate this you will need to issue a "Ctrl + C"

Code Block
languagebash
[root@copy01 ~]# lhsmd -config /etc/lhsmd/agent -debug

...


Functionality Testing

Basic Testing to ensure functionality  

...

Lemur, HPDD community JIRA project: https://jira.hpddwhamcloud.intel.com/projects/LMR