Page History

How to launch

...

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:

Image Modified

Click "Continue to Subscribe" button:

...

Image Added

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

Image Added

And click "Continue to Configuration" button:

Image Added

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:

Image Added

Review selected  configuration and press "Launch" button:

Image Added

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

Image Added

Specify CloudFormation stack details:

Stack name

...

 contains unique name

...

of EXAScaler Cloud environment:

...

Image Added

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.

Image Modified

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.

...

Image Added

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.

...

Image Added

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

...

Image Added

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

Image Modified

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":

...

Image Added

Once the status changes to "CREATE_COMPLETE",

...

you can click on "Outputs" tab to view the deployment output:

...

• WebConsole - URL to view the grid report

...

• ManagementConsole - command line to remote access to the

...

• EXAScaler Cloud

...

• Management Server

...

Image Added

Click on the "WebConsole"

...

URL

...

to open EXAScaler Cloud Web Console:

Image ModifiedImage Modified

Image ModifiedImage Modified

And use a terminal

...

to open

...

an SSH session to the EXAScaler Cloud Management Server:

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

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

host:user$[localhost ~]$ ssh -A -J ec2-user@54.85.158.14 ec2-user@172.31.245.218ec2-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.245253.249@tcp229@tcp:/exacloud   12T  9.8M9M   11T   1% /mnt/exacloud

[ec2-user@EXAScaler-Cloud-worker0 ~]$ lfs df
UUID                   1K-blocks        Used   Available Use% Mounted on
exacloud-MDT0000_UUID    5818973275655388        58205828    5294103674307420   1% /mnt/exacloud[MDT:0] 
exacloud-OST0000_UUID  14873838081483837968        12441252  14122357121468794240   1% /mnt/exacloud[OST:0] 
exacloud-OST0001_UUID  14873838081483837968        12441256  14122357121468794236   1% /mnt/exacloud[OST:1] 
exacloud-OST0002_UUID  14873838081483837968        12481256  14122357081468794236   1% /mnt/exacloud[OST:2] 
exacloud-OST0003_UUID  14873838081483837968        12481260  14122357081468794232   1% /mnt/exacloud[OST:3] 
exacloud-OST0004_UUID  14873838081483837968        12441256  14122357121468794236   1% /mnt/exacloud[OST:4] 
exacloud-OST0005_UUID  14873838081483837968        12441256  14122357121468794236   1% /mnt/exacloud[OST:5] 
exacloud-OST0006_UUID  14873838081483837968        12441260  14122357121468794232   1% /mnt/exacloud[OST:6] 
exacloud-OST0007_UUID  14873838081483837968        12481260  14122357081468794232   1% /mnt/exacloud[OST:7] 

filesystem_summary:  1189907046411870703744       10056 996411750353880 11297885684   1% /mnt/exacloud

[ec2-user@EXAScaler-worker0 ~]$ 

AWS EC2 instance types

AWS EBS volume types

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

Anchor
Small Configuration Profile Small Configuration Profile

Servers

Targets

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

Anchor
Medium Configuration Profile Medium Configuration Profile

Servers

Targets