This post explains a solution whereby Red Hat CloudForms is enabled to show back to the users their remaining tenant budget when ordering services via the service catalog. The implementation uses CloudForms taxonomy and custom methods to display service costs, quota, and a message on the Service Dialog screen.
As a user, I wish to be presented the cost of the service I am ordering, along with my current budget and remaining budget when the service is ordered. I would like my budget to be set and maintained at my tenant level.
Continue reading “Example using Tagging for Displaying Pricing and Quota on Service Dialogs”
Red Hat CloudForms ships as an appliance to simplify deployment as much as possible – a Red Hat Enterprise Linux server with the appropriate software loaded, ready to be configured with a few basic configuration options.
Traditionally, these servers are configured using the command line tool appliance_console. This is a simple, menu-based interface that allows you to configure the core functionality of the appliance and makes it exceptionally easy to do so. Unfortunately, menu-based interfaces don’t lend themselves to being automated easily.
However, there is a solution!
Continue reading “Automating CloudForms Appliance Deployment with Ansible”
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.
Continue reading “My First Contribution to ManageIQ”
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.
Continue reading “Ansible Automation inside Red Hat CloudForms (Summary)”
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.
Continue reading “Debugging Ansible Automation inside Red Hat CloudForms”
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.
Continue reading “Multi-tier Application Deployment using Ansible and CloudForms (Video)”
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.
Continue reading “Implementing Continuous Integration for CloudForms using Git and Travis”
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.
Continue reading “VMware Provisioning Example using Ansible (Video)”
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.