Nutanix Cloud Manager (NCM) Reviews

One goal was to automate things. We had a lot of tools, but we needed a centralized tool. Calm helps us to centralize the deployments of our VMs. 

We have a subsystem installed on Nutanix and we have blueprints for setting up this subsystem very easily. Also, for Kubernetes clusters, we use now CaaS from SUSE and we also create Kubernetes clusters with Calm. Our strategy is to make blueprints for all the virtual machines environments. It's an ongoing process.

Our first project was to create subsystems. This was really an accelerator because we have three environments and over 50 machines. Once we had a sub-template, it was very easy to migrate to Nutanix, to set up a system. Before Nutanix it took days and now it's maybe one or two hours. It's really fast when you use these templates. It creates all the preconditions for an installation. And with that, we were really able to move the system very quickly to this new platform.

The solution automates application management to a single platform, but we're still working on it. 

Our goal is the standardization which Calm makes possible. It's important, from a strategic point of view. We would ultimately like to achieve "infrastructure-as-code" so that we can always create an environment as it initially was. It would be like Kubernetes or container-based where you can destroy something and build it again and it's like it was before. When you have a platform where you can automatically create things, you are sure that nobody will manually change something in it. It's all managed with this framework, and you are sure that when when you need to create the same system it will work, because it is all scripted. The whole "cookbook" for making that machine is there. This is also a requirement: that nobody goes on a virtual machine and installs something manually. It must be scripted with Calm. That gives you insurance that you can build the same system again. For us, that's really the future: infrastructure-as-code. 

This is also a good way for creating the same machine on the cloud, or wherever you want, and to be assured it will run because the building of the machine is in the script.

Also, the solution’s support for scripts, API, and domain specific language has reduced the IT man-hours to deploy and support applications. It's hard to estimate how much time it has saved us, but I would say around 60 percent. We are new on the Nutanix platform and we have not created a lot of the blueprints ourselves. Another company helped us to accelerate that. We went into production with it last year and we see the capabilities that Calm gives us.

Before Calm, we didn't have a specific tool for orchestration. We had some templating things, but they were spread out over various technologies. Now, we have one, centralized solution to manage all the VMs that we have. This is the strength of Nutanix, that you have one starting point where you can do everything. You have all the tools in one platform. Before, we had one tool for this process and another tool for that process. It's helping us a lot.

Calm has also enabled us to react faster to the changing needs of our business. That brings me back to the subsystem I mentioned earlier. We were thinking we would need more time to migrate it, or that we might need to create a sandbox system for testing. But with the subsystem, it was very quick. Calm helped us a lot to make it happen. 

Also, when it comes to cluster systems, we work with the open source version of Couchbase. It's very easy to create a Couchbase cluster. Similarly with Jenkins, we have blueprints for DevOps. If they need a Jenkins environment, we can easily scale out for our Jenkins workers. It really makes life easier because we have a GUI and can scale out. We can say, "Okay, we need two more slaves," and it happens. It really accelerates things.

The scripting, where you can use libraries, is a valuable feature. We don't really make the blueprints, as we have a third-party company that makes them for us. But it enables calling APIs in the blueprints. When we create a machine, we use IPAM from Infoblox and we can get an IP address. It's one platform to script and we can then use all the APIs to complete the scripts. It gives us a central management tool from which we can do a lot of things automatically.

Also, it's easy to use, overall. I'm a Linux guy, so a lot of it is familiar to me. I feel comfortable when I use it. It's not really hard or complex.

And when you have applications that can run on more than one machine, you can easily use blueprints to scale out the infrastructure. You can start with two web front-ends, a web service and then you say, "Okay, I need a third one and a fourth one." This is very easy. It's one click and you can scale it, but you must also script it. It only gives you the framework to do that. So for performance, you can use Calm to scale out and scale in.

But the Nutanix platform also helps you find out if you have some performance problems or oversized machines. But to resize it, it's more that you would use playbooks in Nutanix for that, and not Calm.

It's also a very good tool for team collaboration, but in our use case we don't use Calm for that. We are not that big. We create the machines or the application; it's not that we deploy services so that another service can deploy their machines. We are still centralized, in that sense. With Calm, you can do this: With the templates, the services that need new VMs can make their own VMs, but we do not have this requirement for now. It's only used by the IT team here, which consists of 30 people.

As I mentioned, we use now CaaS from SUSE; it's SUSE's Kubernetes. But it's now changing. They have bought Rancher and I think that CaaS will be replaced by Rancher. So currently, to manage a Kubernetes cluster we have SUSE. But with Karbon we can manage Kubernetes with Calm. But I don't don't know how much we can do with Calm there. There could be room for improvement, although I'm not entirely sure. It's on our agenda to look into Karbon in relation to Calm and what we can do with them together. I don't know how deeply they are integrated. It's not necessarily something that is wrong.

Karbon is a new product. It's been around for about two years. The integration is growing. Last year is when it started working with Calm. It's more a concept still. My wish is that it will really be supported, but I cannot say for sure.

Again, I'm not saying something is wrong here. I think it's a very good platform, but there is always room of improvement.

I have been using Nutanix Calm since last year. We started in 2018 with a proof of concept to go to a hyper-converged platform, and then we chose Nutanix.

The stability of Calm is very good. We have not had problems. We are enhancing our clusters now a lot because we did a proof of concept for two years and last year we went into production. We are really happy with the platform and we are really accelerating and enhancing it.

We are a company with 700 employees. In Nutanix's world, we are not a big player. I don't think that we are ever going to push the boundaries.

We are also using Nutanix Files cluster. We are also planning to go with Era, which is a SQL management platform on Nutanix. It's really that Nutanix is providing a platform strategy for us. We are replacing all the other virtualization infrastructure that we have with Nutanix.

Nutanix technical support is great. It's very fast. In the beginning we had an issue and they were very quick. The support team from Nutanix, compared to others, is amazing. They provide help really quickly. Support is really one of Nutanix's strengths.

We had some templates in XenServer, but they were more a type of predefined image so that when you installed it helped start the machine. We also had Salt scripting, but we didn't have tools to manage them. We are not a big company. We had something like 500 virtual machines and we had templating tools and a lot of manual tasks. So things were semi-automated. We had images for certain applications, but when setting up the machine, we had to manually finish the setup.

One of the drivers for us to go to a hyper-converged system was that we had a 3PAR SAN which went out-of-support. So we had to make a decision about whether to buy a new SAN or to go with hyper-converged where you can grow with the need. And this became one of our preconditions. We wanted a system that does not use traditional SAN. We liked the idea of hyper-converged.

We bought a little machine and did a PoC to see how Nutanix works. We already knew it was a good platform because we had heard good things about it. When we tested it, it was very good and very fast and fulfilled all our needs. That made the decision for us, that it was the right platform. It became a part of our company strategy. 

It was a good decision for us because now we can also replicate the whole cluster to the big cloud providers. You can have a Nutanix environment on all the three of the big ones. That means that we can buy a Nutanix cluster on Azure or Amazon cloud, for example. Then we replicate our cluster to that cluster in the cloud, and then we can switch over. With Nutanix, we can easily deploy a virtual machine in the cloud, but then we are using the cloud provider's functionality. But now Amazon, Google, and Azure make it possible to rent a Nutanix cluster. So if we replicate, and an airplane crashes into our building, we can switch over to the cloud. For us, that was also a statement that we were really going with a good platform. In Switzerland, a lot of big companies are using Nutanix now, well-known companies that are going hyper-converged.

