Team Leader - Nutanix Technology Champion - Nutanix NTC Storyteller

Julien DUMUR
Infrastructure in a Nutshell

To be able to deploy virtual machines on your cluster, you will need images that are available to launch your installations and here is the procedure to follow.

Before you start

An image uploaded via Prism Element can be imported to Prism Central. The reverse is not possible.

An image uploaded or imported via Prism Central is visible but not editable on Prism Element.

An image uploaded via Prism Element can only be used by the cluster to which it was uploaded.

An image downloaded via Prism Central can be used by all clusters managed by this Prism Central

Nutanix provides compatibility with images in the following formats:

  • RAW
  • VHD
  • VHDX
  • VMDK
  • VDI
  • OVA
  • ISO
  • QCOW2

Download via Prism Element

To upload an image via Prism Element, connect to the web interface using your credentials, then navigate to the “Settings > Image Configuration” menu:

Click Upload Image:

Complete the “Name”, “Image Type”, “Storage Container” fields, select the image you wish to transfer then click on “Save”:

Wait during the transfer and then while your image is processed by the cluster. Its status must be “ACTIVE” for it to be operational:

Download via Prism Central

The process for transferring an image through Prism Central is essentially identical to that of Prism Element.

Connect to the web interface then navigate to “Compute & Storage > Images” and click on “Add Image”:

Click on “Add File”, select the image you want to transfer, fill in the description then click on “Next”:

On the next screen, select the image placement mode based on your environment. In most cases, the default method “Place image directly on clusters” will do the trick, click “Next”:

Wait while the cluster transfers and processes the image.

Import images from Prism Element to Prism Central

On the image management page on Prism Central, click “Import Images”:

Then select the transfer method that suits you:

“All images” will repatriate all the images from all the clusters managed by Prism Central

“Images on a cluster” will allow you to select the cluster(s) and source image(s) on a case-by-case basis.

Official Nutanix documentation

Link to official documentation: https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v6_7:wc-image-configure-acropolis-wc-t.html

Read More

For a client file, our boss asked us during the “Thursday meeting” to find a solution to migrate the client’s infrastructure physically, from point A to point B because it has undersized internet access. not allowing a site-to-site migration. Ideas flowed, some quite good, others really crazy, we had a little time to think but it had to be easily transportable, see that it could travel by plane in the hold… Here is the genesis of the MikadoBox.

Sofa R&D (or almost)

The following Saturday, stuck in queues at Spirou Park, I received an SMS from Louis Xavier (LX for short), my CTO, probably slumped on his sofa. Having must have sensed my distress despite the distance from the amusement park, he informed me that he had found the perfect format for a system transportable in a backpack: a Lenovo M80q.

And it was there, while I was breaking down under the effect of waiting and the kids screaming with excitement around me, that I told him that we could totally take 3 and put together a complete cluster in a suitcase:

Pandora’s box was ajar, and we both rushed to open it wide to see what might come out…

Theoretical design

Now that we had this idea for a portable cluster, we had to make a shopping list to get an idea of the total weight (it had to remain transportable).

DISCLAIMER: this type of cluster is not intended to accommodate PROD. This is why we have allowed ourselves not to respect certain Nutanix prerequisites.

In terms of hardware, here is an essential prerequisite for setting up a Nutanix cluster as we imagined:

  • 3 to 4 nodes
  • 1 switch (8 or 16 ports max, 10G uplink)
  • 1 rack-mountable socket rail

As a bonus, we also wanted a 4G router so that we could start the MikadoBox from almost anywhere and have it functional and accessible remotely.

Based on this list, and the fact that we absolutely wanted something visually attractive, we had to find a system allowing us to rack up all the equipment and do a minimum of “cable management” so that it was as clean as possible.

Looking for a rackable case

On the Thomann website, I remembered seeing solutions for racking up sound equipment when I was looking for a bay for the home that wouldn’t take the place of a 42U bay. The width is the same as a computer bay but it is possible to find ones of only a few U.

On paper, it’s not bad:

  • possibility of racking 3U or more (available in several sizes)
  • accessible front and rear
  • handles for transport
  • limited space

But to travel by plane, there is no protection for splashes of water, shocks on the front/rear faces of the cluster, the material is clearly visible to those who will handle it… This is not the case. is not optimal.

