[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Verita
|
From: |
Daniel P. Berrange |
|
Subject: |
Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support |
|
Date: |
Thu, 2 Feb 2017 09:53:02 +0000 |
|
User-agent: |
Mutt/1.7.1 (2016-10-04) |
On Wed, Feb 01, 2017 at 11:59:53PM +0000, Ketan Nilangekar wrote:
> Patch for secure implementation in libqnio is available for review here:
>
> https://github.com/VeritasHyperScale/libqnio/pull/12
IMHO, we really don't want libqnio to be doing the SSL handling
itself. QEMU has a standardized API for doing SSL that the vxhs
layer should be using, so that its behaviour & configuration is
exactly the same as other bits of QEMU using SSL.
To do this, libqnio would have to delegate all socket I/O to
QEMU, by providing a set of callback APIs that QEMU can provide
implementations for.
The QEMU block driver for vxhs would use qio_channel_socket and
qio_channel_tls APIs to setup the socket & do SSL handshakes,
etc.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
Re: [Qemu-devel] [PATCH v7 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support, Ketan Nilangekar, 2017/02/02