"The solution can scale."
"One of the most valuable features is automation. We are doing automation infrastructure, which allows us to automate regular tasks. This solution provides us with a service catalog, like building new services and automating daily tasks."
"Ansible provides great reliability when coupled with a versioning system (git). It helps providing predictability to the network by knowing exactly what's being pushed after validating it in production."
"One of the most valuable features is that Ansible is agentless. It does not have dependencies, other than Python, which is very generic in terms of dependencies for all systems and for any environment. Being agentless, Ansible is very convenient for everything."
"It has improved our organization through provisioning and security hardening. When we do get a new VM, we have been able to bring on a provisioned machine in less than a day. This morning alone, I provisioned two machines within an hour. I am talking about hardening, installing antivirus software on it, and creating user accounts because the Playbooks were predesigned. From the time we got the servers to the actual hand-off, it takes less than an hour. We are talking about having the servers actually authenticate Red Hat Satellites and run the yum updates. All of that can be done within an hour."
"It has an easy-to-use interface. It is REST API driven, and it integrates with Active Directory. It provides the ability to grant permissions to other users who would not necessarily have those permissions via the GUI so that they could run other people's jobs. For example, you could have the Oracle team grant permissions to the Linux team so that they can use each of those playbooks or each other's code. It is called shift-left."
"Being a game-changer in configuration management software is what has made Ansible so popular and widespread. Much of IT is based on SSH direct connectivity with a need for running infrastructure in an agentless way, and that has been a big plus. SSH has become a great security standard for managing servers. The whole thing has really become an out-of-the-box solution for managing a Unix estate."
"There are new modules available, which help to simplify the workflow. That is what we like about it."
"The automation part is most valuable. Because it is a VMware product, the automation capabilities that come with vRA are pretty extensive. We can integrate and build a lot of features on top of it, which makes it extremely useful for us."
"The DevOps for infrastructure capabilities has saved time for our developers by automating processes and reducing provisioning time. Task time has been reduced by 40 percent."
"We provided the ability to request virtual machines to our end users. Before, this was a very manual process, which took engineers to do. Now, it's an automated process."
"A lot of its DevOps for infrastructure capabilities improve reliability. Much effort was put in by some customers, like a large automobile manufacturer, a large telecom, and two large banks, to achieve a certain level of capabilities in this space. These DevOps for infrastructure capabilities have saved time for developers. In one use case for a large marketplace, a typical release cycle took about 80 hours and was brought down to three hours by automating deployment for developers. The quicker that deployments happen, the faster that they can do their product release cycles."
"Having an enterprise service catalog and being able to automate various parts of our infrastructure are among the most important components."
"vRA has enabled us to derive value from the cloud faster. It is five to six times faster than traditional solutions."
"The most valuable feature is being able to deploy a virtual machine from a low level. We can automate everything including network configuration, firewall configuration, storage, storage attachment, OS deployment, middleware, and so forth."
"The preset policies and templates are useful. I would say that vRA is one of the best solutions we have. The CI/CD features also look helpful even though we aren't using them at the moment. We plan to get more involved and train our customers as much as possible."
"Some of the modules in Ansible could be a bit more mature. There is still a little room for further development. Some performance aspects could be improved, perhaps in the form of parallelism within Ansible."
"The area which I feel can be improved is the custom modules. For example, there are something like 106 official modules available in the Ansible library. A year ago, that number was somewhere around 58. While Ansible is improving day by day, this can be improved more. For instance, when you need to configure in the cloud, you need to write up a module for that."
"Improvements should be made in terms of execution speed, which is, I believe, the most lacking feature. Aside from that, re-triggering a failed task is another useful feature."
"Ansible has just been upgraded, and the only issue that we are seeing at the moment is that the user interface can be slow. We're currently investigating the refresh period with Red Hat when you click a job and run a job. It seems that the buffer no longer runs in real-time. We haven't discovered whether that's partially an issue with our environment, but Red Hat has come back and said that they're working on a couple of bugs in the background. We've upgraded to that version in the last six months, and that's the only issue that we've seen."
"Accessibility. Ansible uses a CLI by default. Those accustomed to it can find their way and adopt the YAML files easily over time. But, some users are more comfortable using UIs..."
"When you set up Playbooks, I may have one version of the Playbook, but another member of the team may have a different vision, and we will not know which version is correct. We want to have one central repository for managing the different versions of Playbooks, so we can have better collaboration among team members. This is our use case for using Git version control."
"Ansible is great, but there are not many modules. You can do about 80% to 90% of things by using commands, but more modules should be added. We cannot do some of the things in Ansible. In Red Hat, we have the YUM package manager, and there are certain options that we can pass through YUM. To install the Docker Community Edition, I'll write the yum install docker-ce command, but because the Docker Community Edition is not compatible with RHEL 8, I will have to use the nobest option, such as yum install docker-ce --nobest. The nobest option installs the most stable version that can be installed on a particular system. In Ansible, the nobest option is not there. So, it needs some improvements in terms of options. There should be more options, keywords, and modules."
"We would like support for the post-integration of this product before cloud frameworks because right now their approach is to avoid using on-premises activities and move everything to the cloud."
"We are migrating from vRA version 7 to 8, but the migration is really hectic and time-consuming. There are no straightforward paths to migrate. We are doing an entirely new deployment to go to vRA version 8.0, then somehow get all of the VMs to vRA 8.0. Therefore, it would have been great if VMware had some solutions to upgrade from vRA 7 to 8 seamlessly. This includes the management of all the objects or VMs from the older version. Unfortunately, it is not there."
"Multitenancy management is a little bit difficult to do, so it is an area that can be improved."
"They should concentrate on navigation and service improvements."
"With the workflow aspect, which has manual intervention, a policy needs to be approved by somebody. There could be better management of that piece with better templates. It is like a workflow engine, but does not have enough example templates to do certain things. A lot of people waste a lot of time trying to figure out the same thing, and everybody is trying to figure out the same thing, e.g., how to make a MySQL cluster in a Windows environment?"
"It needs to be more dynamic with variable customization to make new workloads more reliable. It also needs to be faster. We are exploring vRA version 8 right now and maybe what I'm requesting is available in the new version, but we haven't yet explored it fully."
"The solution could be lighter. As an administrator, I would like to simplify the number of services I need to deploy. They took a significant step in that direction by removing all the Windows dependencies that we had in the past, but there are still a lot of services consuming resources."
"VMware needs to make it to where it is not as custom. Right now, you spend a lot of time making the services work. In order to get it up and running initially, that takes time."
"The initial setup was complex from beginning to delivery. The current version is a bit more complex than version 7 to deploy."
VMware vRealize Automation (vRA) is the most up-to-date infrastructure automation platform using performance-based administration and compliance. vRA is created to facilitate organizations to better manage and secure self-service clouds and multi-cloud automation using administration and DevOps-based infrastructure delivery. Organizations using vRA receive the advantages of improved flexibility, reliability, speed, and scalability while they minimize the overall challenges in managing their IT environments, simplify the overall IT process, and deliver a DevOps-ready platform.
vRA seamlessly automates the provision of IT services by creating a platform for delivering and managing applications. With the utilization of its various robust aspects, vRA allows for speedy workflow automation, intuitive automated application infrastructure delivery, seamless multi-cloud provisioning, and secure software configuration management.
This robust cloud automation software lets you deploy across a multi-vendor hybrid cloud infrastructure, giving you both flexibility and investment protection for current and future technology choices.
Benefits of VMware vRealize Automation (vRA)
Features of VMware vRealize Automation (vRA)
Reviews from Real Users
Awais J., CTO/CEO at a tech services company, says, "The automation part is most valuable. Because it is a VMware product, the automation capabilities that come with vRA are pretty extensive. We can integrate and build a lot of features on top of it, which makes it extremely useful for us."
Aravind N., IT Service Manager at Allianz, relates, “vRA helps automate deployment for developers. We do a lot of orchestration or customization within our environment so it will suit each of our customers. We have different business units that have their own templates. This solution has made it very simple for developers. In a way, a layman or NOC guy can deploy a VM. Once they are familiar with the offerings, they can just deploy it without knowing what is going on in the back-end.”
Red Hat Ansible Automation Platform is ranked 2nd in Configuration Management with 9 reviews while VMware vRealize Automation (vRA) is ranked 2nd in Cloud Management with 9 reviews. Red Hat Ansible Automation Platform is rated 8.6, while VMware vRealize Automation (vRA) is rated 8.2. The top reviewer of Red Hat Ansible Automation Platform writes "Enables us to efficiently manage an almost unlimited number of nodes". On the other hand, the top reviewer of VMware vRealize Automation (vRA) writes "Allows for a lot of orchestration or customization within our environment to suit our customers". Red Hat Ansible Automation Platform is most compared with Microsoft Endpoint Configuration Manager, Red Hat Satellite, Microsoft Azure DevOps, BigFix and BMC TrueSight Server Automation, whereas VMware vRealize Automation (vRA) is most compared with vCloud Director, VMware vRealize Operations (vROps), vCenter Orchestrator, SaltStack and Nutanix Cloud Manager Self-Service.
We monitor all Configuration Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.