On Tue, 2014-09-23 at 18:39 +0100, Louis Taylor wrote: > On Tue, Sep 23, 2014 at 01:32:50PM -0400, Andrew Laski wrote: > > I've been thinking along very similar lines, but I don't think each current > > API needs to be replaced. I would very much like to see a unified API > > project that could be responsible for managing requests to "boot an instance > > with this network and that volume" which would make requests to > > Nova/Neutron/Cinder on the users behalf. > > Isn't this what openstacksdk [0] is? > > [0] https://wiki.openstack.org/wiki/SDK-Development/PythonOpenStackSDK
Well, openstacksdk is a client, and we're talking about a server. A server, in this instance, has some advantages over a client, including making it easier to create that client in the first place :) -- Kevin L. Mitchell <kevin.mitch...@rackspace.com> Rackspace _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