The second idea was a “Flyhtcase” type suitcase.

The wheels for transport are great! On the other hand, in terms of size, many models do not fit in a car trunk, and there is generally no mounting rail…

LX then had a brilliant idea: a Gator suitcase.

This suitcase met all our criteria:

  • reasonable size
  • solidity
  • transportable
  • internal mounting rails
  • removable front/rear panel

We had our data center on wheels, all we had to do was fill it.

Racks and options

The new challenge that awaited us was to find solutions to fit all the material that we had retained in the MikadoBox.

The switch, a priori of a U height, would be, whatever the model, either full or half width with the appropriate fixings, so no problem. The 4G router would not have any mounting provided. It would be necessary to provide a shelf or a system that allows it to be positioned so that it is both accessible and fixed in the box.

For the 3 or 4 Lenovo nodes, we had to find a fixing system. While searching the internet, I came across Reddit posts that showed “homelabs” with racked Lenovo Tinys. Since I have a 3D printer, I searched around a bit and ended up finding some STL files that might have been suitable for us.

The disadvantage of 3D printing a rack intended for travel is its lack of resistance. I was very worried that it wouldn’t hold. So I continued searching and ended up finding an Austrian rack system designed for the Lenovo M80q:

Drawer-mounted (optional), rack-mountable, and the icing on the cake: there is a customizable version that would allow us to bring the connections back to the front! These racks are impeccable since they include optional rails to transform the fixed rack into a drawer.

In terms of the arrangement in the box and taking into account the quantity of material that we wish to integrate, here is what we have imagined:

The front is free once the case is opened, as is the rear which allows a flow of air through when the cluster is in operation. Once closed, the case fully protects the cluster without having to disassemble anything, you just need to put away the power cable.

Now that everything is settled from a theoretical point of view and in terms of space, all that remains is to move on to practice…

A small but strong cluster

Configuration level, the nodes are customizable within reason given their extremely small size and restricted hardware slots.

However, the cluster configuration is nothing to be ashamed of:

  • 48 Hearts
  • 256Gb RAM (CVM 20Gb each)
  • a raw storage space of 18Tb or 9Tb useful with an RF2 cluster!

So no, you won’t run an entire large infrastructure, but it can still do the job for certain use cases…

The assembly of the MikadoBox was carried out by LX, his sofa being very far from my cottage, and everything fits perfectly in the box for a weight of around 20kg!

Use cases selected

In terms of use cases, here are some examples of use of the MikadoBox:

  • POC (Nutanix / HYCU / Supervision), perfect for doing demos like at .NEXT Nutanix Paris 2023 for example
  • Crisis BCP
  • Infrastructure migration from point A to point B when network usage is not possible
  • Homelab

You will have understood, and taking into account the tests carried out, we are far from a gadget but much closer to a real cluster such as one could find in a data center.

If you would like to learn more, be sure to keep an eye on mikadolabs.com in the coming days! An article on the installation, configuration and benchmarks of the platform is currently being written.

Read More

HYCU provides a free Community Edition version of its backup solution for owners of a Nutanix Community Edition installation. Here’s how to get it and deploy it on a cluster.

What is HYCU?

HYCU is a backup software for hyperconverged IT environments. The HYCU solution provides data protection for platforms such as Nutanix, Google Cloud Platform and VMware by supporting backup, recovery and

data management for these specific environments. HYCU offers a simplified approach to data backup and recovery compared to the competition.

Here are the main key features of HYCU:

Simplified backup and recovery: HYCU simplifies the data backup and restoration process by automating recurring tasks. This helps reduce administration by teams and speeds up recovery when needed.

Integration with specific environments: HYCU is designed to integrate seamlessly with platforms such as Nutanix, VMware and Google Cloud Platform, providing a solution optimized for these environments.

Backup policy management: Setting custom backup policies based on specific business needs, such as backup frequency, data retention, etc.

Application backup: HYCU now offers to backup your SaaS applications such as Office 365, Jira, Okta, and many others.

Resource optimization: HYCU has been designed and optimized to have a minimal impact on the overall performance of the environment.

Reporting and Monitoring: The tool offers reporting and monitoring tools to track backup status, policy compliance, and overall backup system health.

Disaster Recovery: HYCU provides options for rapid and reliable recovery with the ability to quickly restore data in the event of a disaster or major outage.

Now that the introductions are done, let’s get down to business!

Setup files download

We will start by retrieving the files necessary for deploying the HYCU solution directly from the publisher’s site.

To do this, go to: https://www.hycu.com/get/trial-start

Then select “Nutanix” in the Private Cloud & Data Center category:

You will then need to complete the following form:

Select Nutanix again from the list of available environments:

Then select the type of hypervisor installed on your cluster, in our case it is obviously the Nutanix AHV hypervisor:

PLEASE NOTE: I remind you that this tutorial shows how to deploy HYCU on a Nutanix Community Edition environment for homelab use. If you wish to put this solution into production, I invite you to contact a distributor of the solution in order to obtain a quote for a license adapted to your environment.

Finally click on “download .qcow2” to start downloading the image:

Now that the file is recovered, we can move on to the installation.

Prerequisites for deployment

Before deploying, we will ensure that our Nutanix cluster is ready to receive HYCU.

For sizing the virtual machine, you will need the following resources:

Given that we are in a lab context, the smallest sizing will be largely necessary. Make sure you have these resources available on your cluster before deploying.

A service account on the Nutanix cluster with “cluster admin” rights will also be required. On the Prism Element interface, in “Settings > Local User Management”, click New User:

Then complete the form before validating, remembering to check “Cluster Admin” in the “Roles” section:

Configuring the Data Services IP is also recommended. In “Settings > Cluster Details”, fill in the ISCSI Data Services IP field with a dedicated IP address (that is not yet assigned to other hardware):

You also need internet access and an available IP address for your HYCU virtual machine.

As for specific ports and other particularities, I will leave you the pleasure of going through the documentation: https://download.hycu.com/ec/v4.8.1/help/en/HYCU_UserGuide.pdf

Deploying the HYCU virtual machine

The deployment of HYCU is very simple and is divided into 4 steps:

To upload the image previously downloaded to your cluster, on Prism Element in “Settings > Image configuration”, click on “Upload Image”:

Remplissez le formulaire en veillant impérativement à nommer l’image créée comme le .qcow2 que vous téléchargez (dans le cas présent, il faut la nommer hycu-4.8.1-274) et cliquez sur Save :

You now have to wait while the image downloads. As soon as it is finished, in the “VM” menu, in the Table display, click on “Create VM”:

Complete the form fields as follows:

In the “Disks” section, click “Add new disk”, select “Clone from Image Service” and find the previously downloaded image:

Then add a second 32Gb disk:

Finally, in the “Network Adapters (NIC)” section click on Add New NIC and select a VLAN to which to connect the VM network card:

Now click on “Save”, the VM is now created, start it then open a console on it. On the first screen, select “HYCU Backup Controller”

On the following screen, fill in the requested information:

The software then applies the configuration provided and proceeds to finalize the installation of the VM. This may take a few minutes and the system will notify you once the installation is complete.

Then enter the IP address that you entered during configuration in your browser like this: https://ip-du-serveur:8443

Log in using admin/admin credentials to access the administration console.

Votre HYCU Backup Controller est désormais déployé. Nous verrons dans un prochain article comment réaliser les configurations de base (ajout du cluster, définition d’une destination, création d’une policies…).

Read More

Do you want to improve your Linux diagnostics or kill time while waiting for your infrastructure to reboot? I have the solution !

Sad Servers

The Sad Servers site offers diverse and varied scenarios that will confront you with problems to resolve. Everything happens in the browser, no need for special software other than your usual browser.

sadservers

On the program, a “sick” server that you will have to take care of in as little time as possible. Be careful, although some scenarios may seem simple at first glance, a solid knowledge of Linux commands will greatly help you in your task.

How it works ?

Well it’s very simple, you select your scenario, you read the pitch, you start the console (allow 50 to 60s for the VM to start) and you can start to diagnose!

A help system is present if you no longer know what to do to resolve the current problem.

A perfect way to review your Linux commands and acquire/perfect your problem resolution skills.

The site: https://sadservers.com/

Read More

An SSH access is a privileged entry point for hackers. Today I am offering you a guide that will allow you to strengthen the security of your SSH accesses, to reduce the attack surface, in order to make them much more difficult to attack.

Read More