IN THIS ARTICLE
Outlines how to create a multi-node cloud cluster configuration of QF2 in AWS
- Account limits large enough for 20TB of EBS ST1 and 2TB of EBS GP2
- Permission to launch EC2 instances
NOTE: Modifying the type or size of the EBS volumes in the QF2 AMI will render the software not functional. Please use the AMI volume layout provided in the original image.
Four or more nodes running QF2 in AWS version 2.7.1 or higher
- The free trial AMI cannot run as a multi-node cluster
Command line (qq CLI) tools installed via API & Tools in the Web UI
NOTE: Creating a multi-node cluster using IP addresses in the UI of Qumulo Core is supported in versions 2.8.6 and above.
Running a clustered configuration of QF2 in AWS across 4 or more Qumulo nodes improves performance and increases capacity by providing a minimum of 20TB of raw storage. Larger systems with higher node numbers will have increased storage efficiency dependent on the initial number of nodes used to form the cluster. Before creating your QF2 in AWS cluster, consider the amount of storage and number of nodes that you need.
Before beginning, log into the AWS console to reference the EC2 Instance ID and the Private IPs of the nodes you wish to cluster using the Description tab of the instance listing.
Create a cluster via the UI in 2.8.6 and above
- In a browser window, enter https:// followed by the Private IP address included in the Description tab of the instance listing for one of the nodes
Note: Qumulo is configured with a self-signed certificate by default which may cause your browser to display a warning. This is normal behavior. A custom certificate can be installed at a later time to avoid the warning if needed. At the warning, select ADVANCED and click Proceed to continue.
- Login to the Qumulo Core Web UI
- Review the End User License Agreement, check the box to agree and click Submit
1. Setup Cluster
- Name the cluster
- Enter the IP addresses of the nodes you wish to cluster separating each address with a comma
2. Verify your Identity
- Enter the EC2 instance ID of the node
3. Create a password for your admin account
- Type in the password for your admin account
- Retype the password to confirm
- Click Create Cluster
Complete cluster configuration by confirming the settings for monitoring, networking, and time zone preferences in the right-hand panel of the dashboard.
Create a cluster via the CLI in 2.7.1 and above
- SSH onto one of the nodes using the private IP address
- Username is admin
- Use the private key specified on instance creation
- Use the command listed below to form a multi-node cluster by replacing the following with details specific to your cloud cluster
- NAME: Cluster name for your cloud cluster
- PASSWORD: Your admin password
- EC2_INSTANCE_ID: Instance ID of the ssh'd node
- PRIVATE_IP: List the private IP addresses from all nodes (including the ssh'd node) that will be added to cluster in the commands below using a space to separate
qq cluster_create --cluster-name NAME --admin-password PASSWORD
--max-drive-failures recommended --accept-eula --host-instance-id
EC2_INSTANCE_ID --node-ips PRIVATE_IP PRIVATE_IP
NOTE: Per AWS Marketplace requirements, a cluster creation challenge question was added to our AMI after version 2.7.6 of Qumulo Core. The qq cluster_create command featured above now requires the --host-instance-id argument specifying the EC2 instance ID of the QF2 node from which qq cluster_create is invoked.
Running a clustered configuration of QF2 in AWS is recommended for workloads that require elasticity and have high performance demands. While QF2 in clustered configuration leverages erasure coding for data protection across nodes, coordinated failure of an AWS availability zone can still occur.
IMPORTANT! It is not recommended to run a QF2 cluster in AWS for production data without a replication or backup strategy.
You should now be able to successfully create a multi-node cloud cluster for QF2 in AWS
Like what you see? Share this article with your network!