# Release plans for 0.9, shelving ansible-commander (GUI/REST project) **URL:** \ **Category:** Ansible Project\ **Created:** [November 9, 2012, 1:05am UTC](https://forum.ansible.com/t/release-plans-for-0-9-shelving-ansible-commander-gui-rest-project/12073 "2012-11-09T01:05:04Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\ **Post date:** [November 9, 2012, 1:05am UTC](https://forum.ansible.com/t/release-plans-for-0-9-shelving-ansible-commander-gui-rest-project/12073/1 "2012-11-09T01:05:04Z")
Hi all, The ansible bug queue for 0.9 is getting reasonably short. I think we should plan to release in a couple of weeks. This means feature freeze in about a week. Thanksgiving may move that around a bit. Almost definitely! I need to update the changelog but there is a LOT in it and it will be a strong release. In other news, I have talked about my ideas around building an Ansible GUI and REST API in the past (aka ansible-commander). I currently do \*NOT\* plan to do this, due to (A) bandwidth, and (B) thinking external inventory scripts are almost always going to fill this void first -- maybe you want to store your metadata with your cloud instances, etc... I think that's closer to the future.   If other peopel want to try to build this, great, I encourage that. Some things we DO want to do are supporting multiple simultaneous inventory files and scripts, so that if your inventory file /etc/ansible/hosts is actually a directory, you could drop in an EC2 source and a Nova source and it would all work magically together -- along with some INI files if you wanted too (enabling conf.d style directories as well). It should also be possible to write inventory in plugin format to avoid some shell calls and sharing of state/sessions between executions. (Also, if you want to shell out to ansible-playbook, just write a callback plugin that stores results in whatever format or data store you like) Any questions and so forth, let me know. --Michael ---
**Author:** ![Peter\_Sankauskas](https://avatars.discourse-cdn.com/v4/letter/p/ea666f/32.png) [@Peter\_Sankauskas](https://forum.ansible.com/u/Peter_Sankauskas)\ **Post date:** [November 9, 2012, 1:11am UTC](https://forum.ansible.com/t/release-plans-for-0-9-shelving-ansible-commander-gui-rest-project/12073/2 "2012-11-09T01:11:04Z")
Sounds good. I agree with inventory plugins filling the void because for any cloud provider with an API (AWS EC2, Rackspace Cloud, etc), the always accurate inventory is the response of an API call. Then for speed, it is just a matter of caching. Peter ---
**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\ **Post date:** [November 9, 2012, 1:49am UTC](https://forum.ansible.com/t/release-plans-for-0-9-shelving-ansible-commander-gui-rest-project/12073/3 "2012-11-09T01:49:47Z")
It has also been suggested that for "\ --list" we pass in the filter pattern, like "\ --list webservers" This would allow, at least in theory, less results to be returned for larger host volumes. --Michael