Ansible continues to grow and is the strategic automation engine for Red Hat’s business. Having a solid and constantly improving integration with Ansible is key for CloudForms’ future success.
Ansible Tower Workflows are widely used in by the industry to orchestrate and govern interactions between different playbooks. CloudForms has been able to run Ansible Tower Jobs since its 4.1 release. Starting with CloudForms 4.7, we will expand this support and will be able to utilize Workflows from the Service Catalog.
Continue reading “CloudForms 4.7 – What’s new with Ansible?”
In this article, I will describe how REST API works natively in Red Hat CloudForms.
REST stands for Representational State Transfer. REST is a web standard based architecture and uses HTTP protocol for data communication. It revolves around resources where every component is a resource and is accessed by a common interface using HTTP standards method.
Red Hat CloudForms provides APIs to integrate external systems and initiate provisioning via CloudForms. In CloudForms, REST can be accessed by adding “/api” prefix to the URL.
https://<IP or hostname of appliance> /api/
Continue reading “Playing with REST API”
CloudForms 4.6 provided the ability to run embedded Ansible playbooks as methods, and it can be useful to include such a playbook in an existing workflow such as the VM Provision state machine.
Continue reading “Calling an Embedded Ansible Playbook from the VM Provision State Machine”
Red Hat held an event on the infrastructure part of our portfolio in Milan and Rome on April 17th and 19th, 2018. One of the two demos presented was the management of a hybrid cloud environment with the Cloud Management Platform (CMP) Red Hat CloudForms.
The event information and agenda is available at:
Continue reading “Infrastructure Tour Italy Part 1”
Whether you operate a single standalone CloudForms appliance or multiple multizone regions geographically dispersed with a global master region, effective management makes all the difference.
Continue reading “CloudForms Thought Leadership”
This part will focus on how to create the Custom Button using an Ansible playbook.
Creating Custom Button
CloudForms 4.6 has introduced more options while creating a button. This topic will be discussed in another post.
Continue reading “Ansible Custom Buttons in CloudForms (Part 2 creating the button)”
This series is highlighting the improvements and new capabilities introduced with CloudForms 4.6 about Ansible Custom Buttons.
The Ansible Playbook used in this example will install a user-specified package on the selected virtual machine.
Continue reading “Ansible Custom Buttons in CloudForms (Part 1 configuring the environment)”
One of the exciting new features in CloudForms 4.6 within Automate is Embedded Methods. That is, one can store reusable, directly callable, ruby code within Automate and access from other Automate Methods.
Continue reading “Embedded Methods”
For the last few posts Laurent Domb has been explaining how to squeeze CloudForms and AWS integration by teaching you how to:
- Upload the CF images to AWS
- Create all the needed config files in AWS
- Deploy CF on AWS
- Configure the new in 4.6 SmartState Analysis (SSA)
- Use that SSA to add a compliance policy to an instance
- Use AWS authentication in CF
You can find the blog posts here:
Please let us know what are your thoughts and which other series would you like to read in the blog
If you want to use IAM authentication for CloudForms so that IAM users can authenticate with CFME you need to do the following.
The current code requires you to add root (account owner credentials) to the authentication field. So the Access key and the Secret Key are from the root user, not the IAM user.
Continue reading “CloudForms in AWS part 5 (authentication)”