For me, the initial setup of Calm was straightforward. It comes with Prism Central and Prism Central is a one-click installation, and then you have Calm. It's really easy. The whole Nutanix platform is really easy to manage and to update. When you have Prism Central, you have Calm already. You must buy the license for the blueprints, but it comes with Prism Central.

If you need cluster management, if you have more than one Nutanix cluster, you need Nutanix Prism Central and with Prism Central you have Calm.

Our deployment strategy is "one-at-a-time." We touch one system and make blueprints and then we go on to the next system. We migrate machines to Nutanix without a blueprint, but the goal is that—even though we have a lot of virtual machines and use cases, and this is an ongoing process—all the new projects, as well as when we touch an old project, will go over to a Calm blueprint, to make life easier. You cannot make that shift in one day.

Our overall strategy is to have Calm as a central tool to deploy virtual machines, with a requirement that nobody manually create virtual machines. There should be a blueprint first. 

There are times when it might not make sense, if you need just one machine for a particular use. It could be more work to make the blueprint. But I think it's worth making even these little machines as a blueprint, so that you can always create this machine everywhere, including the cloud, without documentation. And that's another point. As you know, when you write documentation, as soon as you're finished it's already old because things are changing.

We are still building our infrastructure, so it's early for us to look at return on investment. But there will be a return on our investment because we are not buying another SAN. We have saved a lot of money, because the SAN system is very expensive and also requires very expensive switches. So we are definitely ahead there.

Also, we had a lot of XenServers on hosts, and going with Nutanix allowed us to reduce the number of hosts. The new system is very performant and we don't need as much hardware to get the same performance.

In addition, although it has nothing to do with Calm, Nutanix helps by giving us a good overview of what is oversized or undersized. We can look at it and see, "Oh, this machine may be underused or overused," and we can free up resources. This is also an ongoing process. We see that a lot of machines are oversized and we can make them smaller. We save resources for other machines that way. But that part is Nutanix itself, through Prism Central.

Calm comes with Prism Central but you enable features by buying the license for them. You buy by the blueprint, how many blueprints you need to manage.

We also looked at HPE. We compared Nutanix with that solution. We decided then to go for Nutanix and do a proof of concept. The HPE solution was more limited in the nodes it could handle.

We work really closely with HPE. All our servers are from HPE. So HPE proposed a solution to us, But when we compared it by doing a SWOT analysis, part of our consideration was that Nutanix is a newer platform. It empowers a lot of things. It's a different technology.

My advice is "use it." To use Calm, the precondition is that you have Nutanix. To me it doesn't make sense to have Nutanix on-premise and then not use Calm. Then you would have to use SaltStack or Chef or whatever other management software exists for managing virtual machines or physical machines. If you go with Nutanix, it makes really sense to use Calm.

SaltStack and Ansible are also good, but it doesn't make sense to use them when you have Calm. With Nutanix you have one platform where you can manage everything. Calm gives you a lot of possibilities because you can script and easily integrate and control the whole Nutanix cluster with APIs. And you can easily integrate other services because you have the ability to call Python scripts very easily.

For us, it was very easy because we didn't have a lot of existing scripts. Other companies that have a lot of Salt scripts or a lot of Ansible scripts have to recreate them in some way. So we were in a good situation.

We now have 14 blueprint templates, and still growing. We are coming from the Citrix XenServer platform. We are not automatically creating a blueprint. It's ongoing. We had a lot of virtual machines on the Xen platform, and we have moved them over, but we don't automatically have a blueprint when we do. You must create the blueprints. We do them one-by-one. When we touch a system again, we create the blueprint for it. That way we can scale out, scale in, and make test systems.

There is a template for creating a machine, and then you manage that machine with this template. But when you have machines from another platform, like the XenServer virtualization platform, you can move it over, because Nutanix is also a virtualization platform for running VMs. But then you don't automatically have a blueprint, so you have to start a new project to make these blueprints. The strategy is that we will have all the code for our infrastructure so that we can build all our system out of blueprints.

I cannot say Calm is providing centralized control of all our applications because we have some legacy systems. We have IBM iSeries, which is another technology. But with Calm we can centralize all our x86 machines.

It's still early time and there is room for improvement. I give Calm a nine out of 10. I cannot give it a 10 because other platforms are also really good. Ansible and SaltStack are also powerful. It's more an issue of strategy and the fact that it is very easy to use. It's not a complex tool. They make it easy to use. Other frameworks are more complex to use, but may also be more powerful. But for our purposes, it fits exactly what we need. We haven't been blocked from doing anything we need to do with Calm. We haven't had any showstoppers.

Compared with other tools, Calm is newer and the scope of what you can do with it is still growing. They improve things. They make it easier to handle.

70 to 90 percent of the use that we have for the solution is to get virtual machines running. We are also starting to use different aspects of Prism. For example, we just started to deploy their file storage solution. We weren't able to so far (within the last year), because there hasn't been much time to deploy projects on new technologies.

We do use the capacity planning. If we were to speak about the algorithm side of Nutanix, we use the compression algorithm for the compression that's in the storage and the storage deduplication algorithm. We find them really powerful. The capacity planning is a good algorithm, but it's a pretty simple one. It's just a projection of the expected growth of your cluster, so you can forecast if you need to buy more storage, compute, etc. 

The true power of the Nutanix algorithm lies within the storage algorithm: the deduplication, erasure coding, and compression. They are really powerful. We were actually quite surprised, because the experience we had before was only with storage arrays. Basically, when you buy a device that is purely dedicated to storage, you expect it to really perform in that area. That is pretty normal. 

When you buy a device, like Nutanix's hyper-converged solution, and it sells you on the fact that it has a really powerful algorithm for storage, you say, "Alright, it's like when you buy something that can do everything, but it's not really doing everything well. It's doing it okay." When we actually started pushing data on the Nutanix service, we saw that the compression was very good. We didn't expect it to be that good. Therefore, the algorithm for the storage side is well-thought-out and works really well.

The most valuable feature for us is the way we can use it with virtual machine to spin them. It is lightning fast compared to what we had before. The day-to-day tasks on a virtual machine are really fast. We have the economy of not having too much complexity in the menu and design of the solution, and information is accessible pretty quick. The best feature is really how simple it is to interact with virtual machines. 

The Prism features on the backup side have made it so much easier. Now, when we want to backup our VMs and do a cross data center backup, we utilize two clusters located in two data centers in Paris. For each virtual machine that is running, we have what they call a protection domain, which takes a snapshot of the VM and sends it to the other cluster. In the event of a cluster failure on one of the data centers, we can just press one button in another data center on another cluster in Prism. This will spin the VMs that have been backed up from the primary data center to the secondary one and make them run. It is a one-button recovery plan, which is pretty amazing.

There are a lot of features that could be added or, at least, made better.

There are two kinds of Prism. 

