How to launch

EXAScaler Cloud application can be launched on AWS by navigating to the link below and selecting Continue to Subscribe.

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:

TODO

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:

Stack name step 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 profile that will configure AWS Cloud resources to deliver 10TB capacity.
  - Medium profile that will configure AWS Cloud resources to deliver 50TB capacity.
  - Large profile  that will configure AWS Cloud resources to deliver 100TB 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 filesystem - lockdown access to EXAScaler Cloud filesystem. Default can be accessed from anywhere.
• 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", click on "Outputs" to view the deployment output:

• Dashboard - URL to view the grid report
• Gateway - external IP address to remote access to the bastion host and EXAScaler Cloud environment

Click on the "Dashboard URL" button to open EXAScaler Web Console:

And use a terminal session to open a console session to the management host through a connection to the bastion host:

host:user$ eval $(ssh-agent)
Agent pid 79138

host:user$ ssh-add deiter.pem 
Identity added: deiter.pem (deiter.pem)

host:user$ ssh -A -J ec2-user@54.85.158.14 ec2-user@172.31.245.218
[ec2-user@EXAScaler-worker0 ~]$ df -h -t lustre
Filesystem                    Size  Used Avail Use% Mounted on
172.31.245.249@tcp:/exacloud   12T  9.8M   11T   1% /mnt/exacloud

[ec2-user@EXAScaler-worker0 ~]$ lfs df
UUID                   1K-blocks        Used   Available Use% Mounted on
exacloud-MDT0000_UUID    58189732        5820    52941036   1% /mnt/exacloud[MDT:0] 
exacloud-OST0000_UUID  1487383808        1244  1412235712   1% /mnt/exacloud[OST:0] 
exacloud-OST0001_UUID  1487383808        1244  1412235712   1% /mnt/exacloud[OST:1] 
exacloud-OST0002_UUID  1487383808        1248  1412235708   1% /mnt/exacloud[OST:2] 
exacloud-OST0003_UUID  1487383808        1248  1412235708   1% /mnt/exacloud[OST:3] 
exacloud-OST0004_UUID  1487383808        1244  1412235712   1% /mnt/exacloud[OST:4] 
exacloud-OST0005_UUID  1487383808        1244  1412235712   1% /mnt/exacloud[OST:5] 
exacloud-OST0006_UUID  1487383808        1244  1412235712   1% /mnt/exacloud[OST:6] 
exacloud-OST0007_UUID  1487383808        1248  1412235708   1% /mnt/exacloud[OST:7] 

filesystem_summary:  11899070464        9964 11297885684   1% /mnt/exacloud

[ec2-user@EXAScaler-worker0 ~]$