What is your primary use case for VMware vRealize Automation (vRA)?

My customers use it to build their private cloud infrastructure.

I use the solution to provision virtual machines.

Currently, our usage of VMware Aria Automation is relatively light, mainly focused on automating VMs. However, we aim to broaden our use cases to include more complex scenarios, such as integrating with ServiceNow for end-to-end automation from request to execution. Our goal is to transition towards self-service and comprehensive automation.

We use VMware Aria Automation for autoscaling. We have multiple databases on multiple nodes. We leverage Aria Automation to migrate workloads to other nodes during the downfall. Additionally, it facilitates training VMs for rapid deployment as needed.

VMware Aria Automation is mainly used with vRealize Orchestration to orchestrate provisioning. It segregates resource usage among different teams. If there are various tenants utilizing resources, vRA is essential for efficiently managing resource allocation. Whether it's provisioning machines in our data center, supporting customer infrastructure in AWS, Azure, or different vCenters, vRA streamlines the process. Instead of navigating through various console endpoints for provisioning workloads, vRA allows automation with a single click. This means we can automate the provisioning of not just a plain VM or OS but also include applications and databases in a single click. So, we can initiate the process, go about our tasks, and, within 30 to 40 minutes, depending on integrations, our VMs will be built. It significantly reduces manual efforts, and that's why it's called automation. With one click, we can get not just one but as many VMs as needed, with databases installed, all at the click of a button. It's a crucial and necessary product that people have been increasingly adopting.

We are a service integrator. For example, a customer might have a roadmap to migrate to the cloud and want to have a single cloud management platform to manage their virtual machines on both public and private clouds. They need a CMP layer. There are multiple tools that we use for this. For example, we use VMware vSphere for virtualization and automation. I also use other products, such as IBM, which is a multi-cloud management platform for managing workloads running on public clouds (Azure, AWS, and GCP) and on-premises VMware vSphere virtualized environments. So, I use VMware products, such as vSAN and VMware, for virtualization and software.

We use this technology including VMware to support our customers' critical information systems.

VMware Aria Automation is used for automation.

When I started working with VMware Aria Automation, I used it mostly to automate the server build process. We completely automated the entire VM-build and post-build processes. I then used the tool at another organization in relation to CICD pipelines. We now see more hybrid cloud scenarios and enrollment of network automation as well.

Our company uses the solution to have better insights for our on-premises infrastructure. We use some metrics to decide the placement of workloads based on available capacity. We integrate with automation and make dynamic decisions while working on workflows. We are moving a lot of our infrastructure to the cloud so are reducing use of the solution. Right now, we have twenty developers who perform automation tasks.

We primarily use it to automate workloads.

VMware Automation allows you to deploy your blueprint on-prem or on a public cloud, so you have a consistent, unified service catalog. Users can request revisions to our infrastructure, applications, and resources from one portal on the private or public cloud. We only have one or two people with the knowledge and experience to use vRA and the vRA Orchestrator.

Mostly, vRA is for automating deployment. We use it with templates to deploy and maintain compliance based on the certifications we have. It's a way to maintain consistency across cloud and data center environments. We have about 30 to 40 engineers. They are primarily support engineers what we call platform hybrid teams. They create templates and help customers deploy VMs.

I'm not a decision-maker at my current firm. It is a huge company called Allianz Technology. We have vRealize deployed, and I'm part of the administration team. We manage our infrastructure and compute storage as well as the virtualization part with vRA. We have a lot of internal customers and entities of Allianz whom we treat as customers. They make use of the internal cloud portal to spin up VMs and manage them. Our vRA 8.0 is a distributed deployment in Europe, the US, and Australia.

We are using it for infrastructure service, automating things in Active Directory, and deploying Microsoft SQL and Oracle databases. We are also using it to automate some scenarios within our infrastructure.

I was part of the VMware team, doing a double role at VMware: * Leading a sales team for the large financial institutions, the top 50. * Defining what the roadmap for vRealize suite should be. I worked for a consulting company. We helped a lot of customers with many things for vRA from provisioning workflows automation to approvals and policies management. The solution provides a multi-cloud, self-service, infrastructure-as-a-service cloud consumption and delivery layer. vRA 7 was mostly focused on VMware-based internal clouds with a little bit of external clouds. vRA 8 is multi-cloud, which you can host on-prem too. Everybody is moving away to use the cloud, so it is pretty much a done deal that you need to have it.

The goal was to bring the automation process to our customers using virtual machines. We were looking to do the hybrid connection with AWS. It can run on Linux and several versions of Windows that we have.

Our use case is infrastructure automation, like self-service. We utilize all the blades that we had available in the computes, mostly going into VMware vCenter. When I have been using it, it has been mostly for private compute.

We were looking to have a single pane of glass (one console) to manage our complete infrastructure. It has helped us integrate having one user interface to manage our infrastructure and application templates. vRA's multi-cloud strategy is very important to us as a cloud service provider. The hardware that we use is Dell EMC.

Our primary use case is to deploy a private cloud. It has integrated well with an in-house-developed front end. Then we have the vRA's all over the backend and all the deployments in the vSphere.

