With the recent announcement of Amazon’s AWS Config service, there is a Pull Request to integrate with it. The integration will allow ManageIQ to use the AWS Config service as an event source to our Amazon Provider. These events can be used to drive many things inside ManageIQ, including inventory refreshes, policies and automate workflows. Once this Pull Request is merged, our appliance (which is built nightly) will have that functionality incorporated. Until then, if you want to play with the proposed integration, take the code changes from the pull request and integrate them into your appliance or development environment.

We are happy to announce that we are moving forward with the ManageIQ Extensions Depot! The Extensions Depot is a place for the ManageIQ Community to share policies, dialogs, state machines and other items of interest to the greater community.

Travis CI

We have been using travis ci for running our tests automatically on each merge and pull request soon after we open sourced ManageIQ.

For some time now, Booz Allen Hamilton, one of the founding members of the ManageIQ Community, has been hard at work on a “cloud broker”. “What is a cloud broker,” you may ask? It’s a nice tool that allows individuals to pick and choose various service offerings from multiple sources, without knowing (or caring) which cloud or virtualization platform supplies the services. That they chose ManageIQ as the platform of record to build on speaks volumes to the hard work those engineers have put in over the last 8 years.

Here is something I get a lot, “How can I make a service with multiple service items, but then conditional drop some during the deployment?” Eg. You have a Service Dialog like this one here:

Jason Frey is a long-time contributor and architect for the ManageIQ and CloudForms world. If you want to know anything about ManageIQ, he’s your guy. Watch and learn from the following video.

Unless you’ve been under a rock the last few days, you’ve no doubt heard of the Shellshock vulnerability affecting a large number of *nix machines with the Bash shell installed. Note: Bash doesn’t even need to be the default shell - plenty of ‘Dash’ users are also affected. Luckily, there’s a way to avoid this mess - a policy management engine in ManageIQ, combined with VM fleecing, that lets you route around the vulnerability, turning off VMs that are vulnerable. This video gives you the goods: