Re: [openstack-dev] [ironic] support for various glance image reference formats - do we need them all?

Got it, thanks for explaining. Mark On 11 August 2017 at 10:46, Pavlo Shchelokovskyy < pshchelokovs...@mirantis.com> wrote: > Hi Mark, > > I do not propose to remove handling of plain http image references > altogether, just remove the code pieces in glance service utils that > pretend to

Re: [openstack-dev] [ironic] support for various glance image reference formats - do we need them all?

Hi Mark, I do not propose to remove handling of plain http image references altogether, just remove the code pieces in glance service utils that pretend to support such refs *for glance images*. This code is never reached exactly due to plain http links being recognized as such from the very

Re: [openstack-dev] [ironic] support for various glance image reference formats - do we need them all?

Hi Pavlo, #3 is used in Bifrost, where there is no Glance service but the default driver is agent_ipmitool. The images are served by the local nginx service. For example, taken from one ironic node: 'image_source': u'http://10.41.253.100:8080/deployment_image.qcow2' Mark On 10 August 2017 at

Re: [openstack-dev] [ironic] support for various glance image reference formats - do we need them all?

HI Dmitry, On Tue, Aug 8, 2017 at 7:13 PM, Dmitry Tantsur wrote: > Hi! > > Thanks for raising this. > > On 08/07/2017 02:47 PM, Pavlo Shchelokovskyy wrote: > >> Hi all, >> >> currently our GlanceImageService seems to support several ways of >> defining a reference to glance

Re: [openstack-dev] [ironic] support for various glance image reference formats - do we need them all?

Hi! Thanks for raising this. On 08/07/2017 02:47 PM, Pavlo Shchelokovskyy wrote: Hi all, currently our GlanceImageService seems to support several ways of defining a reference to glance image: 1) simple image UUID [0] 2) image UUID prefixed with 'glance://' protocol [1] (well, actually

[openstack-dev] [ironic] support for various glance image reference formats - do we need them all?

Hi all, currently our GlanceImageService seems to support several ways of defining a reference to glance image: 1) simple image UUID [0] 2) image UUID prefixed with 'glance://' protocol [1] (well, actually anything starting with 'glance://' and ending with '/') 3) full REST path to the image (as