Our primary use case of this solution is to automate with our various partners. It performs quite poorly, has a quite steep learning curve, and you have to invest an extraordinary amount of time to be able to do anything.

Primary use case is building a self-service portal for students at our university. It has performed quite well up until now.

We're moving from our normal IT support platform to be a service provider to our hospital. I am with a medical corporation managing more than 95 percent of the healthcare services in Qatar. There are many big hospitals under our IT Operations, and we're trying to move and be a service provider to them.

Our primary use case for this solution is for making a cloud through ICDC. We have to integrate them into many VM masses with vRA.

The primary use case is the automation of the cyber functionalities. Right now, it is performing well.

It is similar to a lab system for testing our software versions. We also use it for cloning customer environments for troubleshooting.

Our primary use case of this solution is to provide our clients with a virtual private cloud. It has been performing very well. We've had some multi-tenancy issues but VMware has been very supportive.

We use vRA to deliver automation on top of the solutions we provide which are desktops, servers, and multiple other products. These products require more actions to implement than what the vendor offers. Our primary use case is integrating customer's environments and performing data operations.

We're using it to automate the lifecycle of all the VMs that we are managing.

We use it to deploy virtual machines and integrate them into our structured environment.

We use it for the automation of VMs. It is performing okay.

We use it mainly for cloud automation with private cloud solutions. It works fine with the exception of integration with public clouds and multi-tenant data centers.

It's a SunBox for the people developing apps for the healthcare company. They can submit the project chapter, implement what they want based on the template that we have in the vRealize Automation, check, compare, and then at the end, they can build a project charter with all the needed components.

Our primary use case is to automate deployments of virtual machines and data actions. We have automated everything using vRA.

We use it for automating the deployment of multiple virtual machines.

My primary use case for this solution is to automate the development of the infrastructure. I deployed the VM for the development team.

We use it to deploy virtual machines and for self-managed firewalls within NSX. It's a self-service portal to speed up things.

We use it to be able to see everything within our VM space.

We use vRealize Automation for our customers. We are an internal service company and use vRA for a SAFE Self Service portal for our customers to provide VMs. We started five years ago with normal virtualization. Then, the platform grew and our customers requested additional services.

We primarily use it for restoration services.

It is primarily used for developers to spin up their own VMs and destroy them at will, afterwards my group spins it up in production machines. Probably, its most valuable feature is it takes time off of my schedule to quickly, securely, and conveniently deploy virtual machines, then I can work on other things.

We have used it mostly for our internal IT. We haven't really published it for customers or other groups to be able to use it. But we've actually just hit the surface. We've used it for rebooting servers, adding applications, automating some scripts; general things like that.

Our primary use case is for our QA department. They use it to deploy machines when they need to test something out. It has performed well. They are able to spin up a new instance of Windows virtual machine and test whatever use case they have, then turn it back down whenever they are done.

Our primary use case for the product is automating the basic rollout of a VM. Our experience with it has been very good. It's one of those things where, if you don't have to think about a product, it just does its thing, it's in the background, you don't have to worry about it, that's always handy.

Our primary use case for the product is self-service IT. VMware builds it as a portal for self-service and infrastructure as a service, which is what we are using it for, as we roll forward automating and orchestrating more tasks and being able to push things out of the hands of sys admins and into the hands of the users and app admins.

Primary use case is, generally, a DevOps lab-type environment that we have, spread across multiple locations throughout the United States. It's meant for a DevOps shop, for our developers to spin up, spin down VMs or applications, and do their testing.

Initially, we used it for private cloud. Now, we are trying to go with a hybrid model. In terms of performance, right now we're making revisions to ensure that it is hybrid-compatible. We have multiple engagements with VMware to facilitate it that.

Our primary use case is to automate the end-user request for either a VDI or a server virtual machine. It has taken some time to implement vRA. Over the different versions, we had a lot of problems doing some upgrades, but as of right now, it's working really well.

Our primary use cases are around deployments supporting DevOps, around service provisioning of IP addresses, DNS; self-service entitlement or enablement. And then, driving some workflow processes from our service marketplace, through automation, to actually have them execute within the infrastructure. It's performing pretty well.

It is used to deploy and manage unified configs in an engineering environment. It has performed pretty well.

The primary use case is to automate systems, and at a faster pace, so we can give them to our end-users faster.

As a software development company with a smaller staff, we've got a lot of technical people - the operations team and myself. Being able to give provisioning of environments over to our developers and the different teams has enabled them to put up environments faster and also freed up time for the IT team. This is really one of our bread and butter solutions for our developers.

We use vRealize Automation for monitoring and for some administration tasks. Anytime we do upgrades or patching, we just read the reports and it makes our lives easier.

We use it to automate workloads and it works well. The performance is as advertised.

Primary use case for us is how do we consolidate, how do we provision machines as fast as possible, provision databases? Also, how do we go from on-prem to cloud?

As a VMware partner, we use it to help us automate the deployment of VMs.

We use it for deploying, data recovery, and DR.

The primary use case is that it fronts VirtualCenter for our entire development environment. The current version performs well.

