Page History

...

• 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 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.

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 Added

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

Next you will see the dashboard notification with EXAScaler stack "Create in progress":

Image Added

TODO