Coming October 25: PeerSpot Awards will be announced! Learn more
Buyer's Guide
Virtualization Management Tools
September 2022
Get our free report covering VMware, IBM, VMware, and other competitors of VMware Aria Operations. Updated: September 2022.
635,162 professionals have used our research since 2012.

Read reviews of VMware Aria Operations alternatives and competitors

Parham Shabaniani - PeerSpot reviewer
Cloud Architect at a tech services company with 501-1,000 employees
MSP
Top 20
Enables us to maximize the available capacity of the environment that workloads are using
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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."

For how long have I used the solution?

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.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What about the implementation team?

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.

What was our ROI?

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.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner/Reseller/Service Provider
Todd Winkler - PeerSpot reviewer
Principal Engineer at a insurance company with 10,001+ employees
Real User
Top 20
Lets us take a good look at our environment and decide how we will size our workloads into new areas
Pros and Cons
  • "It has automated a lot of things. We have saved 30 to 35 percent in human resource time and cost, which is pretty substantial. We don't have a big workforce here, so we have to use all the automation we can get."
  • "There are a few things that we did notice. It does kind of seem to run away from itself a little bit. It does seem to have a mind of its own sometimes. It goes out there and just kind of goes crazy. There needs to be something that kind of throttles things back a little bit. I have personally seen where we've been working on things, then pulled servers out of the VMware cluster and found that Turbonomic was still trying to ship resources to and from that node. So, there has to be some kind of throttling or ability for it to not be so buggy in that area. Because we've pulled nodes out of a cluster into maintenance mode, then brought it back up, and it tried to put workloads on that outside of a cluster. There may be something that is available for this, but it seems very kludgy to me."

What is our primary use case?

Currently, we're doing migrations for older versions of Windows, both in the Azure Cloud and on-prem in our VMware vCenters. We use this tool to do comparisons between the current and future workloads and what would they look like, based on the usage. So, it is kind of a rightsizing exercise or rightsizing, either downsizing or upsizing, depending on the requirements. We just put all that information into Turbonomic, and it builds us out a new VM, exactly the size that we need, based on the trending and analysis. Then, you can also put in some factors, saying, "Look, it was Windows 2008, and we're going to windows 2019, or whatever. We're going to grow the database by X amount." This tool helps you do some of the analysis in order for you to get the right size right out-of-the-box. We love that.

I oversee a lot of stuff, so I don't really get an opportunity to go in there to point and click. We have people who do that.

It is doing Azure Cloud and VMware. Turbonomic understands the resource relationships at each of these layers and the risks to performance for each. You can compartmentalize your most critical workloads to make sure that they are getting the required resources so the business can continue to run, especially when we get hit by a lot of work at once. 

How has it helped my organization?

The solution provides us with a single platform that manages the full application stack. In our decision to go with this solution, this was critical. We had so many vCenters and physical clusters out there. We had virtual and physical machines all over the place. Turbonomic was the way we were able to centralize all our vCenters and get a good picture of what is going on in the environment. It was all over the place without it, so there was no way that we could centralize and work on getting off of some of the older hardware platforms that we were on and start moving to converged, then eventually hyper-converged. This tool allowed us to take a good look at our environment and decide how we were going to size those workloads into those new areas, off of the old blade chassis and old standalone systems, to the more modern hyper-converged systems.

In our organization, it is optimizing application performance as a continuous process that is beyond human scale. The reason is because there are times of the year that we have these big hits. It is like if you were Verizon and you were to sell all your cell phones during the Christmas time. Well, we have a very similar thing here at our company, where we have a period of time we basically shut the business down. We have to give critical resources to critical applications, giving them the resources that they need in order to function. In order for us to do that, we are able to take critical workloads and put them off into their own area, then determine how much we have to take from the rest of the resources, which we take from the rest of the systems in order to put it into new clusters or systems. That is super critical for us every year.

We use it for management and rightsizing of our platforms, specifically for migration activities, because we're always doing it. The migration has been the biggest thing that I personally use.

What is most valuable?

There are a number of tools that we use in it. Some of the things that I request are the data dumps. They write some kind of scripts or something inside there where they are actually able to pull for me CSV files. Then, I can go in, take all that information, and build a master gold list for my migration activities. 

Everything that I ask for, I get. I don't know what they are clicking nor do I know what they're doing, but when I request it, I get it. There are all sorts of different ideas and scenarios that I put forth to the developers.

Turbonomic provides specific actions that prevent resource starvation. While I'm not in there banging around on the tool all the time, I can tell you that I do very much benefit from it. On Monday, I was getting additional information from the Turbonomic guys.

We use the solution’s automation mode to continuously assure application performance by having the software manage resources in real-time. 

What needs improvement?

There are a few things that we did notice. It does kind of seem to run away from itself a little bit. It does seem to have a mind of its own sometimes. It goes out there and just kind of goes crazy. There needs to be something that kind of throttles things back a little bit. I have personally seen where we've been working on things, then pulled servers out of the VMware cluster and found that Turbonomic was still trying to ship resources to and from that node. So, there has to be some kind of throttling or ability for it to not be so buggy in that area. Because we've pulled nodes out of a cluster into maintenance mode, then brought it back up, and it tried to put workloads on that outside of a cluster. There may be something that is available for this, but it seems very kludgy to me.

I would like an easier to use interface for somebody like me, who just goes in there and needs to run simple things. Maybe that exists, but I don't know about it. Also, maybe I should be a bit more trained on it instead of depending on someone else to do it on my behalf.

There are some things that probably could be made a little easier. I know that there is a lot of terminology in the application. Sometimes applications come up with their own weird terminology for things, and it seems to me that is what Turbonomic did. 

For how long have I used the solution?

Three years.

What do I think about the stability of the solution?

I have never had a problem with it. The product is a little over anxious at times.

What do I think about the scalability of the solution?

When we did the rollout in that phased approach, it was not difficult at all to roll in new technologies. They converged and hyper-converged into Turbonomic. So, it's definitely scalable. It moved right into the company pretty easily.

There are quite a few people using it, mostly for operations type of work. There are probably 25 users from operations, support, the performance team, and performance planning.

How are customer service and technical support?

I have worked personally with Turbonomic, one of their guys, on some of this stuff. I haven't talked to him in a while, but he helped us develop a lot. The support for Turbonomic is incredible. 

Their technical support is excellent. By far, they are probably the best. It's probably why I am sitting here talking today, because I have to give these guys top props. I think the employee enthusiasm about this product is absolutely top-notch. It would probably be a great place to work.

I've worked with the Tier 1 support and their consultants. We had a consultant here for a year who was absolutely a top-notch fellow. He just became part of the team. He wanted to learn how we were doing things and tool the application to do what we needed it to do, which he did. He also left great instructions. A lot of his legacy is still there and being used today. 

Which solution did I use previously and why did I switch?

We were using a combination of vROps and VMware. We were also using BMC TrueSight, which we still use today. There are a couple of others out there, because the network team uses a few things. There is all sorts of stuff that I think they were kind of hog-tying together to make them work.

Some of these solutions are ingrained in our processes and have been around literally forever. So, there isn't the staff or the resources right now to rewrite a lot of these things. Currently, we do kind of a side-by-side comparison, and I believe some folks have written some ways to integrate the new data from Turbonomic into the old way of doing things. That's just a culture change at the company. It's just a big place that has been around for a long time, which works slowly.

This solution was brought to us by one of our AVPs. She had worked at HPE, and we didn't know about it. She said, "Let's look at this," because apparently she used it at HPE. We looked at it, and said, "Ah, this is great." Then, we went with it.

Turbonomic is more customizable with a lot more features. 

Even though you can turn on automation in VMware, it's not very good. It's kludgy and has a tendency to break things, where the autobalance of workload management that Turbonomic does within VMware is much better than the VMware tools which are designed for this. That may change, because VMware seems to be doing great with this. However, for right now, Turbonomic is the only way to go. 

