In working on a recent Nova migration bug
https://bugs.launchpad.net/nova/+bug/1414065
I had cause to refactor the way the nova libvirt driver monitors live
migration completion/failure/progress. This refactor has opened the
door for doing more intelligent active management of the live
On Sun, Feb 01, 2015 at 11:20:08AM -0800, Noel Burton-Krahn wrote:
Thanks for bringing this up, Daniel. I don't think it makes sense to have
a timeout on live migration, but operators should be able to cancel it,
just like any other unbounded long-running process. For example, there's
no
On Sun, Feb 01, 2015 at 03:03:45PM -0700, David Medberry wrote:
I'll second much of what Rob said:
API that indicated how many live-migrations (l-m) were going would be good.
API that told you what progress (and start time) a given l-m had made would
be great.
API to cancel a given l-m would
On Sat, Jan 31, 2015 at 03:55:23AM +0100, Vladik Romanovsky wrote:
- Original Message -
From: Daniel P. Berrange berra...@redhat.com
To: openstack-...@lists.openstack.org,
openstack-operators@lists.openstack.org
Sent: Friday, 30 January, 2015 11:47:16 AM
Subject: [openstack
On Mon, Feb 02, 2015 at 08:24:20AM +1300, Robert Collins wrote:
On 31 January 2015 at 05:47, Daniel P. Berrange berra...@redhat.com wrote:
In working on a recent Nova migration bug
https://bugs.launchpad.net/nova/+bug/1414065
I had cause to refactor the way the nova libvirt driver
On Mon, Feb 16, 2015 at 04:31:21PM +0300, Dmitry Guryanov wrote:
On 02/13/2015 05:50 PM, Jay Pipes wrote:
On 02/13/2015 09:20 AM, Daniel P. Berrange wrote:
On Fri, Feb 13, 2015 at 08:49:26AM -0500, Jay Pipes wrote:
On 02/13/2015 07:04 AM, Daniel P. Berrange wrote:
Historically Nova has had
On Wed, Jan 28, 2015 at 08:38:02PM +, Tim Bell wrote:
There are currently 35% of openstack clouds from the survey using this
feature. I would therefore propose that this be reviewed with the
operators in detail before a rapid depreciation is performed. To the
best of my knowledge, the new
On Wed, Jan 28, 2015 at 01:39:31PM -0800, Michael Still wrote:
On Wed, Jan 28, 2015 at 12:38 PM, Tim Bell tim.b...@cern.ch wrote:
There are currently 35% of openstack clouds from the survey using
this feature. I would therefore propose that this be reviewed with
the operators in detail
On Fri, Feb 13, 2015 at 08:49:26AM -0500, Jay Pipes wrote:
On 02/13/2015 07:04 AM, Daniel P. Berrange wrote:
Historically Nova has had a bunch of code which mounted images on the
host OS using qemu-nbd before passing them to libvirt to setup the
LXC container. Since 1.0.6, libvirt is able todo
Historically Nova has had a bunch of code which mounted images on the
host OS using qemu-nbd before passing them to libvirt to setup the
LXC container. Since 1.0.6, libvirt is able todo this itself and it
would simplify the codepaths in Nova if we can rely on that
In general, without use of user
=
KVM Forum 2015: Call For Participation
August 19-21, 2015 - Sheraton Seattle - Seattle, WA
(All submissions must be received before midnight May 1, 2015)
=
KVM is an
A friendly reminder that KVM Forum 2015 accepts proposal submissions
until this coming Friday.
Thanks on behalf of the KVM Forum 2015 Program Committee.
Daniel
On Wed, Mar 18, 2015 at 09:51:31AM +, Daniel P. Berrange wrote
On Wed, May 13, 2015 at 02:31:26PM +, Tim Bell wrote:
Looking through the details of the Venom vulnerability,
https://securityblog.redhat.com/2015/05/13/venom-dont-get-bitten/, it
would appear that the QEMU processes need to be restarted.
Our understanding is thus that a soft reboot of
On Fri, May 15, 2015 at 06:25:48AM +, Tim Bell wrote:
What are the benefits of upping the minimum libvirt ?
We've got 3,200 hypervisors still running v6 with a plan to
gradually migrate to 7 but this does take some time. We'll
see with RDO this week as to how/if we can get something
On Fri, May 15, 2015 at 11:51:22AM +0100, Daniel P. Berrange wrote:
On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote:
The minimum required version of libvirt in the driver is 0.9.11 still [1].
We've been gating against 1.2.2 in Ubuntu Trusty 14.04 since Juno.
The libvirt
On Fri, May 15, 2015 at 11:51:22AM +0100, Daniel P. Berrange wrote:
On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote:
The minimum required version of libvirt in the driver is 0.9.11 still [1].
We've been gating against 1.2.2 in Ubuntu Trusty 14.04 since Juno.
The libvirt
On Fri, May 15, 2015 at 02:45:06PM +0100, John Garbutt wrote:
On 15 May 2015 at 13:28, Daniel P. Berrange berra...@redhat.com wrote:
On Fri, May 15, 2015 at 11:51:22AM +0100, Daniel P. Berrange wrote:
On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote:
There are some
On Fri, May 15, 2015 at 05:27:35PM +0100, John Garbutt wrote:
On 15 May 2015 at 11:51, Daniel P. Berrange berra...@redhat.com wrote:
On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote:
The minimum required version of libvirt in the driver is 0.9.11 still [1].
We've been gating
On Fri, May 15, 2015 at 06:14:08PM +0100, John Garbutt wrote:
On 15 May 2015 at 17:41, Daniel P. Berrange berra...@redhat.com wrote:
Its tempting to say its scheduled for removal in N? So we have time to
work out if thats possible.
I think that at the start of each dev cycle, we look
On Thu, Jul 09, 2015 at 12:00:15PM -0600, David Medberry wrote:
Hi,
When trying to live-migrate between two distinct CPUs, I kind of expect
there to be issues. Which is why openstack supports the cpu_mode=custom,
cpu_model=MODELNAME flags for libvirt.
When I set those to some Lowest
On Fri, Jul 17, 2015 at 06:58:46AM -0600, David Medberry wrote:
HI Daniel,
Yep found that all out.
Now I'm struggling through the NUMA mismatch. NUMA as there are two cpus.
The old CPU was a 10 core 20 thread thus 40 cpus, {0-9,20-29} and then
{10-19,30-39} on the other cell. The new CPU
On Mon, Nov 09, 2015 at 02:57:37AM -0800, Boris Pavlovic wrote:
> Hi stackers,
>
> Intro
> ---
>
> It's not a big secret that OpenStack is huge and complicated ecosystem of
> different
> services that are working together to implement OpenStack API.
>
> For example booting VM is going
On Wed, Oct 07, 2015 at 06:55:44AM -0400, Sean Dague wrote:
> On 10/07/2015 06:46 AM, Daniel P. Berrange wrote:
> > In the Liberty version of OpenStack we had a min libvirt of 0.9.11 and
> > printed a warning on startup if you had < 0.10.2, to the effect that
> > Mit
In the Liberty version of OpenStack we had a min libvirt of 0.9.11 and
printed a warning on startup if you had < 0.10.2, to the effect that
Mitaka will required 0.10.2
This mail is a reminder that we will[1] mandate libvirt >= 0.10.2 when
Mitaka is released.
Looking forward to the N
On Wed, Jun 15, 2016 at 03:19:28PM +, Jesse Keating wrote:
> I'll offer a counter point.
>
> We're not doing Juno to Mitaka, however we are doing Kilo to Mitaka, skipping
> over Liberty.
>
> The database migrations to get from Kilo to Mitaka have ran smoothly for us.
While it is great
=
KVM Forum 2016: Call For Participation
August 24-26, 2016 - Westin Harbor Castle - Toronto, Canada
(All submissions must be received before midnight May 1, 2016)
=
On Fri, Mar 04, 2016 at 11:15:23AM -0800, Adam Lawson wrote:
> Hey all,
>
> We're testing OpenStack Liberty on an ESX host and it installs fine. When
> attempting to create a VM, receiving an error:
>
> *libvirtError: invalid argument : could not find capabilities for
> domaintype=kvm*
>
>
at 06:19:36PM +, Daniel P. Berrange wrote:
> =
> KVM Forum 2016: Call For Participation
> August 24-26, 2016 - Westin Harbor Castle - Toronto, Canada
>
> (All submissions must be received before midni
Hello Operators,
One of the things that constantly puzzles me when reading the user
survey results wrt hypervisor is the high number of respondants
claiming to be using QEMU (as distinct from KVM).
As a reminder, in Nova saying virt_type=qemu causes Nova to use
plain QEMU with pure CPU emulation
On Tue, May 03, 2016 at 07:06:56PM +, Jared Wilkinson wrote:
> So forgive my lack of kvm/qemu knowledge but I couldn’t find anything
> on Google on this. If you deployed an instance of a different architecture
> than the physical CPU, wouldn’t qemu just emulate the processor (if you
> were in
On Tue, May 03, 2016 at 10:20:34PM +0300, Maish Saidel-Keesing wrote:
> I would think that the problem is that OpenStack does not really report
> back that you are using KVM - it reports that you are using QEMU.
>
> Even when in nova.conf I have configured virt_type=kvm, when I run nova
>
On Sun, Jul 03, 2016 at 10:08:04AM -0500, Matt Riedemann wrote:
> I want to use the gate-tempest-dsvm-neutron-full-ssh in nova since it runs
> ssh validation + neutron + config drive + metadata service, which will test
> the virtual device tagging 2.32 microversion API (added last week).
>
> The
On Mon, Feb 20, 2017 at 08:08:00PM +, Jeremy Stanley wrote:
> On 2017-02-20 14:36:15 -0500 (-0500), Clint Byrum wrote:
> > What exactly is the security concern of the metadata service? Perhaps
> > those concerns can be addressed directly?
> [...]
>
> A few I'm aware of:
>
> 1. It's something
On Mon, Feb 20, 2017 at 02:36:15PM -0500, Clint Byrum wrote:
> What exactly is the security concern of the metadata service? Perhaps
> those concerns can be addressed directly?
>
> I ask because anything that requires special software on the guest is
> a non-starter IMO. virtio is a Linux thing,
On Tue, Feb 21, 2017 at 01:09:43PM +, Jeremy Stanley wrote:
> On 2017-02-21 06:24:20 -0500 (-0500), Clint Byrum wrote:
> [...]
> > Why not just make it a virtual USB drive that ejects and
> > re-attaches on changes?
> [...]
>
> Is there a graceful way to trigger that from the host so that the
On Tue, Feb 21, 2017 at 10:08:54AM -0500, David Medberry wrote:
> Doesn't the virtio solution assume/require a libvirt or more exactly a
> QEMU/KVM based hypervisor?
>
> What about the N-1 other hypervisors?
vsock is an equivalent of UNIX domain sockets, for host<->guest communication
that was
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
On Fri, Nov 11, 2016 at 07:11:51PM -0600, Matt Riedemann wrote:
> Chris Friesen reported a bug [1] where injected files on a server aren't in
> the guest after it's evacuated to another compute host. This is because the
> injected files aren't persisted in the nova database at all. Evacuate and
>
On Sat, Jan 07, 2017 at 12:04:25PM -0600, Matt Riedemann wrote:
> A few weeks ago someone in the operators channel was talking about issues
> with ceph-backed nova-compute and OSErrors for too many open files causing
> issues.
>
> We have a bug reported that's very similar sounding:
>
>
39 matches
Mail list logo
