It is highly scalable.

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

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

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

Nutanix Cloud Manager is highly scalable. I've been a part of various Wisconsin Nutanix user groups where people have upwards of a hundred nodes or more. While we may never get that large for our environment, it certainly does scale to a size that we could only ever imagine. I'm thinking we might add a node or two and an additional piece of hardware, but people are out there buying a lot more.

We can scale it.

Currently, there are about 980 users on all nine of our casino properties. 

We can go a few more years with the package that we currently have. Right now, the solution is running perfectly. We may have to look at increasing memory in the next year or so. While our CPU and space are fine, it is the memory where we need a bit more. Right now, we have about 28 terabytes but are using about seven.

Its scalability is great. That was the whole reason we bought it. It was the fact that it can handle so many accounts at once, all in one dashboard to get to things. It's great.

We have 40,000 students and almost the same amount of staff. The University of California is the largest employer in the State of California. We work mostly with UC San Diego itself, but we also work with CloudBank in the National Science Foundation (NFS) to give out awards for cloud usage for researchers from all over the country. It is a big academic, an R1, with about two billion a year in research and other things. 

Nutanix Cloud Manager is scalable. 

The solution is very scalable, and we like the configuration options. You can pick and choose. You don't just have a standard way of doing things. It's pretty dynamic. 

This solution effectively addresses our current automation requirements, especially with regard to repetitive tasks that the team needs to learn how to automate. 

As our company expands, we are interested in shifting the bulk of our workloads away from the public cloud and into our private cloud clusters.

Nutanix Cloud Manager (NCM) offers a lot of automation capabilities that we can take advantage of in the future. While there are already some basic automation features like Nutanix Move, there is significant potential for additional automation within NCM. 

This automation will greatly assist us in scaling our operations without the need for manual repetition. As we continue to explore NCM and prepare for transitioning away from the public cloud, we can leverage a substantial amount of automation to streamline our processes.

The scalability of the system is straightforward, even from a hardware standpoint. 

Simply adding servers to the data center and integrating them into the cluster is a remarkably effortless process. 

I have not come across a solution that offers such ease of scalability.

Cloud Manager scales linearly with the best performance. There's something called Controller Virtual machine available on every node. When you scale the solution, it never affects your performance.

The environment is pretty much stable, though at a year and a half, it is still new for us. In my experience, it is stable. We find it a very stable solution compared to other vendors. I think we have the best solution.

Scalibilty is second name to Nutanix. Scale-out of Nutanix Calm is just another node on the target cluster if things get sluggish.

Since Calm is dependent on Prism Central  you could simply scale-out that too. Nutanix has sizing recommandations for that, conveniently packed at Identify Prism Central requirements - Virtual Ramblings. Up to 25000 VMs should fulfill most requirements.

The goal is to optimize what they currently have and detect any anomalies, particularly in terms of security, for future expansion. This is why they are using it.

Perhaps it would be better if NCM could be optimized to consume fewer resources.

Nutanix is a scalable solution.

We are looking forward to it. We only have a small NCM platform built, but as we move forward, we look forward to using it for other use cases. We definitely want to explore expanding our NCM presence in Azure or in AWS.

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.

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.

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

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.

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

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.

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.

It is a scalable solution.

The details around scaling, like Prism Central and scaling the resources, are highly technical and get highly specific per use case, but it's always scalable. You can always find the documentation very easily, and it's very straightforward to do so.

The solution is very scalable and very easy to scale. I'd rate the ease of expansion ten out of ten. We don't need a physical installation. The cloud makes it very simple. 

We work mostly with enterprise-level organizations. 

The scalability of the solution is way better than anything else. Everything is plug-and-play. That part is pretty awesome.

In terms of scalability, it just works. It has high availability, and we haven't run into any issues where we have needed to scale up.

We have Nutanix clusters located in at least half of our Vopak locations. This year we rolled out the Nutanix platform to 30 locations and, in the next year, 30 additional locations will follow. Currently, the six users of the solution are involved in infrastructure development on the DevOps team. Those are the people who are building on top of Calm.

It is a scalable solution. Our enterprise has three clusters dedicated to it.

It's as scalable as the overall infrastructure. It's great.

I would expect Nutanix Cloud Manager to scale. Since our shop is pretty small, we would not plan to scale the solution, but based on what I've read, it is a scalable solution.

It's good for up to mid-sized enterprises. For us, a mid-segment company has ten thousand virtual machines. They are running somewhere around 400 nodes of containers for elements. One of my big customers is running 6,600 Nutanix nodes.

I have 30 clusters and have not had any problems with scalability.

It's also scalable. We use it across multiple locations and multiple teams. 

Unfortunately, we don't have any plans to increase our usage of it. I have voiced some frustrations, internally, over the years, that I have not gotten to expand and use the product the way it should be used. I wish we could have really given it a lot more play in our shop.

Nutanix Calm, is another portion piece I wanted to look at.

Nutanix is scalable. 

I rate Nutanix 10 out of 10 for scalability. Nutanix is highly scalable on the right version with the right hardware. 