TrueSight is just straight up what you see is what you get.

How was the initial setup?

I went to the training when they first rolled it out, but I wasn't involved in the setup.

They did the setup in sections. So, they started off with the lower environments and some of the clusters out there that really needed a lot of attention, mostly blade servers and such. So, it was a gradual rollout. I think the entire rollout was somewhere in the area of a year to a year and a half. However, to get it fully running, where we could use this solution to our benefit, that was at least six months.

We use scheduling in real-time for implementing the solution’s actions as well as manual execution, which is when we schedule for a later date to change activities. We have had to enable or disable certain things. It seems to do that just fine.

What about the implementation team?

We used Turbonomic for everything to do with the setup. On our side, it required about five FTEs, who were engineering and operations personnel. There were folks who were creating the design and where it would be rolled out. That design was passed down to the operations folks who were actually implementing everything. So, it was done in phases.

We only have two engineers doing maintenance, a primary and a backup, and this is like their extracurricular activity.

What was our ROI?

The ROI would be in the return of hardware, specifically for a lot of the older hardware where we start to go into the converged systems. That is where we are seeing our ROI. We are getting rid of that old, junky hardware, starting to integrate and align things into one specific way of managing all our workloads, but not on old hardware. If anything, the ROI is end of life hardware elimination.

Also, we see ROI in extended support agreements (ESA) for old software. Migration activities seem to be where Turbonomic has really benefited us the most. It's one click and done. We have new machines ready to go with Turbonomic, which are properly sized instead of somebody sitting there with a spreadsheet and guessing. So, my return on investment would certainly be on currency, from a software and hardware perspective.

Turbonomic provides a proactive approach to avoiding performance degradation. Our capacity and performance team use this solution as part of other tools that they utilize.

The solution provides application-driven prioritization, with its AppDynamics integration, to show us how top business applications and transactions are performing. If Turbonomic comes back and tells us, "Hey, this application needs more resources. Or, you're coming up onto a period where it will need more resources. Start planning now." We have certainly used it for that and will continue to use it for that. We have actually used it for troubleshooting a couple of times, saving us 25 percent when it comes to performance-based issues.

We have seen a 25 percent reduction in tickets opened for application issues.

Turbonomic has definitely helped to save human resource time and cost involved in monitoring and optimizing our estate. It has automated a lot of things. We have saved 30 to 35 percent in human resource time and cost, which is pretty substantial. We don't have a big workforce here, so we have to use all the automation we can get.

Which other solutions did I evaluate?

We did an architectural review. We had to look at other options, but I don't know exactly what those were.

Some of the tools which already exist are not that great. They really need to up their game if they're going to keep up with something like Turbonomic.

What other advice do I have?

If you have a big shop, and it's scattered all over the place, then definitely take a look at this tool. Make sure you take a look at this tool because there is probably fit for purpose licensing for any size organization. It's a great automation process.

Turbonomic shows application metrics and estimates the impact of taking a suggested action based on its input from AppDynamics. So, we plug it into AppDynamics, then AppDynamics and Turbonomic seem to work together for that. 

It knows what business-critical applications we have, but I don't think it manages anything specifically within the application itself. It is mostly just resource-driven.

As money starts to get tight and budgets start to get really scrutinized, I think people are going to have to start looking at using Turbonomic to help optimize cloud operations to reduce cloud costs.

We are going to continue to use it going forward. I just don't know at what level. There are a lot of changes being made to the infrastructure, so it's going to depend on the tools and things that become available, like VCF as well as all the products that they have built-in through vROps, enhanced vROps, and things that already come with the software.

