Greetings friends, I have told you on numerous occasions how to deploy Nutanix Community Edition on different platforms such as VMware Fusion, using ISO, using PowerShell to create a cluster of three nodes, and so on.
Today I bring you something much simpler, it only takes 5 minutes to have a Single-Cluster using a simple OVF image I’ve created ready for you to try Community Edition today.
System requirements to deploy Nutanix Community Edition 126.96.36.199 in OVF format
I want to emphasize that this image is based on the latest version of Nutanix Community Edition 188.8.131.52, which was announced a few months ago, and that this OVF is intended only to be deployed nested on vSphere or ESXi, we go with the requirements, the image is consuming the following, but you can edit CPU and RAM:
- Intel CPU, 4 cores minimum, with VT-x support enabled. The image has 8 Cores, 2 processors of 4.
- Memory 16GB minimum. I will recommend something in the order of 24 or 32GB.
- Hot Tier (SSD) One SSD for each minimum Server to install Hypervisor Acropolis, ≥ 16GB
- Hot Tier (SSD) One SSD for each minimum Server, ≥ 200GB per server. We’d better deploy it over SSD.
- Cold Tier (HDD) One SSD for each server minimum, ≥ 500GB per server.
If we meet the requirements, for example in my case I have an SSD of 1TB and launched there all the OVF with their disks and everything.
We should download the OVF image from here, with all the disks and others in the following S3 bucket, download the .zip file and unzip it in a local folder, it will be like this:
Once we have everything unfolded we will be able to pass to the next section.
How to Deploy in vSphere this OVF of Nutanix Community Edition 184.108.40.206
Once we have all the files ready, we will go to our vCenter or ESXi, and we will do right button to deploy OVF, in ESXi Create/Register VM:
Now select the network switch in your environment (it should have promiscuous mode enabled), as well as if we want Thin or Thick (Thin please if you do not want to consume 700GB so suddenly) and if we want to boot when we finish:
How to Install Nutanix Community Edition on vSphere 6.7 in a nested way
We will select the rescue option as I told you to do boot: As a user, we will introduce install and the installation process will begin. We will be able to select the keyboard that we want, in my case I have left US:
- One for Hypervisor Acropolis itself
- Another for CVM virtual machine
We’ll mark it as a Single-Node, add a DNS server, read the EULA and mark that we’ve read it: We can follow the installation process in two ways, seeing if the CVM and Hypervisor are displayed correctly, above, and seeing the remaining points to finish: After a few minutes, we will have our Nutanix Community Edition installed:
Initial Configuration of Nutanix Community Edition 220.127.116.11
Once we restart the VM, we’ll see the typical background image of Nutanix, with the build number.
Remember that we have two IPs, Acropolis and CVM. Once we have ping to the CVM, we could log in through SSH.
- CVM Username: nutanix / Username Acropolis: root
- Password: nutanix/4u
Note: If we check the single-node option, when it starts for the first time the CVM will create the cluster automatically.
We can open the IP in a browser and it will redirect us to PRISM over port 9440 in HTTPS.
In this step we must introduce our NEXT community credentials, you can create one by going to this link:
And we’ll be inside Acropolis, the latest version, where we can start creating VM, add other Host, review all the menus, etc. I hope you like it and do not miss the following posts on Nutanix Community Edition.
Note regarding VMs stuck in SeaBIOS
Something has changed in Nutanix CE, that now requires an extra step if when you boot any VM, you have the next message:
ls /var/cache/libvirt/qemu/capabilities/ -lah
drwxr-xr-x. 2 root root 4.0K Mar 25 21:17 .
drwxr-x---. 3 qemu qemu 4.0K Mar 24 21:34 ..
-rw-------. 1 root root 7.1K Mar 25 20:47 3c76bc41d59c0c7314b1ae8e63f4f765d2cf16abaeea081b3ca1f5d8732f7bb1.xml
-rw-------. 1 root root 7.1K Mar 25 21:17 f4be1fa2d4f264472f03de9360e9ecffe23e924975261d8c90ebae8aeba3f727.xml
You need to edit the one which IS NOT 3c76bc…, so in my case, the one starts with f4b3…, and you need to scroll until the end and follow the next instructions: