Nutanix Cloud Manager (NCM) Reviews

We use Nutanix Cloud Manager to consolidate and manage our Azure and AWS platforms, as well as our VMware server virtualization process.

We looked for a cost and security governance solution that is self-service and does not require any coding. Nutanix Cloud Manager is that solution.

RunBook has had a positive impact on reducing manual intervention, which has been very helpful. We looked for a solution that offered a single pane of glass, ease of use, and self-service orchestration without requiring a lot of coding. I think this really helps users get the policies in place so they don't have to worry. We just need to put in the initial effort, and then we can be hands-off.

The speed of outcomes we received using NCM's low code automation is good. We implemented separate network segmentation for all functions, including our DCS, corporate, and team control.

Our organization values speed and efficiency. We want to be able to upgrade our systems and processes quickly and safely, and we need to ensure that our IT and cloud applications always run smoothly. To do this, we need to have a good understanding of the costs and risks associated with these upgrades, as well as the ability to forecast and manage incidents. We also need to make sure that our systems are compliant with all security regulations, and that our employees have the ability to self-service their IT needs.

As a senior project manager, I am responsible for monthly budgeting and forecasting. The main aspect of this is cost, but proper forecasting is also essential to keep our company running smoothly. We have a policy of accepting variances of up to ten percent, so it is important to have a good management tool that can accurately predict costs. That is why we evaluated different management tools and ultimately chose NCM. NCM helped us to improve our forecasting accuracy, which saved us money and allowed us to better manage our resources.

It is important for NCM to be able to manage both Nutanix and VMware infrastructures because it provides a single pane of glass for management. This simplifies management and reporting.

Our IT team can focus on other tasks thanks to the playbooks. Once we set up the runbooks, we can relax until there is an additional instance of configuration on AWS or Azure.

NCM saved our organization approximately 50 percent of our employees' daily time. This is due to two reasons: One, we no longer need to worry about topologies and self-service orchestration setup, as NCM handles these tasks for us. Two, NCM provides a single pane of glass for all of our data, so we no longer have to spend time searching for different dashboards. This saves time on reporting as well, as we can now find all of the information we need in one place.

We have a multi-cloud and multi-virtualization environment. In this environment, we have many instances running on different platforms, including on-premises and cloud-based platforms. To ensure accuracy, we need a tool that can provide us with ease of use on a daily basis. A single pane of glass, such as NCM, helps us address our automation needs.

Nutanix Cloud Manager's most valuable feature is its self-service capabilities. We have a large VMware footprint, and we are slowly and gradually moving to Azure and AWS. The self-service capabilities allow us to orchestrate our deployments without writing code, and they also use artificial intelligence to improve our security posture. This is a major benefit for us, as security is our top priority.

NCM's pricing structure is confusing and difficult to understand. The company frequently changes its prices, and it is not clear how the subscription-based model works. This could be improved by making the pricing structure more transparent and easier to understand.

I have been using Nutanix Cloud Manager for just over one year.

The technical support is good. When I called, I was able to speak to a real person, not a robot. My problems were resolved quickly, within hours, not days. I am very satisfied with the support I received.

Positive

We previously used Azure Cost Management, but we switched to Nutanix Cloud Manager because it provides visibility into Nutanix, VMware, Azure, and AWS on a single dashboard. Azure Cost Management only supports Microsoft products.

We evaluated Morpheus, Azure Cost Management, Nutanix Cloud Manager, and AWS Cost Management. Our company policy is to evaluate multiple options before reaching a decision.

I give Nutanix Cloud Manager an eight out of ten.

We mainly use it for infrastructure as a service. We use it for managing the clusters and hardware and running the VLCM updates. We do not use it to manage files and all the embedded because we have other solutions corporate-wide for it. It is pretty much being used to manage the infrastructure of the clusters and make sure that we have all the licenses applied to all the different clusters around the world.

We are multinational. I have clusters right now but not on all 53 plants. We have some Acronis data centers. They are called Co Lo data centers. We have a couple of those data centers with Nutanix in them. We have one in Tokyo, one in Ashburn, and then we have a couple of data centers in Mexico with Nutanix. We also have some in the US, some in Portugal where I am from, Italy, Germany, Asia, China, and Japan. We are around the world, and we use Prism to manage all those data centers.

Centralization is the main benefit. We are a company that is growing a lot due to acquisitions. Each of the companies we acquire does not use all of the same hardware or solutions. The mission of my team is to design and deploy solutions for all the new companies around the world and make sure they adopt our solutions. This is good to showcase to them what we have and make them see that they can manage their own side of the world. They can get granularity there and be able to support all their business locally. We still can have a backup team, which is my team, supporting them in case there are issues. There is always someone looking at it if something goes wrong. 

We do not have to be alerted by an outage. We can work on an issue before it happens or as it happens. Sometimes, when people get up, the issue is already fixed because we can do all that remotely. NCM allows that.

Nutanix Cloud Manager has saved our IT time. We got our weekends back. Previously, having a different type of infrastructure with Cisco UCS and VMware, updating the Cisco component, the EMC storage, and downloading everything sometimes was a week's worth of work. We had to do upgrades on weekends because we could not do it online. Since we started using NCM and LCM out of NCM, we went from one-day upgrades to one hour. Earlier, we were running it for a one-year period, and now we are running it every month and that is a complete cluster upgrade. There is no downtime and no business complaints. We just warn them that we are doing this. We have total confidence and total trust that it is not going to be an issue.

In terms of ease of use, I use a lot of hypervisors, and there is nothing that can be compared to it, whether it is VMware, Hyper-V, or even Azure. The Azure portal does not have a one-click to update everything. If you look at the on-prem things, I have Cisco UCS, Lenovo, and IBM servers that I use in VMware. There was no single panel where I could manage all that together. There were always different things to manage. You needed knowledge and training. Nowadays, a new hire can come in, and I can tell them to run this every week. They will be able to do it without training.

It frees up the staff that I have from having to deal with heavy troubleshooting. It is one less worry for me. We have 53 plants operating 24/7. We have problems on a daily basis. We have attacks. It is a huge asset not having the burden of dealing with upgrades because if we do not do those, we are open to vulnerabilities. With NCM, we can focus on everything else. Worrying about updates is a thing of the past. Anybody on the team can go ahead and take a look.

