Happy 2019! We kick off this year with a great feature on collaboration.

We’ve just built Hammer-2. This release contains bug fixes, UI tweaks, and stabilization. Here are just a few of the things added since Hammer-1 release:

Last Month in MIQ is a column about code and code things: everything code, except actual code.

We’ve just built Hammer-3. This release contains bug fixes, UI tweaks, and stabilization. Here are just a few of the things added since Hammer-2 release:

We’ve just built Hammer-4. This release contains bug fixes, UI tweaks, and stabilization. Here are just a few of the things added since Hammer-3 release:

1. We no longer start another refresh worker while another is stopping. If you are still reading this, please continue to 2.

We’ve just built Hammer-5. This release contains bug fixes, UI tweaks, and stabilization. Here are just a few of the things added since Hammer-4 release:

PLAYTEST SESSION 1 V4.30

Red Hat Cloudforms provides several ways to customize virtual machine provisioning, the out-of-the-box VM Provisioning State Machine has multiple steps through which VM provisioning request crawl, among them one of the step is PostProvison, this step is used to perform post-provisioning activities on the provisioned virtual system. In this article, I will explain how to customize PostProvison method using an example of ‘add an additional disk to the VM’ use case.

We’ve just built Hammer-6. This release contains bug fixes, UI tweaks, and stabilization. Here are just a few of the things added since Hammer-5 release:

This is the May celebration of our 95 pull requests merged by 27 people, of which of course, you too could be one, unless you already are quite that fortunate:

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.

We’ve just built Hammer-7. This release contains bug fixes, UI tweaks, and stabilization. Here are just a few of the things added since Hammer-6 release:

We’ve just built Hammer-8. This release contains bug fixes, UI tweaks, and stabilization. Here are just a few of the things added since Hammer-7 release:

Dear ManageIQ community,

We’ve just built Hammer-9. This release contains bug fixes, UI tweaks, and stabilization. Here are just a few of the things added since Hammer-8 release:

On behalf of the ManageIQ team, we’re pleased to announce the Beta1 release for ManageIQ Ivanchuk! You can download the Ivanchuk Beta1 Release here

Vote for the J-Release!!! Here is the Poll on talk.manageiq.org

Red Hat CloudForms allows users to put both VM provisioning and Ansible Tower jobs in the same catalog bundle, with the intention of having that tower job of customizing the VM that was just provisioned. However, it’s not as simple as adding a VM catalog item, and then an Ansible Tower catalog item. This post will guide you through the nuances of utilizing Tower jobs in CloudForms step by step.

Why can’t I just use Update on Launch when CloudForms is a source in Red Hat Tower’s inventory?

You can, as long as you don’t mind the jobs not being concurrent for that inventory. If you have this option checked, then whatever concurrent jobs you have, will wait, since Tower does not update the inventory while a job is being executed.

However, if you wish to have concurrent jobs utilizing CloudForms, please continue reading this blog post. This is the most efficient method utilizing CloudForms I’ve run across and we are currently using this in our lab environment for reproducers in North America for CloudForms CEE team. A caveat of this is that you cannot have 2 VMs of the same name in your CloudForms environment, if you do, the limit will potentially be set to all of the VMs that match that name.

So how do I update the inventory for the newly provisioned host to Tower if we’re not updating on launch?

We will be utilizing an ansible playbook to use an API call to ad hoc add a host to the CloudForms inventory in Ansible Tower

What roles do I need to have enabled on the worker appliance for this to work?

• Automate
• Embedded Ansible
• Provider Inventory
• Provider Operations

You will also need to add the appropriate VM provider and Ansible Tower provider

Setting up the repository for embedded ansible

Go to Automation > Ansible > Repositories > Add New Repository, and use the following URL:

On behalf of the ManageIQ team, we’re pleased to announce the Beta2 release for ManageIQ Ivanchuk! You can download the Ivanchuk Beta2 Release here

The results of the poll on the name of the J release are in. Vlastimil Jansa is the winner! Looking forward to all the exciting features that will come in the Jansa release. Thanks to all that voted - we had 69 total votes for the J-Release.

We’ve just built Hammer-10. This release contains bug fixes, UI tweaks, and stabilization. Here are just a few of the things added since Hammer-9 release:

The ManageIQ team is aware of a vulnerability in rest-client introduced by a compromised account of one of the rest-client maintainers.

On behalf of the ManageIQ team, we’re pleased to announce RC1 for ManageIQ Ivanchuk! You can download Ivanchuk RC1 here

We’ve just built Hammer-11. This release contains bug fixes, UI tweaks, and stabilization. Here are just a few of the things added since Hammer-10 release:

Your experience matters and we are aware of it.

As a CloudForms user, do you ever get frustrated, wondering which button to click on or how to get to your selected location?

If your answer to any of these or similar questions is yes, then let me tell you that your life is going to get easier. Why does CloudForms need to be that complicated? The truth is that it doesn’t and we (with your help) are working on it. Have you already noticed any design changes in CloudForms? Has your menu changed or some reports make more sense now? Sometimes small and at first sight irrelevant changes can bring you peace of mind without you even noticing it. We are working on getting rid of all the unnecessary steps in your workflow to let you just focus on your tasks. We are eliminating painful illogical constraints, unnecessary information inputs and more, to reduce questions like which button to click on. Our job may be invisible but that means that we are doing it right.

Who are we?

With the release of ManageIQ Ivanchuk, we are introducing new integrated provider: Microsoft Azure Stack. Integration was developed by XLAB Steampunk, a trusted Red Hat partner specialized in integrating third-party technologies with Red Hat CloudForms and Red Hat Ansible Automation Platform.

We’ve just built Ivanchuk-2. This release contains bug fixes, UI tweaks, and stabilization. Here are just a few of the things added since the Ivanchuk GA release: