VMware Aria Automation Reviews

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.

Aria Automation gives you the flexibility to deploy tenants with customized blueprints for permissions and policies. Version 7.8 consisted of multiple products, so you had to deploy a lot of virtual machines on one of the servers.  Starting from 8.6, VMware consolidated all the components into one Linux appliance. This allows the option to use vRA or DevOps capabilities.

They could extend the ability to use vRealize Orchestrator Automation for organizations with multiple tenants. It should be easier to operate and extend different capabilities from vRealize Orchestrator. Currently, it's difficult to build advanced services in Aria Automation because you need to use the vRealize Orchestrator. 

I have been using Aria Automation for about three or four years

Aria Automation is stable.

You can deploy a single node or an enterprise cluster consisting of three nodes. 

I rate VMware support six out of 10. 

Setting up Aria Automation is difficult. The complexity varies depending on the environment size and infrastructure. It has a lot of prerequisites. For example, it has to have a firewall prepared before installation. Aria Automation is deployed through an installer called vRealize that integrates VMware identity manager, Aria Automation, and the vRealize Lifecycle Manager. The deployment takes about three days.

I rate VMware Aria Automation seven out of 10. Aria Automation needs products like vRealize Orchestrator to extend its capabilities and accessibility. If you are using Aria Automation by itself, you won't get the features you want, and the license cost is high. It needs to be cheaper, easier to use, and have more native capabilities. 

Before deploying Aria Automation, you need to know the prerequisites for the nodes. Each appliance consists of multiple components, and each has its own log. You need to understand your use case and what you want to use so you can customize the services you need to provide. For simple services, you can use only Aria Automation. If you need to customize advanced services, you will have to purchase vRealize Orchestrator and also CI/CD DevOps tools.

We use SaltStack to configure virtual machines, ESXi hosts, or any Windows product.

The product’s most valuable feature is its ability to provide environmental security.

There could be better initial documentation for the product.

We have been using SaltStack for six months now.

It is a stable product. I rate its stability an eight out of ten.

The platform scales well. We can configure multiple systems. I rate its scalability a ten out of ten.

We can contact VMware support. But we find out the solutions ourselves. Although, its online documentation needs a lot of improvement.

Negative

We have deployed SaltStack on a hybrid cloud. It is difficult to set up and requires one executive to operate the deployment. I rate the process a six out of ten.

It is an open-source product.

The product works great for changing configurations. I recommend it for the DevSecOps environment. I rate it a seven out of ten as it is not user-friendly.

We primarily use it to automate workloads.

The most valuable features are the multimachine blueprint and advanced designer configuration.

Automation or scripting should be simplified so that administrators who are not experts can have a better grasp of automation.

My organization has been working with this solution for about six years.

We have had no issues with stability.

VMware Aria Automation is a very scalable solution because it integrates well with a couple of leading products in the industry. For products that are not already integrated, there are plugins or adapters that can be used with customization. 

Because we are a large organization, we probably have more than 30 people who use the solution.

The basic installation is quite easy. If you have all of the prerequisites ready, then within two to three working days the basic foundation can be created.

Two people could probably deploy and maintain one foundation of the solution.

We deployed the solution ourselves.

We have definitely seen an ROI because automation is directly related to productivity.

Try to use the maximum level of automation possible within VMware Aria Automation. It will help you to achieve the maximum results. This solution has a lot of other features other than provisioning, like tighter integration with third-party products, ISVs, backup software, and open APIs. To fully utilize the product, you would need to get into these areas along with normal provisioning.

On a scale from one to ten, I would rate VMware Aria Automation at nine.

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.

All the feedback that I have received so far from our administrators is very positive. The solution is user-friendly and intuitive.

1. Virtualization
2. The replication to our remote R&D data centers.

We would like them to improve the automation part. This is an upcoming area that we would like to focus on. We used to rely on other technologies to help us with VMware monitoring, but now, we're coming back to VMware technology. Hopefully, they will not take us down and provide something good. We have been watching their roadmaps, and it's promising. Therefore, I think it will be fine.

So far, stability has been good.

Scalability has been working fine.

Technical support is supportive. We are one of VMware's major customers in Qatar, so we receive good attention from them.

For the virtualization part, we have previously used Veeam.

We licensed VMware a long time ago. Now, we are moving from our legacy infrastructure to have a proper, private cloud environment.

Our upgrade experience was good.

We are a government service provider, so ROI is not a main KPI. However, we do plan to see ROI with any new implementation of new technologies being implemented within our environment.

We do regular technology refreshment from all our suppliers to be aware of the latest trends in the market and to select the most suitable ones which fit our needs.

We recommend VMware technologies to any of our colleagues or anyone asking to compare to other virtualization technologies in the market.

We have had VMware for more than twenty years. We are very old VMware customers and have a big setup.

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.

Digital transformation is more of a people problem than a technology problem in many cases. It is getting people used to the idea of self-service people and not having to go talk to the sys admin all the time, and empowering people to get things done. That's a real big thing. That's probably the biggest part of the change that this tool has on our organization: empowerment.

