I'd like to share a link  to Nova Bug Triage wiki page. This page
contains a tag owner list and instructions that allow subscribing not for
all nova bugs, but for a certain tag. It would be great if all tags in a
table have an owner, so if you are interested in some of them, and could
> last year. Recently, as some of you will have noticed, my time has been
> stretched to the extent that I have started to neglect the task. Timofei
> Durakov has stood in for me on several occasions recently and has now
> agreed to take over full time. I had planned to bri
I agree that it's kind of strange thing that nova dumps xml definition to
the disk but doesn't use it(at least I do not aware of it).
How the proposed changed would be aligned with other drivers? The worst
case I could imagine here is that libvirt has an xml as a source of truth,
Bug team meeting on Sept. 13 is canceled. So the next time it will be Sept.
20 18:00 UTC.
By that time I'll update agenda , everyone is welcome to do the same.
 - https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam
Thanks, Markus, for doing this job! I'm interested in this activity.
On Mon, Sep 5, 2016 at 7:20 PM, Sylvain Bauza wrote:
> Le 05/09/2016 13:19, Markus Zoeller a écrit :
>> TL;DR: bug czar role for Nova is vacant from now on
>> After doing bug
Next meeting will be on August 30, 14:00 UTC as usual. Agenda is available
If you have topics to discuss, please update it accordingly.
As you may notice, gate-tempest-dsvm-multinode-live-migration job became
voting. It tests live-migration against no shared storage environment, and
uses Ubuntu Xenial. List of tests being executed:
got a question on that Intel NFV CI: has statistics for stable branches
been checked either?
I have a patch to stable/liberty  that failed on all Intel NFV CI jobs 2
times in a row. Who could help me to figure out the root cause for that?
Thanks in advance,
done. So there will be no upgrades impact related to this change.
On Tue, Aug 2, 2016 at 10:51 PM, Chris Friesen <chris.frie...@windriver.com>
> On 08/02/2016 09:14 AM, Timofei Durakov wrote:
>> Taking into account everything above I'd prefer to s
Taking into account everything above I'd prefer to see
live_migration_tunnelled(that corresponds to VIR_MIGRATE_TUNNELLED)
defaulted to False. We just need to make a release note for this change,
and on the host startup do LOG.warning to notify the operator that there
are no tunnels for
I think we could at least fix-up schema validation.
On Wed, Jul 6, 2016 at 5:51 PM, Matt Riedemann <mrie...@linux.vnet.ibm.com>
> On 7/6/2016 9:37 AM, Timofei Durakov wrote:
>> there are several patches in a tempest that improves micro
there are several patches in a tempest that improves micro
versions coverage for Nova REST API:
This option is already available for live-migration job, as it's hooks are
under nova project.
On Fri, Jul 1, 2016 at 5:13 PM, Jeremy Stanley wrote:
> Have you considered just writing a throwaway devstack-gate change
> which overrides the gate_hook to run that one suspect
talking about live-migration job. If you are OK to re-run tempest tests
multiple times on single environment you could wrap this line:
On Fri, Jul 1, 2016 at 10:31 AM,
- bp is not approved, but the spec is.
On Tue, Jun 14, 2016 at 3:47 AM, joehuang wrote:
> Hi, Matt,
> Thank you for the clarification.
> Best Regards
> Chaoyi Huang ( Joe Huang
I've submitted one more patch with potential fix:
On Mon, Jun 6, 2016 at 11:58 PM, Timofei Durakov <tdura...@mirantis.com>
> On Mon, Jun 6, 2016 at 11:26 PM, Matt Riedemann <
> mrie...@linux.vnet.ibm.com> wrote:
On Mon, Jun 6, 2016 at 11:26 PM, Matt Riedemann
> On 6/6/2016 12:15 PM, Matt Riedemann wrote:
>> On 1/8/2016 12:28 PM, Mark McLoughlin wrote:
>>> On Fri, 2016-01-08 at 14:11 +, Daniel P. Berrange wrote:
On Thu, Jan 07, 2016 at 09:07:00PM
rom verification of states to conductor of
the task(success stories)
On Wed, Jun 1, 2016 at 12:51 PM, Miles Gould <mgo...@redhat.com> wrote:
> On 31/05/16 21:03, Timofei Durakov wrote:
>> there is blueprint that was approved during Liberty and resubmitted
there is blueprint that was approved during Liberty and resubmitted to
The idea is to define state machines for operations as live-migration,
resize, etc. and to deal with them operation states.
The spec PoC patches are overall good. At the same time I think is
We've tested live migration of instances under load for following features:
- XBZRLE compression
Tests were done against qemu 2.5. Instances had 2GB ram and stress tool was
used to emulate load:
$ stress -m 1 --vm-bytes 200M --vm-keep
None of them could be called silver-bullet
>From the first sight there are no restrictions for instance_path option.
Could you please provide some details about the use case?
I wonder would this functionality be really useful for cloud-operators, or
we just should add description to instance path option, forcing to use the
Last week I started thread  on openstack-operators to ask Openstack
users about the way to expose features for live-migrations.
So here are results:
*16,7%* - All this features should work under the hood and I don't want to
enable them manually over Nova API
*33,3%* - There should be
I think it would be ok to store persistently quota details on compute side,
as was discussed during mitaka mid-cycle for migrations. So if
compute service fails we could restore state and update quota after compute
Separate job for testing live-migration with different storage
configurations(No shared storage/NFS/Ceph was implemented during Mitaka and
available to be executed using experimental pipeline.
The job is ready but shows same stability as
Bugs like  
In case of live-migration reporting I'd rather go with real-time stats,
queried from compute, instead of reporting this data to db first. While
amount of of rpc requests/db updates is relatively small, total number of
such requests depends on amount of active migrations. While realtime data
some work items:
- ci coverage for live-migration
- compute + drivers code cleanup
On Fri, Sep 18, 2015 at 6:47 PM, John Garbutt
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova] CI for reliable live-migration
> On Wed, Aug 26, 2015 at 8:18 AM, Matt Riedemann <
, Aug 26, 2015 at 6:18 PM, Matt Riedemann mrie...@linux.vnet.ibm.com
On 8/26/2015 3:21 AM, Timofei Durakov wrote:
Here is the situation: nova has live-migration feature but doesn't have
ci job to cover it by functional tests, only
Here is the situation: nova has live-migration feature but doesn't have ci
job to cover it by functional tests, only
btw), which covers block-migration only.
The problem here is, that live-migration could be different, depending on
In current design there are places when nova fails while executing users
CLI commands, but no error messages, except some logs in nova-compute,
produced  . The problem is that there is no response from compute node
to conductor, as RPC cast is used.
To fix this nova should make a
I'd like to ask for a freeze exception for the follow bug fix:
merged bug fix in master:
Mail list logo