Page History

...

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

EXAScaler Cloud environment can be deployed as a standard Azure application using the Azure Marketplace. And the installation wizard is used to deploy it. Installation wizard contains few configuration steps:

Basic step contains Project details:

• Subscription - because all resources in an Azure subscription are billed together. And we need select one from list of available subscriptions.
• Resource group - is a collection of resources that share the same lifecycle, permissions, and policies. And we can select an existing resource group or create a new one to deploy an EXAScaler Cloud environment.

Instance details:

• Azure region for our deployment. For example, we can select the location closest to us. And we must have enough resources in this location for the deployment (number of available CPU cores).
• Configuration Profile: we can choose predefined configuration profile or create a custom EXAScaler Cloud configuration. We provides two predefined profiles:
  - Small profile that will configure Microsoft Azure resources to deliver 10TB capacity and 1.44 GB/s throughput performance.
  - Medium profile that will configure Microsoft Azure resources to deliver 50TB capacity and 6  GB/s throughput performance.
  - Custom profile, that allows us to deploy any environment according to our requirements.
  DDN EXAScaler Cloud pricing is based on the number of CPU cores configured to meet the defined performance requirements. And DDN Premium Support is recommended for Custom profile.
• Filesystem name that will be mounted from clients as a distributed network resource.

Image Modified

Security step required to select user name and authentication parameters to remote access to the management server. And Microsoft Azure provides two options for
authentication: password and SSH key-based authentication:

Image Added

Lustre Filesystem name - this will be name of your lustre filesystem and also prepended to the names oVM hosts. For example here it is specified as ldemo so our MGS node will be ldemomgs.

TODO