Amazon AWS Cloud Platform provides rich set of high-performance NVMe resources for building true enterprise-class NVMe Over Fabrics 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 AWS cloud documentation for detailed configuration steps.
| Purpose | Machine | Cores | Memory | Network | Storage |
|---|---|---|---|---|---|
| Shared block storage for IP-SAN or NVMeoF | Storage Optimized i3.xlarge Other i3 series | 4 | 30.5GB | ~10Gbps | Ephemeral direct NVMe or SSD 1 x 950 |
| High Performance NFS Server | Storage Optimized i3.2xlarge i2.2xlarge | 8 | 61GB | ~10Gbps | zpool 1 x 1900 (NVMe) 2 x 800 (SSD) |
| High-Availability | High Availability Set | Secondary Private IP address | Synchronous mirroring by using zpool mirror dm raid-1 over NVMe target DRBD replication |
Here is the sequence of steps involved in deploying High-Availability (HA) MayaNAS on AWS cloud platform. The next steps assume you’ve already deployed at two MayaNAS instances from AWS marketplace, with desired Availability Set. In this tutorial we will assume we are planing on deploying All Flash NFS Server configuration
- 2 compute instances
mayanas-ha1, mayans-ha2 - 1TB Premium io1 persistent storage
- Default network for the internal 172.31.26.4 (mayanas-ha1), 172.31.29.231(mayanas-ha2)
- Virtual IP: 172.31.30.30 (Any private IP address matching CIDR of VPC)
Connect to mayanas instances using SSH to secure the Web console GUI access by changing 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
Now you can proceed with High-Availability setup using the wizard from Administration Web console available on http://<mayanas-ip>:2020
