Re: [Openstack-operators] RFC: Next minimum libvirt / QEMU versions for 'T' release

2018-09-27 Thread Kashyap Chamarthy
On Mon, Sep 24, 2018 at 09:11:42AM -0700, iain MacDonnell wrote: > > > On 09/24/2018 06:22 AM, Kashyap Chamarthy wrote: > > (b) Oracle Linux: Can you please confirm if you'll be able to > > release libvirt and QEMU to 4.0.0 and 2.11, respectively? > > Hi

[Openstack-operators] RFC: Next minimum libvirt / QEMU versions for 'T' release

2018-09-24 Thread Kashyap Chamarthy
Hey folks, Before we bump the agreed upon[1] minimum versions for libvirt and QEMU for 'Stein', we need to do the tedious work of picking the NEXT_MIN_* versions for the 'T' (which is still in the naming phase) release, which will come out in the autumn (Sep-Nov) of 2019. Proposal Looki

Re: [Openstack-operators] [openstack-dev] RFC: Next minimum libvirt / QEMU versions for "Stein" release

2018-04-10 Thread Kashyap Chamarthy
On Mon, Apr 09, 2018 at 04:24:06PM -0500, Matt Riedemann wrote: > On 4/9/2018 4:58 AM, Kashyap Chamarthy wrote: > > Keep in mind that Matt has a tendency to sometimes unfairly > > over-simplify others views;-). More seriously, c'mon Matt; I went out > > of my way to

Re: [Openstack-operators] [openstack-dev] RFC: Next minimum libvirt / QEMU versions for "Stein" release

2018-04-09 Thread Kashyap Chamarthy
On Fri, Apr 06, 2018 at 12:12:31PM -0500, Matt Riedemann wrote: > On 4/6/2018 12:07 PM, Kashyap Chamarthy wrote: > > FWIW, I'd suggest so, if it's not too much maintenance. It'll just > > spare you additional bug reports in that area, and the overall default > &

Re: [Openstack-operators] [openstack-dev] RFC: Next minimum libvirt / QEMU versions for "Stein" release

2018-04-06 Thread Kashyap Chamarthy
On Fri, Apr 06, 2018 at 06:07:18PM +0200, Thomas Goirand wrote: > On 04/06/2018 12:07 PM, Kashyap Chamarthy wrote: [...] > > Note: You don't even have to build the versions from 'Buster', which are > > quite new. Just the slightly more conservative libvirt 3.2.0

Re: [Openstack-operators] [openstack-dev] RFC: Next minimum libvirt / QEMU versions for "Stein" release

2018-04-06 Thread Kashyap Chamarthy
On Thu, Apr 05, 2018 at 06:11:26PM -0500, Matt Riedemann wrote: > On 4/5/2018 3:32 PM, Thomas Goirand wrote: > > If you don't absolutely need new features from libvirt 3.2.0 and 3.0.0 > > is fine, please choose 3.0.0 as minimum. > > > > If you don't absolutely need new features from qemu 2.9.0 and

Re: [Openstack-operators] [openstack-dev] RFC: Next minimum libvirt / QEMU versions for "Stein" release

2018-04-06 Thread Kashyap Chamarthy
On Thu, Apr 05, 2018 at 10:32:13PM +0200, Thomas Goirand wrote: Hey Zigo, thanks for the detailed response; a couple of comments below. [...] > backport of libvirt/QEMU/libguestfs more in details > --- > > I already attempted the backports from De

Re: [Openstack-operators] [openstack-dev] RFC: Next minimum libvirt / QEMU versions for "Stein" release

2018-04-04 Thread Kashyap Chamarthy
On Sat, Mar 31, 2018 at 04:09:29PM +0200, Kashyap Chamarthy wrote: > [Meta comment: corrected the email subject: "Solar" --> "Stein"] Here's a change to get the discussion rolling: https://review.openstack.org/#/c/558171/ -- [RFC] Pick next minimum lib

Re: [Openstack-operators] RFC: Next minimum libvirt / QEMU versions for "Stein" release

