[Openstack-operators] [Openstack] Map Nova flavor to glance image

David Medberry openstack at medberry.net
Thu Aug 18 11:49:53 UTC 2016


Hi Jaison,

We do this in Horizon with a custom (locally changed) filter. I'll check to
see if it is upstreamed (it's certainly shareable, so I'll point you at a
git commit if it isn't all the way upstreamed once I get to the office.)

I know of no way of doing this directly in Nova at the api level. There is
a way to make the Murano and Trove instances "somewhat" hidden, by making
them private to certain projects that have that capability enabled thereby
not confusing non Murano, non Trove users but as soon as you add another
project to them, they will become visible everywhere within that project.

(As you might imagine this is a pretty common issue that we've directly
addressed with Trove but have seen no real solutions for yet.)

On Thu, Aug 18, 2016 at 5:45 AM, David Medberry <openstack at medberry.net>
wrote:

> Adding the Ops list.
> ---------- Forwarded message ----------
> From: Jaison Peter <urotrip2 at gmail.com>
> Date: Wed, Aug 17, 2016 at 10:29 PM
> Subject: [Openstack] Map Nova flavor to glance image
> To: OpenStack General <openstack at lists.openstack.org>
>
>
> Hi all,
>
> Is there any way to map a flavor to some specific glance images? For
> example if a user chooses flavor 'general_medium' then it shouldn't display
> any images used for trove or murano so that we can avoid the confusion.
> Right now, all images are displaying while choosing a flavor during
> instance launching. I think metadata is involved in this, but not sure how
> to do it.
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160818/4a0eea27/attachment.html>


More information about the OpenStack-operators mailing list