VMware Aria Automation Reviews

Fast provisioning and integration with public cloud. Our customers want the VMs to be up and running as early as possible. Also, some of our customers need their workloads to be running on the public clouds like AWS to minimize the cost. Using vRA, we can easily integrate AWS and can provision VMs on them.

Fast provisioning.

I don’t see configuration management feasibility. I think there should be a configuration management tool on the user dashboard. It can be used to patch/update the servers provisioned through vRA for an inbuilt facility.

We have seen couple of bugs.

Not really.

Good.

Good.

Yes. Poor vendor support and less stability.

It was straightforward but they still need to improve the IaaS components.

Compared to other vendors in the market the licensing cost is OK.

Yes. HPE.

Go for it.

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

It has helped our organization tremendously.

It provides visibility into the VM space.

It is user-friendly to a greater extent.

It is stable.

It is scalable.

I have used the technical support once or twice, and they were good.

We are highly virtualized, so we like anything related to VMware because we need the visability their products provide. We need to know what is going on, so we can supervise our operations.

The setup is difficult. You need a technical person to help you set it up.

We have not upgraded yet.

I would recommend this solution.

One of the valuable features is controlling VM standards and server sprawl while at the same time providing the ability for end users to self-provision VMs. This is enabled by the blueprint and resource reclamation features.

We no longer need to waste cycles manually building VMs and experience delays associated with service requests attached to those build functions.

More detailed documentation on implementing feature sets and more examples of real world processes would help.

We have used this solution for less than three months.

We have not encountered any issues with stability yet.

We have not yet looked into scaling out the solution.

I have not needed to use technical support yet.

I did not previously use a different solution. This is the first automation tool that I have used.

The initial setup was straightforward. However, the more advanced capabilities of the tool are more difficult to understand and implement.

Be informed and reach out to your VMware sales rep to answer questions.

Take as much training as you can before trying to deploy and use the product.

The most valuable asset is most probably the ability to target the needed hosts, and running commands via modules or a shell on all of them at the same time. This means that mass parallel administration of large server farms is possible.

I am now able to rollout critical updates within seconds on all affected servers, and it doesn't matter if there are five or 500 of them.

So far, everything worked as expected. This means that so far, I heavn't seen anything which needs improvements. The software works as expected and I stumbled across no issues while using it.

We are part of a Cloud team and vRA self-service portal helps our customers worldwide to provision machines and Day 2 operations automatically without logging tickets and wasting time.

We are part of a Cloud service provider. It has helped our business to grow and scale.

Implementation should not be so complex. Certificate replacement should be easier.

Three years.

Performance of the service portal seems to be slow at times. Requires a reboot once a month.

We faced no issues with scalability.

Technical support is good through Ireland and the US.

No, we have been using vRA for three years.

It was complex; the certificate was the worst part.

As an engineer, I didn’t look at the pricing model.

No, we are a partner with VMware so that was our choice.

Read the knowledge base articles from VMware.

Multi-tenancy is one of the best features for configuring a single portal for multiple departments/customers. Multi-tenancy allows us to use a single vRA portal to configure multiple tenants with their individual URLs. Also, this feature allows us to use shared infrastructure for multiple tenants.

The front end portal for end users, which communicates with infrastructure endpoints.

The infrastructure part and VM reconfigure need improvement so that the end user can smoothly perform all the tasks which they are directly performing on the endpoints.

Three years.

No.

No.

Excellent.

No.

Straightforward.

This is one of VMware's best products for automation.

The most valuable features are the EBS (Event Broker Subscription) and NSX integration with BP designer.

Multiple BPs can be deployed with EBS and PG (Property Group) in a lot less time.

IaaS components: I have an assumption that all the IaaS components will be migrated to a Linux appliance, then I think the communication between the Linux appliance and the IaaS components will happen faster and smoother.

We have used this version for almost 1.5 years. We previously used version 7.0.

Sometimes, we encountered stability issues, but they were negligible.

Sometimes, we encountered scalability issues but they were negligible.

Very Good.

Technical support was good.

This is the first product we used.

Installation was straightforward and simple .

It’s very helpful for us to have this product. We already gained the benefits after installation and configuration.

We did not look at alternatives; this is the ultimate product.

Use it for automation in order to achieve Agility, Efficiency and Control over the IT Service Delivery..

• Simple and flexible YAML/JSON configuration management framework which allows simultaneous configuration of thousands of systems
• “Reactor" for event-driven infrastructure which must be present in any cloud based solutions and in CloudOps itself
• Powerful and flexible DevOps orchestration solution

• We decreased deployment CD times from hours to minutes across different cloud providers on several hundred systems.
• We used a SaltStack agent as a “Convergence” agent which provided us with management, monitoring, and backup capabilities.

• Backward compatibility
• The speed of fixing bugs

We have used this solution for under three years.

With the correct infrastructure design, stability issues probably won’t occur. SaltStack supports several features for high availability and fault tolerance.

In terms of SaltStack code/bug issues, it is a very stable product after four years of development from 12,000 developers.

I did not encounter any issues with scalability.

SaltStack is a very straightforward system with very good documentation. There are different solutions for deployments. Many scenarios and best practices are available publicly on the SaltStack site.

We evaluated Ansible and Puppet. SaltStack provided a much more robust solution.