Page History
| Table of Contents | ||
|---|---|---|
|
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
...
- 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.
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.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
localhost$ eval $(ssh-agent)
Agent pid 5095
localhost$ ssh-add
Identity added: /Users/deiter/.ssh/ | ||||||
| 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 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
|
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 stop and start the servers
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
- You need a Microsoft account
- Your system needs the Microsoft Azure CLI
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.
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ az login |
To view the current Azure subscription ID, please use az account show command.
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ 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.
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ az account set --subscription XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX |
Get status of the servers
To get status of EXAScaler Cloud servers:
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ ./esc-ctl.sh resource_group_name status
Name Private_IP Public_IP Status
------------------ ------------ ------------- --------------
exacloud-d101-cls0 10.1.0.4 VM running
exacloud-d101-cls1 10.1.0.13 VM running
exacloud-d101-cls2 10.1.0.11 VM running
exacloud-d101-cls3 10.1.0.6 VM running
exacloud-d101-mds0 10.1.0.8 VM running
exacloud-d101-mgs0 10.1.0.10 40.86.178.179 VM running
exacloud-d101-oss0 10.1.0.9 VM running
exacloud-d101-oss1 10.1.0.12 VM running
exacloud-d101-oss2 10.1.0.7 VM running
exacloud-d101-oss3 10.1.0.5 VM running |
Stop the servers
To stop the EXAScaler Cloud servers:
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
- You need a Microsoft account
- Your system needs the Microsoft Azure CLI
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.
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ az login |
To view the current Azure subscription ID, please use az account show command.
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ 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.
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ az account set --subscription XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX |
List of existing resource groups
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ ./esc-ctl list
Name | ||||
| Code Block | ||||
| ||||
$ ./esc-ctl.sh resource_group_name stop Stop worker exacloud-d101-cls0 Stop worker exacloud-d101-cls1 Stop worker exacloud-d101-cls2 Stop worker exacloud-d101-cls3 Stop ost exacloud-d101-oss0 Stop ost exacloud-d101-oss1 Location Status ---------------- ---------- --------- EXAScaler-Cloud eastus Succeeded |
List of existing deployments for the given resource group
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ ./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
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ ./esc-ctl EXAScaler-Cloud exascaler-cloud-65f1 list Name Stop ost exacloud-d101-oss2 Size Role Version PrivateIP PublicIP Status ------------------------- ---------------- ------ --------- ----------- ------------ ---------- exascaler-cloud-65f1-cls0 Standard_D16s_v3 clt 5.2.3 10.0.0.7 VM Stop ost exacloud-d101-oss3 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 Stop mdt exacloud-d101-mds0 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 Stop mgt exacloud-d101-mgs0 running exascaler-cloud-65f1-oss2 Standard_D16s_v3 ost 5.2.3 10.0.0.6 |
Start the servers
To start the EXAScaler Cloud servers:
VM running
exascaler-cloud-65f1-oss3 Standard_D16s_v3 ost 5.2.3 10.0.0.9 VM running |
Stop the EXAScaler Cloud servers
| Code Block | ||||
|---|---|---|---|---|
| ||||
Start the EXAScaler Cloud servers
| Code Block | ||||
|---|---|---|---|---|
| ||||
| Code Block | ||||
| ||||
All required services will automatically start and the file system filesystem will be mounted and available on all compute clients.
Overview
Content Tools