1. Prism Element: Which is what's installed on each cluster and running each cluster individually.
2. Prism Central: Which you use to connect to all your Prism Elements, meaning all the clusters. Then, it centralizes your view of your infrastructure. We have found a lot of bugs in the interface. Sometimes, when you do an action, it says to you that it's 100% done. However, in the background, the action is still ongoing, and you have no visual update on how long will it take. 

Just this morning, we took an image from Prism Central. That image was installed on one of the clusters. In Prism Central, you have one feature that enables you to place the image on multiple clusters. You just have to select them, and say, "I want my image of my virtual machine to be on all my clusters." So, when I want to spin a VM on an individual cluster, I will find the image. What is happening is that when you use the feature of image placement on Prism Central, you select the clusters on which you want to push the image, then you validate. Once you validate, it says, "Alright, the image update has been done successfully," but in the background, it's actually placing the image. Therefore, you have absolutely nothing visually that tells you whether it will finish soon or last a lot longer. You're just there, sitting and waiting for an update that you have to visually see on the interface by refreshing the interface. 

Imagine if you were to copy a file from one directory to another directory, but you have nothing to tell you whether it's ongoing or will take five minutes, ten minutes, or an hour. You just have to wait in the other directory for the file to appear and see that it's copied. This is not down to the functionality. It's down to the design of the user interface.

If you want to convert a virtual machine to an image, you have to do it via command line. Why is there not a button on the Nutanix interface that does this? 

We have been using it for almost a year.

The stability of the Prism solution is another thing that we have found to be a bit of work. For example, the Prism Central and the appliances use 97 percent of the CPU and RAM of the virtual machine. We don't know why. There is a memory leak somewhere that makes it overuse the memory. Nutanix is aware of this. It has been ongoing for a year, and they still haven't fixed it. I just don't get it.

Scaling is easy, rapid, and pretty straightforward. Now, we have two clusters consisting of 16 nodes on each cluster. If we were to extend the cluster, we would just order a new node, rack it, and image it to have the same version of the operating system off the Nutanix cluster. Adding it to the cluster is really straightforward. Then, Nutanix takes care of everything, because it's going to use the node to deduplicate blocks of storage. It's going to use the node to store VMs on the node. The automated services on Nutanix are really good.

There are mainly 20 users utilizing it, with a maximum of 30 users. We have a SysOps team, which does like Level 1 administration, who uses Prism for their day-to-day tasks, e.g. renaming the server, creating a new server, moving a server from one node to another node, or augmenting the capacity of the server to extend the disks, CPU, or RAM. There is also the SRE team, which is the engineering team, and we do the much more complex tasks. For example, when we work on the design of a new solution, we will present storage directly on the VMs. We do tasks that are a little more complicated than the other users.

I have been in touch with Nutanix support. They have been really fantastic. The only thing that is an issue is that we are in Europe, and when we open a ticket in European time, we get a response off-hours from India. If you are in Europe and you open a ticket during European business hours, you should probably get someone from Nutanix in Amsterdam who responds. Sometimes, we open a ticket up at ten o'clock in the morning and get a response on our ticket at five o'clock in the evening from India. How come it wasn't seen by the European teams first? It's a European company with a European headquarters. You have to specifically request for your tickets to be handled in your time zone for someone from Europe to contact you. 

We are the classical customer. Before, we were using a normal three-tier hosting solution, which consisted of having a stack of storage, a stack of network, and a stack of hypervisors for the compute and memory. We thought it was a burden to maintain, because every time when we had to do updates or security patches, we had three stacks to maintain. Whereas, when we switched to Prism, we benefited from its hyper-converged solution. This meant our time maintaining and keeping the solution up-to-date was divided by a great factor. That brought us to Nutanix.

We originally came from VMware. We also had some Hyper-V also, but we were originally a pure VMware customer for our virtual machines. I have used VMware for far longer than I've been in the IT industry. Nutanix was my first experience other than VMware. It is day and night for me. I would much rather use the Nutanix product line than the VMware one.

There were two factors for moving from VMware to Nutanix. 

1. We had to renew our infrastructure. It was getting a bit old, so we needed more power in order to also forecast the growth of the company. 
2. The simplicity of hyper-converged makes it a leader. For example, it's a bit like when you cook in your kitchen and have all the ingredients, then you have to assemble them and cook them. I compare Nutanix to those new machines that came out where you put all your ingredients together and you just press a button, then it cooks it for you. It is really a little bit like that. It is like everything is hyper-converged, so in one block you have your storage, compute, memory, etc. When you want to expand your cluster, e.g., if you want to add more VMs or more storage, then you just buy one block, plug it in, and link it to your cluster. That's it. You don't have anything else to do because it's all automated, where it was a burden before when we were under VMware.

This solution seems like going from a complex, cross-embedded solution to something which is a Next Generation website. The design is very intuitive; it's easy to find information in the different menus and things like that. The user experience is much better compared to other products.

In the gambling industry, you have a lot of regulation from different countries. One of those regulations states that you have to be able to send all the logs of your Prism to a separate server, what we call the syslog server. On Prism Central, this doesn't work. We have opened a case for it, since this is a basic feature nowadays. We spoke to Nutanix, and they said that it will be in future updates. We did an update, following their support, but once we did the update, it wasn't fixed. 

Nutanix suffers tiny glitches, when you put them one behind another, make the experience just a pain. However, the main features work well. There is no doubt of that.

The initial setup was straightforward: You receive the servers, you pick up the servers, and you rank them. Once you rank them, you plug them into your network. After that, you plug in your computer, you image the cluster, and deploy the appliances. It was a two-man, two-day job to deploy 32 nodes.

We did a high-level design, a low-level design, and a network design, respectively, then we opened the deployment project. It was pretty classical straightforward. Nutanix was pretty easy. The hardest part of the work was in thinking the design of what you wanted, e.g., how many nodes and clusters. We studied the capacity used by our old VMware infrastructure and forecasted the future growth of the company to integrate in how much Nutanix we were going to buy, how many nodes, and how much compute power. Deploying the actual physical hardware and cluster mechanics was easy. It was really a piece of cake.

When you deploy the cluster, make sure you set up the networking. This is really important. If you don't do it right, you will have to come back to it later, and that could be a pain.

Do the testing extensively before you go to production. We spent two days deploying and one full day just testing that the deployment was correct.

I was involved in the deployment of the clusters. I was in the data center to deploy the servers. I was there when we deployed the Prism appliance. I was involved every step of the way (from A to Z), even in the migration from VMware to Nutanix. 

The adoption rate is 90 percent. We also have some cloud and SaaS/PaaS services. Otherwise, the whole company sits on Nutanix. Right now, we have nine million users using our application and placing bets. At the highest peak, we can have a rate of thousands of logins a minute on our infrastructure. When there is big games, e.g., Champions League Games.

Imagine that we have a lot of people placing bets or surfing the website for the offer. Our infrastructure has to respond really quickly. For example, if a customer places a bet and the game finishes, we have to pay that bet quickly so the customer is able to replace a new bet for the following game, the day after, or something else. The stability of the infrastructure, its resiliency, and capacity to take in load is really important. 

Since we switched to Nutanix, we have had fewer bottlenecks and issues during the big game nights. We are using Nutanix and our infrastructure and rely on it for our business.

