Nutanix Cloud Manager (NCM) Reviews

We use Nutanix Cloud Manager to manage all of our Nutanix infrastructure. We have six data centers throughout the world, and we use it to manage all that infrastructure for VMware. We're currently moving to AHV and are managing those as well.

From a resiliency of the infrastructure standpoint, we don't chase outages and major problems like we used to on other arrays such as CMC storage or Dell storage. Our folks have a lot more free time handle to the normal workload instead of troubleshooting.

The ease of use is a valuable feature. For us, it's a consistent interface. It's very easy to train our employees on it, and it's a newer generation interface. It's homogeneous, and every product and subset tie together, giving a very similar look to everything.

We do implement Nutanix Cloud Manager's built-in playbooks. Currently, the biggest one we use that's been very helpful is cleaning up snapshots. As users do snapshots of their virtual machines, it then goes back and cleans those out. We don't have a mess lingering out there.

Because Nutanix Cloud Manager's eScripts are based on Python, it allows me to bring developers in who are Python-centric. They are able to get up to speed quickly and develop the automation pieces we need for our own private cloud and build servers and applications on-premises.

In some ways, Nutanix Cloud Manager abstracts out certain items in a simplified manner, which makes it good for training. At other times, to get to the next technical level, we want to actually dive in, and Nutanix Cloud Manager sometimes restricts us from actually diving into the deeper technical pieces. There's no advance button that lets us do more advanced things without having to drop out to the CLI to do the command line piece.

I've worked with Nutanix Cloud Manager for more than five years.

So far, we've been very impressed with the stability. In the Nutanix ecosystem, everything is clustered, highly available, and fails over. It takes care of itself.

We have very few users who are using Nutanix Cloud Manager at present, but we do have all of our infrastructure running Nutanix on the storage side. From that scale, we're handling thousands of servers with no issues there. In about three months, we will be switching over all of our VMware folks to Nutanix Cloud Manager via ServiceNow. Then, we'll be able to see the full impact of our users using Nutanix Cloud Manager.

I would give a ten out of ten to Nutanix's technical support. We've had excellent support. They always know two or three other people they can call on to help with certain portions of an issue. There's very good networking within the company.

Positive

We're a VMware shop and have vRA, which we used for all the automation on the VMware side. We also used vRealize Orchestrator. Initially, we chose Nutanix over standard disc arrays because we came out of the storage market. As Nutanix has added products, we've seen value in them and went in that direction.

When we bought the storage system and disc encryption, they came with other licenses. Nutanix Cloud Manager was an add-on. When we looked at the cost of other solutions and the opportunities that Nutanix Cloud Manager gives us to tie directly into Nutanix, it just seemed to be the right fit.

It might be too early to tell as we just started using Nutanix Cloud Manager for our private cloud about four months ago. Once we get fully off of VMware, we should definitely see an ROI.

The price is probably right where it should be. It's not vastly expensive, and it's not too cheap. We get very good value for the price with what we're being offered with it.

Nutanix Cloud Manager is a walled garden, and you have to do all of your editing within the interface. Our developers become frustrated with not being able to use other tools such as Visual Studio, Visual Studio Code, and CSE pipelines. These are outside of the Nutanix Cloud Manager interface, and the developers would prefer to use them instead of using the NCM interface. In this sense, Nutanix Cloud Manager has been a struggle to use. The NCM interface could be improved.

The setup is fantastic because you can click a button and deploy it. It's already part of the existing piece, and it's like adding a module. Compared to the setup of other cloud management solutions, Nutanix Cloud Manager's setup is much easier. We just spent about four months upgrading a VMware product, and there were bugs. It was a nightmare. With Nutanix Cloud Manager, it's click-and-play, and we haven't had any issues at all.

The learning curve is a lot easier because it is based on Python, and we have developers who already know it. We don't have to retool. Many of my developers have been up to speed in under a week.

If you're considering Nutanix Cloud Manager, my advice would be to go through the entire POC in-depth to see the value in it. Initially, it may look very simplistic, but when you dive into the code, you will see the depth of the product.

