Page History
...
Click the dashboard name and open the "Go to dashboard" link:
And you can customize this dashboard according to your requirementsthe 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 shell 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:
| 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
Stop ost exacloud-d101-oss2
Stop ost exacloud-d101-oss3
Stop mdt exacloud-d101-mds0
Stop mgt exacloud-d101-mgs0 |
Start the servers
To start the EXAScaler Cloud servers:
| Code Block | ||
|---|---|---|
| ||
$ ./esc-ctl.sh resource_group_name start
Start mgt host exacloud-d101-mgs0
Start mdt host exacloud-d101-mds0
Start ost host exacloud-d101-oss0
Start ost host exacloud-d101-oss1
Start ost host exacloud-d101-oss2
Start ost host exacloud-d101-oss3
Start worker host exacloud-d101-cls0
Start worker host exacloud-d101-cls1
Start worker host exacloud-d101-cls2
Start worker host exacloud-d101-cls3 |
All required services will automatically start and the file system will be mounted and available on all clients.