We have felt the ROI. We don't spend so much time on administration as we did before Nutanix. Before, it was fastidious to update all our VMware, clusters etc. We had to do that every three months. Right now, in Nutanix, it takes us half a day. It is one person who presses a button and goes onto some other business. Nutanix takes care of the update.

We're not using the Prism Pro solution; we are using Prism Ultimate. We have the highest level of license.

Be careful when you buy Nutanix. You get to choose if you're going with Dell, HPE, or Lenovo. Make sure you choose the right one for your company. The vendor is a critical step. 

Don't unlicense your Prism licensing. Pro is the strict minimum for real infrastructure. Go with at least Pro and not with the starter. Ultimate was the best choice for me. 

We did an evaluation with HyperFlex, which is the Cisco solution. It wasn't good at all. Whereas, Nutanix is sending you a hyper-converged infrastructure, and what you see is, what you get. With HyperFlex, they're selling you the same idea, but once you get is not exactly what you expect. It's blocks that you have to assemble yourself in order to make it a hyperconverged solution, while Nutanix is truly a hyper-converged solution. Nutanix gives you the appliance and server, which you just rack and off you go. 

We tried using Nutanix Calm and Karbon for the Kubernetes cluster, but we didn't find them to be as easy to use as we expected. When we heard about Calm, we almost thought that we could do automation at a level that would be similar to Puppet, Chef, or SaltStack. When we looked at the features inside, it wasn't exactly like that. Since what we have to do is pretty complex, doing it under Puppet for the orchestration and things like that, this seemed to us much easier than doing it under Calm.

I think this was because communication was off from the Nutanix side and our understanding was off from our company side. We expected it to be a product that it was not, so we haven't been able to use it. We did try to have a look into Calm, but we haven't found a use case for the product. The use case that we have in the company requires us to direct to another product, which we decided would be Puppet.

We are heading towards a DevOps culture. What will happen is that we're going to head more and more towards hybid datacenters. We might increase our usage of Nutanix.

I would rate it an eight out of 10.

I'm one of the administrators in our data centers. My title is Site Reliability Engineer, so my use case is that of a user and getting it to administer machines and monitor application performance.

The purpose for Nutanix, in general, was to reduce our footprint within our data centers, to scale down to a single point for all of our compute and storage, which it does very well. We're using Prism Pro to access all of the different clusters; we're able to get to them through one interface.

Based on information that we're able to derive from the application, we have utilized another monitoring tool, Splunk, and we're able to retrieve data on a frequent basis. We are able to find information about different VMs, or historical data regarding the process of those machines. That has been greatly beneficial for us to determine problems with our application; when machines move if there's an HA event and what those machines are; if there's a failure, what machines were involved in the problem, and where they're migrating to. It gives us a great deal of detail and it has helped improve our processes to determine where problems lie, where machines are going and what's happening with them, in near real-time. It's helped our troubleshooting process a great deal to have that information at our fingertips.

The most valuable feature for me is being able to find a machine, regardless of which cluster it's located in, as quickly as possible, and being able to work on it. A lot of times we are called upon to troubleshoot an issue. That usually means there's a problem that needs quick attention. Being able to find machines, ascertain their status, and do so in a timely manner, are processes that are very critical to our business needs.

I've used other products that are similar in nature and they can be very complex, but they have good documentation to back it up. Nutanix is no exception to that. Their documentation is quite extensive but can be challenging to read if you don't know the product firsthand. Still, it is very good at describing the features and functionality that you're looking for. But something to improve upon might be the ease of access to documentation, and helping users understand which information is going to provide the detail they need to complete their job.

The integration with Splunk is a little lacking, and this is something that we've worked on with Nutanix quite extensively in the last year or two. It didn't really have a good integration. They built some dashboards, where they were trying to kind of recreate Prism. Prism is its own utility; it works well for what it does. But it doesn't provide us quite the detail that we are looking for or the historical data that we were after. So we had to build our own custom apps for Splunk. Since doing that, we have been working with Nutanix to try and improve, to some extent, what they put out for the public. But in general, we've done some of our own customizing of our own dashboards. 

So the integration itself has not been great, but the work that we have done on our own towards Splunk has been really good. On the plus side for Nutanix is that the API calls it has that allow you to retrieve information about their product are incredible. The amount of data that you can retrieve is immense. The downside would be how to best utilize that data once you have it. That's where it's lacking, and I know that they're taking strides to improve that.

The types of data I'm referring to are CPU statistics, memory usage; when there's an HA event; where machines were located and where they're being moved to. At times, if a node fails or goes down for any reason, or there's a memory failure, it has to live-migrate those machines somewhere else. Being able to identify what those machines are, where they're going, and what impact that has to the infrastructure, is a real help to someone like me. That helps me to know what the impact is going to be to our clients and how quickly we can get the system back up to a stable and fully functional state. If we had a problem with the server, being able to look back in historical data and determine what led up to that event is another use for the data. We have roadmapping graphs that show growth in storage and CPU usage, for predicting when we need to purchase more. There's quite a lot of information there that we use to help with our job.

One thing I would really like for them to do is to correlate multiple machines together, multiple VMs, and get a bigger picture of CPU usage or memory usage. That's a real challenge in Prism Pro that we overcome utilizing Splunk. That might be something they could work on, but we found ways of utilizing the data that they provide already through REST or API calls and having access to it through a Splunk interface.

I've been wanting them to improve and mature their Prism interface. With our utilization of Splunk, I found that we tie those together pretty well. Having them revamp the entire product to try and make it better would be a real challenge.

I have been using Nutanix, in general, and subsequently Prism Pro, for the past three years.

By and large the stability of Prism Pro is very good. 

I do feel that we seem to run into a lot of problems with memory DIMMs within the Nutanix servers. Maybe they're overly cautious, but we do seem to get frequent failures for nodes that are removed for possible memory issues, or just the possibility that there could be a memory issue. If overly cautious is a downside, they're overly cautious. But if that means that our systems perform well and we don't get errors of data corruption, then it's all for the better. 

Their systems are very resilient and their uptime is very good, as they automatically live-migrate machines off to different nodes in the same cluster. They do that very well.

Having the cluster live outweighs having a single node fail, and that's the whole point of having multiple nodes. From that standpoint, the last time we had a system down because of the Nutanix was probably two years ago. And the cause was a network issue, which was something outside of their control. One cluster could not talk to another cluster and it went into a panic state and started shutting down VMs. It wasn't that Nutanix went offline. We had a network issue. They went into a protective mode to protect the data. That may be leaning towards the overly cautious, but we had zero corruption with any of our actual VMs. It did bring our application down, but everything was functional once we got the network issues worked out.

The scalability is fantastic. Anytime you need more hardware, you just throw it in and it consumes it and starts working with it. 

The only downside is the size of the clusters. As you start growing out towards 20 or more nodes, it becomes unwieldy and slows down the administrative processes. Users and administrators have to be aware that they have to scale out their clusters in addition to scaling out nodes when they have to increase capacity. That just goes along with understanding how the systems work and where their peak performance is at, and making sure that you build out correctly.

We have about 20 users of Prism Pro and they range from automation technicians to engineers to site reliability engineers, to those who actually administer the system. We have two staff for deployment and maintenance of Nutanix. Their roles are to maintain and upgrade and monitor the Nutanix infrastructure.

