Re: [openstack-dev] [nova] New image backend: StorPool

2018-03-19 Thread melanie witt
On Fri, 16 Mar 2018 19:24:01 +0200, Peter Penchev wrote: On Fri, Mar 16, 2018 at 09:23:11AM -0700, melanie witt wrote: On Fri, 16 Mar 2018 17:33:30 +0200, Peter Penchev wrote: Would there be any major opposition to adding a StorPool shared storage image backend, so that our customers are not

Re: [openstack-dev] [nova] New image backend: StorPool

2018-03-16 Thread Peter Penchev
On Fri, Mar 16, 2018 at 09:39:14AM -0700, Dan Smith wrote: > > Can you be more specific about what is limiting you when you use > > volume-backed instances? > > Presumably it's because you're taking a trip over iscsi instead of using > the native attachment mechanism for the technology that

Re: [openstack-dev] [nova] New image backend: StorPool

2018-03-16 Thread Duncan Thomas
On 16 March 2018 at 16:39, Dan Smith wrote: >> Can you be more specific about what is limiting you when you use >> volume-backed instances? > > Presumably it's because you're taking a trip over iscsi instead of using > the native attachment mechanism for the technology that

Re: [openstack-dev] [nova] New image backend: StorPool

2018-03-16 Thread Peter Penchev
On Fri, Mar 16, 2018 at 09:23:11AM -0700, melanie witt wrote: > On Fri, 16 Mar 2018 17:33:30 +0200, Peter Penchev wrote: > > Would there be any major opposition to adding a StorPool shared > > storage image backend, so that our customers are not limited to > > volume-backed instances? Right now,

Re: [openstack-dev] [nova] New image backend: StorPool

2018-03-16 Thread Dan Smith
> Can you be more specific about what is limiting you when you use > volume-backed instances? Presumably it's because you're taking a trip over iscsi instead of using the native attachment mechanism for the technology that you're using? If so, that's a valid argument, but it's hard to see the

Re: [openstack-dev] [nova] New image backend: StorPool

2018-03-16 Thread young, eric
I can provide some insights from the Dell EMC ScaleIO side. As you can see from the patch that Matt pointed to, it is possible to add ephemeral/image backend support to Nova. That said, it is not easy and [IMHO] prone to error. There is no ‘driver model’ like there is in Cinder, where you just

Re: [openstack-dev] [nova] New image backend: StorPool

2018-03-16 Thread Peter Penchev
On Fri, Mar 16, 2018 at 11:04:06AM -0500, Sean McGinnis wrote: > Just updating the subject line tag to glance. ;) Errr, sorry, but no, this is for a Nova image backend (yes, namespace overload, I know) - the driver that lets a Nova host create "local" images for non-volume-backed instances. > On

Re: [openstack-dev] [nova] New image backend: StorPool

2018-03-16 Thread melanie witt
On Fri, 16 Mar 2018 17:33:30 +0200, Peter Penchev wrote: Would there be any major opposition to adding a StorPool shared storage image backend, so that our customers are not limited to volume-backed instances? Right now, creating a StorPool volume and snapshot from a Glance image and then

Re: [openstack-dev] [nova] New image backend: StorPool

2018-03-16 Thread Matt Riedemann
On 3/16/2018 10:33 AM, Peter Penchev wrote: Would there be any major opposition to adding a StorPool shared storage image backend, so that our customers are not limited to volume-backed instances? Right now, creating a StorPool volume and snapshot from a Glance image and then booting instances