The single pane of glass is valuable. Seeing all my clusters there and getting all the alerts in one place helps to manage our global infrastructure. To me, the ability to view or see everything in one single place is very valuable.

We are also able to do lifecycle management and run updates. We have got our weekend back. That is very important. IT guys never have weekends. With Nutanix Cloud Manager, we are able to run updates during normal business hours. We are able to do it with the click of a button. Not having to worry and not having to see how it is running on the other side of the world makes a huge difference.

We have clusters not only with HPE. We have some with VMware to use Cisco Call Manager for VoIP. That only runs on VMware. They upgrade the ESXi host but not vCenter, which manages the ESXi host. It would be great if there is a way to include vCenter on the VM because you run the updates, but you do not update vCenter. It complains that you still have not updated it.

We started using the first version when it was called Prism in 2018. 

The technical support from Nutanix is excellent. It is not always the same experience. It differs. Sometimes you get someone who is very experienced on a given module or hardware. It depends on who you get, but even if you do not get the fastest guy at the first call, you will get it once the escalation happens. We have not had a case where the issue was not completely solved with a definite solution. I am very happy with Nutanix's support. 

We work with a lot of brands, and it is not always like that. Even with Microsoft, when we open a ticket, the first person is going to tell me to try things that my team has already tried before. We have to tell them that this is not the first rodeo that we are at. We have done this. We need to go beyond that, but they still have to do their due diligence. They do not care about that. They still want to run their script till they get to it. Nutanix is different. We tell them what we have done. They know we are certified. They take that into consideration and go to the next step, which is troubleshooting.

I would rate them a ten out of ten. They are by far the ones we like to work with.

Positive

The price depends. I struggle a lot with that because I manage a budget. Not all businesses have the ability to spend that amount of money. When I have a plant that needs 10 VMs running, the smallest cluster I can offer them for high availability is a three-node cluster. It is going to cost me a hundred thousand dollars, whereas I could get a Dell box with 6K Windows Standard installed on it and get Hyper-V running and a couple of VMs, but there is no high availability. We had plants that were running like that because they did not want to spend the money. We had a ransomware attack. In the case of sites with Nutanix, we were up in a week, whereas in the case of the sites with that kind of hardware, we were up three weeks later. They then understood the importance of having proper hardware that can support resiliency and high availability.

It is expensive when you are looking at small locations that need low-latency workloads, but for larger locations, as compared to other guys, even using VMware, it is not that expensive because if you add it all up, it is going to be pretty much the same value. You just need to look at a similar size solution to be able to make a comparison.

We do not use low-code automation. We support manufacturing plants. We do not have to deploy and stop VMs. We use Red Hat OpenShift for some containerized stuff but not a lot. We have some websites for looking for products. We do not have any need to build VMs and destroy them and build them again. It is pretty much what we do on our Azure footprint. We have 400 VMs there. We do not have automation there. We never build templates. We build one or two VMs per month when we get requests. My team builds those VMs even for our developers so that we have cost and check. We do not need to use automation at this point. We appreciate the automation of life cycle management and all those rapid tests that we have to make, but that is the standard automation we use.

I do use playbooks out of Azure but not out of Nutanix.

I would rate Nutanix Cloud Manager a ten out of ten. I have no issues with bad-mouthing it or praising it. In this case, praise is due for sure.

We work in the public sector, which includes local governments, fire departments, and transportation. The most interesting use case is that we have set up a private cloud with two sites where they are replicated, and from the same console, we have synchronous replication using 1M Ethernet. The RPO is zero.

Our clients like its simplicity. That is a great value. We moved from a three-layer infrastructure to a private cloud infrastructure. It has resulted in a lot of simplicity which is reflected in the availability of services.

Simplicity is the biggest value that we can see. This is super important for us because the technical team is dedicated to looking at the data and how to generate value for the business instead of worrying about the technology.

Using the built-in playbooks has freed up the time for our IT team. Instead of managing storage, CPU, and memory, they can dedicate their time to thinking about the needs of the business and attending to those needs. We have had clients who reduced their operations time by 60% to 70%.

Nutanix Cloud Manager helps your team a lot to address your current automation needs while planning for future expansion. You have a forecast of how your infrastructure is being used. This allows you to have visibility of what actions you should take to avoid reaching day zero. It helps you a lot.

Its installation is relatively simple. The administration is very intuitive. You have an HTML 5 interface that you can use on any device. I have clients who manage their infrastructure from their smartphones, no matter where they are. Its being very intuitive has helped us to deliver 4-hour workshops. We had an interesting case in the sector of transportation in Quito, Ecuador. A person who provided support and was with the help desk went on to manage the data center with just a 4-hour training. He went from being help desk support to being the data center manager, all with Nutanix. That easily gives an idea about its learning curve.

Nutanix Cloud Manager’s setup, learning curve, and ease of use were definitely important when deciding on a cloud management solution. In fact, we have been growing in infrastructure, and it has been maintained precisely due to the ease of use and small learning curve. It frees up time from the daily issues of looking at technology. The customers are happy and continue to grow.

Simplicity is most valuable because, with a single click, we have visibility of the entire infrastructure. We can focus more on the availability of services instead of being aware of the CPU, memory, or hard drives. With one click, we can see the availability of our services.

The interoperability with different clouds can be better so that one can even integrate the infrastructure of different clouds. They can interoperate better with other clouds because currently, you have to buy Nutanix resources in the cloud.

It has been four years as partners and service providers for our clients.

Its stability is very good. We did not have any issues for which we had to stop our services.

It is a very important aspect of Nutanix solutions.

It is efficient and fast. It is in Spanish, which is an advantage. There is always the option for technical support in Spanish.

Positive

In Ecuador, Nutanix began to introduce itself in 2016 in such a way that the customers moved from traditional infrastructures to Nutanix right away.

We have both kinds of deployments. We have clients who have private clouds, and then we have clients who have hybrid clouds. Our clients use Amazon Web Services and Microsoft Azure.

