[glance][interop] standardized image "name" ?

Monty Taylor mordred at inaugust.com
Mon Apr 8 10:41:48 UTC 2019

On 4/8/19 10:10 AM, Graham Hayes wrote:
> On 08/04/2019 07:14, Tim Bell wrote:
>> You could use the standard image properties (https://docs.openstack.org/glance/stein/admin/useful-image-properties.html) to find the image using a query
>> e.g. os_distro=centos, os_version=7 and sort by upload date
>> Tim
> I like the idea of it being discoverable, not defined by using the name
> - it fits better in my head with the way we are doing interop and allows
> current clouds to not have to change name formats (which could break
> other users).

I would love it if we could provide guidance - or maybe even somehow get 
this in to RefStack or something - that clouds *should* provide that 

At the same time, needing to search for an image (and a flavor) on the 
cloud makes this:

   openstack server boot --image=<image> --flavor=<flavor> foo

a bit harder. Perhaps we could add some parameters ... like:

   openstack server boot --image-os=debian --image-version=7

And it would use the latest image matching those or fail if the 
properties arent' defined on that cloud.

>> -----Original Message-----
>> From: Mark Voelker <mvoelker at vmware.com>
>> Date: Monday, 8 April 2019 at 05:45
>> To: Mohammed Naser <mnaser at vexxhost.com>
>> Cc: OpenStack Discuss <openstack-discuss at lists.openstack.org>
>> Subject: Re: [glance][interop] standardized image "name" ?
>>      I don’t think I have a perfect answer here, but just to add fodder to the discussion: it’s often been suggested in the past that one way of dealing with this is to simply ensure that you can bring your image to any cloud you work with.  Thus, rather than relying on an image to be named the same across the clouds you deal with, you can simply provide it yourself on those clouds so you know it’s identical.  Many of the caveats to this approach should be fairly obvious (footprint, duplication, quotas, format conversion, etc), but for some workflows it provides the sorts of useful guarantees an end user may want.
>>      At Your Service,
>>      Mark T. Voelker
>>      > On Apr 7, 2019, at 5:35 PM, Mohammed Naser <mnaser at vexxhost.com> wrote:
>>      >
>>      > Hi everyone,
>>      >
>>      > Something that I've been dealing with is the fact that regardless of
>>      > what cloud you're using, the naming structure is very much different.
>>      > While we aim to be interoperable, if I want to "boot an Debian Stretch
>>      > server", the image name will probably be different all over the
>>      > places.
>>      >
>>      > Is there some sort of way we can eliminate this by implementing a
>>      > standard naming convention which would allow us to use the same images
>>      > across all systems?
>>      >
>>      > I'm just opening the idea for discussion, I'd love to hear what others
>>      > think about this.
>>      >
>>      > Mohammed
>>      >
>>      > --
>>      > Mohammed Naser — vexxhost
>>      > -----------------------------------------------------
>>      > D. 514-316-8872
>>      > D. 800-910-1726 ext. 200
>>      > E. mnaser at vexxhost.com
>>      > W. https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvexxhost.com&data=02%7C01%7Cmvoelker%40vmware.com%7C35dc7472fc9b465af68908d6bba19d77%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C636902700146796905&sdata=ek0QPuY4h0Bvso6dk3c%2BPWovZ4suu89a9Rv0Z1VliIY%3D&reserved=0
>>      >

More information about the openstack-discuss mailing list