Our shop is 100 percent Nutanix. We do have some bare-metal servers that have functions for other applications, but all of our compute runs on Nutanix. So our use of it is rather extensive. We utilize it in all of our data centers exclusively.

Their support is second to none. Anytime you have an issue, they know what they're doing. They get the right people involved and your issues are taken care of in a very timely manner. Their support is fantastic. I hate giving people a 10 out of 10, because I think there's always room for improvement, but their support is really close to a 10. They're responsive and knowledgeable. And when they don't know the answer, they quickly get to someone who does.

Previously, we were running on Hyper-V from Microsoft. We found that it didn't suit our needs. We needed the compute, the storage, and everything under one roof, which Nutanix provides for us. Also, Nutanix's solution is more elegant than Hyper-V because you're able to bring multiple servers together into a cluster and maintain your VMs in a cluster of servers. That's as opposed to a single point of failure with one server or one array or the like.

I wasn't deeply involved with the initial setup, but I think that it was fairly simple. I do know that anytime we need to add more infrastructure, the integration with additional nodes or adding a new chassis is extremely simple and well laid-out. They excel at that.

We did work with an integrator and we had two sales engineers from Nutanix who assisted with that process. They were fantastic. Nutanix is a great team to work with.

I'm not privy to the numbers, but I think our ROI is quite high for Nutanix.

The contributing factor is, being able to have all of our infrastructure in one location. We use Nutanix not just for the software, the hypervisor, but for the entire solution. We're utilizing their chassis and their nodes. Having that all in one place, and being able to just add more hardware as we grow our infrastructure, is incredibly useful. It allows us to grow as we need and when we need. That alone allows us to dictate what drives our costs — when we need compute, how much compute we need — and allows us to stay ahead of our growing client base. 

In addition to that, their uptime allows us to have the performance and reliability that our customers demand.

It's cost-effective. It's not necessarily cheap, but it's also not inordinately expensive. It comes down to how much you use it to offset some of the costs. If you're all-in with Nutanix, and you have a lot of nodes, it drives down the cost.

I know Hyper-V was a consideration. We may have also considered VMware.

Do your homework and make sure to get some engineers involved at Nutanix who can assist you. You'll run into issues that they can help steer you around. Nutanix is willing to help if you are willing to ask. The system is not without its complexities. It has a lot of features and there are a lot of things that you can do with it. If you engage the professionals at Nutanix, they can steer you in the right direction. You should utilize them.

Prism Pro can be quite complex, if you want it to be. At its heart there are a lot of features available. If you utilize it for simple purposes, then you can get simple answers. The ease of use really depends on what level of technicality you want to have with it. But in general, the interface is well laid-out. There's a little bit of a learning curve in making sure you're going to the right location and knowing what you're trying to locate. But otherwise, I feel that the interface is well laid-out and intuitive to use.

Some other things they've done recently, like having events tied back to documentation, which is something that they are working on right now, have been great.

The biggest lesson I've learned from using the solution is that you get what you pay for. Nutanix has been a great company to work with. As I said, their support is fantastic. If you're going to use someone for your critical business needs, make sure that it's a company that's going to stand behind you and help make your job better and easier.

Our organization is utilizing Nutanix Hyperconverged Infrastructure for the majority of our infrastructure applications software, systems software, print processing software, and web application software as well as all of our core it infrastructure applicaitons and processes including alerting, monitoring, logging. Our only exceptions are currently our large data base implementations and our accounting edi batch processing solutions which are said to require ultra low latency and high performance network and storage.

Nutanix Prism Pro has improved the quality and efficiency of our organization's infrastructure team operations throughout our entire datacenter. Nutanix Prism Pro is powered by machine learning and task automation and it intelligently optimizes capacity, proactively detects performance anomalies, and enables our infrastructure team to automate operations tasks with ease and confidence, recapturing valuable time we can utilize elsewhere within our organization. Traditional Infrastructure Team Operations Management tools were built for traditional static infrastructure. These tools often overwhelm infrastructure teams with overly obnoxious alerts. In dynamic and scalable modern data centers with high performance and diverse workloads, infrastructure teams need simplicity and accuracy to achieve high productivity. Prism Pro automagically mines large volumes of system data to generate actionable insights and enables our infrastructure team to automate remediation of everyday tasks for performance management and capacity optimization.

ONE-CLICK UPGRADES! - Nutanix Prism Pro provides robust upgrading Nutanix clusters mechanism that has long been a delightful experience delivered via one-click upgrades. The one-click process hides a lot of complexity by using advanced automation and consumer-grade design experience. Historically, each cluster had to be upgraded one at a time. While the process itself was simple, this constraint still extended the length of time required to complete upgrades for multi-cluster environments.

Advance Search- Nutanix prism Pro offers to search Nutanix infra related entities as a content format. For example, it shows for VMs who is using memory equal to or greater than 10GB,VM memory =< 10GB. This is a very advanced feature that helps to get deeper details of Nutanix cluster entities.

The Life Cycle Manager tracks software and firmware versions of all entities in the cluster, integrated both on Prism Element and Prism Central.
LCM consists of a framework and a set of modules for inventory and update.
LCM supports software updates for all platforms that use Nutanix software.
LCM supports firmware updates for specific platforms.
From Prism Element, you can use LCM to update AHV, NCC, Foundation, BIOS, BMC, DATA Drives, HBA Controllers, SATADOMs, and M.2 Drives (G6 and later). From Prism Central, you can update Calm, Epsilon, Karbon, and Objects. When you run a firmware upgrade on multiple nodes, the LCM updates one node at a time to prevent any downtime in your cluster. Before the upgrade starts, all the VMs on that node are migrated to another host and the node enters maintenance mode. Always make sure that your cluster can tolerate a node failure by having the data resiliency status as “OK” in Prism Element.

LCM could be our second favorite feature right up there with One-Click Upgrades if it worked as smoothly but We have had a few issues with LCM but those appear to have been related to OEM hardware vendor not in sync with Nutanix software, not sure how this could be improved in the future.

We have been utilizing Nutanix for fifteen months.

We have found Nutanix solution to be very stable; we have never experienced any downtime with these solutions and aside from a few LCM hiccoughs we have never had any performance impacts utilizing this solution.

We have found Nutanix solution to be highly scalable; the Shared Nothing Distributed Architecture works well for our implementation.

Nutanix support has definitely been best in class there has been more than one occasion where we have contacted for support with an issue and tech/engineer has noted unrelated issues and insisted on resolving either during the session or at our earliest convenience.

Previously we utilized traditional hardware-software infrastructure solutions Nutanix is our first hyperconverged infrastructure solution.

I was not involved in the initial rollout of our first cluster sets but continued rollouts of new clusters has been straightforward.

Our implementation efforts have generally been a joint effort between vendor team and our in-house IT personnel the level of expertise has been quite good although there have been some communication breakdowns along the way.

Unfortunately I can not provide exact ROI calculations but we continue to invest in converting our traditional infrastructure to Nutanix HCI.

Unless your organizaiton is in a very limited niche don't pay the hypervisor tax it just isn't worth it.

I was not involved in the initial shortlisting of HCI vendor solutions.