I would rate it an eight (out of 10). Personally, there is a lot that it does that a regular person like me does not have the time to sit down and dig into it. We expect things to be a little bit more automated. That is why I gave it an eight. I would give it a 10 (out of 10) if I got in there and it's like, look, click, click, and click. However, I don't know if there is that kind of a comfort level here yet to just let this thing go and have its day with the place.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
CEO at Orieta.tech
Real User
Top 5Leaderboard
Works in virtualized environments with high performance requirements with hyperscale availability
Pros and Cons
  • "Nutanix Prism is popular in the Indian market, particularly in enterprises where they need a DR type of environment, and where they look for less than finite RPO and RTO. If you have this environment on-premises, and if you can just rent out some portion to any of the service providers, then you can easily set up a DR environment to give you a finite list versus RPO and RTO."
  • "Nutanix Prism needs more flexibility commercially and more flexibility with their licensing. Currently they're very fixed on their licensing model, for example, it's based on terabyte calculation."

What is our primary use case?

Nutanix Prism is used in a virtualized environment with high-performance requirements where people can have the VMs and run the databases with infrastructure as a given service, that has five nines or four nines uptime environments.

What is most valuable?

Nutanix Prism is popular in the Indian market, particularly in enterprises where they need a DR type of environment, and where they look for less than finite RPO and RTO. If you have this environment on-premises, and if you can just rent out some portion to any of the service providers, then you can easily set up a DR environment to give you a finite list versus RPO and RTO.

What needs improvement?

Nutanix Prism needs more flexibility commercially and more flexibility with its licensing. Currently, they're very fixed on their licensing model, for example, it's based on terabyte calculation.

For how long have I used the solution?

I've been using Nutanix Prism for two years now.

What do I think about the stability of the solution?

Nutanix Prism is a very stable solution.

What do I think about the scalability of the solution?

Nutanix Prism is a scalable solution. It also has hyperscale availability.

How are customer service and support?

We contacted the support team for Nutanix Prism during the initial setup. There were some configurations we were not able to understand, but their support team was very helpful.

Which solution did I use previously and why did I switch?

We used VMware predominantly. We also used Cisco HCI before using Nutanix Prism. We didn't need to switch, but we wanted to have different flavors in our environment to cater to more customers.

How was the initial setup?

Nutanix Prism has a very straightforward initial setup. They provided very helpful guidance during the setup process. If one knows the basic setup criteria of the network, the solution can be easily deployed in any environment.

What about the implementation team?

Implementation of Nutanix Prism took a few weeks. We set up the environment in-house without using a consultant or integrator, but we had help from the Nutanix support team.

What's my experience with pricing, setup cost, and licensing?

The license we bought for Nutanix Prism is perpetual, so once you have it, you can keep on using it. It's a three-year license that you pay once for. The license we have covers the three-node cluster, but then you need to have the basic networking gear for the infrastructure to work in the type of environment we're in. For example, the only additional thing we need to do apart from getting the license is to plan the network connectivity.

What other advice do I have?

I use Nutanix Prism. It's a three-node solution for virtualization. It's an on-premise solution. I don't remember which version I'm using.

The solution is being used within our organization, but we also have customers hosted on top of that, so I don't remember exactly how many people are using Nutanix Prism. For deployment and maintenance of the solution, you'll need two people: one system administrator and one network L2 or L3.

I can recommend Nutanix Prism to others who want to start using it, but my advice is for them to get the POC done first. They have to understand the environment, use cases, and what they're looking for, then they can make their call.

I'm rating Nutanix Prism nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Matjaž Godec - PeerSpot reviewer
CoOwner & CTO at a tech services company with 11-50 employees
Real User
Top 10
Good optimization but is immature and integration is complicated
Pros and Cons
  • "The optimization of the solution is quite interesting."
  • "The solution is still quite immature."

What is most valuable?

The optimization of the solution is quite interesting. It means we can prepare a bunch of VMs, and of course with self-service provisioning.

What needs improvement?

The solution is still quite immature.

Those CloudForms and similar products are very capable if you are some sort of programmer. It has the infrastructure, however, to actually make it work, you have to program it yourself inside the platform. It's okay as a platform, however, it is not a ready-made product. You have to do a lot of work.

The product is expensive. It would be ideal if they could work on their pricing model.

