In this blog post, I am going to share my experience on how I made my first contribution to ManageIQ, the upstream open source project for Red Hat CloudForms. The post explains how I encountered and investigated an issue, and finally fixed it thereby sending my first “Pull Request” to ManageIQ repository.
This blog post concludes our series on Ansible Automation inside Red Hat CloudForms. We hope that the content and demo videos were able to get you a grasp on how Ansible Automation, the leading simple, powerful, and agentless open source IT automation framework, adds value to Red Hat CloudForms and extends its capabilities.
Red Hat CloudForms natively supports Ansible Automation and eases the deployment of infrastructure and IT services across clouds. Users can automate multi-cloud management by defining a wide range of policies and processes with no coding or scripting required.
Debugging might not be one of your favorite things to do, but when your automation fails it is good to know where to look to find information and troubleshoot. In this blog post, we investigate how to make sure Ansible Automation is correctly configured inside CloudForms, and how to troubleshoot issues that might occur when running Ansible Automation. Content for this blog post is based on the knowledge base article published on Red Hat Customer Portal.
This article is a follow up on our previous blog post VMware provisioning example using Ansible, where we deployed a simple virtual machine on VMware using Ansible from the CloudForms service catalog. In this week’s demonstration, we go a step further and provision a multi-tier application on Amazon Web Services (AWS). Once provisioned, the application lifecycle, as well as all day 2 operations are performed from Red Hat CloudForms.
Christian Jung recently posted another interesting article as a follow-up on Best Practice Recommendations for Automate. This time, he focuses on setting up Continuous Integration for Red Hat CloudForms.
In our previous post, we demonstrated how to create a basic Ansible Service and provision it from Red Hat CloudForms Service Catalog. In this post, we demonstrate how we can deploy a VMware virtual machine using an Ansible Playbook.
This document is to position two different types of integration with a CMDB and Red Hat CloudForms.
We discuss the use of HP uCMDB because it supports both types of integration but also other CMDBs are available such as Service-Now.
The two types of integration are known as;
Pull – Where by the information/data is collected (Pulled) by the CMDB from the end points. CMDB Server initiated.
Push – Where by the information/data is sent (Pushed) to the CMDB server by the end point. Endpoint initiated.
Other CMDB servers may not support a PULL approach at which point you have only the PULL solution as the only option.
We shall now dive deep into each integration type.
A few days ago, Michele Naldini posted a series on the Red Hat Developer Blog about how to build a Software Defined Data Center (SDDC) using Red Hat CloudForms and Red Hat OpenStack Platform.
Red Hat CloudForms allows to more quickly deploy and scale Red Hat OpenStack Platform (also known as OSP) private clouds, combine existing IT infrastructure investments, and federate public cloud deployments. This series includes both background information and hands-on tips to implement a full SDDC in practice.
This is a follow up to the Ansible Series with a new video that shows how to create a button that executes an Ansible Service. In this post, we re-use the same Ansible Service that we created in our previous post: My First Ansible Control Action.