It can grow with my environment. With Prism Pro, it manages your entire Nutanix cluster. If I add more clusters onto that, I can manage it from the Prism Center, I just need to redistribute the cluster, then I can manage it like it's one machine. It doesn't matter if I have two or 100 clusters, I can manage it from a single point, which is good. This saves me time because if I need to update (for example), I can update a lot of machines from 1-click. Then, it will go on each machine of the clusters and update them. I am saving at least 40 percent of my time managing multiple clusters from a single point.

I am using the solution’s machine learning algorithms for things like predictive capacity planning or other functions but I already sp;have good capacity inside of my cluster. I think if I create new machines, it is really good but I am not using it so much. I have enough capacity at the moment. For the tools on Prism, I'm not planning to create so many machines. However, I already do use the tool and the predictions are really amazing. It is really helpful for planning in advance (e.g., six months, one year, or two years) the capacity for the cluster. I can estimate what will be the capacity of my cluster. For example, if I am a planning for one year to create 20 machines with a specific size, the machine learning algorithms can show me if I have enough capacity on the cluster to do that or if I need to expand the cluster. 

Between my colleagues from the operations team and me, there are around six people using it. I'm the owner of the contract for this company as the infrastructure architect. The other five guys are Linux and Windows administrators.

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

It is Software as a Service, so there is nothing to scale. We can target customers with a small cloud footprint or customers that are huge. There is no need to scale anything because it's SaaS.

It's a great technology and it's part of the larger ecosystem which scales really real. Because of how it is tied into the Nutanix ecosystem, I am confident that scalability, and maintainability, will be very easy and smooth in the long term.

I would rate scalability a seven out of ten. 

From my understanding, the solution can very easily be scaled up. The scalability should be really good.

Nutanix Cloud Manager is the next version of Prism Pro. If we renew Nutanix next year, we will use NCM. It is a better version of Prism Pro and I'm looking forward to that.

The solution can scale as needed.

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

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

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

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

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

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

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

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

I'm very satisfied with the product's scalability since it's very good.

Nutanix has very good scalability as long as you are not limited to just their features. This is a common issue with virtualized solutions, where the more features you want, the more you have to pay. However, all virtualized solutions can scale well, including Nutanix.

In my opinion, Nutanix's ability to scale well is due to its partnership with different vendors. They now offer regular BYO(Bring Your Own) computing and storage, which is not limited to only Nutanix appliances anymore. Other vendors, such as HPE and even Cisco can now be used, and you are not required to use Nutanix appliances. This has helped Nutanix to scale even better than before.

So overall, the ability to use different vendors and not be locked into a Nutanix appliance has been a big advantage for users.

Extremely easy to add nodes to the clusters.

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

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

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

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

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

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

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

The scalability is also good. We have around 4,000 users across India and we are planning to increase our node in six or seven months.

Currently, we need no more than four or five staff to operate the Nutanix infra.

It really great lets you grow and manage everything from one point Prism.

It's very scalable. We just have one Prism Pro VM. I know you can scale out the setup where you have multiple Prism Pro instances if you have a bigger environment. Our environment is small so we only needed one Prism Pro instance. That made it simple for us to get it up and going. If you do have multiple instances, they act like a cluster to balance out resources and manage different clusters. You can definitely scale out.

I would recommend keeping the cluster to smaller number of members which will help in faster maintenance and upgradation activities.

Scalability is very technical now. I think you can install a second instance. 

We are three people that work with Prism Central and they're all in service core IT. It's the people from the infrastructure.

We have an external partner that does the maintenance. We will be getting it handed over to us, but until now this external company does all of the maintenance and upgrades. They announce that there is a new upgrade, we plan when we can do it, and then we participate.

We are still in the learning curve and we need really a company that has a lot of experience because it's mission-critical. We have systems that are very mission-critical. We really should be sure that we have people that really know what to do. When we are over the learning curve, then maybe we can take it over. For now, we give all of this stuff to an external company.

We don't use Nutanix as a self-service platform. In our IT, we manage Central so it's not that we use it like many other companies. Like a company that can say "Okay. This department can create the resources that I need" themselves. Now, it all comes into the Central place and we do that. It's still in this little team. Only these core IT people have contact with the Nutanix dashboards.

We have blueprints in the Marketplace but it's not a goal that we made for other people. When a service asks for resources, they communicate to us what they need and we create it with this. When they have a project and they need some new software, they tell us, "Okay. We need this database, those application servers," and then we set up it for them.

We have scaled Nutanix Prism Pro at least 300 percent after deploying it and we are still not at the bottleneck point. Our current footprint is quite large, we are not seeing any challenges. However, each cluster will have to be kept at a finite number. If the cluster size should is too big, your maintenance window will increase for a very long time. If you can keep cluster size to a minimum, then it will be easy for you. For example, if you have a hundred node cluster and have to do maintenance, then the patching will be happening on a single node layer. Patching all the servers one by one will take too much time for us. It makes sense, in the design phase, to keep those clusters to a smaller figure, approximately 20 nodes.

I have not used previous solutions

It is very easy to scale out, you can just keep adding node to have more capacity, and mange from the same prism.

The scalability is high.

The sky is the limit with the scalability of this solution, new nodes and cluster integrate seamlessly and quickly.

Scalability is one of the intrinsic characteristics of environments. It is a perfect web scale model

It is scalable. We work with small, medium, and enterprise-size customers.