We use it to monitor our production VMware infrastructure. We use it to watch for things like resource contention and to automate around mostly similar needs.

My customer is the largest in Turkey, a university. The university has more than 48 servers in its data center, and they ask for between at least five to ten virtual machines daily. They were looking for a solution that automates VM creation, especially for SQL sites, because they have a very large SQL Server requirement, especially for project management. They are looking for an HPC solution. We performed a PoC at the customer's site using vRealize Automation. After that, they bought it for all their sockets, approximately 100 sockets.

DevOps is our primary use case. It's performing okay. We're getting ready to upgrade and move into an HA environment, so it will be much better.

Our primary use case is production IT, VM provisioning workloads. It performs pretty well most of the time.

We mainly use it for deploying SAP machines, SAP-type systems.

We are looking at doing automation at the enterprise-class level.

We use it to automate redundant tasks. We're limited to two guys, so automation is beneficial and we'll probably implement it with ServiceNow, down the road.

We use it for server deployments, typically. It's mostly for managing our own private cloud, for infrastructure-as-a-service deployments. It has performed well. We just recently went through an upgrade that had some hiccups to it, but it's been performing well for us.

For us, it's a software-defined data center, automating compute, network security, and storage; all the infrastructure components.

We use vRealize Automation not only to track the utilization of the environment but to deploy new VMs on a regular basis. When DevOps decide they need a whole bunch of VMs spun up for a new version of an application we are already running, we can duplicate everything we've already got, spin them all up, get them running. When they're done with whatever test case they have going on, we can either move them over to staging or we can completely wipe out the entire environment, and that's a lot easier to monitor and manage.

Everything that takes away from my having to do my own tasks is a very big plus. With Automation and a lot of the components we are looking at right now, I will be able to template everything out and streamline the process, which is going to save me a lot of time. My main focus is COOP sites and disaster recovery, so automating those makes my job easy.

Primary use case is for automatic deployment of VMware guests. It's performing as we want. We're not really asking anything too complex of it, but it does what we ask of it.

We use it for server virtualization.

We mostly use it for generating VMware instances. Things are getting to a point now where you need to be able to do more with less. Anything you can automate is always going to help you in the long run. I'm in the government sector. We're in extreme "do-more-with-less," so we're constantly looking for solutions where we can automate things that we're doing on a day-to-day basis. That's especially true when you have repeatable processes. Automation becomes paramount to get your mission completed in a timely fashion.

We are using it for developers to test code. Our Customer Care uses it to troubleshoot customer issues. We also have a training business unit and they deploy classes for customer training. We've been using it for four years now. It performs well. It does the functions we need. We do have some issues from time to time. I wish there was a little bit of more maturity out of the product, but it is getting better with every release.

We use it for about 1,000 clients at Santander Bank in Brazil and, nowadays, we have about 22,000 machines. It's performing very well.

We use it to deploy virtual machines in our traditional VMware environment. We don't use it as a front-end for our customers but it works fine for us, on the back-end.

The primary use case is going to be managed services. We're a hosting provider and we're looking to provide provisionable resources across multiple cloud platforms and to be able to support Day 2 Operations. We're trying to fully manage the lifecycle process as well as fully integrate with all of our management end-points, whether it would be inventory, ITSM, or backups, etc.

* We use it for our own private hosting. * We do services for departments within the State of California. * We have a large agency where we design and deploy an automation solution around vRealize Automation.

We use it to push out automation for all of our servers, not only to developers who are requesting what we call "cattle" - they want hundreds of servers to be able to test - but also to start getting away from the "onesie, twosie" builds, to save us more time on deploying so we can work on other projects.

It's our private cloud platform.

The primary use case is to deploy an automated self-service portal for virtual machines for testers and developers to use. It is performing well.

Automation and operations.

We use it for the deployment of new environments and multiple stacks, as well as deployment inside of NSX. It is also used for easy application deployment and container management.

The primary use is to automate the provisioning of applications that my organization uses as well as sells to customers.

Automating the data center.

We are using it to offer self-service capabilities to our customers, a self-service portal.

We use vRealize Automation for all of our court locations and the customers are able to, on any day of the week, 24/7, provision VMs at will and maintain them.

The primary use case for deployment of vRealize Automation was to facilitate a service provider web portal front-end to our Hosted Private Cloud and Business Continuity solution. This is a fully automated virtualized SDDC, using VMware as the base hypervisor. We also incorporate NSX for network automation, vCenter Orchestrator for workflow execution, and additional software packages to support the service as a whole (vROps, Log Insight, Network Insight, NSX Manager, etc.). Our core networking is made up of a spine/leaf architecture using Cisco ACI/APIC and our storage is virtualized behind a Hitachi (HDS). We use SnapMirror and NetBackup as our DR tools. We needed vRA to easily integrate with our hypervisor, orchestration, security (tenant segmentation, PCI), workflows, custom code, and internal monitoring/management tools. Since we didn’t have time to develop our own web front-end during the development sprints, vRA saved considerable time and resource cycles. Its ability to easily integrate with all of the VMware cloud products as well as public cloud providers, like AWS and Azure, out-of-the-box, makes it an even more powerful tool.