Azure Cloud Platform provides rich set of resources for building true enterprise-class NAS server readily. Please note that the network bandwidth is tied to the number of cpu cores of the compute instance. The storage IOPS is based on capacity of provisioned storage. Please refer to Azure cloud documentation for detailed configuration steps.
|Shared block storage for IP-SAN or NVMeoF|
Ephemeral direct NVMe or SSD
Capacity Optimized NFS server
LVM + VDO + XFS + NFS Server
Bcache(writeback) on Premium_LRS
Data on Standard_LRS
ssd:standard ratio 1:4
|High Performance NFS Server|
Bcache uses Premium_LRS
Data on Standard_LRS
All Flash NFS server
ZFS Storage Appliance
|D32s_v3||32||128GB||~16Gbps||Data & Log uses SSD Persistent Disk (Premium_LRS)|
High Availability Set
Requires Service Principal
Azure internal LoadBalancer.
Floating Virtual IP address
Here is the sequence of steps involved in deploying High-Availability (HA) MayaNAS on Azure cloud platform. The next steps assume you’ve already deployed at two MayaNAS instances from Azure marketplace, with desired Availability Set. In this tutorial we will assume we are planning on deploying All Flash NFS Server configuration
- 2 compute instances
- 1TB Premium SSD persistent storage
- Default network for the internal
- Virtual IP: 22.214.171.124
Connect to mayanas instances using SSH to setup Service Principal account, which is required only if you are planning to configure HA services. Otherwise you may skip to Step 2. MayaNAS requires a Service Principal account with sufficient permissions to manipulate disk attachments for proper sharing and fencing, and also storage read-write access to object storage. It also needs sufficient permission to float the virtual IP across multiple instances. By having separate service account for all MayaNAS deployments you can enforce proper security measures as the assigned roles are limited to this project instance only.
The service principal account is created from Azure cloud shell or other system where login credentials were already established, and not from the MayaNAS instances
az ad sp create-for-rbac --name mayanas-sp --password Mayanas@123
Please take a note of the tenant ID for the newly created service principal account. You may choose the same service principal name but the password is given as an example only.
sudo az login--service-principal -u --tenant b9f7862a-7153-4501-8039-8d9b37d7c0a9
sudo az login--service-principal -u--tenant b9f7862a-7153-4501-8039-8d9b37d7c0a9
Please make sure login to service principal is done as root user. It is a one time setup only.
Change the default password to something random by running
Or to set your own password
And then restart the web server for password changes to take effect
Now you can proceed with High-Availability setup using the wizard from Administration Web console available on http://<mayanas-ip>:2020