Configure MayaNAS

Connect to Administration Web console available on http://<mayanas1-ip>:2020 and login as admin and click Getting Started

Click Next to proceed with the wizard configuration. To exit from Wizard click Cancel and again Cancel for the prompt.

To skip a step click Cancel and OK for the prompt

1. Label: Give a name for this cloud profile. Ex: gcpaccount
2. Description: Give a short description on this account
3. Select Cloud Provider Storage Type
   AWS
   Azure
   Google Storage

• Account or Access Key: Copy and paste the Access Key avaiable from Cloud Console settings
• Secret: Copy and paste the key from Cloud provider console

Click Next to proceed with High Availability

Provide configuration details for High Availability. If you do not wish to setup HA simply click Cancel  and then click OK to skip this step and proceed with the wizard configuration.

• Active/Passive is selected
• Primary: hostname  filled automatically
• Secondary: Enter hostname that should match uname -n output
• Resource ID: Enter any number 1 to 255
• Virtual IP address: Enter  valid VIP address that is applicable for your cloud environment
  GCP: IPv4 address from  secondary address range assigned as IPaliases
  AWS: Available Private IP address within the subnet
  Azure: Any valid IPv4 address that is outside the subnet range of the instance
• Heartbeat Link1: (Left) Select the interface to use and enter IP address of the secondary node
• Heartbeat Link1:(Right)  Select the interface to use and enter IP address of the primary node
  Provide Heartbeat Link2 if more interfaces available

Click Next to proceed to the next step.

Please wait while High Availability configuration is being applied to both the MayaNAS instances.  This typically takes around 30 seconds to finish.

Click Next to proceed to the next step.

Provide details for the Cloud Disk

• Existing Bucket: If empty buckets created from the Cloud Console use existing one
  Otherwise select New Bucket
• New Bucket: Enter new bucket name here. If using exsting bucket it will be automatically filled for you
• Disk Name: Internal disk name for the cloud bucket name. If needed you may pick a different name or leave it as bucket name.
• Loop Device: Indicate whether you want the cloud disk to appear as loop device to Linux
  For Bcache this option will be selected
• Cache File: For HA operation no cache file be used. For single node it can be selected
• Disk Size: Though cloud storage has no limit you can simply specify reasonable size here.
• Block Size: Use the maximum block size 1MB to reduce cloud storage access costs.
• ClusterID: This field will be automatically filled in HA mode.

Click Next to proceed to the next step.

Provide details for ZFS storage pool

• Zpool cache Type:
  ZIL - Recommended for heavy write workloads
  Bcache - Better for bursty and low latency workloads
• Click and then add .nvme1 suffix
• Portal Tag: Click and accept default value 1
• Interfaces: Select the interface where the backend NVMe mirroring traffic will occur
• IP Address: This field will be filled automatically once interface is selected
• Port Number: Click and accept default value 4422. This way it is different from the default NVMe TCP port 4420 that will be used for the NVMe clients
• Authorized access only: Leave this checkbox unchecked
• Disks: Click to select all the available NVMe

Click Next to add VDEV disks to storage pool.

Select ZIL disk if that option was selected earlier.

Next select the Cloud disks as VDEV disks to pool

Click Next to proceed to the next step.

Provide Storage Pool details

• Label: Name for the storage pool
• Description: Optionally enter some description for this pool

Rest of the fields will be automatically filled. Click Next to proceed to the next step.

Select Storage Pool where new volumes will be provisioned

• Click the checkbox under Name columne of the storage pool
• Volume Type:
  Click on Block for block volumes sharing over iSCSI or NVME/TCP protocol
  Click File System for file system sharing using NFS or SMB protocol

Click Next to proceed to the next step.

Provide new volume details

• Label: Enter file sysntem dataset name
• Description: Optionally enter some description for this volume
• ZFS Options: Select appropriate options for the new volume
  LZ4 Compression: Select if compression is preferred
  Sparse: Select if thin provisioning volume is preferred
  Sync: Select option for data consistency
  always → writes will be acknowledged only after committed to stable storage
  standard → writes will be committed only if the client requested
  never → all writes are fully async
• Sequence of File System: Select if more than one volumes in sequence to be created.
  For example for default 3 it will create 3 new file systems client1,client2,client3 if label is client

Click Next to proceed to the next step.

Provide details on how the new volumes will be shared

• Volume: Select the volume to be mapped
• Controller:
  Choose iscsi or nvme-tcp for block volume
  Choose NFS or SMB for file system

Click Next to proceed to the next step.

Provide details on how the file system will be shared

• Share Label: Dataset
• Record size: This should match NFS record size
• Allowed Clients: Wild card * allows for all clients.
  List of hostnames comma separated or IP addresses or subnets can be entered
• name Click on this radio button to create new NVMe target for the first mapping to make use of Virtual IP address
  otherwise the mapping will be a local resource only and will not be controlled by HA faiilover scripts
  Add custom name after nqn.2022-20.com.zettalane:
• Export Options:

Click Next to proceed to the next step.

Review the mapping details provided by you

If there are more mappings to be specified for other volumes click on checkbox to Configure more mapping and the next step will present you with option to provide more mappings.

Click Next to proceed to the next step.

Final review of mapping details on how the new volumes

Click Finish to finish Getting Started Wizard.

Click on Add or remove Mappings to make sure the new volumes are activated and ready for access from clients.