[Openstack] Management API

Jay Pipes jaypipes at gmail.com
Fri Mar 4 14:39:00 UTC 2011

Hi Glen,

I've read through the wiki page and although I think the individual
commands are worthy commands to add to the API, I don't see why this
is all being bunched into (yet another) API. I think if you broke out
these commands into individual blueprints:

* Contributors could have already completed work on some of them and
others would have already gotten a good head start
* We wouldn't be setting up (yet another) giant debate on whether all
this functionality should be grouped into a Management API

In addition, some of the added commands have dependencies that other
commands don't. An example: the /accounts stuff clearly depends on the
Authentication stuff currently being prototyped and debated. But the
/hosts commands clearly don't. Grouping all this stuff together
implies that the commands cannot be logically coded separately and
distinctly proposed for inclusion into the singular OpenStack API.

While I certainly recognize and respect that you need to provide a gap
analysis to management inside Rackspace, doing things this way will
actually prolong the coding of at least a good portion of these things
IMHO. And, since we're now less than 2 weeks from feature freeze, I
can't see how prolonging the coding on these features is going to
help. I would propose that blueprints be created and assigned almost
immediately to contributors for the commands in the proposed
management API that do not have dependencies on things like
Authentication. The fact that authentication is happening so late in
the release cycle is already going to throw a wrench in many
blueprints that are dependent on it...


On Wed, Mar 2, 2011 at 3:49 PM, Glen Campbell
<glen.campbell at rackspace.com> wrote:
> There's been some discussion of an admin/management API and what functions
> would be provided there. I've been tasked with handling the technical
> coordination of implementing Nova at Rackspace, and have thus been
> identifying gaps between functionality that our current system provides and
> those provided by Nova.
> I've created a preliminary proposal
> at http://wiki.openstack.org/NovaAdminAPI – this is still somewhat early,
> but I want to make sure that the OpenStack community has the opportunity to
> provide feedback.
> My expectations are that management API features will fall into two
> categories: (1) those that would be generally useful to anyone who deploys
> OpenStack Compute, and (2) those that are specific to Rackspace's needs (or
> perhaps another service provider). One of the goals of this discussion is to
> identify those different features. While all these features will initially
> be implemented using the API 1.1 extensions mechanism, those that fall into
> category (1) may be migrated to Nova-core in the near future, while (2) will
> remain Rackspace-specific extensions.
> Glen Campbell
> Confidentiality Notice: This e-mail message (including any attached or
> embedded documents) is intended for the exclusive and confidential use of
> the
> individual or entity to which this message is addressed, and unless
> otherwise
> expressly indicated, is confidential and privileged information of
> Rackspace.
> Any dissemination, distribution or copying of the enclosed material is
> prohibited.
> If you receive this transmission in error, please notify us immediately by
> e-mail
> at abuse at rackspace.com, and delete the original message.
> Your cooperation is appreciated.
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

More information about the Openstack mailing list