I cannot recall any specific features that need improvement. Nutanix likely has a big backlog of requested features from their clients. We'd like the demos to be longer - maybe two to three months. Some clients need much more time for a POC.
Tech Lead Platform Services | Infrastructure Consultant at Vopak
Consultant
2021-10-25T10:29:00Z
Oct 25, 2021
There is room for improvement in the remote script execution. The way logs are shown in Calm, it's not always keeping up properly. It's really the interface that needs attention there. I believe it is something being worked on at the moment by Nutanix. Also, the integrated scripting language, which is a very limited form of Python, should be improved. It should be made into a more modern version of Python, and maybe other languages as well. I would also like to see an improved ability to integrate with APIs.
Leader of Environments and Automation at a financial services firm with 1,001-5,000 employees
Real User
2021-04-22T15:04:00Z
Apr 22, 2021
One thing that comes directly to mind is how they manage version control. I would love to see Calm create a built-in source control feature, one that we could tie into a repository and it would self-manage changes in versions. All the version control is built within Calm right now. I would love to see that integrated with an external repository and make it easy to tie it into GitHub or Git repositories.
Project Manager at a healthcare company with 501-1,000 employees
Real User
2020-09-30T08:03:00Z
Sep 30, 2020
As I mentioned, we use now CaaS from SUSE; it's SUSE's Kubernetes. But it's now changing. They have bought Rancher and I think that CaaS will be replaced by Rancher. So currently, to manage a Kubernetes cluster we have SUSE. But with Karbon we can manage Kubernetes with Calm. But I don't don't know how much we can do with Calm there. There could be room for improvement, although I'm not entirely sure. It's on our agenda to look into Karbon in relation to Calm and what we can do with them together. I don't know how deeply they are integrated. It's not necessarily something that is wrong. Karbon is a new product. It's been around for about two years. The integration is growing. Last year is when it started working with Calm. It's more a concept still. My wish is that it will really be supported, but I cannot say for sure. Again, I'm not saying something is wrong here. I think it's a very good platform, but there is always room of improvement.
The list of blueprints and applications could be more configurable so you see all the fields you need and not just some predefined fields which are not customizable now. There are lots of pre-defined blueprints in the online marketplace but often it is a trial and error to get the pre-defined blueprints to work due to some firewall issues. But that may because of our internal firewall being too restrictive. More support for VMware environments would be great. Most blueprints are tailored for Nutanix AHV or the cloud providers. Hyper-V is currently not supported.
Head of Operations at a university with 1,001-5,000 employees
Real User
2020-06-18T08:15:00Z
Jun 18, 2020
Even though it's a lot easier, it could be a bit slicker for the end-users. The ability to create their own blueprints could be without their having to understand the details of what they're trying to do. If they could just tick this, this, this, and this — whatever they need — and it would go spinning those up, that would be better. Now, we still guide them quite a bit.
System Engineer at a non-tech company with 10,001+ employees
Real User
2020-04-14T06:13:00Z
Apr 14, 2020
There is room for improvement in making the solution easier still. If you don't know Calm, it's not so easy to use. Blueprint repositories are not all in the same place. Sometimes they are in the Marketplace, sometimes they are on the cluster. And from start to finish, it's not so easy to create a blueprint.
Nutanix Cloud Manager (NCM) is a cloud management tool that drives consistent governance across private and public clouds for its users. The solution brings simplicity and ease of use to managing and building cloud deployments by providing a unified multicloud management that addresses common cloud adoption challenges. Nutanix Cloud Manager offers four key value drivers:
Intelligent operations: They include monitoring, insights, and automated remediation.
Self-service and orchestration:...
I am very satisfied with the solution. The pricing of the solution is an area of concern that needs improvement.
I cannot recall any specific features that need improvement. Nutanix likely has a big backlog of requested features from their clients. We'd like the demos to be longer - maybe two to three months. Some clients need much more time for a POC.
There is room for improvement in the remote script execution. The way logs are shown in Calm, it's not always keeping up properly. It's really the interface that needs attention there. I believe it is something being worked on at the moment by Nutanix. Also, the integrated scripting language, which is a very limited form of Python, should be improved. It should be made into a more modern version of Python, and maybe other languages as well. I would also like to see an improved ability to integrate with APIs.
One thing that comes directly to mind is how they manage version control. I would love to see Calm create a built-in source control feature, one that we could tie into a repository and it would self-manage changes in versions. All the version control is built within Calm right now. I would love to see that integrated with an external repository and make it easy to tie it into GitHub or Git repositories.
As I mentioned, we use now CaaS from SUSE; it's SUSE's Kubernetes. But it's now changing. They have bought Rancher and I think that CaaS will be replaced by Rancher. So currently, to manage a Kubernetes cluster we have SUSE. But with Karbon we can manage Kubernetes with Calm. But I don't don't know how much we can do with Calm there. There could be room for improvement, although I'm not entirely sure. It's on our agenda to look into Karbon in relation to Calm and what we can do with them together. I don't know how deeply they are integrated. It's not necessarily something that is wrong. Karbon is a new product. It's been around for about two years. The integration is growing. Last year is when it started working with Calm. It's more a concept still. My wish is that it will really be supported, but I cannot say for sure. Again, I'm not saying something is wrong here. I think it's a very good platform, but there is always room of improvement.
The list of blueprints and applications could be more configurable so you see all the fields you need and not just some predefined fields which are not customizable now. There are lots of pre-defined blueprints in the online marketplace but often it is a trial and error to get the pre-defined blueprints to work due to some firewall issues. But that may because of our internal firewall being too restrictive. More support for VMware environments would be great. Most blueprints are tailored for Nutanix AHV or the cloud providers. Hyper-V is currently not supported.
Even though it's a lot easier, it could be a bit slicker for the end-users. The ability to create their own blueprints could be without their having to understand the details of what they're trying to do. If they could just tick this, this, this, and this — whatever they need — and it would go spinning those up, that would be better. Now, we still guide them quite a bit.
There is room for improvement in making the solution easier still. If you don't know Calm, it's not so easy to use. Blueprint repositories are not all in the same place. Sometimes they are in the Marketplace, sometimes they are on the cluster. And from start to finish, it's not so easy to create a blueprint.