As a company, we do the implementations autonomously. It is simple. I do not personally do it. Our technical team does it. We can do the deployment or migration of about 15 to 20 virtual machines in four hours, so investing about four hours to move an entire legacy data center solution to a Nutanix Infrastructure is more than fine. 

We have an implementation strategy. We follow the best practices. We have a trained technical team, and they follow the objectives.

If you compare it with a traditional model or with a native cloud, then definitely the best alternative is to make an investment in Nutanix solutions. The return on investment varies depending on what you compare it with. In Ecuador, in the public sector, they force them to buy a three-year licensed solution. So, if you compare it to three years with traditional or cloud-native infrastructure, the Nutanix solution is definitely a winner.

For Ecuador, this is a sensitive issue. It is a small economy, so the issue of budget is very sensitive. You find many small businesses and government clients who do not renew, for example, support or guarantees, which raises the risk level for them. We are always advising them that it is necessary to renew the services or infrastructure.

We evaluated many solutions before switching to Nutanix Cloud Manager. However, once the customers get to know Nutanix, they always prefer to stay with the solution.

Our customers choose Nutanix for the experience. Our customers have stayed with Nutanix because they did feel a change before and after. Before Nutanix, managing storage required time and working on weekends outside of business hours. Having to shut down the services to make firmware updates of different components of the data center was an issue. Now they can do this during business hours without the risk of services being unavailable.

Overall, I would rate Nutanix Cloud Manager a ten out of ten.

We started migrating from VMware to Nutanix four years ago, and we're seeing much better performance.

We had a difficult disaster recovery situation that we handled with Nutanix Cloud Manager. We also migrated licenses from on-premises in a local environment to the cloud, which is much cheaper.

Nutanix Cloud Manager is easier for technicians than VMware, so fewer people are needed to do the same tasks. It's critical because if we do things faster, we do them at a lower price, especially if we use fewer human resources. 

NCM’s built-in playbooks have freed our IT team to focus on other tasks in some areas, but we also have our own local playbooks. This has freed up time for our IT team. Since 2023, we have spent an average of six hours completing an implementation, which allows us to use our IT staff more effectively for other tasks.

The learning curve has been smooth, and the technicians are performing a little better regarding response times. The only thing that makes a little difference is the virtualization part, which I believe is compensated by the performance part. A short learning curve is important because the infrastructure team is a bit large, so doing things with less time is better. If we take longer, then it will be more expensive.

We are still learning about cloud usage and the integrations we are targeting right now at the event. I believe there is room for improvement, especially with the prices, which are not very friendly.

I have used Nutanix Cloud Manager for four years.

We haven't experienced any downtime. 

It's easy to scale Nutanix Cloud Manager for the cloud and local services.

I rate Nutanix support nine out of 10. We are happy with the customer service.

Positive

We used VMware previously. It's okay. We made the switch four years ago when we purchased another company that was already using Nutanix. From that moment, we started working with Nutanix, which we didn't know about before.

Deploying Nutanix was a smooth experience. The technicians were fluid, and the deployment had no major problems. 

We used the help of EDVAL, an integrator company. I liked working with them

Due to the migration, we are at around 9 percent. We are now talking with them because we have VMware things we are going to migrate to Nutanix. There is a migration and expulsion plan, there is an optimal communication process with them. We are talking to salespeople about reaching around 15 percent or 20 percent reduction thanks to Nutanix's approach and scaling nature.

I rate Nutanix Cloud Manager eight out of 10. I wouldn’t give it a 10 because of the price.

We completely migrated all of our data centers from VMware to Nutanix. We were running a hyper-converged infrastructure based on HPE systems. We chose the full Nutanix stack because of the level of performance and the availability. There was the robustness of the systems, and it also looked simpler to manage than VMware.

The system is more robust now. In terms of performance, some users mentioned performance improvement for some legal applications without having to touch anything.

When it comes to faster outcomes, we are not dealing with projects that need to be delivered to the market very fast, so that is not the most important point for us. Nutanix does help us with our DevOps operations. We can support our development teams in a better way by providing them with resources faster than before. We have completely automated the provisioning of Linux systems that are used to host web applications. We are better than before.

Its ease of use is very important because the team is limited in capacity. We wanted a good partner to support us. One concern before migrating to Nutanix was that the community is less developed than VMware. Now that we have migrated, it is not a concern anymore. Nutanix was able to live up to our expectations.

There is less management for the team than before, so there is a complete gain of time. It freed up our staff's time for other work. This is something that is important for our company. We have 130 people in our company, and my IT infrastructure and operations team has six people, including two people for the service desk. We do not have many system engineers or network engineers, so the more we can gain on basic tasks, the more time we have for the projects or to improve our different solutions. We are able to save 10% to 15% of the time or at least one infrastructure engineer's time.

The web interface could be improved at some points.

We are currently facing one issue regarding management. We have two clusters supported on different sites with synchronous replication. The central point of management must be completely deployed on a Nutanix system with a witness. That is something that should be improved in the future.

The other issue that we are facing is related to integration. There is a lack of integration with our Veeam backup solution. It is not very well integrated with that, but this issue is not completely on the Nutanix side.

We migrated to Nutanix last summer. It has been almost one year.

It meets our current needs. I would rate it an eight out of ten for that. In terms of future expansion, when we migrated last year, we already planned for the resources. We are okay for the next three to four years. We may install a new cluster next year on a third site.

Their technical support is excellent. They are easy to approach, and their action time is very fast. For all the priority cases that can impact production, I can directly contact my local Nutanix team. Within 20 minutes of opening a case, we get a message.

We did not use a similar solution before, so I cannot compare it with others, but it is easier than what we were doing before.

We are using only the Azure cloud. We deployed the new infrastructure in parallel to the old one. We interconnected everything. The migration lasted two weeks. In two weeks, we migrated all of our virtual machine servers from the development environment to the production environment.

It was a very simple process from Nutanix's point of view. We also moved to new firewall technology in parallel. It took two weeks because we were retaining all the firewall policies at the same time. If we had to move only from VMware to Nutanix, we could have done the job in one night for 1,200 virtual machines.

Its price is correct.

There was a competition with VMware for the virtualization part and with different types of vendors, such as Cisco, HPE, etc.

I would rate Nutanix Cloud Manager an eight out of ten. Some interfaces can be improved, but its performance is perfect.

