# Status of ansible-commander and plans for 0.9

**URL:** <https://forum.ansible.com/t/status-of-ansible-commander-and-plans-for-0-9/11961>\
**Category:** Ansible Project\
**Created:** [October 9, 2012, 12:11am UTC](https://forum.ansible.com/t/status-of-ansible-commander-and-plans-for-0-9/11961 "2012-10-09T00:11:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**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:** [October 9, 2012, 12:11am UTC](https://forum.ansible.com/t/status-of-ansible-commander-and-plans-for-0-9/11961/1 "2012-10-09T00:11:30Z")

</div>

Previously I was looking at ansible-commander as a REST API that would  
run on machines you could also log in and run ansible on, and had  
ruled out using Riak since it didn't have an auth scheme -- it turns  
out it /does/ have a sufficient auth scheme, and I need to gut some  
things, because it's clear the current direction of ansible-commander  
is not gathering moss at the level I want it to.

My intent for 0.9 will be to resurrect and simplify commander, just  
like fireball was a focus in 0.8.

Data stores will not be pluggable, as I want to use everything I have  
access to at full power.

One of the first things we need to do is to be able to support adding  
SSH keys to the REST API. You will be able to upload the path to a  
passwordless key or a key+password and be able to command nodes over  
the REST API.

Another thing I should really simplify is to make the groups and hosts  
API mirror what the external inventory script serves up. This means  
that the REST API will probably not model any inventory structure  
(groups of groups) at first, but just maintain what hosts are in what  
groups and what variables they have. Basically what you get back  
from the external inventory script -- you'll be able to push and post  
in exactly that format.

The end result is the REST API gets to become infinitely more  
simplified, the web app gets accelerated, and you will be able to  
register the names of playbooks to make them triggerable over REST  
too.

Over time, we'll expand, but it will start small.

--Michael