You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 46 Next »

How to deploy an EXAScaler Cloud Application

EXAScaler Cloud application can be launched on Microsofts Azure platform by navigating to the link below and selecting GET IT NOW

Step by step deployment video

Step by step deployment guide

The steps below will show how to create a EXAScaler Cloud Cluster on Microsoft Azure platform. 

You will need an Azure account. Sign in.

Login to your account and go to the dashboard.

You can get to the dashboard from anywhere by clicking on the blue "Microsoft Azure" in the upper left corner of the GUI. 

To get started click on "Create a resource" to get ready to start deployments of a new instance of EXAScaler Cloud.

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.

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

and Instance details section:

  • 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: EXAScaler Cloud Application on Microsoft Azure Marketplace 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. 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 configuration profile, that allows us to deploy any environment according to our requirements.


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.

  • Filesystem name that will be mounted from compute clients as a distributed network resource.

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

Copy and paste the "" URL on a new browser tab to display detailed deployment statistics:

Some additional information is available on the 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.

How to access the EXAScaler Cloud environment

To remote access the EXAScaler Cloud environment (management, metadata, storage servers 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.

SSH session to the management server
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   1% /mnt/exacloud[MDT:0]
exacloud-OST0000_UUID  3181466888   570662088  2578541648  19% /mnt/exacloud[OST:0]
exacloud-OST0001_UUID  3181466888   590910696  2558305972  19% /mnt/exacloud[OST:1]
exacloud-OST0002_UUID  3181466888   580374740  2568825852  19% /mnt/exacloud[OST:2]
exacloud-OST0003_UUID  3181466888   570645704  2578552816  19% /mnt/exacloud[OST:3]

filesystem_summary:  12725867552  2312593228 10284226288  19% /mnt/exacloud

How to stop and start the EXAScaler Cloud environment

If you want to stop and start the servers in your EXAScaler Cloud environment (for example, to save cost on weekends) - please use the esc-ctl script.

Prerequisites

Before use the Microsoft Azure CLI for Microsoft Azure, you will need to authenticate under the Microsoft account you used to log into the Microsoft Azure Portal. You will use a Microsoft account and its credentials to allow the shell script to start/stop the EXAScaler Cloud servers.

Steps to authenticate via Microsoft account

Obtains access credentials for your user account via a web-based authorization flow. When this command completes successfully, it sets the active account in the current configuration to the account specified. Learn more.

$ az login

To view the current Azure subscription ID, please use az account show command.

$ az account show
{
  "environmentName": "AzureCloud",
  "homeTenantId": "00000000-0000-0000-0000-000000000000",
  "id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
  "isDefault": true,
  "managedByTenants": [],
  "name": "Pay-As-You-Go",
  "state": "Enabled",
  "tenantId": "00000000-0000-0000-0000-000000000000",
  "user": {
    "name": "user@domain.com",
    "type": "user"
  }
}

if you have more than one subscriptions - please set the default subscription. Learn more.

$ az account set --subscription XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

List of existing resource groups

$ ./esc-ctl list
Name              Location    Status
----------------  ----------  ---------
EXAScaler-Cloud   eastus      Succeeded

List of existing deployments for the given resource group

$ ./esc-ctl EXAScaler-Cloud list
Name                            Created                    Status
------------------------------  -------------------------  ---------
exascaler-cloud-65f1            2021-08-24T18:56:27+00:00  Succeeded

List of EXAScaler Cloud servers for the given deployment

$ ./esc-ctl EXAScaler-Cloud exascaler-cloud-65f1 list
Name                       Size              Role    Version    PrivateIP    PublicIP      Status
-------------------------  ----------------  ------  ---------  -----------  ------------  ----------
exascaler-cloud-65f1-cls0  Standard_D16s_v3  clt     5.2.3      10.0.0.7                   VM running
exascaler-cloud-65f1-cls1  Standard_D16s_v3  clt     5.2.3      10.0.0.5                   VM running
exascaler-cloud-65f1-cls2  Standard_D16s_v3  clt     5.2.3      10.0.0.8                   VM running
exascaler-cloud-65f1-cls3  Standard_D16s_v3  clt     5.2.3      10.0.0.13                  VM running
exascaler-cloud-65f1-mds0  Standard_E8s_v3   mdt     5.2.3      10.0.0.12                  VM running
exascaler-cloud-65f1-mgs0  Standard_F4s      mgt     5.2.3      10.0.0.11    20.62.171.73  VM running
exascaler-cloud-65f1-oss0  Standard_D16s_v3  ost     5.2.3      10.0.0.10                  VM running
exascaler-cloud-65f1-oss1  Standard_D16s_v3  ost     5.2.3      10.0.0.4                   VM running
exascaler-cloud-65f1-oss2  Standard_D16s_v3  ost     5.2.3      10.0.0.6                   VM running
exascaler-cloud-65f1-oss3  Standard_D16s_v3  ost     5.2.3      10.0.0.9                   VM running

Stop the EXAScaler Cloud servers

$ ./esc-ctl EXAScaler-Cloud exascaler-cloud-65f1 stop
Stop compute client exascaler-cloud-65f1-cls0
Stop compute client exascaler-cloud-65f1-cls1
Stop compute client exascaler-cloud-65f1-cls2
Stop compute client exascaler-cloud-65f1-cls3
Stop storage server exascaler-cloud-65f1-oss0
Stop storage server exascaler-cloud-65f1-oss1
Stop storage server exascaler-cloud-65f1-oss2
Stop storage server exascaler-cloud-65f1-oss3
Stop metadata server exascaler-cloud-65f1-mds0
Stop management server exascaler-cloud-65f1-mgs0

Start the EXAScaler Cloud servers

$ ./esc-ctl EXAScaler-Cloud exascaler-cloud-65f1 start
Start management server exascaler-cloud-65f1-mgs0
Start metadata server exascaler-cloud-65f1-mds0
Start storage server exascaler-cloud-65f1-oss0
Start storage server exascaler-cloud-65f1-oss1
Start storage server exascaler-cloud-65f1-oss2
Start storage server exascaler-cloud-65f1-oss3
Start compute client exascaler-cloud-65f1-cls0
Start compute client exascaler-cloud-65f1-cls1
Start compute client exascaler-cloud-65f1-cls2
Start compute client exascaler-cloud-65f1-cls3

All required services will automatically start and the filesystem will be mounted and available on all compute clients.


  • No labels