We evaluated Calm primarily as an automation platform because that's what it is. I work for a service provider and we represent a lot of customers.

Our journey with Calm started because we wanted to decentralize our platform of services to customers, because agility is one of the biggest concerns. As a service provider, we have very rigid practices because we follow ITIL processes. If we're managing a customer's environment, we need to have controls. The unfortunate reality of controls is that they add rigidity, and that works in contrast to the agility of cloud where customers want to be able to adopt and migrate and move quickly, based on their businesses needs.

We're developing Calm in a way where we give customers choice and flexibility, so that we don't have to consume workloads for them. We give them Marketplace, and part of Marketplace is that we publish open source applications, as well as managed applications and unmanaged applications. These applications could be as simple as a stack of load balancers, middleware, and database. Or it could just be an operating system. It's really the customer's choice. We've given them a platform, similar to the way public cloud providers do, a marketplace where they can go consume, but in our marketplace, that consumption can be on their platform. We provide a shared platform like a public cloud, and the hyperscalers, so they can consume it in Amazon and Microsoft Azure as well.

Part of our journey with Calm was that we wanted to speed the process up, but at the same time, have a standard catalog in that process, and let that catalog evolve with our customer feedback.

In our organization, we are both a partner, a service provider, and reseller of Nutanix. We have a very strong relationship with them. We have adopted Nutanix as a standard for our service provider cloud, which is located in five data centers in the central United States. In these environments, we have deployed Nutanix for our own services and shared services, and we are also selling private cloud, based on the Nutanix platform, to our customers. With these deployments, we are standardizing on Calm as a centralized management marketplace. So it's doing a couple of things. It's letting customers consume against their own platform, and it's allowing customers the access to be able to consume hyperscale and/or our shared platform if they choose to do so.

Our journey, right now, is balancing between managing operating systems and our managed service practice for our customers. We're trying to automate that managed service practice with Calm and their blueprints and the openness of scripting that they support, so that we can automate adding an application, an operating system, from our catalog. It goes through an ITIL process of creating a customer asset in our service library. It grabs values of that asset—naming conventions, components of the infrastructure, et cetera—and puts them into the customer's asset library.

These are all bits of underlying automation that you normally wouldn't necessarily have to do, but as a managed product we do so on behalf of the customer for inventory purposes. And that's just one aspect, what a managed platform does. The other aspect is an unmanaged platform. A customer can say, "I want to do 10 things and I'm managing them myself, and I'm going to probably destroy them when I'm done." We wanted that ubiquitousness, so a customer can choose whether they want something managed by us or managed by them, but where we keep the experience for doing so the same. It's a standard journey instead of their having to open a ticket and request something and then wait for a period of time for it to be executed. We're trying to remove ourselves as friction.

Our use case for Calm has been wrapped around giving customers a marketplace to standardize their experience and to determine what the components of that standardization are, which includes workloads that we manage, workloads that the customer manages, and those two scenarios can be on their private cloud, our shared platform, or the hyperscalers.

The beauty of the Calm platform is that it's really an open platform so you're not locked into a language that you're forcing developers and your team to use. We're working on enabling a DevOps journey inside of our company where we're not forcing people to adopt a tool and use a framework that they're not familiar with. We're allowing Microsoft people to use PowerShell. We're allowing our Linux teams to use shell scripts and Python. They have their choices. It's also allowing other components, like JSON. Our DevOps team that uses Terraform and other technologies uses JSON as a component for infrastructure automation. Blueprints allow all of that functionality.

You can also create a library of these scripts so that other team members can use what you've already developed to help speed and accelerate the automation journey. That is the next step for us. We're getting all this source that is very decentralized today—where people write their scripts, they store them, and they're not really a shared platform—and we're using Calm as a mechanism to bring it all together. The next step will be to integrate Calm with our source library and CI/CD pipeline. That is a forward-looking statement. Those are things we're working on. The DNA within our company, historically, wasn't as a software development shop, but we're transforming that now and using Calm as a mechanism to get there.

We have long-time customers, and our method of managing their workloads has been very traditional. When a request comes in, we go through a process of provisioning and deploying that request. We've enabled Calm on their platforms, so when a request comes in, one of our engineers executes the request, but instead of manually pulling triggers for the customer, to execute that request we now use Calm to deploy the customer's request and allow the automation to do the rest. We have scenarios with some customers where we are completely hands-off. They come to us and they say, "I want 10 of these and 20 of those." We execute that request for them using Calm, but that experience is somewhere on an order of magnitude of a fraction of the time that they used to have to wait previously, to have that request delivered.

In addition, by using Calm, we have the ability to keep these blueprints and images up to date. Previously, we had an automation process that built these images but they were constantly having to go through a management lifecycle. With Calm, we have been able to streamline that lifecycle so that what we're providing our customers is really the latest and the greatest.

Calm's abilities, in terms of team collaboration, come out in our standard marketplace or platform where teams are using the same experience. It's the same UI, so they're able to talk through their experience and talk through what they run into. We're using some of the functions of Calm to build project teams so they have the same access level and the same control. They're sharing the platform together. That gives them the ability to collaborate better across the platform.

And Calm is an HTML5 interface. It's all web-based applications at this point. Given what's happened over the last 12 months [as a result of COVID-19] and that everyone is remote, it's a lot easier to collaborate because it is all HTML5 and web-based. Our teams don't have to worry about legacy tools and applications to try to work together. From that perspective, we haven't really lost time in the journey because of all the recent events. We've been able to keep on working and keep on moving things forward.

In terms of Calm's ability to optimize, the analogy we use is a T-shirt because we have an extra small, a small, a medium, and a large. Those are really just subsets of components of the underlying infrastructure: this many CPUs, that much memory, this much storage. We use that to catalog our resources. The beauty of that catalog that we're building is that it is consumed against an infrastructure. By "T-shirting" these consumption models, we're able to maximize the available capacity of the environment that these workloads are sitting on. By contrast, when you randomly consume, which was typical in the "old days" where you would manually provision something, you provisioned them to non-standard tiers of infrastructure. That meant you were not consuming a platform linearly and that you were usually under-consuming something. You would make an investment and not maximize the output of that investment. By standardizing our "T-shirts" with Calm, we have also standardized the infrastructure that things are consumed against. So when our customers invest thousands of dollars on both infrastructure and tools with us, we allow them to get the maximum utility of that infrastructure investment, by using Calm as a mechanism to consume against it.

