On Thu, Sep 22, 2016 at 04:25:00PM +1000, Tony Breeds wrote:
> On Wed, Sep 21, 2016 at 02:05:51PM -0400, Sean Dague wrote:
>
> > Well, the risk profile of what has to be changed for stable/liberty
> > (given that all the actual code is buried in libraries which have tons
> > of other changes).
On Tue, Sep 20, 2016 at 12:48:49PM +0200, Kashyap Chamarthy wrote:
> The said patch in question fixes a CVE[x] in stable/liberty.
>
> We currently have two options, both of them have caused an impasse with
> the Nova upstream / stable maintainers. We've had two-ish months to
On Tue, Sep 20, 2016 at 04:20:49PM +0100, Daniel P. Berrange wrote:
> On Tue, Sep 20, 2016 at 11:01:23AM -0400, Sean Dague wrote:
[...]
> > Here is my reconstruction of the snapshot issue from what I can remember
> > of the conversation.
> >
> > Nova defaults to live snapshots. This uses the
===
The call for proposals is now open for the Virtualization & IaaS devroom
at the upcoming FOSDEM 2017, to be hosted on February 4, 2017.
This year will mark FOSDEM’s 17th anniversary as one of the
longest-running free and
On Tue, Oct 11, 2016 at 02:09:33PM +0200, Markus Zoeller wrote:
[Snip well-written backrgound detail]
> Request
> ---
> My question is, if you have interest in this plugin and its
> capabilities, are you at the Summit in Barcelona and do you have time
> for a short working session there?
On Tue, Oct 11, 2016 at 05:53:24PM +0200, Thomas Goirand wrote:
> On 10/11/2016 02:09 PM, Markus Zoeller wrote:
> > * How to create a "*.deb" package out of the source code of
> > libvirt/qemu? (surprisingly enough, I'm still struggling with this)
>
> What version of libvirt / qemu are you trying
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)
=
On Mon, Nov 06, 2017 at 01:37:10PM +0100, Kashyap Chamarthy wrote:
> I'm delighted to announce that the call for proposals is now open for
> the Virtualization & IaaS devroom at the upcoming FOSDEM 2018, to be
> hosted on February 3 and 4, 2018.
>
> This year will mark FOSDEM
On Thu, Dec 14, 2017 at 12:02:13PM +0100, Kashyap Chamarthy wrote:
> On Wed, Dec 13, 2017 at 05:17:26PM +0100, Thierry Carrez wrote:
[...]
> > What it means:
> >
> > - We'd only do one *coordinated* release of the OpenStack components
> > per year, and maintain
On Fri, Dec 15, 2017 at 10:11:24AM +0800, Zhenyu Zheng wrote:
> On Thu, Dec 14, 2017 at 7:02 PM, Kashyap Chamarthy <kcham...@redhat.com>
> wrote:
[...]
> > For a relatively mature (~7 years; and ~5 years if we count from the
> > time governance changed to OpenStack
On Wed, Dec 13, 2017 at 05:17:26PM +0100, Thierry Carrez wrote:
> Hi everyone,
Hey Thierry,
> Over the past year, it has become pretty obvious to me that our
> self-imposed rhythm no longer matches our natural pace. It feels like we
> are always running elections, feature freeze is always just
On Sat, Dec 16, 2017 at 08:16:13AM -0600, Matt Riedemann wrote:
> On 12/16/2017 5:51 AM, Kashyap Chamarthy wrote:
Hi Matt,
First, thanks for the detailed reply with specific examples.
[...]
> > But one pontential question that comes to mind from that old thread is
> > how is th
I'm delighted to announce that the call for proposals is now open for
the Virtualization & IaaS devroom at the upcoming FOSDEM 2018, to be
hosted on February 3 and 4, 2018.
This year will mark FOSDEM’s 18th anniversary as one of the longest-running
free and open source software developer events,
On Mon, Jun 11, 2018 at 11:55:29AM +0200, Sahid Orentino Ferdjaoui wrote:
> On Fri, Jun 08, 2018 at 11:35:45AM +0200, Kashyap Chamarthy wrote:
> > On Thu, Jun 07, 2018 at 01:07:48PM -0500, Matt Riedemann wrote:
[...]
> > > The 26 volumes thing is a libvirt
On Thu, Jun 07, 2018 at 01:07:48PM -0500, Matt Riedemann wrote:
> On 6/7/2018 12:56 PM, melanie witt wrote:
> > Recently, we've received interest about increasing the maximum number of
> > allowed volumes to attach to a single instance > 26. The limit of 26 is
> > because of a historical
On Mon, Jun 11, 2018 at 10:14:33AM -0500, Eric Fried wrote:
> I thought we were leaning toward the option where nova itself doesn't
> impose a limit, but lets the virt driver decide.
Yeah, I agree with that, if we can't arrive at a sensible limit for
Nova, after testing with all drivers that
On Tue, May 22, 2018 at 05:41:18PM -0400, Brian Haley wrote:
> On 05/22/2018 04:57 PM, Jay Pipes wrote:
[...]
> > Please don't take this the wrong way, Dean, but you aren't seriously
> > suggesting that anyone outside of Windriver/Intel would ever contribute
> > to these repos are you?
> >
> >
On Tue, May 22, 2018 at 01:54:59PM -0500, Dean Troyer wrote:
> StarlingX (aka STX) was announced this week at the summit, there is a
> PR to create project repos in Gerrit at [0]. STX is basically Wind
From a cursory look at the libvirt fork, there are some questionable
choices. E.g. the config
On Mon, Jan 22, 2018 at 05:09:31PM -0600, Matt Riedemann wrote:
[...]
> To anyone that cares, I don't plan on running for Nova PTL again for the
> Rocky release. Queens was my fourth tour and it's definitely time for
> someone else to get the opportunity to lead here. I don't plan on going
>
On Wed, Aug 22, 2018 at 11:03:43AM -0700, melanie witt wrote:
[...]
[Randomly jumping in on one specific point.]
> Aside from that, it has always been difficult to add folks to
> nova-core because of the large scope and expertise needed to approve
> code across all of Nova.
The complexity of
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
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
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 spen
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
libvirt
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
> > experience
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 and QEMU
&g
On Mon, Mar 26, 2018 at 12:28:02PM -0700, melanie witt wrote:
> On Mon, 26 Mar 2018 14:12:52 -0500, Matt Riedemann wrote:
> > On 3/26/2018 6:24 AM, ChangBo Guo wrote:
> > > What's your use case for ListOpt, just make sure the value(a list) is
> > > part of 'choices' ? Maybe we need another
Hi there,
I was looking at oslo_config/cfg.py[*], and the StrOpt() class has
'choices' parameter, to allow a sequence of valid values / tuples of
valid values for descriptions.
However, I don't see the same 'choices' parameter for the ListOpt()
class. Out of curiosity, is there a reason to not
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.
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
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
[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 "Queens
Dear OpenStack community,
FOSDEM 2019 will feature a Virtualization & IaaS DevRoom again. Here is
the call for proposals. Please check it out if you would like to submit
a talk.
Regards,
Kashyap
---
We are excited to
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
101 - 134 of 134 matches
Mail list logo
