ManageIQ Blog
Sprint 15 ruby 2 appliances available
Earlier this week, we mentioned moving to ruby 2 on our github repository and in travis-ci for testing. Ruby 2 nightly build appliances based on sprint 15 are available here.
ManageIQ Integrates with Amazon AWS Config Service
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.
The Extensions Depot Needs You - Call for Participation
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.
Ruby 2 Update
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.
Booz Allen Open Sources Jellyfish Cloud Broker for ManageIQ Community
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.
Service Item Selection
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: