Does QEMU support hardware initiators? iSER?
No, this is only for case where you're doing pure software based
iSCSI client connections. If we're relying on local hardware that's
a different story.
We regularly fix issues with iSCSI attaches in the release cycles of
OpenStack,
because it's all
On Fri, Jun 24, 2016 at 08:05:38AM -0600, John Griffith wrote:
> On Fri, Jun 24, 2016 at 2:19 AM, Daniel P. Berrange
> wrote:
>
> > On Thu, Jun 23, 2016 at 09:09:44AM -0700, Walter A. Boring IV wrote:
> > >
> > > volumes connected to QEMU instances eventually become directly connected?
> > >
> >
On Fri, Jun 24, 2016 at 2:19 AM, Daniel P. Berrange
wrote:
> On Thu, Jun 23, 2016 at 09:09:44AM -0700, Walter A. Boring IV wrote:
> >
> > volumes connected to QEMU instances eventually become directly connected?
> >
> > > Our long term goal is that 100% of all network storage will be
> connected
On Thu, Jun 23, 2016 at 09:09:44AM -0700, Walter A. Boring IV wrote:
>
> volumes connected to QEMU instances eventually become directly connected?
>
> > Our long term goal is that 100% of all network storage will be connected
> > to directly by QEMU. We already have the ability to partially do th
On 06/23/2016 Daniel Berrange wrote (lost attribution in thread):
> Our long term goal is that 100% of all network storage will be connected
>
to directly by QEMU. We already have the ability to partially do this with
> iSCSI, but it is lacking support for multipath. As & when that gap is
> addre
On Thu, Jun 23, 2016 at 12:07:43PM -0600, Chris Friesen wrote:
> On 06/23/2016 10:09 AM, Walter A. Boring IV wrote:
> >
> >volumes connected to QEMU instances eventually become directly connected?
> >
> >>Our long term goal is that 100% of all network storage will be connected
> >>to directly by QE
On Thu, Jun 23, 2016 at 09:50:11AM -0700, Preston L. Bannister wrote:
> Daniel, Thanks. Looking for a sense of direction.
>
> Clearly there is some range of opinion, as Walter indicates. :)
>
> Not sure you are get to 100% direct connection to QEMU. When there is
> dedicated hardware to do off-bo
On 06/23/2016 10:09 AM, Walter A. Boring IV wrote:
volumes connected to QEMU instances eventually become directly connected?
Our long term goal is that 100% of all network storage will be connected
to directly by QEMU. We already have the ability to partially do this with
iSCSI, but it is lack
Daniel, Thanks. Looking for a sense of direction.
Clearly there is some range of opinion, as Walter indicates. :)
Not sure you are get to 100% direct connection to QEMU. When there is
dedicated hardware to do off-board processing of the connection to storage,
you might(?) be stuck routing through
volumes connected to QEMU instances eventually become directly connected?
Our long term goal is that 100% of all network storage will be connected
to directly by QEMU. We already have the ability to partially do this with
iSCSI, but it is lacking support for multipath. As & when that gap is
add
On Wed, Jun 15, 2016 at 04:59:39PM -0700, Preston L. Bannister wrote:
> QEMU has the ability to directly connect to iSCSI volumes. Running the
> iSCSI connections through the nova-compute host *seems* somewhat
> inefficient.
>
> There is a spec/blueprint and implementation that landed in Kilo:
>
On Wed, Jun 15, 2016 at 5:59 PM, Preston L. Bannister
wrote:
> QEMU has the ability to directly connect to iSCSI volumes. Running the
> iSCSI connections through the nova-compute host *seems* somewhat
> inefficient.
>
I know tests I've run in the past virt-io actually does a really good job
her
One major disadvantage is lack of multipath support.
Multipath is still done outside of qemu and there is no native multipath
support inside of qemu from what I can tell. Another
disadvantage is that qemu iSCSI support is all s/w based. There are
hardware iSCSI initiators that are supported by
QEMU has the ability to directly connect to iSCSI volumes. Running the
iSCSI connections through the nova-compute host *seems* somewhat
inefficient.
There is a spec/blueprint and implementation that landed in Kilo:
https://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/qemu-built
14 matches
Mail list logo