The solution has increased the infrastructure agility from people's perceptions of the infrastructure: Having an actual private cloud or something on-premise, which people can turn to a Window and provision things when they need it. The end result is it appears to be more agile, then the back-end is just the back end. 

• vRealize Automation has improved the speed of provisioning just by automating things, making people think about whether a human really needs to do something or can we make the machines do it for us. It is a lot faster to deploy things now.
• It has improved time to market. Just by improving them, making provisioning increases, time to provision, time to market is a definitely improved. 
• It makes a developer's life easier. They don't have to interact with their sys admins for everything anymore. It's an empowering thing.

We can automate a number of things which weren't automated before, then tie into things like VMware NSX and vRealize Operations Manager. We put things into their hands directly that were never there before, so not only do they feel empowered, but they can get their job done faster.

vRealize Automation on the back-end is still a little complicated. It has a lot of moving pieces, simplifying that from a pure infrastructure point of view would be a good thing. I would then like to have more out-of-the-box functionality and integrations with VMware components.

vRealize Automation stability is pretty good. They are always fixing bugs. The product team is doing a great job of addressing any issues that we might have.

In terms of scalability, vRA has connections to a lot of different systems. It's very flexible and an impressive product. It's almost scarily flexible.

We came to the conclusion that vRealize automation was right for us as part of an effort on our campus to consolidate IT from a real distributed model into a less distributed model, but still retain a lot of local control with departments.

A lot of higher education institutions have similar problems. People want to retain local control, but all the IT is spread out all over campus. This is a real problem. 

As we talked to people, a private cloud was the way we felt we needed to go: To be able to do self-provisioning and self-service for groups who really wanted it. We also wanted to be able to add additional advanced features, workflows, integration points, and approval processes, and vRealize Automation could do all of that. 

We were able to span from our simplest customer to our more complicated customer in the same product. This is why the product appealed to us.

I was involved in the initial setup of our environment.

The vRealize Automation team, when they released version 7 awhile ago, made immense improvements as far as being able to install and deploy the product, which has been super helpful. 

We track vRealize automation versions pretty closely. There are always new features which are of interest to us, bugs which have been fixed, and the upgrade process has been really smooth lately.

There is confusion between licensing levels. There are three different licensed versions of vRealize Automation, and there are different things which can happen in each of them. This is confusing.

vRealize automation really should be a front door to the whole VMware suite of products. The front door to a cloud: Just open it up, and let everyone do whatever they need.

We've been with vRealize Automation for a while now. 

OpenStack was pretty immature at the time that we were evaluating the solution. We also looked at Embotics and their stuff.

There are a lot of good options in this space. There is a lot of competition now. Do your due diligence around it. The VMware solutions stand on their own, but look around. Know what you are after: 

• Are you after infrastructure? 
• Are you after multi-cloud? 

Everything has a different focus.

The solution is getting better. VMware has been paying a lot of attention to it lately, and it's been inheriting a lot of their cloud efforts, user interface improvements, and getting more intuitive. It's a nice thing. To be able to build custom forms and do more things, which directly respond to our customer's needs.

If I had to rate the solution one to ten, I would give it a seven. There is room for improvement, but it looks like they are making those improvements and putting a lot of work into it.

It's our private cloud platform.

My engineers were able to pick it up quickly and we provisioned and created a private cloud in roughly three months.

Even with the virtualization, it would take us at least three or four days to create a VM. With vRA we have brought that down to seven minutes. The solution has helped increase infrastructure, agility, speed of provisioning, time to market, application agility. Everything got super fast.

It's also easier for IT to support developers. As soon as the developer wants a box, we can pretty much put it out there in a few minutes, instead of wading through a lot of manual paperwork and forms and email boxes and the like.

The solution is intuitive and user-friendly. It only took three months to start a private cloud. It was very good. Guys that didn't have a lot of knowledge in scripting picked up on it. Then I hired a VMware solutions architect and it just skyrocketed from there because he knew the ins and outs.

I can't say what new features I'd like right now because we're looking forward to the stuff that's in 7.5. I need some stick-time on 7.5 and then I can tell you what I want to see in 7.6 or 7.7.

It's very stable. We haven't had any issues and we've been using it for roughly two years. We're upgrading to the 7.5 now.

It scales fine. We've been scaling on storage but we actually have two divisions. We just deployed it to another division to help them out. The company I work for grows by acquisition so the new acquisitions are now getting this pointed to them so they can provision faster, with basically the same standards, instead of doing stuff manually.

Regarding technical support, because we have a solution architect on board, we have a lot of problems but his questions are not normal questions. His questions almost have to be escalated to a developer immediately. He doesn't ask anything simple or even just plain hard. His stuff is nearly impossible.

From that perspective, technical support has not done very well. But we have rockstars on the team and there's no way you're going to get great support because these guys are asking questions that even the rockstars of the VM world are scratching their heads about.

