Page tree
Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 7 Next »

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.


PurposeMachineCoresMemoryNetworkStorage
Shared  block storage for IP-SAN or NVMeoF

Storage Optimized

Lsv2-series

864GB~3Gbps

Premium_LRS

Ephemeral direct NVMe or SSD

Capacity Optimized NFS server

LVM + VDO + XFS + NFS Server

General Family

D-series

416GB~8Gbps

Bcache(writeback) on Premium_LRS

Data on Standard_LRS

ssd:standard ratio 1:4

High Performance NFS Server

General Family

DS-Series

830GB~16Gbps

Bcache  uses Premium_LRS

Data on Standard_LRS

All Flash NFS server

ZFS Storage Appliance

D32s_v332128GB~16GbpsData & Log uses SSD Persistent Disk (Premium_LRS)
High-AvailabilityHigh Availability Set

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.  In this tutorial we will assume we are pllaning on deploying All Flash NFS Server configuration

In this tutorial we will assume we are planning on deploying All Flash NFS Server configuration with
  • 2 compute instances mayanas1, mayans2
  • 2TB pd-ssd persistent storage
  • Default network for the internal
  • Virtual IP: 10.9.0.10


MayaNAS HA Setup on GCP



  1. Connect to mayanas instances using SSH  to create Service Principal account.  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.

    On Azure cloud shell or other system where login credentials were already established
    az ad sp create-for-rbac --name mayasnas-sp --password Mayanas@123

    Please take a note of the tenant ID for the newly created service principal account.
    On mayanas1:
    sudo az login--service-principal -u http://mayanas-sp --tenant  b9f7862a-7153-4501-8039-8d9b37d7c0a9

    On mayanas2:
    sudo az login--service-principal -u http://mayanas-sp --tenant  b9f7862a-7153-4501-8039-8d9b37d7c0a9


    Please make sure login to service principal is done as root user.

  2. Change the default password to something random by running

    # /opt/mayastor/web/genrandpass.sh

    Or to set your own password

    /opt/mayastor/web/changepass.sh
    Login name (default admin): 
    Login password: 
    Password again: 
    
    
    

    And then restart the web server for password changes to take effect


    /opt/mayastor/web/stop
    
    /opt/mayastor/web/start





    40.78.60.49

  3. Now you can proceed with High-Availability setup using the wizard from Administration Web console available on http://<mayanas-ip>:2020

  • No labels