[openstack-dev] [nova][glance] Future of nova's image API

Joe Gordon joe.gordon0 at gmail.com
Mon Aug 5 19:10:48 UTC 2013

On Mon, Aug 5, 2013 at 7:26 AM, John Garbutt <john at johngarbutt.com> wrote:

> On 3 August 2013 03:07, Christopher Yeoh <cbkyeoh at gmail.com> wrote:
> > Some people had concerns about exposing the glance api publicly and so
> > wanted to retain the images support in Nova.
> > So the consensus seemed to be to leave the images support in, but to
> demote
> > it from core. So people who don't want it exclude the os-images
> extension.
> I think a lot of the concern was around RBAC, but seems most of that
> will be fixed by the end of Havana:
> https://blueprints.launchpad.net/glance/+spec/api-v2-property-protection

I figured it was something like that but wanted to be sure.

> Given v3 is will not be "finished" till Icehouse, maybe we should look
> at removing os-images extension for now, and putting it back in for
> Icehouse if it causes people real headaches?

+1, I don't like the idea of solving glance concerns by using nova in front

> > Just as I write this I've realised that the servers api currently returns
> > links to the image used for the instance. And that won't be valid if the
> > images extension is not loaded. So probably have some work to do there to
> > support  that properly.
> Have we decided a good strategy for this in v3? Referring to image in
> glance, and networks and ports in neutron.

So neutron is a little different, because we still have nova-networking,
but we don't have a nova-images.

> The pragmatic part of me says:
> * just use the uuid, its what the users will input when booting servers
> But I wonder if a REST purest would say:
> * an image is a REST resource, so we should have a URL pointing to the
> exposed glance service?
> What do you think? I just want to make sure we make a deliberate choice.

Good question

> John
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130805/49ccb5d4/attachment.html>

More information about the OpenStack-dev mailing list