Re: [openstack-dev] [nova] correct API for getting image metadata for an instance ?

2015-05-28 Thread Vladik Romanovsky
As part of the work to object-ify the image metadata dicts, I'm looking at the current way the libvirt driver fetches image metadata for an instance, in cases where the compute manager hasn't already passed it into the virt driver API. I see 2 methods that libvirt uses to get the image

Re: [openstack-dev] [nova][libvirt] RFC: ensuring live migration ends

2015-02-02 Thread Vladik Romanovsky
- Original Message - From: Daniel P. Berrange berra...@redhat.com To: Robert Collins robe...@robertcollins.net Cc: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org, openstack-operat...@lists.openstack.org Sent: Monday, 2 February, 2015

Re: [openstack-dev] [nova][libvirt] RFC: ensuring live migration ends

2015-01-30 Thread Vladik Romanovsky
- Original Message - From: Daniel P. Berrange berra...@redhat.com To: openstack-dev@lists.openstack.org, openstack-operat...@lists.openstack.org Sent: Friday, 30 January, 2015 11:47:16 AM Subject: [openstack-dev] [nova][libvirt] RFC: ensuring live migration ends In working on a

Re: [openstack-dev] [nova][NFV][qa] Testing NUMA, CPU pinning and large pages

2015-01-28 Thread Vladik Romanovsky
and large pages - Original Message - From: Vladik Romanovsky vladik.romanov...@enovance.com To: openstack-dev@lists.openstack.org Hi everyone, Following Steve Gordon's email [1], regarding CI for NUMA, SR-IOV, and other features, I'd like to start a discussion about the NUMA

Re: [openstack-dev] multi-queue virtio-net interface

2015-01-23 Thread Vladik Romanovsky
Unfortunately, I didn't get a feature freeze exception for this blueprint. I will resubmit the spec in next cycle. I think the best way for you to contribute is to review the spec, when it's re-posted and +1 it, if you agree with the design. Thanks, Vladik - Original Message - From:

[openstack-dev] [nova] request spec freeze exception for virtio-net multiqueue

2015-01-12 Thread Vladik Romanovsky
Hello, I'd like to request an exception for virtio-net multiqueue feature. [1] This is an important feature that aims to increase the total network throughput in guests and not too hard to implement. Thanks, Vladik [1] https://review.openstack.org/#/c/128825

[openstack-dev] [nova][NFV][qa] Testing NUMA, CPU pinning and large pages

2015-01-11 Thread Vladik Romanovsky
Hi everyone, Following Steve Gordon's email [1], regarding CI for NUMA, SR-IOV, and other features, I'd like to start a discussion about the NUMA testing in particular. Recently we have started a work to test some of these features. The current plan is to use the functional tests, in the Nova

Re: [openstack-dev] [nova] nova host-update gives error 'Virt driver does not implement host disabled status'

2014-11-26 Thread Vladik Romanovsky
- Original Message - From: Vineet Menon mvineetme...@gmail.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Wednesday, 26 November, 2014 5:14:09 AM Subject: Re: [openstack-dev] [nova] nova host-update gives error 'Virt

[openstack-dev] [nova] [feature freeze exception] FFE for libvirt-start-lxc-from-block-devices

2014-09-04 Thread Vladik Romanovsky
Hello, I would like to ask for an extension for libvirt-start-lxc-from-block-devices feature. It has been previously pushed from Ice house to Juno. The spec [1] has been approved. One of the patches is a bug fix. Another patch has been already approved and failed in the gate. All patches has a

[openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

2014-09-04 Thread Vladik Romanovsky
+1 I very much agree with Dan's the propsal. I am concerned about difficulties we will face with merging patches that spreads accross various regions: manager, conductor, scheduler, etc.. However, I think, this is a small price to pay for having a more focused teams. IMO, we will stiil have

Re: [openstack-dev] [Nova] Feature Freeze Exception process for Juno

2014-09-03 Thread Vladik Romanovsky
+1 I had several pacthes in start lxc from block device series. The blueprint was waiting since Icehouse. In Juno it was approved, however, besides Daniel Berrange no one was looking at these patches. Now it's being pushed to Kilo, regadless of the fact that everything is +2ed. Normally, I

[openstack-dev] [nova][libvirt][lxc] Attach volumes to LXC is broken

2014-06-19 Thread Vladik Romanovsky
Hello Everyone, I've been recently working on bug/1269990, re: attached volumes to LXC are being lost after reboot/power on, after fixing it, I've realized that the initial attach volume to LXC operation is not functional at all. (bug/1330981) I've described the problem in details in the bug. In

[openstack-dev] [nova] unittests are failing after change I5e4cb4a8

2014-01-06 Thread Vladik Romanovsky
Hello everyone, I'm just wondering, is there anyone else who is affected by this bug: https://bugs.launchpad.net/nova/+bug/1266534 ? It looks to me that everyone should be affected by it (after change https://review.openstack.org/#/c/61310 has been merged), but I also see many tests in Jenkins

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

2013-12-19 Thread Vladik Romanovsky
I think it was: ceilometer sample-list -m cpu_util -q 'resource_id=vm_uuid' Vladik - Original Message - From: Daniel P. Berrange berra...@redhat.com To: John Garbutt j...@johngarbutt.com Cc: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

2013-12-19 Thread Vladik Romanovsky
Or ceilometer meter-list -q resource_id='vm_uuid' - Original Message - From: Daniel P. Berrange berra...@redhat.com To: John Garbutt j...@johngarbutt.com Cc: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Thursday, 19 December,

Re: [openstack-dev] [nova] VM diagnostics - V3 proposal

2013-12-19 Thread Vladik Romanovsky
of time per every meter and resource: ceilometer statistics -m cpu_util -q 'timestampSTART;timestamp=END;resource_id=vm_uuid' --period 3600 Vladik - Original Message - From: Daniel P. Berrange berra...@redhat.com To: Vladik Romanovsky vladik.romanov...@enovance.com Cc: OpenStack

Re: [openstack-dev] [Nova][libvirt]when deleting instance which is in migrating state, instance files can be stay in destination node forever

2013-12-16 Thread Vladik Romanovsky
I would block it in the API or have the API cancelling the migration first. I don't see a reason why to start an operation that is meant to fail, which also has a complex chain of event, following it failure. Regardless of the above, I think that the suggested exception handling is needed in

Re: [openstack-dev] Unified Guest Agent proposal

2013-12-12 Thread Vladik Romanovsky
Subject: Re: [openstack-dev] Unified Guest Agent proposal Vladik, Thanks for the suggestion, but hypervisor-dependent solution is exactly what scares off people in the thread :-) Thanks, Dmitry 2013/12/11 Vladik Romanovsky vladik.romanov...@enovance.com Maybe it will be useful

Re: [openstack-dev] Unified Guest Agent proposal

2013-12-10 Thread Vladik Romanovsky
Maybe it will be useful to use Ovirt guest agent as a base. http://www.ovirt.org/Guest_Agent https://github.com/oVirt/ovirt-guest-agent It is already working well on linux and windows and has a lot of functionality. However, currently it is using virtio-serial for communication, but I think it

Re: [openstack-dev] [nova][Libvirt] Disabling nova-compute when a connection to libvirt is broken.

2013-10-13 Thread Vladik Romanovsky
AM Subject: Re: [openstack-dev] [nova][Libvirt] Disabling nova-compute when a connection to libvirt is broken. +1 for me. And I am willing to be a volunteer. 2013/10/12 Joe Gordon joe.gord...@gmail.com On Thu, Oct 10, 2013 at 4:47 AM, Vladik Romanovsky vladik.romanov...@enovance.com

[openstack-dev] [nova][Libvirt] Disabling nova-compute when a connection to libvirt is broken.

2013-10-10 Thread Vladik Romanovsky
Hello everyone, I have been recently working on a migration bug in nova (Bug #1233184). I noticed that compute service remains available, even if a connection to libvirt is broken. I thought that it might be better to disable the service (using conductor.manager.update_service()) and resume