Re: [openstack-dev] [nova] Request Spec Freeze Exception (DRBD for Nova)

2015-02-16 Thread Daniel P. Berrange
On Mon, Feb 16, 2015 at 03:06:34PM +0100, Philipp Marek wrote:
 Hi all,
 
 Nikola just told me that I need an FFE for the code as well.
 
 Here it is: please grant a FFE for 
 
 https://review.openstack.org/#/c/149244/
 
 which is the code for the spec at
 
 https://review.openstack.org/#/c/134153/

The current feature freeze exceptions are being gathered for code
reviews whose specs/blueprints are already approved. Since your
spec does not appear to be approved, you would have to first
request a spec freeze exception, but I believe it is too late for
that now in Kilo.

Regards,
Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [nova] Request Spec Freeze Exception (DRBD for Nova)

2015-02-16 Thread Philipp Marek
Hi all,

Nikola just told me that I need an FFE for the code as well.

Here it is: please grant a FFE for 

https://review.openstack.org/#/c/149244/

which is the code for the spec at

https://review.openstack.org/#/c/134153/


Regards,

Phil

-- 
: Ing. Philipp Marek
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com :

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [nova] Request Spec Freeze Exception (DRBD for Nova)

2015-02-16 Thread Philipp Marek
Hi Daniel,
 
 The current feature freeze exceptions are being gathered for code
 reviews whose specs/blueprints are already approved. Since your
 spec does not appear to be approved, you would have to first
 request a spec freeze exception, but I believe it is too late for
 that now in Kilo.
I sent the Spec Freeze Exception request in January:
http://lists.openstack.org/pipermail/openstack-dev/2015-January/054225.html


Regards,

Phil

-- 
: Ing. Philipp Marek
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com :

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [nova] Request Spec Freeze Exception (DRBD for Nova)

2015-01-30 Thread Duncan Thomas
+1

Very excited to see this in and usable

Duncan Thomas
On Jan 30, 2015 2:56 AM, Philipp Marek philipp.ma...@linbit.com wrote:

 Hi all,

  in Paris (and later on, on IRC and the mailing list) I began to ask
 around
  about providing a DRBD storage driver for Nova.
  This is an alternative to using iSCSI for block storage access, and would
  be especially helpful for backends already using DRBD for replicated
  storage.
 any news about this?
 https://review.openstack.org/#/c/134153/


 To reiterate:
   * Spec was submitted in time (Nov 13)
   * Spec wasn't approved, because the Cinder implementation
 (https://review.openstack.org/#/c/140451/) merge got delayed,
 because its prerequisite (https://review.openstack.org/#/c/135139/,
 Transition LVM Driver to use Target Objects) wasn't merged in time,
 because on deadline day (Dec. 17) Gerrit was so much used that
 this devstack run got timeouts against some python site during
 setup
   * Spec Freeze Exception was submitted in time

 http://lists.openstack.org/pipermail/openstack-dev/2015-January/054225.html
   * Having DRBD for Cinder is good, but using the *same* protocol
 to the Nova nodes should really help performance (and reliability);
 for example, the transitions
   Network - Kernel - iSCSI daemon - Kernel - Block Device
 wouldn't be needed anymore; the Kernel could directly respond to the
 queries, and in the near future even using RDMA (where available).
 Reliability should be improved as the Nova node can access multiple
 storage nodes _at the same time_, so it wouldn't matter if one of them
 crashes for whatever reason.


 Please help us *now* to get the change in. It's only a few lines in
 a separate driver, so until it gets configured it won't even be
 noticed!


 And yes, of course we're planning to do CI for that Nova driver, too.


 Regards,

 Phil

 --
 : Ing. Philipp Marek
 : LINBIT | Your Way to High Availability
 : DRBD/HA support and consulting http://www.linbit.com :

 DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.

 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [nova] Request Spec Freeze Exception (DRBD for Nova)

2015-01-30 Thread Philipp Marek
Hi all,

 in Paris (and later on, on IRC and the mailing list) I began to ask around 
 about providing a DRBD storage driver for Nova.
 This is an alternative to using iSCSI for block storage access, and would 
 be especially helpful for backends already using DRBD for replicated 
 storage.
any news about this?
https://review.openstack.org/#/c/134153/


To reiterate:
  * Spec was submitted in time (Nov 13)
  * Spec wasn't approved, because the Cinder implementation
(https://review.openstack.org/#/c/140451/) merge got delayed,
because its prerequisite (https://review.openstack.org/#/c/135139/,
Transition LVM Driver to use Target Objects) wasn't merged in time,
because on deadline day (Dec. 17) Gerrit was so much used that
this devstack run got timeouts against some python site during
setup
  * Spec Freeze Exception was submitted in time
http://lists.openstack.org/pipermail/openstack-dev/2015-January/054225.html
  * Having DRBD for Cinder is good, but using the *same* protocol
to the Nova nodes should really help performance (and reliability);
for example, the transitions
  Network - Kernel - iSCSI daemon - Kernel - Block Device
wouldn't be needed anymore; the Kernel could directly respond to the
queries, and in the near future even using RDMA (where available).
Reliability should be improved as the Nova node can access multiple
storage nodes _at the same time_, so it wouldn't matter if one of them
crashes for whatever reason.


Please help us *now* to get the change in. It's only a few lines in
a separate driver, so until it gets configured it won't even be
noticed!


And yes, of course we're planning to do CI for that Nova driver, too.


Regards,
 
Phil

-- 
: Ing. Philipp Marek
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com :

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [nova] Request Spec Freeze Exception (DRBD for Nova)

2015-01-12 Thread Philipp Marek
Hello all,

in Paris (and later on, on IRC and the mailing list) I began to ask around 
about providing a DRBD storage driver for Nova.
This is an alternative to using iSCSI for block storage access, and would 
be especially helpful for backends already using DRBD for replicated 
storage.


The spec at

https://review.openstack.org/#/c/134153/

was not approved in December on the grounds that the DRBD Cinder driver 

https://review.openstack.org/#/c/140451/

should be merged first; because of (network) timeouts during the K-1 
milestone (and then merge conflicts, rebased dependencies, etc.) it wasn't
merged until recently (Jan 5th).

Now that the Cinder driver is already upstream, we'd like to ask for 
approval of the Nova driver - it would provide quite some performance boost 
over having all block storage data.


Thank you for your kind consideration!


Regards,

Phil

-- 
: Ing. Philipp Marek
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com :

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev