[openstack-dev] [Nova] Future of nova-api operations that act on all servers on a host

Álvaro López García alvaro.lopez.garcia at cern.ch
Mon Apr 22 17:58:12 UTC 2013

On Mon 22 Apr 2013 (12:47), Kevin L. Mitchell wrote:
> On Mon, 2013-04-22 at 13:33 -0400, Russell Bryant wrote:
> > Of the things that already exist, python-novaclient makes the most
> > sense.  I'm concerned with the significant scope increase, though.  This
> > takes novaclient from a fairly straight forward API wrapper library and
> > cmd line tool to something that orchestrates nova operational
> > activities.  Maybe that's ok, though.  I'd like to see some more in
> > depth exploration of how this might be structured so that it's only
> > exposed to admins and kept somewhat separate from the traditional stuff
> > in novaclient that is just wrapping the API.
> Maybe the solution then is not to implement these sorts of
> administrative tools in novaclient; just implement the base calls, then
> write a new administrative tool that uses the novaclient API and
> performs the calls; you could call it "nova-admin".

+1 on this.

Álvaro López García                              aloga at ifca.unican.es
Instituto de Física de Cantabria         http://devel.ifca.es/~aloga/
Ed. Juan Jordá, Campus UC                      tel: (+34) 942 200 969
Avda. de los Castros s/n
39005 Santander (SPAIN)
"Those that can, do. Those that can't, complain." -- Linus Torvalds

More information about the OpenStack-dev mailing list