When it comes to application development and deployment, we have a series of management tools that we provide to our customers but those tools have a backend. We're trying to build automation into those tools so that they can be deployed and distributed automatically. We're using Calm to centralize and deploy those scripts automatically, in a distributed way, down to customers' private clouds and other environments. The intent is to build an application catalog with our customers so they can consume against it, using the Nutanix Marketplace to purchase those applications, very similar to what Amazon and Microsoft marketplaces are like. We're easily seeing a 20 percent improvement, and probably more, in that application development. That's a conservative number.

Calm is also transforming the way we QA and operate—the whole nine yards. Our process for delivering an application, an environment, goes through what we call a readiness exercise, a validation exercise. In the software world you would call it an SDLC stack where you go through dev, test, UAT, and release. That can be a very static and manual process, and it's very hands-on. What we're doing with Calm is transforming the process. We're saying, "Well, instead of manually doing the exercise, why don't we build triggers in our automation so that we can validate whether things are working properly or not along the way." We're making it a continuous validation process and an automated validation process. We're going through that journey right now, but when it ends, in all likelihood it will cut our validation time in half. We probably spend half our time validating an environment before we hand it over. If we automate that validation, we don't have to actually spend time doing it. Currently we spend time meeting with teams to do acceptance of our validation. So all that time will be freed up because we won't need a meeting to talk about validation.

Overall, we've gone from deploying workloads in 45 minutes or 90 minutes and we've taken that down, in some cases, to seven minutes.

The greatness of the Calm platform is that it removes itself, in a sense, so it's unknown to many people. It's a marketplace. You consume resources. If you design it properly, it obfuscates itself. Part of our challenge in the journey working with customers is to have them understand that that is what you want. You want it to be simple. But usually making something simple on one side is fairly hard to do on the other.

We use Calm's one-click self-service feature and it's really transforming the team's efficiency. The teams are used to being reactive, which is typical of what you find in IT organizations and service providers. Customers run into problems and teams react. What we're trying to do is reduce that slope and be more proactive in approach. The one-click ability is enabling us to take some of those activities and put them into operation, versus people manually responding.

We have a very close relationship with Nutanix and I have a very close relationship with the Calm team. I've given them a lot of feedback around multi-tenancy. Because we're a service provider, multi-tenancy is a big deal. 

Another aspect is that, while there are multiple clouds supported, we want less friction around the ease of delivery. We want the ability to integrate other clouds, unify the accounts.

Identity access management or IdP are other areas we've talked to Nutanix about, to move toward more of an identity access model, not just with the ability to use IdP to authenticate, but to also attach our back controls to the IdP so that we can have that centralized and decentralized model with customers.

And we want the marketplace and the blueprints to be a little bit more "brandable," for lack of a better word. This is really a service provider play, but we want the ability to make that a little bit more brandable so that we can scale that marketplace. We want it to be easy to determine which cloud you're selecting when you're picking something from the marketplace to consume. 

We also want to show cost to the customer. We want a model that says, "Well, if you consume that, this is approximately what it's going to cost you, depending on where you consume it, which cloud you're consuming it in."

I've been using Nutanix Calm for about two years now. We evaluated it just over two years ago. I was familiar with it in its early stages.

We haven't had any issues with Calm. Nutanix is really embracing that reference architecture within other aspects of its core applications. Calm is a containerized application that Nutanix deploys within their platform.

Calm has the ability to autoscale resources, so that if you need to scale up a resource, you can build those mechanics into your blueprints. We're consuming that ability internally, for testing purposes. We've talked to our customers about that and we're going to introduce it to them as that agility becomes reality.

The challenge is whether their applications have that "breathability" or not, and whether they are familiar with that. We want to be careful on the autoscaling aspects for customers because not all customers have web-scale applications. A lot of them have traditional applications. But we're definitely adding that to our subset of tools and resources so that there's an automation lifecycle with the ability to scale out a resource. Calm definitely has that capability and we've been using it for a while ourselves, evaluating and testing it. We're trying to work that into our discussion with our customers.

Overall, Calm is highly scalable and we haven't had any performance issues with it. The specifications numbers are in the specs, but we haven't hit anywhere near that. Those tolerance ranges are fairly significant. If you were to ask me about this a year from now, I might say that we will hit some scalability issues based on adoption. The good news with Nutanix is that they're constantly looking at this stuff as well. We're in constant communication with them about the platform.

The people in our organization using Calm include our DevOps team, our "high-end" engineers on both Windows and Linux, and our architecture team. That's roughly 20 people who are using Calm or developing within it. Those teams also work with customers against the Calm platform. We're now working on the next half of the journey, which is to bring the rest of the company along, extend our product catalog with Calm, and to start showcasing it to customers.

Nutanix technical support is a top-notch team. It's really one of the best experiences we have had and that I've personally had. When we call into Nutanix, their SREs are just phenomenal. Their discipline is absolutely amazing. We can get through escalation if we need to and get to a team, whether that's Calm or any other team, in a very short period of time. And that extends, for us, into their product team, into their engineers, or their QA if we need to.

It's an amazing experience to go through with Nutanix. Their knowledge is phenomenal. Their agility is phenomenal.

And with the Nutanix platform, they have the ability to see everything remotely as well, through logs. The platform uses a tool called Pulse which collects all the background information. It's a follow-the-sun approach, depending on what you need and what your escalation is. They can hand that ball around across the globe to get you to your result.

It's not that you'd ever want to have to call in to support for a problem, but with the way they have built the platform and the great team they have built, if you do have to call in, you can really feel comfortable that they're going to get you to where you need to be and they're going to get you there quickly.

Before Calm we tried many solutions. At some point tried Morpheus. That was prior to my joining our company, although I had previous experience with Morpheus. One of the challenges with Morpheus were some of the core things we have talked about. It was a completely independent platform. We had some API issues with it, as a service provider, and it didn't necessarily accelerate our journey. It unified things, because it was one interface, but the core, underlying infrastructure pieces weren't necessarily transformed as a result of it. While the experience became unified, it still took 30 minutes or 45 minutes or an hour to get something deployed. Whereas Calm now sits on top of a whole new ecosystem and that ecosystem has transformed a lot of things. 