Overall, I would rate Nutanix Cloud Manager a six because the automation tools are still in the early stages. There are things that need to be fleshed out in the private cloud as well as the public cloud. I don't see anything badly wrong with it, but I think there's a lot of room for improvement as an industry in general.

The company went with Nutanix and hyper-converged. Just the sheer number of disparate vendor products and hardware the company had to deal with was a lot. The solution was used for consolidating everything into a much more easily managed payment class. Prism brings it all under one umbrella.

Prism Ultimate is where it can't get any better. We've got all the feature sets available.

We use the runbook on occasion and we don't really use a lot of automation.

We did some site migration activities with a large number of guest systems that needed to be relocated, it was pretty convenient. I don't remember experiencing any issues. We did a pretty big data center relocation and we used Nutanix protection domains to do most of that. We ran into a couple of issues outside of any automation and those were just our own configuration issues that we quickly figured out.

The speed of the outcomes we've received using the solution's low-code automation would be as expected. We have no complaints about the processes with Nutanix.

The man-hours saved are pretty important for us. We have a pretty large environment for our team to handle and anywhere we can optimize tasks more efficiently and not have to do them in scheduled maintenance Windows after hours is a big plus.

Monthly, as far as general maintenance, the systems used to have to be babysat by somebody. We save probably twenty to twenty-four hours a month in man-hours, just on being able to schedule and automate a mundane task that used to have to be handled with kid gloves.

As far as maintainability, we do tasks more efficiently and we've saved money. The ability to even just have the built-in monitoring and alerting system that is in the product by default, just by running the infrastructure under, is great. Prism Nutanix saves us quite a bit of effort and time. I don't know if you could really put a number to that time.

We use the solution to manage both Nutanix and VMware infrastructures. We are in the process of progressing towards getting as much as possible off of VMware ESX and onto AHV. We currently have about 70% on Nutanix and the remaining on ESX.

It's great that the solution can manage both of those infrastructures. It's a lot more efficient and convenient to have all of this in one payment class rather than have to monitor two separate infrastructures.

The solution helps provide a continuous validation process and it's pretty impressive. Just what you get by bringing that infrastructure under the umbrella of Prism without having to do any monitoring setup at all, covers more than 90% of what we really need. This feature's effect on our validation time is exceptional. I would say that it probably reduced it by more than half.

The solution is better than expected in terms of helping our team address our current automation needs while planning for future expansion.

Its speed when delivering infrastructure as a service has been good. We haven't had any complaints about the performance or implementation of new systems with this product.

We haven’t really gotten into the solution's capacity planning and runway analytics to help forecast storage and compute needs. Since I came in, we have been doing a lot of forklift upgrades and data center relocations. Most of the clusters have been in so much flux that the runway and those estimations haven't been accurate enough simply due to the fact that we pull the carpet out from the data and change the environment so often. Hopefully, once we have one more major cluster to put in, we'll get most of the rest of our PSX environment over. AT that point, those forecastings will be valuable to us. However, our environment and underlying hardware have been in so much flux, that nothing could really give us real accurate forecasting.

There's a split between Prism Central and Prism Element and having to know which interface I need to get into to do certain feature sets or just having to switch between them having all the feature sets available would be my biggest ask. They've been moving towards that more and more.

I've been using Nutanix and Prism for nearly five years now. I came in about two years after the implementation started. It's the same product that we've been using for three years, just with a new name. We have been using the Nutanix Cloud Manager version for the past several months.

The stability is incredible. We are on Lenovo OEM and the only issues we've experienced since I've been on board for three years, have been related to some Lenovo firmware issues in our environment that would have caused a host outage. We've had other issues with the Nutanix solution, however, those have not impacted production or impacted the host.

The scalability is great. It's easily expandable storage-wise and compute-wise. We can do that comfortably without fear of the impact on production. We do a lot during production hours that used to have to be done outside of production hours on maintenance Windows.

In my more than twenty-five years of experience in the industry, I would say the technical support goes above and beyond any other vendor that I've ever worked with. It's probably one of their strongest points.

There have been multiple times when we've called in about some issue and the techs look into it and ensure that everything else on that cluster is copacetic as well. They won't look just at the problem. They'll say: "Hey, I noticed this, let's take care of that while we're in here." They're not trying to blow you off.

