Step by step guide

The steps below will show how to create a EXAScaler Cloud Cluster on AWS platform.

You will need a AWS account. Sign in.

Login to your account and go to the AWS Marketplace.

In the search box that appears, type "EXAScaler Cloud" and hit return. For some reason the completions that start to show up do not work as expected:

Click "Continue to Subscribe" button:

To create a subscription, review the pricing information and accept the terms for this software:

And click "Continue to Configuration" button:

EXAScaler Cloud environment can be deployed as a standard AWS Cloud Formation template. And the installation wizard is used to deploy it. Installation wizard contains few configuration steps.

Configuration step:

  • Choose the "CloudFormation Template" delivery method
  • Choose a "Custom" or "Predefined" template
  • Choose a region

And press "Continue to Launch" button:

Review selected  configuration and press "Launch" button:

"Create stack" step - click "Next" button:

Specify CloudFormation stack details:

Stack name contains unique name of EXAScaler Cloud environment:

Filesystem details:

  • Filesystem name that will be mounted from clients as a distributed network resource.
  • Configuration profile we can choose predefined configuration profile or create a custom EXAScaler Cloud configuration. We provides three predefined profiles:
    - Small Configuration Profile that will configure AWS Cloud resources to deliver 10TB capacity.
    - Medium Configuration Profile that will configure AWS Cloud resources to deliver 50TB capacity.
    DDN EXAScaler Cloud pricing is based on the number of CPU cores configured to meet the defined performance requirements.

Network and security details step to configure AWS Virtual Network which enables resources to securely communicate with each other. And the subnets inside the virtual network where Bastion host and EXAScaler Cloud environment will be deployed to:

  • SSH public key - name of an existing EC2 SSH key to enable SSH access to EXAScaler Cloud environment. Please select an item in the drop-down list.
  • Virtual network name - existing VPC network where EXAScaler Cloud environment will be deployed to. Please select an item in the drop-down list.
  • Public subnet name - name of an exisiting public subnet within the previously selected VPC network. Public subnet will be used to deploy bastion host instance.
  • Private subnet address range - address range in CIDR notation for new private subnet within the previously selected VPC network. For example, 10.0.1.0/24. Private subnet will be used to deploy EXAScaler Cloud environment.
  • Placement group - name of placement group to use. Optional, leave blank if not required.
  • Cloud Watch - enable forwarding of EXAScaler Cloud logs to AWS Cloud Watch.
  • Access to the management WEB console - lockdown access to EXAScaler Cloud management web console. Default can be accessed from anywhere.
  • Access to the management SSH console - lockdown SSH access to the bastion host. Default can be accessed from anywhere.

Compute client details step to configure EXAScaler Cloud compute clients. We can change:

  • Type of compute client - AWS instance type for EXAScaler Cloud compute client(s).
  • Number of compute clients - configure the number of EXAScaler Cloud compute client(s).
  • Bucket name - optionaly we can import data from the existing S3 bucket. Leave blank if not required.
  • Destination name - subdirectory in EXAScaler Cloud filesystem to import data into. Will default to ImportPrefix, if specified. Optional, leave blank if not required.
  • Import prefix - import all keys below prefix in ImportBucket. If unspecified, all keys in ImportBucket will be imported. Optional, leave blank if not required.

Press Next button to review  and check all the parameters we have chosen before starting the deployment:

Before starting the deployment, enable the Capabilities checkbox to allow the creation of the required resources:

And we can press a "Create stack" button and send the selected configuration for deployment.

Next you will see the dashboard notification with EXAScaler Cloud stack "CREATE_IN_PROGRESS":

Once the status changes to "CREATE_COMPLETE", you can click on "Outputs" tab to view the deployment output:

  • WebConsoleURL to view the grid report
  • ManagementConsole - command line to remote access to the EXAScaler Cloud Management Server

Click on the "WebConsole" URL to open EXAScaler Cloud Web Console:

And use a terminal to open an SSH session to the EXAScaler Cloud Management Server:

[localhost ~]$ eval $(ssh-agent)
Agent pid 79138

[localhost ~]$ ssh-add deiter.pem 
Identity added: deiter.pem (deiter.pem)

[localhost ~]$ ssh -A ec2-user@EXAScaler-ElasticL-1483AQZ7Z1YQ5-267879774.us-east-1.elb.amazonaws.com

[ec2-user@EXAScaler-Cloud-mgs ~]$ loci hosts
172.31.253.30	EXAScaler-Cloud-mds0
172.31.253.229	EXAScaler-Cloud-mgs
172.31.200.227	EXAScaler-Cloud-nat
172.31.253.67	EXAScaler-Cloud-oss0
172.31.253.106	EXAScaler-Cloud-oss1
172.31.253.227	EXAScaler-Cloud-worker0
172.31.253.126	EXAScaler-Cloud-worker1
172.31.253.38	EXAScaler-Cloud-worker2
172.31.253.254	EXAScaler-Cloud-worker3

[ec2-user@EXAScaler-Cloud-mgs ~]$ ssh 172.31.253.227

[ec2-user@EXAScaler-Cloud-worker0 ~]$ df -h -t lustre
Filesystem                    Size  Used Avail Use% Mounted on
172.31.253.229@tcp:/exacloud   12T  9.9M   11T   1% /mnt/exacloud

[ec2-user@EXAScaler-Cloud-worker0 ~]$ lfs df
UUID                   1K-blocks        Used   Available Use% Mounted on
exacloud-MDT0000_UUID    75655388        5828    74307420   1% /mnt/exacloud[MDT:0] 
exacloud-OST0000_UUID  1483837968        1252  1468794240   1% /mnt/exacloud[OST:0] 
exacloud-OST0001_UUID  1483837968        1256  1468794236   1% /mnt/exacloud[OST:1] 
exacloud-OST0002_UUID  1483837968        1256  1468794236   1% /mnt/exacloud[OST:2] 
exacloud-OST0003_UUID  1483837968        1260  1468794232   1% /mnt/exacloud[OST:3] 
exacloud-OST0004_UUID  1483837968        1256  1468794236   1% /mnt/exacloud[OST:4] 
exacloud-OST0005_UUID  1483837968        1256  1468794236   1% /mnt/exacloud[OST:5] 
exacloud-OST0006_UUID  1483837968        1260  1468794232   1% /mnt/exacloud[OST:6] 
exacloud-OST0007_UUID  1483837968        1260  1468794232   1% /mnt/exacloud[OST:7] 

filesystem_summary:  11870703744       10056 11750353880   1% /mnt/exacloud

AWS EC2 instance types

TypevCPUMemory, GBNetwork Bandwidth, GbpsDisk Bandwidth, Mbps
c5n.9xlarge3696509500

c5.18xlarge

721442519000

AWS EBS volume types

TypeSize, GBIOPSThroughput, MiB/s
gp21 - 1638416000250
io14 - 16384640001000

Small Configuration Profile (10TB and 1.44GB/s)

Servers

RoleTypeCount
MGSc5n.9xlarge1
MDSc5n.9xlarge1
OSSc5n.9xlarge2

Targets

RoleTypeSize, GBCount
MGTgp2161
MDTio11281
OSTgp2

1434

4

Medium Configuration Profile (50TB and 6GB/s)

Servers

RoleTypeCount
MGS

c5.18xlarge

1
MDS

c5.18xlarge

1
OSS

c5.18xlarge

3

Targets

RoleTypeSize, GBCount
MGTgp2161
MDTio12561
OSTgp221249
  • No labels