Installing IML on Vagrant
Software Contributor Documentation Table of Contents
Please refer to https://github.com/whamcloud/vagrantfiles on how to create a virtual HPC storage cluster with vagrant before attempting to install IML.
Install Virtualbox and Vagrant
Verify that the following vagrant plugins are installed:
vagrant plugin list vagrant plugin install vagrant-shell-commander vagrant plugin install vagrant-proxyconf <--- Optional, for example, this may be needed if behind corporate firewall.
Clone the Vagrantfiles repo from github
git clone firstname.lastname@example.org:whamcloud/Vagrantfiles.git
navigate to the
Start the VM cluster
Install IML via vagrant provisioning
vagrant provision adm --provision-with install-iml-5
Test that a connection can be made to IML by going to the following link in your browser: https://localhost:8443
You should now be able to see IML when navigating to https://localhost:8443. Click on the login link at the top right and log in as the admin user (password: lustre). After logging in, go to the servers page by selecting the following:
Configuration -> Servers
Add Servers button and enter the following hostlist expression:
Next button and all servers will be verified for installation. After verifying all servers, proceed to the profile selection screen. Select the appropriate profile based on the setup type:
- Monitored Storage Server: A monitored storage profile is a good option to use for server nodes that are already part of an existing filesystem. Instead of attempting to manage the server nodes, using a monitor profile will simply monitor the storage server and provide metrics for the filesystem operations on the dashboard page.
- Managed Storage Server: This allows the manager GUI to configure Corosync and Pacemaker, configure NTP, etc., so that the manager software can monitor and manage the server. Managed storage servers must be physically configured for high-availability/server failover.
- POSIX HSM Agent Node: An HSM Agent node is used in hierarchical storage management to run an instance of Copytool. Copytool transfers certain files between the Lustre file system and the archive. Archived files are deleted from the Lustre file system. See Configuring and using Hierarchical Storage Management
- Robinhood Policy Engine Server: This server hosts the Robinhood policy engine, which enables automation of hierarchical storage management activities. See Configuring and using Hierarchical Storage Management.
Finally, select the
Proceed button and the servers will be configured based upon the selected profile.
Once all servers have been added, each server will need to know which interface should be assigned the lustre network. This can be done manually or automated by a provisioning script depending on the type of filesystem being created.
1. Managed ldiskfs and ZFS filesystems
On the servers page, navigate to each server’s detail page by clicking on the server link. Scroll to the bottom of the server detail page where you will see a list of network interfaces. Click on the
Configure button and you will be given the option to change the network driver and the network for each interface.
The vagrant file indicates that the lustre network will run on 10.73.20.x. If
Lustre Network 0 is specified for a different IP address, you will need to change its interface to
Not Lustre Network and update the network for 10.73.20.x to use
Lustre Network 0. It is very important that Lustre Network 0 is specified on the correct interface; otherwise, creating a filesystem will fail. Make sure that all servers have been updated where appropriate.
2. Monitor only ldiskfs and ZFS filesystems
The interfaces can be configured automatically by running the following script:
vagrant provision mds1 mds2 oss1 oss2 --provision-with configure-lustre-network
Continue with Setup
Select the following options to continue setting up the filesystem:
Top of page