Positive

The company never used a hyper-converged solution like Nutanix previously. There was a traditional three-tier and Nutanix was brought out to consolidate.

I have not used any other solutions like this. This was my first introduction to any type of hyper-converged solution.

I wasn't a part of the initial setup. I came in two years after it was implemented.

The product requires maintenance. In this case, considering the breadth of our implementation, typically it's only one man dedicated for an hour or two a week. This is just to ensure things are kicking off as expected and things have been completed as expected.

I know the company was looking at other companies. I don't know which ones, however, as that was all pre my history with the organization. Likely, at that time, Nutanix was probably the best solution available.

I'm a customer and end-user and we're in a long-term stable release. 

There's a lot of naming in Nutanix. There's Prism Element and there's Prism Central. This depends on how wide a view you're taking. We use both here.

Prism Pro and Prism Element are different levels of feature sets in Prism. Ultimate has more features available than Pro has, however, it's the same product overall. Prism Element is tied to a cluster of Nutanix-based systems and Prism Central is a collection of those clusters. That gives a view of the entire environment. We are Prism Ultimate licensed.

We use a private cloud as our environment is all internal to our organization.

I'd rate the solution nine out of ten.

We are an education institute, and we use Nutanix Cloud Manager to manage student applications, employee applications, and for other educational purposes.

The most valuable feature of Nutanix Cloud Manager is the flexibility we're finding in expanding our technology and our support. We can't mess with the student's data, and we need to protect the data of many students within our data centers to ensure continuous business. One of the benefits of using NCM is the ecosystems we have within the organization and other organizations.

Nutanix Cloud Manager could partner with more partners to bring technologies that align with the area's policies and business needs.

We've been using Nutanix Cloud Manager for six to seven years now.

Nutanix Cloud Manager is a stable solution.

Nutanix Cloud Manager is a scalable solution. We are using six nodes and planning to add more features like the video in the future.

Nutanix Cloud Manager's technical support is reachable and solves the problem in a matter of seconds.

Positive

From the documents I'm reviewing, Nutanix Cloud Manager's initial setup was a straightforward process. There were no issues in the solution's implementation.

We're seeing a return on investment from Nutanix Cloud Manager, but since ours is an educational business, there's not much to assess.

Nutanix Cloud Manager's pricing is fair at the moment. However, its pricing should be reassessed, and different pricing categories should be set for different business needs.

When we approached Nutanix Cloud Manager, they presented the technology well. We chose Nutanix Cloud Manager because we found it could be sustainable for the future. Users should consider Nutanix Cloud Manager's use cases and opt for the solution depending on their type of business.

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

We are still working on moving workloads from the old environment to Nutanix. We are planning to use Nutanix for our mid-tier. The mid-tier consists of noncore applications like medical services.

Nutanix is customer friendly. The efficiency of Nutanix Clusters is amazing. The product communicates with the hardware far better than any other product.

I love that we can clone the server once it is deployed. The solution’s ease of use is mind-blowing.

Compared to Dell HCI, Prism’s home screen is quite mundane. When we tried to migrate an application from the old cluster, we couldn't run it on Nutanix’s native hypervisor. So we had to install a different hypervisor to run that particular application.

My organization has been using the solution for two months.

The solution has been very stable so far. We have had no issues.

So far, the product is quite scalable. It's easy to add clusters and nodes. We have about three nodes in disaster recovery and six nodes in production.

The solution’s support is one of the fastest supports we've experienced. We always get a response within an hour.

Positive

Previously we used Dell HCI, which was running on VMware ESXi. We had resource constraints in our previous environment. It wasn't as efficient as Nutanix.

There is a level of complexity to the initial setup because it is new. However, it was not as complex as other products.

The solution’s price is competitive. Compared to Dell HCI, Nutanix is a lot cheaper.

We reached out to OEM vendors in the market. We compared the offers based on price, features offered, and the cost of support for several years, and Nutanix came up at the top.

We just completed the installation and deployment for the disaster recovery branch. I work for the Central Bank of Nigeria. We have three different environments in the bank. We use IBM for our core systems. We also have test and development environments where we run stress tests before deployments.

When I had to deploy about ten or twelve different servers that use the same operating systems, I deployed one and cloned it. The product’s ability to clone is by far the best thing I have seen. It took me only two to three minutes instead of 30 minutes or an hour.

Overall, I rate the solution an eight out of ten.

I do a lot of tasks via automation which I previously would have to hire people to do. The solution has helped me to eliminate a lot of low-skilled labor. I can put the money required for this job into other things.

Getting an update about my clusters is the most valuable feature of the product.

The support provided after office hours could use some improvement.

I have been using the solution for four years.

The product is really stable compared to everything else in my environment. I had one major problem over a five-year period.

I've had no problems with scale, and I keep growing my environment every day.

The support is good.

Positive

The initial setup was easy.

We used a combination of our employees and consultants to deploy the solution.

Since we are able to automate more, we are able to deploy faster. So customers are happier, and it leads to customer retention.

The solution’s pricing is not outrageous like other products. However, reducing the price would always be useful.

I've evaluated options across the board, and Nutanix’s structuring platform has saved me a lot of time and effort. It takes three times more people to do tasks on VMware than Nutanix.

I have different products. It seems like Nutanix is headed toward making things more seamless, which really excites me. I need solutions with improved speed of creating and automating the processes and making them seamless. I need solutions to grab everything from everywhere. NCM is self-sufficient. You don't need to know everything about it. It installs itself, and it takes care of itself. We have used the older versions of the solution too.

The speed of the outcomes is great. I couldn’t be happier. I can deliver to my developers and my end customers faster. Faster outcomes are very important to my organization.

NCM’s built-in playbooks have freed up time for my IT team by 25%. I love that the product allows me to fix things that are broken now and think about the future at the same time. Compared to other products, NCM is much easier to use. I don't need highly trained people to use the solution.

Overall, I rate the product a nine out of ten.

We use it for our service, running everything through Nutanix.

It is easy to access. Since it is web-based, you just punch in the API and it gives you all the servers in the company. The solution has helped optimize database performances.

Nutanix helps us save on Tier 1 storage, which is very important to us. As a company, you need backup. Working with this solution is easy and fast.

As a company, backup is very important. Anything can happen to a company so you always want to have backup. The important part is that this solution is cloud-based. Therefore, if a fire happens, you still have your backup.

Since last year, we haven't really worked after hours.

Nutanix has 100% improved our team's ability to troubleshoot operational issues. This is excellent for business. It now makes things easier for us to troubleshoot, helping us know where or what the problem is. It makes things simpler.

It provides healing to the system. If there is something wrong with the system, then it gives you an alert and decides what the problem is. It tells you in detail if there is something wrong with your server.

It is not time-consuming. It makes things easier for the company, because now you know exactly what is wrong because it tells you what it is. It is easy to access.

We use it with SQL Server workloads. This solution is good and quite fast for that.

The design could be more user-friendly. There is always room for improvement when it comes to a site being more user-friendly.

My company has been using it for about six months.

I have been very impressed with the stability.

Customer service has been good. So far, I can't complain. I haven't picked up anything that I might complain about since everything is running smoothly and has been simplified. I would rate them as nine out of 10.

Positive

This has been an improvement for me because I am used to old physical servers.

I was not involved in the initial setup. Everything was already up and running when I started using it.

It has helped us cut deployment times.

Nutanix has decreased the time it takes to snapshot and clone databases. Because of this, the business is running smoothly. Everything happens quickly, so it is quick to do things on this platform, i.e., less time-consuming.

The increased backup frequency has helped to limit data loss.

When it comes to data management, the solution has reduced time spent on operational database workloads.

We use Veeam for the backup and restore of databases.

This is the way to go. Technology is growing and improving. I feel like a lot of companies in my country are still stuck in the old way of using physical servers. Whereas, we now have something like this that makes things simple with a feature that sends alerts. In a way, it is running the whole infrastructure.

There is always something out there that can improve your life, simplifying your life. There is always something out there that you can learn about.

It has improved my life and the way the company is running. We use it almost every day.

There are about 10 of us using it, including support, system engineers, my assistant management, and management.

I would rate this solution as nine out of 10.

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.

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.