Manage container, virtual, private, and public cloud infrastructures
| Type | Title | Date | |
|---|---|---|---|
| Category | Cloud Management | Jun 1, 2025 | Download |
| Product | Reviews, tips, and advice from real users | Jun 1, 2025 | Download |
| Comparison | Red Hat CloudForms vs VMware Aria Automation | Jun 1, 2025 | Download |
| Comparison | Red Hat CloudForms vs Nutanix Cloud Manager (NCM) | Jun 1, 2025 | Download |
| Comparison | Red Hat CloudForms vs VMware Aria Operations | Jun 1, 2025 | Download |
| Title | Rating | Mindshare | Recommending | |
|---|---|---|---|---|
| VMware Aria Automation | 4.0 | 11.8% | 94% | 170 interviewsAdd to research |
| IBM Turbonomic | 4.4 | 5.6% | 98% | 205 interviewsAdd to research |
Managing a complex, hybrid IT environment can require multiple management tools, redundant policy implementations, and extra staff to handle the operations. Red Hat® CloudForms simplifies IT, providing unified management and operations in a hybrid environment.
As your IT infrastructure progresses from traditional virtualization toward an Infrastructure-as-a-Service (IaaS) model, CloudForms evolves, protecting your investments and providing consistent user experience and functionality.
Our company used the solution as a pre-defined server and internal cloud. We automated infrastructure as a code and delivered it to the user portal to meet logins and request machines.
After the machine was created, we integrated with Ansible Towers to install applications or services that sat on top of the machine.
The intent was to see our entire environment and replace all manual processes. We wanted one dashboard to handle all daily tasks. We had 10,000 users with 1,000 of them engaged in installation and testing.
Users found the solution simple to use but it never launched as a production. Five team members handled development and management before the solution was decommissioned.
The solution was beneficial because it gave us a full view of our infrastructure and the ability to calibrate each team's requests or machines.
The solution is compatible and integrates with various infrastructures or vendors. You provide APIs and integration occurs, even with vendors that are not out-of-the-box partners.
For example, integrations are possible with Nexus, Solaris, RBC via an Oracle API, IBM, VMware, OpenStack, and Red Hat.
In contrast, other solutions dictate which vendors you are permitted to connect with or administrate.
It is difficult to create a complete dashboard that includes all the needed features or catalogs. To compete with other vendors, much development is needed such as including predefined plug-and-play modules
It takes a lot of development to integrate with Remedy and request new machines or create tickets.
The approval cycle for deployment and implementation is too long.
I used the solution for two years.
We did not experience a lot of time in production but configuration and deployment was stable in our environment.
I handled implementation and that did not include expanding our environment or scalability.
We used technical support to assist with installation.
We previously used Ansible to automate machines.
The setup and configuration was very straightforward.
We utilized partnerships with OpenStack and third parties for implementation.
Deployment took some time because there was a lot of development work to design and set up regions. We have a huge network with multiple regions, sites, and security protocols. Each item needed to be installed and OVA or OVF files needed to be configured.
Once everything was opened from the firewall perspective, deployment took one or two days.
Other work included pre-installing the post implementation applications or services, developing the dashboard and service catalogs, and integrating with Remedy.
We did not review other products prior to choosing the solution.
Based on internal decisions, the solution was decommissioned and replaced with VMware Cloud Director.
I rate the solution a nine out of ten.
