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
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
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
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/
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 it's awesome!
> 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/
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.
* 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
Nice interface! I’m kinda excited about this now.
The API will probably be paginated.