Page History
...
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:.
➊ Basics step contains
Project details section:
- Subscription - all resources in an Azure subscription are billed together. So 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.
...
- 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).
- Deployment type: Install to create a new deployment or Upgrade to update an existing deployment.
➋ Deployment step contains
Deployment details section
- Configuration Profile: we can choose predefined configuration profile or create a custom EXAScaler Cloud configuration. We provides two Two predefined profiles available:
- Small configuration profile that will configure Microsoft Azure resources to deliver 10TB capacity and 1.44 GB/s throughput performance.
- Medium configuration profile that will configure Microsoft Azure resources to deliver 50TB capacity and 6 GB/s throughput performance.
- And one Custom profile configuration 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 configuration profile.
- OS image: we can choose Red Hat Enterprise Linux or CentOS Linux as a base OS to deploy.
- Filesystem name that will be mounted from compute clients as a distributed network resource.
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:
Network step to configure Azure Virtual Network which enables resources to securely communicate with each other. And the subnet inside the virtual network where EXAScaler Cloud virtual machines will be deployed to.
We can create a new virtual network for deployment or we can use an existing network, for example, if we already have an environment with clients that need a HPC storage:
Management step to configure EXAScaler Cloud management server. For the Custom Configuration profile we can choose:
- Size of management server
- Type and size of management target
- Type and size of monitoring target
For Small and Medium Configuration profiles all configuration options are read-only:
Metadata step to configure EXAScaler Cloud management server. For the Custom Configuration profile we can choose:
- Size of metadata server
- Type and size of metadata target
For Small and Medium Configuration profiles all configuration options are read-only:
Storage step to configure EXAScaler Cloud object storage servers. For the Custom Configuration profile we can choose:
- Size of storage server
- Number of storage servers
- Type, size and count of storage targets
For Small and Medium Configuration profiles all configuration options are read-only:
Client step: optionally we can deploy client instances and by default the size and number of client instances matches the size and number of object storage servers. As an option we can create and attach local disks to each EXAScaler Cloud client. We can change:
- Size of storage client
- Number of storage clients
- Type, size and count of storage targets
And all storage client options can be changed for any Configuration profile:
Review + create step: at this stage Microsoft Azure checks all selected options against the subscription quota. And we can review and check all the parameters we have chosen before starting the deployment:
- Subscription
- Resource group
- Region
- Configuration profile
- Filesystem name
- User name and authentication parameters
- Network properties
- Management server options
- Metadata server options
- Storage server(s) options
- Storage client(s) options
And we can press a "Create" button and send the selected configuration for deployment.
Next you will see the dashboard notification with "Deployment is in progress":
Once the status changes to "Your deployment is complete", click on "Outputs" to view the deployment output:
In the "Outputs" screen:
command to remote access
to mount EXAScaler distributed file system. All storage clients created in this deployment should mount this filesystem
- EXAScaler Cloud Private IP Addresses
To remote access the EXAScaler Cloud servers (management, metadata, object storage and storage clients), we must go through the management server public IP address, using the command.
And then using the management server console as a jump host we can open a SSH sessions to all other servers.
Availability options section
Azure offers a range of options for managing availability and resiliency. And we can choose:
- None - no infrastructure redundancy required.
- Availability set - logical grouping of virtual machines that allows Azure to provide redundancy and availability. Each virtual machine in an availability set is assigned an update domain and a fault domain by the underlying Azure platform. Fault domains define the group of virtual machines that share a common power source and network switch. And the virtual machines configured within an availability set are separated across 3 fault domains. Update domains indicate groups of virtual machines and underlying physical hardware that can be rebooted at the same time.
- Availability zone - unique physical locations within an Azure region. Each zone is made up of one or more datacenters with independent power, cooling, and networking. To ensure resiliency, there is a minimum of three separate zones in all enabled regions. The physical separation of availability zones within a region protects applications and data from datacenter failures. An availability zone in an Azure region is a combination of a fault domain and an update domain.
➌ 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 based authentication
and SSH public key-based authentication
➍ Network step to configure Azure Virtual Network which enables resources to securely communicate with each other. And the subnet inside the virtual network where EXAScaler Cloud environment will be deployed to.
We can use an existing network or create a new virtual network and specify address range
Also we can assign external IP addresses:
- Management server - public IP address will be assigned to the management server only
- All servers - public IP addresses will be assigned to all servers
- None - no public IP addresses sill be assigned
And configure remote access for SSH and HTTP protocols
➎ Management step to configure EXAScaler Cloud management server.
For the Custom configuration profile we can configure:
- Type of management server
- Type and size of management target
- Type and size of monitoring target
And all selected configurations are checked for compliance
For predefined Small and Medium configuration profiles all configuration options are read-only.
➏ Metadata step to configure EXAScaler Cloud management server. For the Custom configuration profile we can change:
- Type of metadata server
- Type and size of metadata target
For predefined Small and Medium configuration profiles all configuration options are read-only.
➐ Storage step to configure EXAScaler Cloud storage servers. For the Custom configuration profile we can change:
- Type of storage server
- Number of storage servers
- Type, size and count of storage targets
For predefined Small and Medium configuration profiles all configuration options are read-only.
➑ Client step: optionally we can deploy compute client instances and by default the size and number of compute client instances matches the size and number of object storage servers. As an option we can create and attach local disks to each EXAScaler Cloud compute client. We can change:
- Size of storage client
- Number of storage clients
- Type, size and count of storage targets
And all compute client options can be changed for any type of the configuration profile.
➒ Review + create step: at this stage Microsoft Azure checks all selected options against the subscription quota. And we can review and check all the parameters we have chosen before starting the deployment:
- Subscription
- Resource group
- Region
- Deployment type
- Configuration profile
- OS image
- Filesystem name
- Availability type
- Availability zone
- User name and authentication parameters
- Virtual network and subnet parameters
- Public IP address options
- Remote access parameters
- Management server options
- Metadata server options
- Storage server(s) options
- Compute client(s) options
And we can press a "Create" button and send the selected configuration for deployment.
Next we will see the dashboard notification with "Deployment is in progress":
Once the status changes to "Your deployment is complete", click on "Outputs" to view the deployment output:
In the "Outputs" screen:
- Dashboard URL to display the deployment details
command to remote access to the management server
to mount EXAScaler Cloud distributed file system. All compute clients created in this deployment should mount this filesystem
- Private IP addresses
To remote access the EXAScaler Cloud servers (management, metadata, storage and compute clients), we must go through the management server public IP address, using the command.
And then using the management server console as a jump host we can open a SSH sessions to all other servers.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
localhost$ eval $(ssh-agent)
Agent pid 5095
localhost$ ssh-add
Identity added: /Users/deiter/.ssh/id_rsa (/Users/deiter/.ssh/id_rsa)
localhost$ ssh -A stack@20.62.171.73
Last login: Tue Aug 24 19:11:18 2021 from 181.241.16.227
[stack@exascaler-cloud-65f1-mgs0 ~]$ loci hosts
10.0.0.7 exascaler-cloud-65f1-cls0
10.0.0.5 exascaler-cloud-65f1-cls1
10.0.0.8 exascaler-cloud-65f1-cls2
10.0.0.13 exascaler-cloud-65f1-cls3
10.0.0.12 exascaler-cloud-65f1-mds0
10.0.0.11 exascaler-cloud-65f1-mgs0
10.0.0.10 exascaler-cloud-65f1-oss0
10.0.0.4 exascaler-cloud-65f1-oss1
10.0.0.6 exascaler-cloud-65f1-oss2
10.0.0.9 exascaler-cloud-65f1-oss3
[stack@exascaler-cloud-65f1-mgs0 ~]$ ssh exascaler-cloud-65f1-cls0
[stack@exascaler-cloud-65f1-cls0 ~]$ lfs df
UUID 1K-blocks Used Available Use% Mounted on
exacloud-MDT0000_UUID 315302464 5744 309928012 | ||||||
| Code Block | ||||||
| ||||||
localhost$ eval $(ssh-agent) Agent pid 5095 localhost$ ssh-add Identity added: /Users/deiter/.ssh/id_rsa (/Users/deiter/.ssh/id_rsa) localhost$ ssh -A exacloud@137.135.11.112 [exacloud@exacloud-5606-mgs0 ~]$ ssh 10.1.0.9 [exacloud@exacloud-5606-oss3 ~]$ df -h -t lustre Filesystem Size Used Avail Use% Mounted on /dev/sdc 504G 1.3M 479G 1% /mnt/targets/exacloud-OST0012 /dev/sdd 504G 1.3M 479G 1% /mnt/targets/exacloud-OST0013 /dev/sde 504G 1.3M 479G 1% /mnt/targets/exacloud-OST0014 /dev/sdf 504G 1.3M 479G 1% /mnt/targets/exacloud-OST0015 /dev/sdg 504G 1.3M 479G 1% /mnt/targets/exacloud-OST0016 /dev/sdh 504G 1.3M 479G 1% /mnt/targets/exacloud-OST0017 [exacloud@exacloud-5606-oss3 ~]$ exit logout Connection to 10.1.0.9 closed. [exacloud@exacloud-5606-mgs0 ~]$ ssh 10.1.0.7 [exacloud@exacloud-5606-cls0 ~]$ lfs df UUID 1K-blocks Used Available Use% Mounted on exacloud-MDT0000_UUID 315302464 6204 288452716 1% /mnt/exacloud[MDT:0] exacloud-OST0000_UUID 528246848 1256 501385664 1% /mnt/exacloud[OST:0] exacloud-OST0001_UUID 528246848 1260 501385660 1% /mnt/exacloud[OST:1] exacloud-OST0002_UUID 528246848 1260 501385660 1% /mnt/exacloud[OST:2] exacloud-OST0003_UUID 528246848 1260 501385660 1% /mnt/exacloud[OST:3] exacloud-OST0004_UUID 528246848 1260 501385660 1% /mnt/exacloud[OST:4] exacloud-OST0005_UUID 528246848 1264 501385656 1% /mnt/exacloud[OST:5] exacloud-OST0006_UUID 528246848 1240 501385680 1% /mnt/exacloud[OST:6] exacloud-OST0007_UUID 528246848 1244 501385676 1% /mnt/exacloud[OST:7] exacloud-OST0008_UUID 528246848 1244 501385676 1% /mnt/exacloud[OST:8] exacloud-OST0009_UUID 528246848 1248 501385672 1% /mnt/exacloud[OST:9] exacloud-OST000a_UUID 528246848 1252 501385668 1% /mnt/exacloud[OST:10] exacloud-OST000b_UUID 528246848 1252 501385668 1% /mnt/exacloud[OST:11] exacloud-OST000c_UUID 528246848 1244 501385676 1% /mnt/exacloud[OST:12] exacloud-OST000d_UUID 528246848 1248 501385672 1% /mnt/exacloud[OST:13] exacloud-OST000e_UUID 528246848 1248 501385672 1% /mnt/exacloud[OST:14] exacloud-OST000f_UUID 528246848 1252 501385668 1% /mnt/exacloud[OST:15] exacloud-OST0010_UUID 528246848 1256 501385664 1% /mnt/exacloud[OST:16] exacloud-OST0011_UUID 528246848 1260 501385660 1% /mnt/exacloud[OST:17] exacloud-OST0012_UUID 528246848 1244 501385676 1% /mnt/exacloud[OST:18] exacloud-OST0013_UUID 528246848 1248 501385672 1% /mnt/exacloud[OSTMDT:190] exacloud-OST0014OST0000_UUID 3181466888 528246848 570662088 2578541648 1248 501385672 1% 19% /mnt/exacloud[OST:200] exacloud-OST0015OST0001_UUID 5282468483181466888 590910696 2558305972 1252 501385668 1% 19% /mnt/exacloud[OST:211] exacloud-OST0016OST0002_UUID 3181466888 528246848 580374740 1256 501385664 2568825852 1%19% /mnt/exacloud[OST:222] exacloud-OST0017OST0003_UUID 3181466888 528246848 570645704 2578552816 1256 501385664 1% 19% /mnt/exacloud[OST:233] filesystem_summary: 1267792435212725867552 2312593228 10284226288 30052 12033256028 1% 19% /mnt/exacloud |
Copy and paste the "" URL on a new browser tab to view EXAScaler Cloud Web Consoledisplay detailed deployment statistics:
Some additional information is available on the deployment Azure shared dashboard: Azure portal → Home → Resource groups → EXAScaler-Cloud:
Click the dashboard name and open the "Go to dashboard" link:
And you can customize the dashboard according to your requirements.
...
Overview
Content Tools