CloudForms Service Bundle creation using VM Provisioning and Ansible Tower automation job

Service catalog bundles are a really useful CloudForms feature that enable us to mix and match various existing service catalog items together to form bundles of tasks.

 

One of the more useful examples of a bundle is to create a new VM, and then run an Ansible Tower job template on the resulting VM to configure it with an application role. If we have an Ansible Tower server added to our CloudForms installation as an automation provider, this is quite simple. We described the procedure to configure an Ansible Tower provider in CloudForms as part of our previous series on Ansible Tower integration in CloudForms 4.1.

 

Continue reading “CloudForms Service Bundle creation using VM Provisioning and Ansible Tower automation job”

My First Ansible Control Action (Video)

With this short video, we continue our series based on Red Hat Knowledge Base articles exploring how to take advantage of Ansible Automation inside Red Hat CloudForms. This post is a follow-up of our previous My First Ansible Service article.

As a summary, what we do in this video is to create a control policy that checks if the VM CPU or memory size has changed, and if so, resets the size to 1 CPU and 1GB automatically.

Continue reading “My First Ansible Control Action (Video)”

Using an Ansible Job Template in a CloudForms Service Bundle

This is part 5, the last post of our series on Ansible Tower Integration in Red Hat CloudForms.

As you saw from previous articles, Job Templates can be launched from CloudForms via Ansible Tower to run playbooks on targeted hosts. In particular we have looked at launching them from a button on a VM and from the CloudForms Service Catalog. In this last article, we examine how to expose Job Templates as Service Items to utilize them as part of a Service Bundle.

In this example, we reuse our ‘Deploy PostgreSQL’ Job Template to automate the installation and configuration of a PostgreSQL database on a newly provisioned VM. Our service bundle will deploy a new RHEL7 instance on Amazon EC2 and launch our Ansible Job Template to configure the database on this host.

Continue reading “Using an Ansible Job Template in a CloudForms Service Bundle”

Publishing an Ansible Job Template as a Service in CloudForms

This is part 4 of our series on Ansible Tower Integration in Red Hat CloudForms.

In the previous article, we have seen how Ansible Job Templates can be launched from a VM button in CloudForms. In this article, we explore how Ansible Job Templates can be published as Catalog Items and made available for end user consumption from a CloudForms Service Catalog.

In this example, we use ec2_elb_lb, an Ansible core module, to demonstrate how we can easily extend the capabilities of CloudForms by re-using automation already provided by Ansible. In particular, we provide the ability to create an Amazon Elastic Load Balancer (ELB) from CloudForms Service Catalog without having to write any Ruby code.

Continue reading “Publishing an Ansible Job Template as a Service in CloudForms”

Launching our First Ansible Job Template on a VM in CloudForms

This is part 3 of our series on Ansible Tower Integration in Red Hat CloudForms.

In this article, we will explore how to use the Ansible Tower integration in CloudForms by configuring the launch of an Ansible Template Job on a click of a button from a VM.

In this example, we use an Ansible Job Template created based on a role found on the Ansible Galaxy role library. In particular, we installed on our Ansible Tower the sfromm.postgresql role dedicated to managing PostgreSQL. Our associated Ansible Playbook is available on GitHub.

Continue reading “Launching our First Ansible Job Template on a VM in CloudForms”

Configuration of an Ansible Tower provider in CloudForms

This is part 2 of our series on Ansible Tower Integration in Red Hat CloudForms.

As mentioned in our previous post, CloudForms 4.1 brings native integration capabilities with Ansible Tower. This post explores the Ansible Tower requirements as well as the configuration of the provider in CloudForms.

Like all providers within CloudForms, the Ansible Tower provider is agent-less and only requires connectivity and credentials to the Ansible Tower API.

Continue reading “Configuration of an Ansible Tower provider in CloudForms”

  • Page 2 of 2
  • <
  • 1
  • 2