# Ansible-commander UI and REST API project repo **URL:** \ **Category:** Ansible Project\ **Created:** [September 7, 2012, 11:10pm UTC](https://forum.ansible.com/t/ansible-commander-ui-and-rest-api-project-repo/11872 "2012-09-07T23:10:07Z")\ **Posts on this page:** 6\ **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 7, 2012, 11:10pm UTC](https://forum.ansible.com/t/ansible-commander-ui-and-rest-api-project-repo/11872/1 "2012-09-07T23:10:07Z")
I'm going to try being totally transparent here and letting you watch this project start while there is nothing here yet... Starting this here -- [https://github.com/ansible/ansible-commander](https://github.com/ansible/ansible-commander) As you can see, there's almost nothing here yet! Many things will be initially very very rough and will evolve over time. If it looks like I'm doing something dumb, it's probably because I am intending to fix them later. Pull requests won't be accepted for a while until things get established, and I'll let you know when that is for each piece of things. I have put my plans in TODO.md, and will check them off as things get done. [https://github.com/ansible/ansible-commander/blob/master/TODO.md](https://github.com/ansible/ansible-commander/blob/master/TODO.md) The first thing that's here -- to make sure we stay honest and that nobody complains about database setup, setup uses an Ansible playbook! --Michael ---
**Author:** ![Marco\_Vito\_Moscarito](https://avatars.discourse-cdn.com/v4/letter/m/97f17d/32.png) [@Marco\_Vito\_Moscarito](https://forum.ansible.com/u/Marco_Vito_Moscarito)\ **Post date:** [September 8, 2012, 10:00am UTC](https://forum.ansible.com/t/ansible-commander-ui-and-rest-api-project-repo/11872/2 "2012-09-08T10:00:36Z")
> The first thing that's here -- to make sure we stay honest and that > nobody complains about database setup, setup uses an Ansible playbook! Just a simple prototype of UI, I try to display information required to only see what is available on servers.    \* [http://mavimo.github.com/ansible-ui/](http://mavimo.github.com/ansible-ui/) Some day ago I start to prototype an application to display my infrastructure using ansible and webpy (my app is really customized on own infrastructure, so is not usefull to share), but I think will be usefull to have a "pluggable" interface for ansible commander, so "basic structure" can be "standard ansible application" but other user can add some custom elements (eg.: RackSpace load balanacer monitoring, AWS bind to S3, ..) > --Michael Bye        Marco PS: take a look to [http://wrapbootstrap.com/preview/WB0F35928](http://wrapbootstrap.com/preview/WB0F35928) it's awesome! ---
**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 8, 2012, 12:09pm UTC](https://forum.ansible.com/t/ansible-commander-ui-and-rest-api-project-repo/11872/3 "2012-09-08T12:09:36Z")
> \> The first thing that's here -- to make sure we stay honest and that > \> nobody complains about database setup, setup uses an Ansible playbook! > > Just a simple prototype of UI, I try to display information required > to only see what is available on servers. > > \* [http://mavimo.github.com/ansible-ui/](http://mavimo.github.com/ansible-ui/) This is nice work! One of the small UX challenges I have is how to represent large numbers of systems. We can probably list all groups flat, but systems are probably going to need do to either be shown when looking at a single group. > Some day ago I start to prototype an application to display my > infrastructure using ansible and webpy (my app is really customized on > own infrastructure, so is not usefull to share), but I think will be > usefull to have a "pluggable" interface for ansible commander, so > "basic structure" can be "standard ansible application" but other user > can add some custom elements (eg.: RackSpace load balanacer > monitoring, AWS bind to S3, ..) Absolutely. This is something I was always trying to push in the Red Hat management UIs (Satellite, etc) though it never really happened. ---
**Author:** ![Marco\_Vito\_Moscarito](https://avatars.discourse-cdn.com/v4/letter/m/97f17d/32.png) [@Marco\_Vito\_Moscarito](https://forum.ansible.com/u/Marco_Vito_Moscarito)\ **Post date:** [September 8, 2012, 2:16pm UTC](https://forum.ansible.com/t/ansible-commander-ui-and-rest-api-project-repo/11872/4 "2012-09-08T14:16:42Z")
> > \* [http://mavimo.github.com/ansible-ui/](http://mavimo.github.com/ansible-ui/) > > This is nice work! Thank you. > One of the small UX challenges I have is how to represent large numbers of systems. > > We can probably list all groups flat, but systems are probably going to need do to either be shown when looking at a single group. Maybe can be paged? How many system can you consider "a limit"? I think create a limited number of page that display all information (only for list,of course), inside a "large number of page", with display only a limited number of items can be preferible to have a complete overview of infrastructure. I tnk a hundred of server (per project) can be considered a "limit". > > Some day ago I start to prototype an application to display my > > infrastructure using ansible and webpy (my app is really customized on > > own infrastructure, so is not usefull to share), but I think will be > > usefull to have a "pluggable" interface for ansible commander, so > > "basic structure" can be "standard ansible application" but other user > > can add some custom elements (eg.: RackSpace load balanacer > > monitoring, AWS bind to S3, ..) > > Absolutely. Ok. > This is something I was always trying to push in the Red Hat management UIs (Satellite, etc) though it never > really happened. In other application I use there are "module", each module implement some "hook" that expose information into main system that manage this data, eg: \* Module "firewall" expose a "hook\_block" and "hook\_page" \* Main system use information from hook\_block to add some element into dashboard and hook\_page to add item to page list. Bye        Marco ---
**Author:** ![Mark\_Theunissen](https://avatars.discourse-cdn.com/v4/letter/m/898d66/32.png) [@Mark\_Theunissen](https://forum.ansible.com/u/Mark_Theunissen)\ **Post date:** [September 8, 2012, 3:31pm UTC](https://forum.ansible.com/t/ansible-commander-ui-and-rest-api-project-repo/11872/5 "2012-09-08T15:31:40Z")
Nice interface! I’m kinda excited about this now. - Mark ---
**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 8, 2012, 4:05pm UTC](https://forum.ansible.com/t/ansible-commander-ui-and-rest-api-project-repo/11872/6 "2012-09-08T16:05:44Z")
The API will probably be paginated.