On Thu, Jan 9, 2014 at 9:01 AM, Thomas Goirand <
zigo@debian.org> wrote:
>
> On 01/09/2014 03:08 PM, Juerg Haefliger wrote:
> >> More on this. Even though I see the is_public=True flag when I do a
> >> "glance image-show", I still see the image as private in Horizon (and I
> >> don't see it at all in the HP web interface).
> >
> > What do you mean by 'see the image as private in Horizon'? For me, it's
> > in the list at
> >
https://horizon.hpcloud.com/project/images_and_snapshots/. Marked
> > properly as public.
> >
> > ...Juerg
>
> That one screen is just right, however, when I click on:
> + Launch instance
>
> to create a new VM, then I select:
> Instance boot source: Boot from image
>
> Then on the Image name popup, I can see my image at the bottom of the
> list, under "Private image - Linux".
Ah. OK. Confirmed. Seems to be a Horizon bug. Best is if you open a support ticket. A ticket from a customer gets more attention than my internal complaining :-)
> So there's still something wrong. Note that when I do "glance
> image-list", I do see the properties you suggested to add, and I do see
> the image as public.
>
> Cheers,
>
> Thomas Goirand (zigo)
>
> P.S: I still don't get what's the use of the config drive in the HP
> cloud context. Could you explain?
Do we support config drive? In general, config drive is OpenStack's equivalent of Amazon's EC2 metadata service. It's used to provide instance information (instance name, IP address, SSH key aso) to the instance though a mountable (read-only CDROM) drive but the image needs to support it. cloud-init's support of config drive is very limited and IIRC only supports static networking configuration at the moment (Rackspace needs this because they use static IPs in their environment hence the instance can't get to the EC2 metadata service without configuring the network first).
...Juerg