Our organization has been pleased with the Nutanix HCI solution overall. The majority of our issues have been related to non-Nutanix hardware underlying the entire solutions so if We had it to do over again We would probably choose to go with Nutanix hardware.

We wanted to find a way to start getting our academics used to paying for compute without having to actually pay, but still to do it for real in the cloud. We use the self-service portal within Nutanix for them to deposit some funds, which is a cost charge, not a credit card, and then we say, "Okay, based on that, you have bought X amount of CPUs, Y amount of memory, and Z amount of storage." They can then go in and say, "Okay, well, I know I've got a pool of 10 BCPs for a month. I want to spin up three of them to process this data, which I'll then tear down afterwards."

We use it for our neurological psychology department where they do a lot of brain scans. They want to upload them to a place where they can compute the output of those scans and then they want to tear down their compute afterwards, because they don't need to be running all the time. 

Another area uses it for looking at weather data, which is typically quite a large amount of data. They only need to process once and then they can destroy it because they don't need to look at it again, once they've done analytics on it. 

Those are our typical use cases: to allow our research areas to spin up their resources against a pricing model that they've secured funding for, and not have to engage the IT teams to provide the resources for them. It also allows them not to go beyond their budgets and stay within predefined lanes.

We have it on-premise. We built our own private cloud and we host it on there for our academics to consume and spin up their own resources. We know that we could burst up to Azure, AWS, and GCP, but we don't. We keep it all within our private cloud at the moment.

It gives the end-users control of what they need. If they have requested a VM with two VCPUs but they actually need four, they have the ability to go in and do that themselves, from the same pool of resources that they've been allocated. It gives them the complete flexibility to do it themselves. If they're working remotely and they access the cluster from, say, Australia on the opposite side of the world from us, to use an extreme example, and they want to do stuff overnight, they don't have to wait for IT to wake up eight o'clock in the morning, or even later. They can do it at whatever time is relevant to them locally.

It's helped us in terms of ease of compliance and simplicity for the researchers in governing their research grants. The grants are usually very strict regarding how money can be spent, to make sure there's no waste allowed and to get the best value out of the grants. Rather than having to spend thousands on something they may only need for very small periods in a month or a year, it allows them to do more research than they could necessarily afford to do if they had to buy the hardware. It really gives them that agility. The capital that the researchers would have had to spend on hardware, to achieve this, is now all part of a central service using hardware that we've already procured.

In addition, because it does allow the end-users to look after their compute themselves, it means that they can work on things together. They don't have to put a request into IT for them to spin up the resource for them. They can dip in, spin it up, and use it straight away, so if they're actually working very closely with somebody, they don't have to wait for IT. That means the collaboration window is going to be a lot slicker. The actual activity can be done at the time it's needed, rather than having to plan way in advance or slow it down because they need some resource and they haven't got the ability to use it. The ultimate message is that they have the power in their hands, which means the collaboration becomes more fluid because they don't need to wait on IT to give them services.

Nutanix Calm's one-click self-service feature means that we don't have to look after it. The end-users can, as I said, serve themselves so they can set the blueprint and spin up some resources. They don't need to wait for IT, which means that we, in IT, can actually focus on adding value by making sure that the clusters are healthy and by looking to help them with some of their requirements. IT doesn't have to be the "organ grinder" and turn that key to keep giving them resources that they need. Because they have that basic control, we can provide them more value.

It allows the research to happen a lot faster, for the researchers to do the work that they need to do and then tear it down. It certainly does support a much faster turnaround time. Typically, in the past, we would allocate up to a week to provide them with a complete resource, depending on what the requirements were and if we had them available or not. With this, it allows them to do it themselves within a matter of minutes. The speed at which they can do research is now a lot greater.

The solution has enabled us to react faster to the changing needs of the organization, absolutely. That's the main incentive.

One of the valuable features for us is the ability for people to reserve some resources and then use them as and when they need them, rather than us having to give them those resources as they request them. It's very much aligned things to a cloud mindset before letting them loose with an actual credit card.

The fact that these are non-technical people — they're experts in their fields but they're definitely not technical — and they can just log in to the portal and select the resource that they believe they need, and manage it themselves, speaks to the ease of use. It shows them their live costs, etc., as they're spending. The fact that they can do that without any problems, or having to engage the IT teams, is a true testament to it. There's no need for any user training at all. It wasn't overly easy back in the early days of Calm to use it. It was a bit "hacky" in terms of the way you had to build the blueprints, but now it's a lot easier to use. It's a very "light touch" IT solution for an IT service that we provide.

Even though it's a lot easier, it could be a bit slicker for the end-users. The ability to create their own blueprints could be without their having to understand the details of what they're trying to do. If they could just tick this, this, this, and this — whatever they need — and it would go spinning those up, that would be better. Now, we still guide them quite a bit.

I've been using Nutanix Calm for about two years now.

We haven't had any problems. In two years it's never gone down. Every time we patch it, it patches seamlessly. We've never had any problems with it and we've never had to do anything to try to resolve any problems.

Because it's all based at Nutanix, it's really easy to scale it out. We have increased our capacity on our platform a number of times, and it seamlessly rebalances the clusters as it needs to.

It's purely our researchers who are using it. We don't use it ourselves, as an IT department. We have capacity for 100 active VMs at any time and there are about 300 academics in the department who have access to use it.

We haven't used Nutanix technical support for this solution. We have used it for other products, but Calm looks after itself. We have not had any problems with it at all.

We didn't have a previous product. We would do it ourselves, which was part of the challenge for us because we couldn't deliver at the speed at which they wanted us to deliver. The researchers were going off and trying to do it themselves within public cloud, and therefore spending and wasting a lot of money which they could have spent in better ways.

We moved to Calm to make it more efficient for the academics. It would give them a bit more power and control, and ultimately we want to be a lot more cloud-orientated. To achieve that, there needs to be a degree of governance. If they are used to that governance in how they operate, then migrating them to a public cloud piece should be easier. They will  be used to being sensible with when their resources are turned on or not.

Everything is very straightforward to set up. It's as few clicks as possible, which works very nicely.

Our deployment was done within about a day. That was two years so it would be hard to put a more specific time on it. It was also a very different product then, as compared to now.

In terms of an implementation strategy, we essentially got the solution because we wanted to help some of the areas that were complaining about our speed of delivery. We only really offered it to those areas. But we've now gone full circle and just committed to some more Calm licenses to grow our capability because of the speed of delivery it gives to our researchers. That's especially true with their being remote. They can then do it all themselves and don't have to engage with IT to help them spin things up. In the past, they just knocked on the door and got some support from the computing team. With people working remotely now, that's obviously a lot harder. It allows us to achieve remote work.

As for maintenance, It's part of the wider stack. When there's an update, we will roll that out. But it's all pretty much one click and away you go. You come back a little bit later and it's done.

We did it ourselves, based on the guidance that they provided to us.

We have absolutely seen ROI. It doesn't cost us very much and it makes our academic flows a lot easier and we don't get complaints anymore about not being responsive to their needs.

I can't really comment on pricing because, being in the public sector, we get different pricing to what is out there in the world.