2018-03-31 Thread Kashyap Chamarthy
[Meta comment: corrected the email subject: "Solar" --> "Stein"] On Fri, Mar 30, 2018 at 04:26:43PM +0200, Kashyap Chamarthy wrote: > The last version bump was in "Pike" release (commit: b980df0, > 11-Feb-2017), and we didn't do any bump during "Q

Re: [Openstack-operators] RFC: Next minimum libvirt / QEMU versions for "Solar" release

2018-03-31 Thread Kashyap Chamarthy
On Sat, Mar 31, 2018 at 03:17:52PM +0200, Kashyap Chamarthy wrote: > On Fri, Mar 30, 2018 at 09:49:17AM -0500, Sean McGinnis wrote: [...] > > > Taking the DistroSupportMatrix into picture, for the sake of discussion, > > > how about the following NEXT_MIN version

Re: [Openstack-operators] RFC: Next minimum libvirt / QEMU versions for "Solar" release

2018-03-31 Thread Kashyap Chamarthy
On Fri, Mar 30, 2018 at 09:49:17AM -0500, Sean McGinnis wrote: > > While at it, we should also discuss about what will be the NEXT_MIN > > > > libvirt and QEMU versions for the "Solar" release. To that end, I've > > > > spent going through di

[Openstack-operators] RFC: Next minimum libvirt / QEMU versions for "Solar" release

2018-03-30 Thread Kashyap Chamarthy
The last version bump was in "Pike" release (commit: b980df0, 11-Feb-2017), and we didn't do any bump during "Queens". So it's time to increment the versions (which will also makes us get rid of some backward compatibility cruft), and pick future versions of libvirt and QEMU.

[Openstack-operators] Call For Proposals: KVM Forum 2017 [Submission deadline: 15-JUN-2017]

2017-06-09 Thread Kashyap Chamarthy
KVM Forum 2017: Call For Participation October 25-27, 2017 - Hilton Prague - Prague, Czech Republic (All submissions must be received before midnight June 15, 2017) =

Re: [Openstack-operators] [openstack-dev] [nova] Next minimum libvirt version

2017-02-10 Thread Kashyap Chamarthy
On Thu, Feb 09, 2017 at 05:29:22PM -0600, Matt Riedemann wrote: > Since danpb hasn't been around I've sort of forgotten about this, but we > should talk about bumping the minimum required libvirt version in nova. > > Currently it's 1.2.1 and the next was set to 1.2.9. > > On master we're gating o

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

2016-05-11 Thread Kashyap Chamarthy
On Tue, May 03, 2016 at 02:27:00PM -0500, Sergio Cuellar Valdes wrote: [...] > I'm confused too about the use of KVM or QEMU In the computes the > file​/etc/nova/nova-compute.conf has: > > virt_type=kvm > > The output of: > > nova hypervisor-show | grep hypervisor_type > > is: > > hyperviso

Re: [Openstack-operators] raw ephemeral disks and qcow2 images

2015-10-23 Thread Kashyap Chamarthy
ds input from other Nova developers who're more familiar with the intricacies of qcow2 cache configuration. > > -Original Message- > > From: Kashyap Chamarthy [mailto:kcham...@redhat.com] > > Sent: 23 October 2015 12:37 > > To: Tim Bell > > Cc: Marc H

Re: [Openstack-operators] raw ephemeral disks and qcow2 images

2015-10-23 Thread Kashyap Chamarthy
On Fri, Oct 23, 2015 at 06:21:23AM +, Tim Bell wrote: > > On 22/10/15 20:01, "Marc Heckmann" wrote: > > >Hi, > > > >On Thu, 2015-10-22 at 08:17 -0700, Abel Lopez wrote: > >> I've actually looked for this for our RBD backed ephemeral instances, > >> but found the options lacking. I last looke

[Openstack-operators] [nova] Change from Mitaka: Expected UNIX signal to generate Guru Meditation (error) Reports

2015-10-21 Thread Kashyap Chamarthy
Background -- Oslo Guru Meditation (error) Reports (GMR)[*] are a useful debugging mechanism that allows one to capture the current state of a Nova process/executable (e.g. `nova-compute`, `nova-api`, etc). The way to generate the error report is to supply the 'User-defined signal', SIGUS