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: EXAScaler Cloud Application on Microsoft Azure Marketplace to create a new deployment or EXAScaler Cloud Application on Microsoft Azure Marketplace to update an existing deployment.
➋ Deployment step contains
Deployment details section
...
- 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
allows you to choose 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 Password based authentication
and SSH public key-based authentication
➍ Network step
To 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.
...
And configure remote access for SSH and HTTP protocols
➎ Management step
To to configure EXAScaler Cloud management server.
...
For predefined Small and Medium configuration profiles all configuration options are read-only.
➏ Metadata step
To to configure EXAScaler Cloud management server. For the Custom configuration profile we can change:
...
For predefined Small and Medium configuration profiles all configuration options are read-only.
➐ Storage step
To to configure EXAScaler Cloud storage servers. For the Custom configuration profile we can change:
...
For predefined Small and Medium configuration profiles all configuration options are read-only.
➑ Client step
Optionally : 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:
...
And all compute client options can be changed for any type of the configuration profile.
➒ Review + create step
At : 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:
...
And you can customize the dashboard according to your requirements.
How to access
...
an 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.
...
| 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 |
How to stop and start
...
an 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.
...
Then launch the standard EXAScaler Cloud Azure application using the Azure Marketplace
➊ Basics step:
- specify your Azure subscription
- new resource group
- region
- and select "Upgrade" value for the "Deployment type" option:
➋ Deployment step
Select : select an existing EXAScaler Cloud deployment:
...
Base OS image (you can upgrade Red Hat Enterprise Linux to CentOS Linux and vice versa) and availability options:
➌ Security step
Specify : specify user name and authentication parameters (you can use user name and authentication parameters other than the existing environment):
➍ Network step
Specify : specify network and subnet (you can create a new one) and public IP addresses options:
➎ Management step
You : you can change the type of management server and the type of management and monitoring targets, but the size of the targets must be the same as in the existing environment:
➏ Metadata step
You : you can change the type of metadata server and the type of metadata target, but the size of the target must be the same as in the existing environment:
➐ Storage step
You : you can change the type of storage servers and the type of storage targets, but the number of the storage servers and the number and size of the storage targets must be the same as in the existing environment:
➑ Client step
You : you can change the type of compute clients and the type of compute targets, but the number and size of the compute targets must be the same as in the existing environment:
➒ Review + create step
At : 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:
...
Overview
Content Tools