We played with the VMware tools for a period of time, but those are expensive tools. It was very expensive to adopt that platform. We were trying to figure out the best mechanics for accelerating the platform without adding too much cost. That's when we started our Nutanix journey.

Nutanix makes the deployment easy, just like everything else that they have in their software stack. It's a very simple deployment model. It's part of the Nutanix software tool chain.

We have a combination of a uniform implementation strategy for Calm and taking different customers' requirements into account. We work with our customers to get feedback. We've started with a baseline of operating systems, primarily, because most of our customers are still in the traditional consumption model. And we're complementing that based on their feedback. We're also working with Nutanix because Nutanix has a large customer base as well. We've just really started that journey.

When we adopted the platform, we engaged Nutanix's services team so we could accelerate our journey with them. We had nothing but a great experience with them and their team. We were able to get Calm and core components of the platform up fairly quickly and get base applications going. 

Now we're taking that framework and applying the aspects of our business to it.

The biggest thing with Calm is that it has helped to fill a hole in our journey: How we were going to automate across all these different environments in the cloud, and without necessarily having to go build and develop a platform.

We're a service provider with a very strong relationship with Nutanix. We have multiple mechanisms of licensing Calm. From our perspective, the pricing is flexible and it's also unique. As a service provider, we can talk to Nutanix at a different level around how we license Calm.

You typically license Calm against your environment or you can license it by the workload. That makes a lot of sense, because workloads can live within your private cloud or the public cloud, it makes no difference. With any deal with Nutanix, they provide a certain number of seats with your purchase. So you get to use it from day one. I believe you get 25 seats with a purchase. There's nothing stopping you from embracing the journey because you've already paid for it.

My advice would be patience. It's very exciting and sometimes you want to jump in with both feet and go really fast. It's not that I'm against that, but my take is that it's such a capable platform that you should take on things that you can achieve and then achieve them. Take on activities that you can succeed with and show that incremental progress. Sometimes you want to take on too much and go big-bang. As enticing as that is, take on pieces of Calm and succeed with them, and let the platform evolve. Don't try to wholesale adopt it too fast. If you're more traditional in nature and you're doing typical project management, your windows could be big. Those steps up can be huge. So you want to make sure you show some incremental progress.

There's a plethora of automation tools out there as well as methods for how you build automation. Most of these platforms are frameworks and you have to build your own methods and use your own sets of tools. And when you're a service provider, and I think this would apply to the enterprise, cloud is an ubiquitous platform. In today's world, cloud is a ubiquitous term where companies don't necessarily look at just a cloud. They look at a cloud ubiquitously, because while you have three or four major hyperscale cloud-platform providers, they all have their different sets of software-based tools. In some cases, one cloud does certain things really well, while other clouds do other things that are better.

Limiting yourself and your business to one cloud might not be your best choice. And that has historically been the case in a lot of companies' journeys, but that situation is now evolving. Now, you don't just look at one cloud. Suppose you're a company that is heavily invested in Microsoft solutions. There are certain aspects of Microsoft, either your technology or your financial investments, which behoove you to use Microsoft Azure because it's beneficial to you. But there are certain things in the lifecycle of your software development where Amazon might be a better fit for certain aspects of what you do. In today's world, companies are evolving and they're open to the flexibility.

In that scenario, how do you decide your tool chain? How do you decide to invest in the use of tools from one platform provider or the other? Part of that assessment is cost and this is where Calm comes in because, as a lifecycle automation manager, it doesn't care which cloud you provision. You have choices. And the good news is that you control your source. So you don't have to use the tool set that Microsoft provides and then try to automate into Amazon from it, or vice-versa. You can try to develop those tools to automate by yourself, and a lot of large companies have made that significant investment in software—both in resources as well as capital. But these are platforms that consist of a lot of tools which have costs wrapped around them. The beauty of Calm is that it gives you your choice. Nutanix uses the expression "freedom of choice." That's really the conclusion we've come to, as a service provider. Part of what we want to do is give our customers choices. We want to help them along their journeys and help them make good choices, both technical and financial. And of course, those two pieces work off of each other.

Calm's support for scripts is a tale with two stories. First, it's exposing the scripts to a lot of people within the team. They can now use the same sets of scripts and augment them to do a specific function, versus starting from scratch. It may save them from having to research something. We have a library of these scripts that we're building.

Second, it's a step back before it's a step forward, because the team members have to get familiarized with this mechanism and with the delivery blueprint. We're ramping things up to get everyone slowly trained on the platform and to get them used to the platform, and that takes time. The mechanism of delivering the scripts is different from what they're familiar with. We're probably 10 percent into that journey. We've got a core team that has been working in it. Now, we're trying to extend that across other areas of the organization. Once we get everyone to participate and get a standardized library of scripts, we will see a very significant reduction in time. We'll see the agility of building applications a lot faster. 

What Calm has done for us is it's enabled the rigidity to be lifted. We're looking at a lot of different ways of changing things. It's a transformative tool. If you embrace it and adopt it properly, it opens the door to developing a life cycle process and the tools to use around Calm in terms of a repository and pipelining. Calm is also bringing us to discuss mutable and immutable infrastructure. Do we need to use tools like Puppet or Chef as a version control? Or, now that we have Calm, and we can strip out an application-ware or a middleware or something else, and start moving into a quasi microservices journey, does that infrastructure now become more mutable, where you can just destroy it and recreate it? Why try to save its configuration?

These are core topics, and they are big. It's traditional and nontraditional. This is a journey that Calm enables. If you embrace it, a lot of things become transformative with it. When you look at all those things, in many cases, you have to take a couple of steps back. But can you embrace Calm and do a lot of things right upfront? Of course you can. How quickly depends on your company size. We have a fairly large organization and we have a lot of customers, so we have to think of all those moving parts in embracing the journey. The good news with us is that we're going to be able to extend Calm to a lot of our customers. Calm will be a platform that a lot of customers will be able to use and embrace.

It's a great platform and I would rate it at eight out 10. The difference between eight and a nine is in the different things that we're asking for as a service provider. An enterprise or a commercial business might look at it slightly differently, but for me eight is a great score. It's a score I don't usually give out. Calm is a great team. They have developed a great platform and it's continuously improving. I look forward to seeing a lot of people adopt it.

We use Nutanix Cloud Manager (NCM) for the hyperconverged platform and to be able to centralize all our workload in a resilient platform.

We have integrated NCM with our service portal to provide seamless delivery of services, from the demand portal to the deployment of virtual machines. Both the help desk and service desk can manage everything from clusters to disaster protection and protection groups using the same API. We also have integrated IBM into the system.

Regarding Calm, which I am familiar with since Nutanix acquired it, it has become a very useful feature. However, the main concern currently is the licensing issue.

The challenge with Calm lies in its licensing model. We deploy it once, but we cannot manage it afterward, and we cannot purchase more licenses than what we have. When we deploy an application, it consumes a license, which limits our ability to use Calm as intended. Despite this challenge, Calm is a great tool for managing the life cycle of an application.

We use various APIs to enable automatic project delivery and one-click upgrades for all nodes, ensuring minimal downtime during the process.

I cannot give you an exact amount of time saved, but I can say that we have been able to reduce the number of people managing the platform by more than twenty percent since we started using automation and a simplified management approach. This is the best figure that we can provide.

The first use case is the hyperconverged platform with back-end storage.

The file management feature is also useful to us. Currently, we are also using Object Store.

Although we have evaluated Calm, we have not yet implemented it as it does not seem to be a valid use case for our role as a broker of IT solutions. 

We do not manage Azure workloads or life cycles, and it seems to be more suitable for developers.

For instance, let's consider File. The benefit of using File is that you can leverage both block and file use cases on the same platform with a single admin console. This makes it a valuable tool for managing storage efficiently.

Consider Files, for instance. Its value lies in the ability to leverage both block and file use cases on a single platform with a unified administrative interface.

We are able to simplify our storage infrastructure by replacing some of the older file system platforms. By using public cloud stores, we can offer new storage capabilities on the same platform, which is beneficial. We can also link these storage capabilities to our Splunk application, making it easier to manage and analyze data.

The primary benefit of using a unified platform is to simplify the management of the platform and reduce the skills required to manage it. 

With the natural attrition of skilled workers, companies must do more with fewer resources, and the most skilled people often lead the company. 

By using a unified platform, we can complete tasks that may have required highly skilled personnel in the past. 

This does not diminish the value of skilled personnel but allows us to accomplish more with fewer resources, which is beneficial for us in terms of simplification and cost-effectiveness.

The solution is designed to be easy to onboard and learn, even for those who have never used it before. This is because it is a unified platform that encompasses multiple technologies, reducing the need for users to learn and maintain multiple systems. 

The unified platform is also very user-friendly and clickable, similar to the Windows environment, making it easier for users to navigate and maintain.

This simplicity also enables the service desk to provide level-one support, which covers basic tasks and troubleshooting, leaving more complex issues to the experts. 

Additionally, the unified platform streamlines the support process, making it easier and more efficient for the service desk to resolve user issues.

The flow and management capabilities of the platform could be improved to handle additional features and functionalities, especially since the company currently uses some other solutions from a competitor. 

With the right enhancements, NCM could be capable of handling more features than the current hypervisor and offer a more comprehensive and robust platform for the company's IT needs.

While VMware is no longer part of NCM, it would be beneficial to include additional features such as AHPs, HyperAnalyzer, and similar capabilities found in VMware's ESXi. These enhancements would add value to the platform and increase its competitiveness in the market.

To maintain a competitive edge against ESXi, it's essential to have a dual bundle strategy, which is what we are currently pursuing. Having feature parity at a comparable level is important for us to succeed in the market.

I have been using Nutanix Cloud Manager (NCM) for more than five years.

The stability and resiliency of NCM are among the main factors that have kept us using it.

The operational method and process have remained the same since the beginning.

We have continued to use NCM due to its consistent operation method and process, as well as its unchanged UI look and feel over time.

The reason for our ability to scale and extend the platform is due to its scalability. With multiple data centers across different regions in North America, Europe, and APAC, we have a global platform that allows us to add a new team each year to manage it worldwide.

Scalability is another strong point of NCM. We don't have an excessively large cluster, but rather a big one that is very stable, and we can scale it as needed.

Currently, we have over two hundred nodes deployed across various countries, with the majority located in France.

We do not have a direct support agreement with Nutanix as we purchase the entire Lenovo infrastructure. However, our experience with their support has been very positive and valuable.

I have direct contact with the new Nutanix team and they are always available when we need them, providing us with valuable support.

I would rate the technical support a nine out of ten.

There is always room for improvement. 

There is some turnover in our supply chain, with changes happening once per year or once per two years. We experienced a significant shift in personnel in the last two years.

Previously, I worked with Symptivity. It was the first Hyperconverged platform.

Symptivity was a good solution, but at the time Nutanix was just emerging and VMware's VSAN was not yet available. Since then, Nutanix has continued to grow and expand its offerings, while Symptivity did not see the same level of growth.

In my opinion, Nutanix stands out from its competitors because it has invested heavily in developing its platform and expanding its offerings to cover various areas. Moreover, Nutanix has also obtained certifications from different vendors, including Red Hat, which has enabled it to be recognized and accepted in the industry. 

This was something that was lacking in the past, and it has helped Nutanix gain an edge over its competitors.

Nutanix has done an excellent job of ensuring that its platform meets the requirements and standards necessary to be used by a wide range of customers.

I was part of the initial deployment team during the early stages, but at that time, the offering was not the best. However, I am still involved and play an active role in the ongoing growth and development of the platform within the company.

The platform met our expectations and was straightforward to deploy and onboard. We experienced no issues as long as we continued to use ESXi.

We were able to observe how easy it was to handle Nutanix in comparison to Simplivity at that time. This is because we faced a lot of issues with Simplivity, but we did not face them with Nutanix.

