# So ... ansible-commander -- some new ideas, and a reminder to check things out **URL:** \ **Category:** Ansible Project\ **Created:** [September 25, 2012, 1:43am UTC](https://forum.ansible.com/t/so-ansible-commander-some-new-ideas-and-a-reminder-to-check-things-out/11924 "2012-09-25T01:43:26Z")\ **Posts on this page:** 8\ **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:** [September 25, 2012, 1:43am UTC](https://forum.ansible.com/t/so-ansible-commander-some-new-ideas-and-a-reminder-to-check-things-out/11924/1 "2012-09-25T01:43:26Z")
So, database-arguments aside, haven't had a lot of feedback on the emergent ansible-commander project just yet. [https://github.com/ansible/ansible-commander](https://github.com/ansible/ansible-commander) The REST API is certaintly usable for controlling inventory right now.   Who has tried it? Are there folks interested in helping build out the UI as it stands? Just not enough time? That's ok if so, though I'd like to see lots of folks get involved as that's worked so well for Ansible so far. One idea I have -- actually James Cammarata of Cobbler fame did all the work in trying to integrate Ansible with Cobbler (patch still not merged quite yet) -- is to make the REST API be able to accept reference to SSH keys (optionally, with passwords). This can, more or less, make playbooks and general commands REST triggerable. It's actually super easy to do, and it would turn ansible, if so engaged, into a full web-servicey-integratable sort of thing. Pretty exciting. I think that will make things a /LOT/ more appealing, and also open up more uses for the GUI than just inventory management. --Michael ---
**Author:** ![Chamberlain\_Darren](https://avatars.discourse-cdn.com/v4/letter/c/ee7513/32.png) [@Chamberlain\_Darren](https://forum.ansible.com/u/Chamberlain_Darren)\ **Post date:** [September 25, 2012, 3:00pm UTC](https://forum.ansible.com/t/so-ansible-commander-some-new-ideas-and-a-reminder-to-check-things-out/11924/2 "2012-09-25T15:00:26Z")
Speaking for myself, the reason I've not been testing ansible-commander is that we're aready managing our inventory externally (updating a system inventory database regularly, using a script to build /etc/ansible/hosts from that, and puppet to distribute it), and fronting it with Jenkins, which we already use everywhere and integrates seamlessly with our inventory system, authentication provider, and puppet. Thus, since ansible is entirely disconnected from our inventory system, other than as a downstream consumer, ansible-commander doesn't it into our ecosystem right now. Having said that, I find ansible-commander very interesting as an working example of how to build a service that provides an API to a set of data. I've been following the project closely for that reason. \* Michael DeHaan \ [2012/09/24 21:43]: ---
**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:** [September 25, 2012, 3:18pm UTC](https://forum.ansible.com/t/so-ansible-commander-some-new-ideas-and-a-reminder-to-check-things-out/11924/3 "2012-09-25T15:18:51Z")
Thanks for the feedback -- I think the trick is to make it not focus /exclusively/ on inventory and make the API (and interface) try to encompass more of what Ansible can do. ---
**Author:** ![Edgars](https://avatars.discourse-cdn.com/v4/letter/e/f17d59/32.png) [@Edgars](https://forum.ansible.com/u/Edgars)\ **Post date:** [September 26, 2012, 8:25am UTC](https://forum.ansible.com/t/so-ansible-commander-some-new-ideas-and-a-reminder-to-check-things-out/11924/4 "2012-09-26T08:25:53Z")
> I have tried several times to install it, but no luck so far. I am stuck at ./setup.sh: after each task I have “no hosts matched or remaining” ---
**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:** [September 26, 2012, 11:10am UTC](https://forum.ansible.com/t/so-ansible-commander-some-new-ideas-and-a-reminder-to-check-things-out/11924/5 "2012-09-26T11:10:12Z")
This is because you had a failure while running the playbook. Some return codes are ignored for idempotency reasons (temporary hack until they could use the postgres modules Ansible ships with). Without the output of what that failure was, and what your platform was, there is nothing I can do for you. Please supply more information. I assume you had installed the PostgreSQL deps first, as the playbook will not do that for you presently (because I haven't added all the only\_if logic for different platforms yet). ---
**Author:** ![Edgars](https://avatars.discourse-cdn.com/v4/letter/e/f17d59/32.png) [@Edgars](https://forum.ansible.com/u/Edgars)\ **Post date:** [September 26, 2012, 12:31pm UTC](https://forum.ansible.com/t/so-ansible-commander-some-new-ideas-and-a-reminder-to-check-things-out/11924/6 "2012-09-26T12:31:37Z")
Here it is: > TASK: [configure password authentication for ansible\_commander database] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* > failed: [127.0.0.1] =\> {“failed” : true, “msg” : “line= doesn’t match regexp=”} All psql deps are installed… ---
**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:** [September 26, 2012, 12:37pm UTC](https://forum.ansible.com/t/so-ansible-commander-some-new-ideas-and-a-reminder-to-check-things-out/11924/7 "2012-09-26T12:37:51Z")
I'm guessing this is the problem: Make sure you are using ansible (and library files) from 0.8. The lineinfile module has been upgraded so the regexp module matches partial lines, like you would expect a regex to do, rather than having to match the entire line. The result of this is you can use simple strings with lineinfile and it's a lot easier to use -- but that's not available in 0.7. ---
**Author:** ![Edgars](https://avatars.discourse-cdn.com/v4/letter/e/f17d59/32.png) [@Edgars](https://forum.ansible.com/u/Edgars)\ **Post date:** [September 26, 2012, 1:04pm UTC](https://forum.ansible.com/t/so-ansible-commander-some-new-ideas-and-a-reminder-to-check-things-out/11924/8 "2012-09-26T13:04:40Z")
> Yes! It works with 0.8 Thanks