But in terms of approach, size it on what your minimum would need to be and then add additional licensing as you need it, rather than trying to go too big, too quickly. The whole point of Nutanix software is that you can grow and size the estate, rather than going instantly to a monolithic solution from day one.

We didn't look at other solutions. We already had Nutanix to provide some research compute for other things, so we went with Calm in addition to the suite that we had at the time.

The biggest lesson I've learned using this solution is how easy it is to empower users to achieve what they need to achieve. Without this, it would be very hard to build the trust up and allow our academics to do what they need to do.

In our case, Calm doesn't help us to implement standardization across our organization because the research is usually quite specific. The types of VMs that they would spin up would all be slightly different. Some might have much bigger storage requirements, some might have higher RAM requirements, and some might need to be quite low compute but for longer periods. It does tend to vary quite a lot. But on the flip side, it allows them to all work the same way so they're not going off and burning money in public cloud environments.

When we first got it, it probably would have been a five out of 10 because it wasn't the easiest to build the initial blueprints. Now, we're certainly up to an eight. There's always room for improvement with something like this.

Prism Pro lets us manage multiple Nutanix Clusters through a single interface. I can view all the alerts or health of each Cluster from one website instead of going to each one individually. 

When I started with the company, we did not have Nutanix. Within the first six months, we installed Nutanix software and Prism Pro. In the very beginning of the first six months, I was working a lot of overtime, having to fix a lot of things. I don't have a lot of overtime anymore. I don't have the nights and weekends that I used to because of all the time savings the solution has given me.

We use the solution’s machine learning algorithms for things like predictive capacity planning or other functions. This shows us what our capacity is, where it's going, and what trend it has been on. Thus, we can decide whether we need to purchase it next year.

The Pro license gives us Capacity Behavior Analytics. This feature lets you see what your capacity is and what you're using in your Cluster. It predicts what it's going to look like in a few months. You can forecast if you need more infrastructure. It sees how much your environment's growing and helps with the sizing of VMs to meet your workload growth.

The 1-Click Centralized Upgrades are really nice. When you go in and want to upgrade your Cluster, you just click a button and everything will upgrade. You don't have to go to each individual server to do the upgrades.

These features save time. They give us insight into what our data is doing and what we need to do to ensure it's running properly.

It is very intuitive and easy to use. It just makes sense. You don't have to look around for a lot of things. The things that you will be using are just there. Everything is on one screen. You can click through to go where you want to go, but there are not a million buttons that you have to figure out (where to go for what).

We use the solution’s X-Play automation feature. The anomaly detection is nice, as it give us insight into things that are anomalies. We can then take corrective actions on them. Its codeless approach to automation is good because I don't like to code. It's point and click, which is nice. It sets up your automation without having to do any coding. 

X-Play has a page that provide us with a single tool for monitoring automation. This page is where I go if I need to set up automation or check if something needs to be done.

Pricing could be worked on a bit. I feel that when I talk to people about it who have looked into Nutanix, they say, "Well, it's pretty expensive compared to the other thing I was looking at." I tell them it's worth it. 

I would also recommend getting the word out. I still talk to a lot of people about the solution in the industry. They are not aware of it, and say, "What is that?"

About five years.

The stability is great. I haven't had it go down on me, so I haven't really had any issues with Prism Pro. We've had some hardware issues, but the way that Nutanix has their software setup, it doesn't have downtime to the end user and the VMs don't go down. Everything just keeps working.

I do the deployment and maintenance for this solution.

We have been adding a server per year. We have gotten to the point where we will be taking out a server and adding a server, so we're in the sweet spot right now. It's been great. It's not like other solutions where you buy it all upfront, then by the time you need more, you have to replace the whole thing. With this solution, I can easily just add some capacity or CPU by adding another node.

We have 150 VMs across four Clusters with 18 nodes. We are utilizing the solution at 100 percent. 

We are not a huge company so we probably have two users: a system administrator (me) and my networking guy. The help desk doesn't even need to get in it, so they don't use it.

It is the best support that I have ever dealt with. They're knowledgeable and have always been great, easy, and accommodating to work with, e.g., in the first couple of months of deploying Nutanix, we had an issue with certain nodes that were rebooting automatically. Nothing went down, but it was concerning. Within a week of having the problem, we had a dedicated support person who worked with us for about a month and a half while they found the bug and developed a new patch for it. We tested it for them, then once it was working, everything was good. About a month later, the head of the support team down in North Carolina came out to visit us just to make sure everything was okay. 

We had IBM and Dell EMC storage before, but both of them have their own interfaces, so there were two or three things that I had to look at. With this solution, since we have Nutanix, it's just one. That makes it a lot easier.

At my previous job, I used Cisco UCS and NetApp storage.

The initial setup was very easy. You just click a button, and it will set up your Prism Pro VM that runs. Installing the Nutanix platform from the beginning was amazingly easy. At my old job, we just installed new hardware, and that took about a month. Nutanix took four hours, so it was a huge difference.

We talked the implementation over with the vendor when we were ordering. A couple guys came onsite to help us. It was very simple. The Nutanix guys were great. Any little problem that we would run into was fixed in a minute, then we just rolled through it. That's why the implementation was so quick. 

We have seen ROI with Nutanix. We have more reliability than what we had before. We used to have outages all the time where I would be working overtime, and that costs money.

Some people say that Nutanix is a bit more expensive. However, when we were looking at Nutanix versus Cisco and NetApp before deploying this solution, the prices were very similar. Being a government entity, we got a bit more of a discount on Nutanix so it was a bit cheaper. The time savings after the fact has been really worth it.

Prism Pro is a license that we have on all of our products for Nutanix. It gives us a bunch of different new features.

Prism Pro is a bit more upfront. It costs a bit more for some of the features that you get. We have four Clusters, and two of them don't have Prism Pro because they weren't even available with what we bought. Those two Clusters also run well, but they don't have all the features.

When I started, we were looking at Nutanix, but also at NetApp and Cisco, which is what I had just come from and done a new installation. I was pushing for that. However, when I saw the presentation from Nutanix, I was like, "Well, this is how it just should work. Let's give it a try." It's not easy running the whole thing by myself in a normal situation, but with Nutanix, it lets me do that because I don't have to worry about all the little bits and pieces. It's just one interface which is easy to manage.

From my previous experience, I worked with Cisco and NetApp, where Cisco was the servers and NetApp was the storage. I transitioned into just doing storage and did storage all day, every day at my old job. I moved things around trying to make space for this, that, or someone wanting to put something where we didn't have space. I would have to move all types of stuff. It was a big pain. When I came to my new job, and we started Nutanix, you don't have to do any of that. There isn't anything I almost ever do with storage unless I'm adding a new node. It's all shared in one giant pool of storage. This saves so much time. It's like, "Why was the other company doing it that way?" It doesn't make any sense and was a pain.

You have to at least look at this solution. Once you do, you will buy it. All my old colleagues that have moved onto different jobs too, and I always tell them about it.

They are always expanding what they have and what they are offering.

It can do a bunch of other things that we don't use yet, but are thinking about.

Biggest lesson learnt: IT doesn't have to be super complicated.

I would rate Prism Pro as a 10 (out of 10).