I brought VMware into the company in 2004. Before that it was manual, bare metal boxes.

I was involved in the initial setup but not as an engineer. Before I hired Alex, we had a guy put the stuff up. He did it in a couple of days. It was straightforward and it was functional, it worked really well. Then we got this new guy and he had so much insider knowledge. He worked out of Moscow. He was doing all the work for the all the other customers and we hired him in.

We're on 7.4, we're going to upgrade to 7.5 after Labor Day. Since we've gone live, we've done three upgrades and they've all been really good. No issues.

I can't provide numbers off the top of my head but going from three or four days to seven minutes to create a VM - and that seven minutes can go up to 50 servers wide - means it has worked beautifully.

We evaluated Hyper-V, that was a big failure. We looked at KBM, that was pretty good. We're using Acropolis Hypervisor right now. Everything is still primitive, but among the other ones, AHV from Nutanix seems to be the most stable functionally but it is still missing a whole lot of toolsets that you need. So we're not moving in that direction any time soon.

The other competitors are throwing everything at you for free but they don't have any management. You don't have the feature set that you have in vROps. vRA is much more sophisticated. You get what you pay for with VMware. You're getting all the feature set. Where everybody else is trying to give you stuff for free, they're harder to work with and then you spend more man-hours.

Start with VMware vRA. Other solutions haven't been in the game long enough. You're going to have a lot of custom-scripting that VMware already puts in there.

I rate it an eight out of 10 only because I wish we had a way to get through the technical support department faster. We've been with them long enough - and I've already talked to the sales guy about this - that they should almost have an "express lane." You lose two or three days going through the normal process. It goes to level-one and he bounces it to level-two, to level-three, when pretty much, because we've got this long history, they should know that when we call, it needs to be bounced all the way up to the top. That's just the reality.

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. 

For repeated installations and the provisioning of VMs, we now have a clear definition of what has been installed, and we can monitor all that stuff. There are some functions for the ICDs, and we have continuous development and deployment.

It theoretically could help provision new clients faster if you adhere to the limits of the product then it makes provisioning the new client a lot faster. If you have customers like we have that are really demanding and want special solutions it will end up in huge customization.

We like the blueprint designer. We can create topologies with it. 

I have found it to be user-friendly because it's very UI centric. We have a problem that most of our developers would like to have it more on a flat file format. For our end user, it's just perfect.

I would like to see multi-tenancy in NSX and better functionality. 

We have found this solution to be stable as long as we don't test its limits. We have had huge installations where we had some problems with performance and stability. 

If you have a normal use case like a conventional enterprise and use it for yourself then you might never test its limits. In our case, our customers are creating a lot of business groups and this led to a lot of problems later on.

Their technical support is very good and swift. 

We switched because we don't want to focus on the cloud management platform. We want to have this resolved and supported by a vendor because we are system integrators and want to supply the services and the knowledge above that. 

The initial setup was complex because we have a high availability cluster. Especially when it comes to upgrades, we have a lot of downtimes and problems. The upgrade experience has been painful. 

The product as a whole was offered by Dell EMC but we used VMware as an integrator and for the setup. We still have some VMware specialists working within our team.

We have seen ROI. 

We built everything from scratch, it ended up being very costly. 

I would rate this solution a seven because it hasn't perfectly adapted to our use cases with multi-tenancy. 

If you're looking into this solution I would tell you that if you use this solution only within your own company, you'll be fine. If you have a business like ours, it can get complicated. 

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?

We like vRA because it helps make systems available on time for our customers, on demand. Previously, if a customer requested machines or servers it would take three or four days to deliver. But now we can give them specific tools, or a portal, where they can shop and select which server they want. We provision servers faster. For example, to get a database machine provisioned it would take a week. Now it's a matter of 30 minutes.

Also, we now have control over the network, the server team, the storage. We only need a single team, customers are only talking to one team.

I don't think it's intuitive or user-friendly. I think it's a good tool. Any automation tool, these days, the learning curve is kind of high. You're teaching sysadmins who never developed stuff. Maybe they modified a little bit of code and now you tell them, "Hey, here's the tool, use it." But you have to know a little bit of DevOps. So you have to train them how to do the scripting.

They could also improve a lot on the interface itself.

We have not had any outages or crashes so far.

Scalability is very agile. You can scale it however you want.

If you have the Premium Support you might get somebody. Other than that...

I was responsible for the upgrade. It was very complex. One the reasons was that we were going version to version. We learned that some of the objects that were supported in previous versions were duplicated across the board. So we had to clean a lot of the databases to get the new versions.

We are still at an early stage so our assessment is probably going to be at the end of the next quarter.

My advice would be to hire Professional Services. Don't do it yourself.

When looking to work with a vendor, the most important factor is skills. They need to have the right skills, especially when you don't have time, your project timeline is very short. Skills are the key: someone who knows the product, who has lot of experience, and who has done it before.