Although we have seen a return on investment, it wasn't as high as we were expecting. This is because running ESXi on top of the new device platform incurs additional costs in terms of run operations, resiliency, and new capabilities. 

While there are already some benefits, there is still room for improvement in terms of simplifying the platform to further increase ROI.

In my opinion, Nutanix Cloud Manager (NCM) is expensive.

Based on what we have, we always aim to meet our pricing requirements and we are open to discussing and negotiating to get the best price possible. However, in my experience, I didn't find the pricing model for Calm to be satisfactory. 

As a large company with numerous instances, the pricing for Calm was not favorable for us. There is definitely room for improvement in this area.

I would rate Nutanix Cloud Manager (NCM) a nine out of ten.

Whenever we face any challenges related to the movement of virtual machines from one cluster to another, we are using Prism Pro. It makes our life easy because with the help of the Prism Pro, we can manage the movement of virtual machines between clusters. We can validate and do complete health checks of physical hosts and logical hosts, as well as of the complete compute storage and other components. All those are converged and are a part of a single solution. With the help of Prism Pro, we are able to simplify our operations and administrative tasks.

It is deployed in an on-premises data center. Both data centers have a couple of pairs of clusters, and the clusters are interconnected, just like the data centers are connected. Both clusters are replicated between themselves to have their data synchronized and updated so that in the event of a failure in one of the data centers, the other data center can take over.

Its top benefits include:

• Time savings
• Simplification of operations
• Environment stability
• Application accessibility

We can assess the performance and the capabilities of the host. We can initiate sessions, and we can evaluate those sessions with the help of the Prism Pro dashboard, which helps with capacity planning. We can forecast our capacity planning, and we have complete infrastructure visibility through the dashboard to get an understanding of how to utilize our hardware and applications in a better way to gain maximum performance. It helps with ROI and achieving long-term goals. It also increases employee productivity and workforce satisfaction. 

It saves cost. After using this solution, we have clear-cut savings of more than 40%. It also saves time.  We were able to see the results within 45 days from the time of its deployment.

It simplifies the administration and reduces human errors. It simplifies operation by providing a single dashboard. It also encourages the use of more automation.

Its integration with third-party tools is very easy. We have complete visibility. We can very nicely use the solution in our ITSM model. We are using third-party tools from different vendors for more insights, and with the help of automation, we are able to do application optimization, alert optimization, etc.

We are using it to manage VMware and Nutanix. The important part is that we don't have to depend on a multi-vendor management prototype. We can extend support to third-party vendors as well.

It reduces our overall power consumption. We follow the go-green environmental approach. We like to utilize the resources in a more efficient way. With this solution, we are able to save power.

The fact that NCM is sold as one product with multiple tiers is very important for us. A single-vendor solution is easy to manage. A heterogeneous type of environment is very difficult to manage because we require different types of skill sets, and managing the solution becomes more complex.

We are using Prism Pro, and the features related to the reporting capabilities, health checks, and automated alerts to Nutanix call-home are very important. We are using it as a management and reporting tool, and we are able to get a complete overview or summarized form of clusters that we are using in the production.

It has been helpful for forecasting and planning. It has also been helpful for analytics. With the help of this solution, we can have a better understanding of how much storage we are utilizing and how many processes are currently in use. Based on this information, we get a better understanding of how much expansion we need going forward, which is very important because ultimately it saves cost. It simplifies operations and helps with more revenue and productivity. It brings stability to our production environment. With the help of forecasting and capacity planning, we can achieve all of our long-term organizational goals. 

It is more cost-centric as compared to other solutions. It provides us with a holistic view of all the applications that we are using, and the most important point is that everything is converged. It is a one-box solution. It fits well with our requirements, and we are happy to have this type of solution in our production environment.

For Nutanix, there are options to go with different types of hardware vendors for using the AOS operating system. We can deploy it on Dell, Lenovo, or IBM servers. If Nutanix had its own server, it would be good.

We have been using this solution for the last two years. We have been using the Nutanix Cloud Manager version for the past several months.

There have been no issues related to its stability. We haven't faced any challenges in our deployed solution. On a periodic basis, we receive notifications from Nutanix about any vulnerabilities. Whenever a vulnerability is identified, we immediately get a notification to apply a patch and fix it. The system is up to date, and there are no vulnerabilities. It is stable, and we haven't faced any challenges in accessing applications. The overall performance related to the CPU memory, IO processes, and storage is at an optimal level, and we don't have any challenges. We are good.

In terms of scalability, it is very flexible. There are no challenges. It is a highly scalable solution, and expansion and migration are very easy. Everything is good.

Their technical support is excellent. If we need any support, they have 24/7/365 support. There are multiple ways to reach the support, and we get immediate assistance. In case of any criticality, they are able to manage the issue. They were able to resolve small, moderate, and high-level issues in a quick manner. We didn't face any issues related to escalations or unavailability with them.

Their knowledge is wonderful. Their technical teams are well-equipped in terms of skills. I would rate them a 10 out of 10.

Positive

Before this deployment, we were not using any similar solution.

It was straightforward because there was no migration or extension involved. We were using the solution as a first-time solution. So, everything had to be put in place new, and everything went well. We didn't face any challenges in terms of setup, deployment, and support. The deployment went well in a simplified case-to-case manner, and the operations have been very smooth. It didn't take more than 60 days.

Apart from the post-sales training where our resources got trained by Nutanix, our technical team members are also getting trained on a regular basis. We have regular schedules for technical training of our teams.

Its acquisition and support cost is nominal. It is not too high, and it is not too low. It is within the budget, and there are no issues on that part.

We looked at solutions from Cisco, Dell, and Nutanix. That's all. We chose Nutanix because of the cost and also because of the complete package. It included a multi-year support contract, and it is an all-in-one-box type of solution.

It is easy to migrate and expand. Most of the things are web-based. So, it is easy for anyone to understand and stabilize the operations. Our applications ran very well on the platform during the PoC. They are running well now too. These were the factors for using this solution.

This solution is very unique for our office. No other vendor has this type of solution in place, even though they are claiming to have a converged solution. As per our understanding and observation, Nutanix has a unique and excellent solution in place.

I would rate it a 10 out of 10 because everything is stable, and we are able to achieve all of our objectives. We are happy customers.