We consider it our "private cloud," and all of our workloads are deployed on it. Through our application, we offer secure cloud storage. Most of our customers are law firms or financial institutions and they really care about the security of their documents and they really care about document workflow. Because of that, we have to abide by government rules and regulations. For example, if you're a German law firm, you don't want to store your documents in Australia, you want to keep them in the European Union. 

Our product is set up in multiple regions, so we've deployed the solution, on-premises, in each region. We have an instance in the U.S. to service U.S. customers. We have an instance in the United Kingdom to service customers there, and We have one in Germany to take care of the European Union. We also have one in Australia, where we take care of Australia and the Asia Pacific region. In each of those regions, we have data centers that we lease space from. In each region, it's a centralized solution. Our entire application that the end-user interfaces with runs on top of Nutanix.

Nutanix Cloud Manager has allowed us to scale really quickly. For example, during the COVID pandemic, everyone was working from home and a lot of people started buying our product because it allows them to work from home. We grew really quickly and we were able to scale our infrastructure really quickly because Nutanix has invested a lot of time into that.

The most valuable feature is the ability to automate. Nutanix has made it really easy to automate everything that we do. That's important to me and our organization. We can get more done every day by automating tasks.

It's hard to think of anything that needs to be improved. One issue, though, is that you can set up DHCP but it's a little bit clunky. I wish they would streamline and centralize the management of DHCP.

I have been using this Nutanix solution for about nine years. We have been using the Nutanix Cloud Manager version for the past several months. 

NCM is super stable. We're very happy because that translates into our uptime which is pretty great. Our customers are happy with how available our application is.

It's very scalable and we're very happy with how we've seen it scale. We don't have any concerns about that.

The technical support is amazing. Nutanix invests a lot of time and money into making sure that their technical support is top-notch.

Recently they have implemented a series of solutions that make it very proactive. They analyze our environment, including the version of their software that we're running and the hardware. They analyze every little detail. If they detect an issue, they let you know. They're using artificial intelligence to aggregate all the data and to parse through it. As a result they say, "Hey, you have an issue in your environment," and then they tell you how to explain it. 

The second way that they're very proactive is, under certain circumstances, they'll automatically open a support case and automatically collect the logs from your environment. So if something happens in the middle of the night, before it becomes a problem, they'll open a case with support and collect the logs. When I wake up, someone from Nutanix has already been assigned to the case and they've already reviewed the logs, and they'll generally have a good solution.

And one of my favorite things about Nutanix support is that they're very willing to teach you. When I'm working with them I'll ask them a lot of questions about what they're doing or about the situation. They're more than happy to explain it all and to teach me so I can understand the situation better and become better at my job.

Positive

We used to use Microsoft Hyper-V, which is good, but it's difficult to manage and it's difficult to scale.

The solution was purchased before I came to the company, but when I arrived I realized that it hadn't been implemented in the best way. I spent a couple of years fixing the architecture so that it would follow best practices. They had inadvertently painted themselves into a corner and I took away the paintbrush and the paint and fixed things so that it would work and scale better, going forward.

The initial deployment was pretty straightforward, but the people involved just didn't have experience with Nutanix at scale. They didn't necessarily do it wrong, they just didn't do it with the end goal in mind. They had tunnel vision in which they said, "We have a task that needs to be performed and we have to get it done as quickly as possible." It was a very task-oriented implementation. What I was able to do, with my experience, was take a step back and say, "Let's look at the big picture. Where are we going to be in five years?" I was able to architect a solution that would make sure that we could get where we needed to be in five years and in 10 years.

We make sure that we follow best practices from Nutanix. When deploying the product, we make sure that our cluster size—how many physical Nutanix servers we purchase and group together—follows best practices. We make sure that we plan for the ability to perform an upgrade in the environment and we plan for potential hardware failures. We've also started purchasing specialized configurations to match our workload. All of these things are a part of how we architect and deploy the environment.

We have about 250 Nutanix servers around the world. Our application consists of four or five independent offerings and those 250 nodes are spread across those four or five offerings. There are three of us who manage the environment. I'm the architect who created and implemented the solution. I also ensure that we have enough capacity to continue to grow and to take on new projects. Another member of our team does a lot of the project work: Here are the tasks that we've been assigned. How do we get from point A to point B? And the third member of our team focuses on upgrades and hardware break-fix.

We've absolutely seen a return on our investment. One way is through our uptime—how much of the day, week, month, and year our application is running. Because Nutanix is scalable and it's distributed, we're able to easily perform upgrades and keep our application running. Because of the design and implementation, we've been able to make sure that we're always running the latest version of the software, which means that we have all the latest bug fixes and security fixes. In uptime, upgrades, and security fixes, we've seen a huge return on investment. 

I've worked at my current company for four years and our business has just exploded. A lot of that increased business is due to the fact that our Nutanix environment is so stable. It's very reliable and predictable for our customers, and that translates into a better user experience. As a result, another way that we've seen a return on investment is in increased sales.

We use so much of Nutanix that we decided to do a long-term licensing agreement with them. That saved us a lot of money, but it was a difficult journey to understand what we were purchasing and to convince finance and upper management that it was something we should do. Nutanix has taken our feedback and they've worked on streamlining it and making it easier to understand and communicate to non-technical people.

We looked at all the players in the market. We interviewed them and looked at their features and we felt that Nutanix had the best offering.

Nutanix's main competitor is VMware vSAN. Nutanix built their product from the ground up, and because of that, they were able to do some really innovative things to make sure that scaling and automation are taken care of. VMware wedged vSAN into its existing offerings and, because of that, it's really clunky, difficult to set up, and it doesn't perform as well.

When we first started evaluating Nutanix, our upper management had a hard time understanding what it was and what it would do for us. It's different from a lot of traditional solutions and you have to approach it differently.

As you understand that this is the next generation of infrastructure—that it's the next generation of virtualization, the next generation of private cloud—it's a little bit easier to say, "This is going to be different. This is going to be challenging in some ways, but as far as security and compliance go, and as far as performing upgrades goes, nothing could be easier. And when it comes to getting support, they have your back. Nutanix is a company that cares about your experience and your thoughts and improving things. I've never met a company that does a better job. It is different, but it's way better than what I've used in the past.

Nutanix has invested a lot of time and money to make it a really good and solid application, but there's always a little bit of room for improvement.

The solution is a management portal for the entire solution. You can have a look at your configuration and do different kinds of configuration monitoring management. You have the infrastructure implementation workflows on top of it, so that's the portal that will manage these underlining nodes.

It's a stable solution.

The solution scales well.

Technical support is helpful.

It's easy to set up.

Licensing could be more flexible in future releases.

We've used the solution for two years. 

It's a stable solution. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

The solution can scale as needed.

I can't speak to how many people are using the product right now.

Technical support is great. They helped during the setup and were excellent. 

The solution is very straightforward. The deployment took about five to six days. It took about a week's time.

Anyone who is comfortable with any virtual edition of a solution with five to six years of experience will be able to manage it. I can manage the entire solution myself.

The solution is easy to self-deploy. During the initial setup, we worked directly with technical support, and they were quite helpful.

I'd like them to offer a more flexible licensing model.

I'm not sure which version of the solution we're using.

I would recommend the solution to others. Overall, I would rate it nine out of ten. We've been very happy with it. I'd advise potential users should first run a POC and then go for it.