Last year has been pretty exciting and eventful for ManageIQ! If you’re new to the community, or if you just want a refresher, let me be your guide and summarize the cool progress we made throughout 2016.
Happy New Year! We’re starting off 2017 with a notable change in the ManageIQ process. In an effort to become more agile, and allow more flexibility in planning and scheduling, we will be switching from 3-week Sprints to 2-week Sprints.
Vote for the F-Release!!! Here is the Poll on talk.manageiq.org
Vote for the E-Release!!!
As we’re approaching the Darga release, we are adding translations for ManageIQ UI, and we need you to be part of the community translation effort!
If you run
git pull on your ManageIQ appliance to pull down updates, restart and find that you can’t login in the web UI as the buttons are unresponsive, it’s likely you’re running in production mode, some assets were added or changed and haven’t been precompiled.
If you’ve been visiting Planet ManageIQ recently, you know we’ve made some additions:
If you’ve been participating in our sprint reports, you’ve no doubt found them to be an excellent way to stay apprised of feature progress in ManageIQ. I’m happy to announce that our community activities are now part of the 3-week sprints and included in the sprint reports.
We’ve turned on one more web app to round out the manageiq.org experience: the Planet ManageIQ blog aggregator. For now, we syndicate the following blogs:
As we get ever closer to the Botvinnik release, we turn our eyes to the next release cycle. In keeping with our nomenclature of using chess grandmasters and world champions as release names, we have a couple of candidates for the next cycle. Read about Viswanathan Anand and Mikhail Botvinnik to see whom we chose for the “A” and “B” releases, respectively.
I sat down with Chris Hample and Chris Kacerguis from Booz Allen Hamilton to discuss their newest release of the Jellyfish Cloud Broker, which is at version 2 as of this writing.
We can now take the covers off of the ManageIQ Community Depot and show it to you live. Just understand it’s in beta and may (will) have some bugs. The Depot is where you can share, download and collaborate on extensions and other software built for ManageIQ.
Here is a lab I put together for a recent event, it was well received and I think it is very valuable to the ManageIQ and CloudForms user bases. In the lab you will GET and POST RESTapi actions. Its a basic look at some common use cases such as, Query a VM’s hardware inventory. Read the rest
Here is the list of GEMs and their info that are included in the CLOUDFORMS 5.3.0 appliance. I thought it would be useful to post, I need this recently for some work I am doing. It was really easy as most things in CLOUDFORMS usually are I simply wrote some ruby to utilise an existing… Read Original Post
The ManageIQ Depot will be where community members can collaborate, share and download extensions and other software developed for the ManageIQ hybrid cloud management platform. I made a quick video showing how to grab the latest depot code from GitHub, add your extension, and then test it locally before issuing a pull request to add it to the git repository.
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.
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:
Aaron Patterson joined us from Russia on this fun podcast, covering many topics, from the Rails 4 migration and the ManageIQ Design Summit to why you should “just use Ruby”.
I think most know who follow this blog that I have started posting some video content on Cloudforms as thats quite and easy way to digest or see it for real. Here’s a link to videos on my cloudformsnow youtube channel
We are thrilled to announce that Aaron Patterson (@tenderlove) has joined the ManageIQ team.
The votes are in, and “Botvinnik” is the winner! In planning for Botvinnik (which we’ll sometimes shorten to “bot”) we’re now accepting blueprints for proposed features. Just submit your blueprint and make sure to categorize it properly. Next, you’ll need to propose an abstract for the ManageIQ Design Summit. Make sure to put your proposal in the Abstracts category.
When we originally open-sourced ManageIQ, the ManageIQ GitHub Repo was integrated with Code Climate. Integrating with Code Climate allowed the developer community to find code with too much complexity and/or duplication and refactor it.
This week, we integrated the ManageIQ GitHub Repo with Travis CI, the continuous integration service. This service runs on each GitHub pull request to ensure that no new code is breaking existing tests (i.e. no regression). If the pull request does cause a regression, the core maintainers of the ManageIQ project will not merge it until this is resolved.
So, keep creating pull requests to make ManageIQ better, but make sure that they do not break any tests!
Here’s a great introduction written by Bryan Che, a Red Hat cloud strategy guy, on why we released ManageIQ as an open source project, as well as a look at the cloud management landscape. Cloud management is currently a nice car with four flat tires, and all four of them with different sizes, colors, and recommended pressure.
As I mentioned in the previous blog post, it’s a great day to be in the cloud. Yesterday marked our announcement at the OpenStack Summit, and the reaction was pretty swift and positive. There is pent-up demand for software that lets others take control of their clouds and virtualization environments.