What I expect from Red Hat is for it to make configurations for common use cases. Red Hat CloudForms allows you to integrate with external sources. Yet, if you want to integrate something, then you have to program it in Ruby in order to integrate. If you want some features with this integration, they also have to be programmed. I know that with other products, it is more of a point and click integration. Often, also, there are knowledge bases or use cases that are already present as point-and-click functionality. 

For how long have I used the solution?

I've been using the solution for about three years at this point. It's been a while now.

What do I think about the stability of the solution?

The stability has been very good so far. We haven't had to deal with bugs or glitches. It doesn't crash or freeze. It's good.

What do I think about the scalability of the solution?

While we haven't tried to scale the VMs just yet, for us the scalability has been okay. An organization that needs to expand it should be able to.

Currently, in our company, we only really have four people on the solution that administer it.

How are customer service and technical support?

We don't use technical support very much due to the fact that we are a very open-source company and are accustomed to doing our own self-support.

Which solution did I use previously and why did I switch?

We did not previously use a different solution.

How was the initial setup?

The initial setup is not too complex. It's pretty straightforward and simple. We didn't face any complications during implementation.

What's my experience with pricing, setup cost, and licensing?

The pricing of the solution is quite high. It's something that could be worked on.

Which other solutions did I evaluate?

We evaluated a few other solutions. We knew the products of VM-Ware and others like Oracle VM and so, however not so much about their cloud management. 

We have looked into the OpenStack and implemented some OpenStack, however, it is not quite in the same territory. With CloudForms, for example, we can manage OpenStack, however, OpenStack can manage itself only, and not other platforms.

What other advice do I have?

We're partners with Red Hat.

I'm not sure of which version of the solution we are using. It's some aspect of version four.

We use both hybrid and on-premises deployment models.

On a scale from one to ten, I would rate the solution at a five.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Gagan Pattanayak - PeerSpot reviewer
Chief Revenue Officer at a tech services company with 51-200 employees
Real User
Top 5
Straightforward to set up and reasonably-priced, but the integration with other tools is limited
Pros and Cons
  • "The most valuable feature is Optima, which is something that we use quite extensively."
  • "Technical support is an area that can be improved."

What is our primary use case?

We are a provider of cloud solutions and the RightScale Cloud Management Platform is one of the products that we implement for our clients.

What is most valuable?

The most valuable feature is Optima, which is something that we use quite extensively.

What needs improvement?

Technical support is an area that can be improved.

If you are looking for a lot of automation then, because there are domain-specific languages, there is a learning curve. Once you learn that, and the language is not that difficult, it is okay.

There are a limited number of integrations. I would like to be able to integrate natively with a few other infrastructure tools.

For how long have I used the solution?

We have been working with this platform for about six months.

What do I think about the stability of the solution?

In terms of stability, we have had no problems up to this point.

What do I think about the scalability of the solution?

This is a scalable product. Our clients are medium-sized companies.

How are customer service and technical support?

Technical support is something that can improve, but we have our own technical team so we have not had to rely on them.

Which solution did I use previously and why did I switch?

We have worked extensively on Red Hat CloudForms, which is now part of IBM Cloud Pak. There are some features in Cloud Pak that are not there in this product.

How was the initial setup?

The initial setup is straightforward. 

What about the implementation team?

We have our own team that provides technical support internally.

What's my experience with pricing, setup cost, and licensing?

The pricing for this product works differently, as they charge you based on your cloud spend. The price is higher than an open-source product, or CloudForms, or IBM Cloud Pak, but it is still not very high. It's okay.

Which other solutions did I evaluate?

We did a POC with vRealize, and one with CloudCheckr.

What other advice do I have?

On the cloud management side, this product works well and there is nothing that our customers have mentioned they would like to have improved.

As a product, it is pretty well designed. My only real complaint is about the technical support. That said, if you have your own team then it's not a big issue.

I would rate this solution a seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Virtualization Management Tools
September 2022
Get our free report covering VMware, IBM, VMware, and other competitors of VMware Aria Operations. Updated: September 2022.
635,162 professionals have used our research since 2012.