Re: [openstack-dev] [nova] live migration in Mitaka

2015-09-22 Thread Daniel P. Berrange
On Tue, Sep 22, 2015 at 09:05:11AM -0600, Chris Friesen wrote: > On 09/21/2015 02:56 AM, Daniel P. Berrange wrote: > >On Fri, Sep 18, 2015 at 05:47:31PM +, Carlton, Paul (Cloud Services) > >wrote: > >>However the most significant impediment we encountered was custo

Re: [openstack-dev] [nova] live migration in Mitaka

2015-09-22 Thread Daniel P. Berrange
On Tue, Sep 22, 2015 at 09:29:46AM -0600, Chris Friesen wrote: > >>There is also work on post-copy migration in QEMU. Normally with live > >>migration, the guest doesn't start executing on the target host until > >>migration has transferred all data. There are many workloads where that > >>doesn't

Re: [openstack-dev] [nova] live migration in Mitaka

2015-09-21 Thread Daniel P. Berrange
On Fri, Sep 18, 2015 at 05:47:31PM +, Carlton, Paul (Cloud Services) wrote: > However the most significant impediment we encountered was customer > complaints about performance of instances during migration. We did a little > bit of work to identify the cause of this and concluded that the

Re: [openstack-dev] [nova] live migration in Mitaka

2015-09-18 Thread Daniel P. Berrange
On Fri, Sep 18, 2015 at 11:53:05AM +, Murray, Paul (HP Cloud) wrote: > Hi All, > > There are various efforts going on around live migration at the moment: > fixing up CI, bug fixes, additions to cover more corner cases, proposals > for new operations > > Generally live migration could do

Re: [openstack-dev] Fwd: [nova] live migration in Mitaka

2015-10-05 Thread Daniel P. Berrange
On Mon, Oct 05, 2015 at 01:10:45PM +0300, Pavel Boldin wrote: > Daniel, > > It is done already in the proposed patch. > > But this one is about Wily having libvirt 1.2.16 and libvirt-python 1.2.15. Assuming you are refering to this patch:

Re: [openstack-dev] [nova] Testing concerns around boot from UEFI spec

2015-12-04 Thread Daniel P. Berrange
On Fri, Dec 04, 2015 at 07:43:41AM -0500, Sean Dague wrote: > Can someone explain the licensing issue here? The Fedora comments make > this sound like this is something that's not likely to end up in distros. The EDK codebase contains a FAT driver which has a license that forbids reusing the code

Re: [openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

2015-11-27 Thread Daniel P. Berrange
On Fri, Nov 27, 2015 at 07:37:50PM +0800, 少合冯 wrote: > 2015-11-27 2:19 GMT+08:00 Daniel P. Berrange <berra...@redhat.com>: > > > On Thu, Nov 26, 2015 at 05:39:04PM +, Daniel P. Berrange wrote: > > > On Thu, Nov 26, 2015 at 11:55:31PM +0800, 少合冯 wrote: > >

Re: [openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

2015-11-27 Thread Daniel P. Berrange
On Fri, Nov 27, 2015 at 12:17:06PM +, Koniszewski, Pawel wrote: > > -Original Message- > > > > Doing this though, we still need a solution to the host OOM scenario > > > > problem. We can't simply check free RAM at start of migration and > > > > see if there's enough to spare for

Re: [openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

2015-11-27 Thread Daniel P. Berrange
On Fri, Nov 27, 2015 at 01:01:15PM +, Koniszewski, Pawel wrote: > > -Original Message- > > From: Daniel P. Berrange [mailto:berra...@redhat.com] > > Sent: Friday, November 27, 2015 1:24 PM > > To: Koniszewski, Pawel > > Cc: OpenStack Development Mailing

Re: [openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

2015-11-26 Thread Daniel P. Berrange
On Thu, Nov 26, 2015 at 11:55:31PM +0800, 少合冯 wrote: > Hi all, > We want to support xbzrle compress for live migration. > > Now there are 3 options, > 1. add the enable flag in nova.conf. > such as a dedicated 'live_migration_compression=on|off" parameter in > nova.conf. > And nova simply

Re: [openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

2015-11-26 Thread Daniel P. Berrange
On Thu, Nov 26, 2015 at 05:49:50PM +, Paul Carlton wrote: > Seems to me the prevailing view is that we should get live migration to > figure out the best setting for > itself where possible. There was discussion of being able have a default > policy setting that will allow > the operator to

Re: [openstack-dev] [nova] [RFC] how to enable xbzrle compress for live migration

2015-11-26 Thread Daniel P. Berrange
On Thu, Nov 26, 2015 at 05:39:04PM +, Daniel P. Berrange wrote: > On Thu, Nov 26, 2015 at 11:55:31PM +0800, 少合冯 wrote: > > 3. dynamically choose when to activate xbzrle compress for live migration. > > This is the best. > > xbzrle really wants to be used if th

Re: [openstack-dev] [nova][infra] Getting a bleeding edge libvirt gate job running

2015-11-18 Thread Daniel P. Berrange
On Wed, Nov 18, 2015 at 05:18:28PM +1100, Tony Breeds wrote: > On Tue, Nov 17, 2015 at 03:32:45PM -0800, Jay Pipes wrote: > > On 11/17/2015 11:10 AM, Markus Zoeller wrote: > > >Background > > >== > > >The blueprint [1] wants to utilize the *virtlogd* logging deamon from > > >libvirt. Among

Re: [openstack-dev] [cinder][nova]Move encryptors to os-brick

2015-11-20 Thread Daniel P. Berrange
On Fri, Nov 20, 2015 at 03:22:04AM +, Li, Xiaoyan wrote: > Hi all, > > To fix bug [1][2] in Cinder, Cinder needs to use nova/volume/encryptors[3] > to attach/detach encrypted volumes. > > To decrease the code duplication, I raised a BP[4] to move encryptors to > os-brick[5]. > > Once it is

Re: [openstack-dev] [cinder][nova]Move encryptors to os-brick

2015-11-20 Thread Daniel P. Berrange
On Fri, Nov 20, 2015 at 02:45:15PM +0200, Duncan Thomas wrote: > Brick does not have to take over the decisions in order to be a useful > repository for the code. The motivation for this work is to avoid having > the dm setup code copied wholesale into cinder, where it becomes difficult > to keep

Re: [openstack-dev] [cinder][nova]Move encryptors to os-brick

2015-11-23 Thread Daniel P. Berrange
On Fri, Nov 20, 2015 at 02:44:17PM -0500, Ben Swartzlander wrote: > On 11/20/2015 01:19 PM, Daniel P. Berrange wrote: > >On Fri, Nov 20, 2015 at 02:45:15PM +0200, Duncan Thomas wrote: > >>Brick does not have to take over the decisions in order to be a useful > >

Re: [openstack-dev] [cinder][nova]Move encryptors to os-brick

2015-11-23 Thread Daniel P. Berrange
On Fri, Nov 20, 2015 at 11:34:29AM -0800, Walter A. Boring IV wrote: > On 11/20/2015 10:19 AM, Daniel P. Berrange wrote: > >On Fri, Nov 20, 2015 at 02:45:15PM +0200, Duncan Thomas wrote: > >>Brick does not have to take over the decisions in order to be a useful > >

Re: [openstack-dev] [nova] Migration progress

2015-11-23 Thread Daniel P. Berrange
On Mon, Nov 23, 2015 at 08:36:32AM +, Paul Carlton wrote: > John > > At the live migration sub team meeting I undertook to look at the issue > of progress reporting. > > The use cases I'm envisaging are... > > As a user I want to know how much longer my instance will be migrating > for. >

Re: [openstack-dev] [cinder][glance]Upload encrypted volumes to images

2015-11-23 Thread Daniel P. Berrange
On Mon, Nov 23, 2015 at 03:45:55AM +, Li, Xiaoyan wrote: > Hi all, > More help about volume encryption is needed. > > About uploading encrypted volumes to image, there are three options: > 1. Glance only keeps non-encrypted images. So when uploading encrypted > volumes to image, cinder

Re: [openstack-dev] [cinder][glance]Upload encrypted volumes to images

2015-11-23 Thread Daniel P. Berrange
On Mon, Nov 23, 2015 at 07:05:05AM +0100, Philipp Marek wrote: > > About uploading encrypted volumes to image, there are three options: > > 1. Glance only keeps non-encrypted images. So when uploading encrypted > >volumes to image, cinder de-crypts the data and upload. > > 2. Glance maintain

Re: [openstack-dev] [Infra] Remove .mailmap files from OpenStack repos

2015-11-19 Thread Daniel P. Berrange
On Thu, Nov 19, 2015 at 07:28:03PM +0300, Mikhail Fedosin wrote: > Currently we have .mailmap files in the root of almost all OpenStack repos: > https://github.com/openstack/glance/blob/master/.mailmap > https://github.com/openstack/horizon/blob/master/.mailmap >

Re: [openstack-dev] [Nova][Glance] Nova + Glance_v2 = Love

2016-01-08 Thread Daniel P. Berrange
On Fri, Jan 08, 2016 at 10:01:45AM -0430, Flavio Percoco wrote: > On 29/12/15 07:41 -0600, Sam Matzek wrote: > >On Thu, Dec 24, 2015 at 7:49 AM, Mikhail Fedosin > >wrote: > >>Hello, it's another topic about glance v2 adoption in Nova, but it's > >>different from the

Re: [openstack-dev] [nova][libvirt] Deprecating the live_migration_flag and block_migration_flag config options

2016-01-08 Thread Daniel P. Berrange
On Thu, Jan 07, 2016 at 09:07:00PM +, Mark McLoughlin wrote: > On Thu, 2016-01-07 at 12:23 +0100, Sahid Orentino Ferdjaoui wrote: > > On Mon, Jan 04, 2016 at 09:12:06PM +, Mark McLoughlin wrote: > > > Hi > > > > > > commit 8ecf93e[1] got me thinking - the live_migration_flag config > > >

Re: [openstack-dev] [nova][neutron][os-vif] os-vif core review team membership

2016-01-13 Thread Daniel P. Berrange
On Tue, Jan 12, 2016 at 10:28:49PM +, Mooney, Sean K wrote: > > -Original Message- > > From: Moshe Levi [mailto:mosh...@mellanox.com] > > Sent: Tuesday, January 12, 2016 4:23 PM > > To: Russell Bryant; Daniel P. Berrange; openstack- > > d...@lists.o

[openstack-dev] [nova][neutron][os-vif] os-vif core review team membership

2016-01-12 Thread Daniel P. Berrange
So far myself & Jay Pipes have been working on the initial os-vif prototype and setting up infrastructure for the project. Obviously we need more then just 2 people on a core team, and after looking at those who've expressed interest in os-vif, we came up with a cross-section of contributors

Re: [openstack-dev] [nova] Using image metadata to sanity check supplied authentication data at nova 'create' or 'recreate' time?

2016-06-07 Thread Daniel P. Berrange
On Tue, Jun 07, 2016 at 09:37:25AM -0400, Jim Rollenhagen wrote: > On Tue, Jun 07, 2016 at 08:31:35AM +1000, Michael Still wrote: > > On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote: > > > > > Hello all, > > > > > > At Rackspace we're running into an interesting problem:

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

2016-06-10 Thread Daniel P. Berrange
On Thu, Jun 09, 2016 at 12:35:06PM -0600, Chris Friesen wrote: > On 06/09/2016 05:15 AM, Paul Michali wrote: > > 1) On the host, I was seeing 32768 huge pages, of 2MB size. > > Please check the number of huge pages _per host numa node_. > > > 2) I changed mem_page_size from 1024 to 2048 in the

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

2016-06-03 Thread Daniel P. Berrange
On Fri, Jun 03, 2016 at 12:32:17PM +, Paul Michali wrote: > Hi! > > I've been playing with Liberty code a bit and had some questions that I'm > hoping Nova folks may be able to provide guidance on... > > If I set up a flavor with hw:mem_page_size=2048, and I'm creating (Cirros) > VMs with

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

2016-06-13 Thread Daniel P. Berrange
On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > Hi, > > You may or may not be aware of the vlan-aware-vms effort [1] in > Neutron. If not, there is a spec and a fair number of patches in > progress for this. Essentially, the goal is to allow a VM to connect > to multiple Neutron

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

2016-06-13 Thread Daniel P. Berrange
On Mon, Jun 13, 2016 at 08:06:50AM +, Wang, Shane wrote: > Hi, OpenStackers, > > As you know, Huawei, Intel and CESI are hosting the 4th China OpenStack Bug > Smash at Hangzhou, China. > The 1st China Bug Smash was at Shanghai, the 2nd was at Xi'an, and the 3rd > was at Chengdu. > > We are

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

2016-06-14 Thread Daniel P. Berrange
On Mon, Jun 13, 2016 at 11:35:17PM +, Peters, Rawlin wrote: > That said, there are currently a couple of vif-plugging strategies > we could go with for wiring trunk ports for OVS, each of them > requiring varying levels of os-vif augmentation: > > Strategy 1) When Nova is plugging a trunk

Re: [openstack-dev] [nova] Initial oslo.privsep conversion?

2016-06-14 Thread Daniel P. Berrange
On Fri, Jun 10, 2016 at 09:51:03AM +1000, Tony Breeds wrote: > On Fri, Jun 10, 2016 at 08:24:34AM +1000, Michael Still wrote: > > On Fri, Jun 10, 2016 at 7:18 AM, Tony Breeds > > wrote: > > > > > On Wed, Jun 08, 2016 at 08:10:47PM -0500, Matt Riedemann wrote: > > > > > >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

2016-06-14 Thread Daniel P. Berrange
2 also requires you to pass a second bridge name to nova/os-vif, unless I'm mis-understanding the description below. > On Tue, Jun 14, 2016 at 1:29 AM, Daniel P. Berrange <berra...@redhat.com> > wrote: > > > On Mon, Jun 13, 2016 at 11:35:17PM +, Peters, Rawlin wrote: >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

2016-06-14 Thread Daniel P. Berrange
On Tue, Jun 14, 2016 at 02:35:57AM -0700, Kevin Benton wrote: > In strategy 2 we just pass 1 bridge name to Nova. That's the one that is > ensures is created and plumbs the VM to. Since it's not responsible for > patch ports it doesn't need to know anything about the other bridge. Ok, so we're

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

2016-06-14 Thread Daniel P. Berrange
On Tue, Jun 14, 2016 at 07:49:54AM -0400, Sean Dague wrote: [snip] > The crux of the problem is that os-brick 1.4 and privsep can't be used > without a config file change during the upgrade. Which violates our > policy, because it breaks rolling upgrades. os-vif support is going to face exactly

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

2016-06-13 Thread Daniel P. Berrange
On Mon, Jun 13, 2016 at 07:39:29AM -0400, Assaf Muller wrote: > On Mon, Jun 13, 2016 at 4:35 AM, Daniel P. Berrange <berra...@redhat.com> > wrote: > > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > >> Hi, > >> > >> You may or may

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

2016-06-13 Thread Daniel P. Berrange
On Mon, Jun 13, 2016 at 02:08:30PM +0200, Armando M. wrote: > On 13 June 2016 at 10:35, Daniel P. Berrange <berra...@redhat.com> wrote: > > > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > > > Hi, > > > > > > You may or may

Re: [openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

2016-05-31 Thread Daniel P. Berrange
On Tue, May 24, 2016 at 01:59:17PM -0400, Sean Dague wrote: > The team working on live migration testing started with an experimental > job on Ubuntu 16.04 to try to be using the latest and greatest libvirt + > qemu under the assumption that a set of issues we were seeing are > solved. The short

Re: [openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

2016-05-31 Thread Daniel P. Berrange
On Tue, May 31, 2016 at 08:24:03AM -0400, Sean Dague wrote: > On 05/31/2016 05:39 AM, Daniel P. Berrange wrote: > > On Tue, May 24, 2016 at 01:59:17PM -0400, Sean Dague wrote: > >> The team working on live migration testing started with an experimental > >> job on Ubun

Re: [openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

2016-05-31 Thread Daniel P. Berrange
On Tue, May 31, 2016 at 08:19:33AM -0400, Sean Dague wrote: > On 05/30/2016 06:25 AM, Kashyap Chamarthy wrote: > > On Thu, May 26, 2016 at 10:55:47AM -0400, Sean Dague wrote: > >> On 05/26/2016 05:38 AM, Kashyap Chamarthy wrote: > >>> On Wed, May 25, 2016 at 05:42:04PM +0200, Kashyap Chamarthy

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

2016-06-23 Thread Daniel P. Berrange
On Wed, Jun 15, 2016 at 04:59:39PM -0700, Preston L. Bannister wrote: > QEMU has the ability to directly connect to iSCSI volumes. Running the > iSCSI connections through the nova-compute host *seems* somewhat > inefficient. > > There is a spec/blueprint and implementation that landed in Kilo: >

Re: [openstack-dev] [nova] libvirt driver: who should create the libvirt.xml file?

2016-06-23 Thread Daniel P. Berrange
On Mon, Jun 20, 2016 at 05:47:57PM +0200, Markus Zoeller wrote: > White working on the change series to implement the virtlogd feature I > got feedback [1] to move code which creates parts of the libvirt.xml > file from the "driver" module into the "guest" module. I'm a bit > hesitant to do so as

Re: [openstack-dev] [grenade] upgrades vs rootwrap

2016-06-24 Thread Daniel P. Berrange
On Fri, Jun 24, 2016 at 11:12:27AM +0200, Thierry Carrez wrote: > Angus Lees wrote: > > [...] > > None of these are great, but: > > > > Possibility 1: Backdoor rootwrap > > > > However if we assume rootwrap already exists then we _could_ rollout a > > new version of oslo.rootwrap that contains

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

2016-06-24 Thread Daniel P. Berrange
On Fri, Jun 24, 2016 at 08:05:38AM -0600, John Griffith wrote: > On Fri, Jun 24, 2016 at 2:19 AM, Daniel P. Berrange <berra...@redhat.com> > wrote: > > > On Thu, Jun 23, 2016 at 09:09:44AM -0700, Walter A. Boring IV wrote: > > > > > > volumes connected to QE

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

2016-06-24 Thread Daniel P. Berrange
On Thu, Jun 23, 2016 at 11:04:28PM +0200, Thomas Goirand wrote: > On 06/23/2016 06:11 PM, Doug Hellmann wrote: > > I'd like for the community to set a goal for Ocata to have Python > > 3 functional tests running for all projects. > > > > As Tony points out, it's a bit late to have this as a

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

2016-06-24 Thread Daniel P. Berrange
On Thu, Jun 23, 2016 at 09:09:44AM -0700, Walter A. Boring IV wrote: > > volumes connected to QEMU instances eventually become directly connected? > > > Our long term goal is that 100% of all network storage will be connected > > to directly by QEMU. We already have the ability to partially do

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

2016-06-24 Thread Daniel P. Berrange
On Thu, Jun 23, 2016 at 10:08:22AM +0200, Sylvain Bauza wrote: > > > Le 23/06/2016 02:42, Tony Breeds a écrit : > > On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote: > > > Le 22/06/2016 à 10:49, Thomas Goirand a écrit : > > > > Do you think it looks like possible to have Nova

Re: [openstack-dev] [nova][pci-passthrough] definitely specify VFIO driver as the host PCI driver for passthrough

2016-06-24 Thread Daniel P. Berrange
On Fri, Jun 24, 2016 at 04:52:31PM +0800, Chen Fan wrote: > > > On 2016年06月24日 16:20, Daniel P. Berrange wrote: > > On Fri, Jun 24, 2016 at 12:27:57PM +0800, Chen Fan wrote: > > > hi all, > > > in openstack, we can use the pci passthrough featur

Re: [openstack-dev] [nova][pci-passthrough] definitely specify VFIO driver as the host PCI driver for passthrough

2016-06-24 Thread Daniel P. Berrange
On Fri, Jun 24, 2016 at 12:27:57PM +0800, Chen Fan wrote: > hi all, > in openstack, we can use the pci passthrough feature now, refer to > https://wiki.openstack.org/wiki/Pci_passthrough > but we can't definitely specify the host pci driver is LEGACY_KVM or > newer VFIO, > new

Re: [openstack-dev] [all] Proposal: copyright-holders file in each project, or copyright holding forced to the OpenStack Foundation

2016-01-15 Thread Daniel P. Berrange
On Fri, Jan 15, 2016 at 12:53:49PM +, Chris Dent wrote: > On Fri, 15 Jan 2016, Thomas Goirand wrote: > > >Whatever we choose, I think we should ban having copyright holding text > >within our source code. While licensing is a good idea, as it is > >accurate, the copyright holding information

Re: [openstack-dev] [all] Proposal: copyright-holders file in each project, or copyright holding forced to the OpenStack Foundation

2016-01-15 Thread Daniel P. Berrange
On Fri, Jan 15, 2016 at 08:48:21PM +0800, Thomas Goirand wrote: > This isn't the first time I'm calling for it. Let's hope this time, I'll > be heard. > > Randomly, contributors put their company names into source code. When > they do, then effectively, this tells that a given source file

[openstack-dev] [nova][docker][powervm] out of tree virt driver breakage

2016-01-19 Thread Daniel P. Berrange
mmit fbe31e461ac3f16edb795993558a2314b4c16b52 Author: Daniel P. Berrange <berra...@redhat.com> Date: Mon Jun 8 17:58:09 2015 +0100 compute: convert manager to use nova.objects.ImageMeta Update the virt driver API so that all methods with an 'image_meta' parameter take a nova.objects

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

2016-02-08 Thread Daniel P. Berrange
On Sun, Feb 07, 2016 at 03:07:20PM -0500, Jay Pipes wrote: > I would love to see the OpenStack contributor community take back the design > summit to its original format and purpose and decouple it from the OpenStack > Summit's conference portion. > > I believe the design summits should be

Re: [openstack-dev] [nova] ram size and huge page number for VM

2016-02-09 Thread Daniel P. Berrange
On Mon, Feb 08, 2016 at 07:47:56PM +, Serguei Bezverkhi (sbezverk) wrote: > Hello, > > I using the latest Liberty and I am trying to bring up a VM with some numa > options configured using flavor. Specifically I need to give this VM 16GB > of RAM and in addition it will need to use 12x1GB

Re: [openstack-dev] [Nova][Cinder] Multi-attach, determining when to call os-brick's connector.disconnect_volume

2016-02-11 Thread Daniel P. Berrange
On Tue, Feb 09, 2016 at 11:49:33AM -0800, Walter A. Boring IV wrote: > Hey folks, >One of the challenges we have faced with the ability to attach a single > volume to multiple instances, is how to correctly detach that volume. The > issue is a bit complex, but I'll try and explain the

Re: [openstack-dev] [nova] Migration progress

2016-02-03 Thread Daniel P. Berrange
On Wed, Feb 03, 2016 at 10:44:36AM +, Daniel P. Berrange wrote: > On Wed, Feb 03, 2016 at 10:37:24AM +, Koniszewski, Pawel wrote: > > Hello everyone, > > > > On the yesterday's live migration meeting we had concerns that interval of > > writing migration prog

Re: [openstack-dev] [nova] Migration progress

2016-02-03 Thread Daniel P. Berrange
On Wed, Feb 03, 2016 at 10:37:24AM +, Koniszewski, Pawel wrote: > Hello everyone, > > On the yesterday's live migration meeting we had concerns that interval of > writing migration progress to the database is too short. > > Information about migration progress will be stored in the database

Re: [openstack-dev] [nova] Migration progress

2016-02-03 Thread Daniel P. Berrange
On Wed, Feb 03, 2016 at 11:27:16AM +, Paul Carlton wrote: > On 03/02/16 10:49, Daniel P. Berrange wrote: > >On Wed, Feb 03, 2016 at 10:44:36AM +0000, Daniel P. Berrange wrote: > >>On Wed, Feb 03, 2016 at 10:37:24AM +, Koniszewski, Pawel wrote: &

Re: [openstack-dev] [nova][virt] rebuild action not in support-matrix

2016-02-02 Thread Daniel P. Berrange
On Mon, Feb 01, 2016 at 05:04:37PM -0700, Matt Riedemann wrote: > > > On 2/1/2016 12:39 PM, Chen CH Ji wrote: > >Hi > > We have been trying to enablement of our CI work for our nova > >virt layer code ,so we need to configure the tempest cases based on our > >nova driver capability > >

Re: [openstack-dev] [all] A proposal to separate the design summit

2016-02-25 Thread Daniel P. Berrange
On Thu, Feb 25, 2016 at 12:40:27PM +0100, Thierry Carrez wrote: > Qiming Teng wrote: > >[...] > >Week 1: > > Wednesday-Friday: 3 days Summit. > > * Primarily an event for marketing, sales, CTOs, architects, > > operators, journalists, ... > > * Contributors can decide whether they

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

2016-02-29 Thread Daniel P. Berrange
On Mon, Feb 29, 2016 at 11:59:06AM -0500, Sean Dague wrote: > The nova/hooks.py infrastructure has been with us since early Nova. It's > currently only annotated on a few locations - 'build_instance', > 'create_instance', 'delete_instance', and 'instance_network_info'. It's > got a couple of unit

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

2016-02-29 Thread Daniel P. Berrange
On Mon, Feb 29, 2016 at 12:03:00PM -0600, Matt Riedemann wrote: > > > On 2/29/2016 11:23 AM, Andrew Laski wrote: > > > > > >On Mon, Feb 29, 2016, at 12:12 PM, Dan Smith wrote: > >>>In our continued quest on being more explicit about plug points it feels > >>>like we should other document the

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

2016-02-29 Thread Daniel P. Berrange
On Mon, Feb 29, 2016 at 12:23:09PM -0500, Andrew Laski wrote: > > > On Mon, Feb 29, 2016, at 12:12 PM, Dan Smith wrote: > > > In our continued quest on being more explicit about plug points it feels > > > like we should other document the interface (which means creating > > > stability on the

Re: [openstack-dev] [all] A proposal to separate the design summit

2016-02-22 Thread Daniel P. Berrange
On Mon, Feb 22, 2016 at 04:14:06PM +0100, Thierry Carrez wrote: > Hi everyone, > > TL;DR: Let's split the events, starting after Barcelona. Yes, please. Your proposal addresses the big issue I have with current summits which is the really poor timing wrt start of each dev cycle. > The idea

Re: [openstack-dev] [nova] nova-compute blocking main thread under heavy disk IO

2016-02-22 Thread Daniel P. Berrange
On Mon, Feb 22, 2016 at 12:07:37PM -0500, Sean Dague wrote: > On 02/22/2016 10:43 AM, Chris Friesen wrote: > > Hi all, > > > > We've recently run into some interesting behaviour that I thought I > > should bring up to see if we want to do anything about it. > > > > Basically the problem seems to

Re: [openstack-dev] [all] A proposal to separate the design summit

2016-02-26 Thread Daniel P. Berrange
On Fri, Feb 26, 2016 at 10:39:08AM -0500, Rich Bowen wrote: > > > On 02/22/2016 10:14 AM, Thierry Carrez wrote: > > Hi everyone, > > > > TL;DR: Let's split the events, starting after Barcelona. > > > > > > > > Comments, thoughts ? > > Thierry (and Jay, who wrote a similar note much

Re: [openstack-dev] [all] A proposal to separate the design summit

2016-02-26 Thread Daniel P. Berrange
On Fri, Feb 26, 2016 at 08:55:52AM -0800, James Bottomley wrote: > On Fri, 2016-02-26 at 16:03 +0000, Daniel P. Berrange wrote: > > On Fri, Feb 26, 2016 at 10:39:08AM -0500, Rich Bowen wrote: > > > > > > > > > On 02/22/2016 10:14 AM, Thierry Carrez wrote: >

Re: [openstack-dev] [nova][infra] Ability to run newer QEMU in Gate jobs

2016-01-19 Thread Daniel P. Berrange
On Tue, Jan 19, 2016 at 05:47:58PM +, Jeremy Stanley wrote: > On 2016-01-19 18:32:38 +0100 (+0100), Kashyap Chamarthy wrote: > [...] > > Matt Riedemann tells me on IRC that multi-node live migration job is > > currently Ubuntu only, and to get a newer QEMU, it has to be added to > > Ubuntu

Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

2016-01-21 Thread Daniel P. Berrange
On Wed, Jan 20, 2016 at 01:23:02PM -0430, Flavio Percoco wrote: > Greetings, > > At the Tokyo summit, we discussed OpenStack's development themes in a > cross-project session. In this session a group of folks started discussing > what > topics the overall community could focus on as a shared

Re: [openstack-dev] [glance][ironic][cinder][nova] 'tar' as an image disk_format

2016-01-26 Thread Daniel P. Berrange
On Sun, Jan 24, 2016 at 12:00:16AM +0200, Duncan Thomas wrote: > I guess my wisdom would be 'why'? What does this enable you to do that you > couldn't do with similar ease with the formats we have and are people > trying to do that frequently. > > We've seen in cinder that image formats have a

Re: [openstack-dev] [glance][ironic][cinder][nova] 'tar' as an image disk_format

2016-01-27 Thread Daniel P. Berrange
On Wed, Jan 27, 2016 at 08:32:58AM -0430, Flavio Percoco wrote: > On 27/01/16 08:20 -0430, Flavio Percoco wrote: > >On 26/01/16 09:11 +0000, Daniel P. Berrange wrote: > >>On Sun, Jan 24, 2016 at 12:00:16AM +0200, Duncan Thomas wrote: > >>>I guess my wisdom would be 'w

Re: [openstack-dev] [Kuryr] will we use os-vif in kuryr

2016-02-18 Thread Daniel P. Berrange
On Thu, Feb 18, 2016 at 09:01:35AM +, Liping Mao (limao) wrote: > Hi Kuryr team, > > I see couple of commits to add support for vif plug. > https://review.openstack.org/#/c/280411/ > https://review.openstack.org/#/c/280878/ > > Do we have plan to use os-vif? >

[openstack-dev] KVM Forum 2016: Call For Participation

2016-03-10 Thread Daniel P. Berrange
= 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) =

Re: [openstack-dev] [nova] Minimal secure identification of a new VM

2016-04-06 Thread Daniel P. Berrange
On Tue, Apr 05, 2016 at 06:00:55PM -0400, Adam Young wrote: > We have a use case where we want to register a newly spawned Virtual machine > with an identity provider. > > Heat also has a need to provide some form of Identity for a new VM. > > > Looking at the set of utilities right now, there

Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-06 Thread Daniel P. Berrange
On Wed, Apr 06, 2016 at 12:28:02PM +0200, Roman Dobosz wrote: > On Wed, 6 Apr 2016 16:12:16 +0800 > Zhipeng Huang wrote: > > > You are actually touching on something we have been working on. There is a > > team in OPNFV DPACC project has been working acceleration related

Re: [openstack-dev] [nova] post-copy live migration

2016-04-05 Thread Daniel P. Berrange
On Tue, Apr 05, 2016 at 05:17:41PM +0200, Luis Tomas wrote: > Hi, > > We are working on the possibility of including post-copy live migration into > Nova (https://review.openstack.org/#/c/301509/) > > At libvirt level, post-copy live migration works as follow: > - Start live migration with a

Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-06 Thread Daniel P. Berrange
On Wed, Apr 06, 2016 at 07:34:46AM +0200, Roman Dobosz wrote: > On Tue, 5 Apr 2016 13:58:44 +0100 > "Daniel P. Berrange" <berra...@redhat.com> wrote: > > > Along similar lines we have proposals to add vGPU support to Nova, > > where the vGPUs may or may not

Re: [openstack-dev] [nova] Minimal secure identification of a new VM

2016-04-06 Thread Daniel P. Berrange
On Wed, Apr 06, 2016 at 04:03:18PM +, Hayes, Graham wrote: > On 06/04/2016 16:54, Gary Kotton wrote: > > > > > > On 4/6/16, 12:42 PM, "Daniel P. Berrange" <berra...@redhat.com> wrote: > > > >> On Tue, Apr 05, 2016 at 06:00:55PM -0400, Adam

Re: [openstack-dev] [nova] FYI: Removing default flavors from nova

2016-04-06 Thread Daniel P. Berrange
On Wed, Apr 06, 2016 at 04:29:00PM +, Fox, Kevin M wrote: > It feels kind of like a defcore issue though. Its harder for app > developers to create stuff like heat templates intended for cross > cloud that recommend a size, m1.small, without a common reference. Even with Nova defining these

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

2016-03-01 Thread Daniel P. Berrange
On Mon, Feb 29, 2016 at 12:36:03PM -0700, Rich Megginson wrote: > On 02/29/2016 12:19 PM, Chris Friesen wrote: > >On 02/29/2016 12:22 PM, Daniel P. Berrange wrote: > > > >>There's three core scenarios for hooks > >> > >> 1. Modifying some aspect

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

2016-03-02 Thread Daniel P. Berrange
On Tue, Mar 01, 2016 at 01:53:18PM -0500, Rob Crittenden wrote: > Daniel P. Berrange wrote: > > On Mon, Feb 29, 2016 at 12:36:03PM -0700, Rich Megginson wrote: > >> On 02/29/2016 12:19 PM, Chris Friesen wrote: > >>> On 02/29/2016 12:22 PM, Daniel P. Berrange wrote: &

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

2016-03-03 Thread Daniel P. Berrange
On Thu, Mar 03, 2016 at 09:09:03AM -0600, Sam Matzek wrote: > On Wed, Mar 2, 2016 at 8:25 PM, Adam Young wrote: > > On 02/29/2016 01:49 PM, Andrew Laski wrote: > >> > >> > >> On Mon, Feb 29, 2016, at 01:18 PM, Dan Smith wrote: > > Forgive my ignorance or for playing

Re: [openstack-dev] [Nova] FPGA as a resource

2016-04-05 Thread Daniel P. Berrange
On Tue, Apr 05, 2016 at 02:27:30PM +0200, Roman Dobosz wrote: > Hey all, > > On yesterday's scheduler meeting I was raised the idea of bringing up > the FPGA to the OpenStack as the resource, which than might be exposed > to the VMs. > > The use cases for motivations, why one want do this, are

[openstack-dev] [nova][neutron] os-vif status report

2016-04-13 Thread Daniel P. Berrange
I won't be present at the forthcoming Austin summit, so to prepare other people in case there are f2f discussions, this is a rough status report on the os-vif progress os-vif core --- NB by os-vif core, I mean the python packages in the os_vif/ namespace. The object model for

Re: [openstack-dev] [nova] Encrypted Ephemeral Storage

2016-04-25 Thread Daniel P. Berrange
On Mon, Apr 25, 2016 at 04:28:17PM +, Coffman, Joel M. wrote: > Based on the comments to the RBD encryption change [1], it looks > like there will be a new direction for ephemeral disk encryption > (embedding it in QEMU directly). I assume LVM will work the same > way when the time comes. Will

Re: [openstack-dev] [nova][neutron] os-vif status report

2016-04-22 Thread Daniel P. Berrange
On Fri, Apr 22, 2016 at 04:25:54AM +, Angus Lees wrote: > In case it wasn't already assumed, anyone is welcome to contact me directly > (irc: gus, email, or in Austin) if they have questions or want help with > privsep integration work. It's early days still and the docs aren't > extensive

Re: [openstack-dev] [nova] next min libvirt?

2016-04-29 Thread Daniel P. Berrange
On Fri, Apr 29, 2016 at 10:13:42AM -0500, Sean Dague wrote: > We've just landed the libvirt min to bump us up to 1.2.1 required. It's > probably a good time consider the appropriate bump for Otaca. > > By that time our Ubuntu LTS will be 16.04 (libvirt 1.3.1), RHEL 7.1 > (1.2.8). Additionally

Re: [openstack-dev] [oslo.config] Encrypt the sensitive options

2016-04-26 Thread Daniel P. Berrange
On Tue, Apr 26, 2016 at 08:19:23AM -0500, Doug Hellmann wrote: > Excerpts from Guangyu Suo's message of 2016-04-26 07:28:42 -0500: > > Hello, oslo team > > > > For now, some sensitive options like password or token are configured as > > plaintext, anyone who has the priviledge to read the

Re: [openstack-dev] KVM Forum 2016: Call For Participation

2016-04-27 Thread Daniel P. Berrange
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

Re: [openstack-dev] [oslo.config] Encrypt the sensitive options

2016-04-26 Thread Daniel P. Berrange
On Tue, Apr 26, 2016 at 04:24:52PM +0200, Jordan Pittier wrote: > On Tue, Apr 26, 2016 at 3:32 PM, Daniel P. Berrange <berra...@redhat.com> > wrote: > > > On Tue, Apr 26, 2016 at 08:19:23AM -0500, Doug Hellmann wrote: > > > Excerpts from Guangyu Suo's messag

Re: [openstack-dev] [nova] Thoughts on deprecating the legacy bdm v1 API support

2016-05-19 Thread Daniel P. Berrange
On Tue, May 17, 2016 at 09:48:02AM -0500, Matt Riedemann wrote: > In the live migration meeting today mdbooth and I were chatting about how > hard it is to follow the various BDM code through nova, because you have the > three block_device modules: > > * nova.block_device - dict that does some

Re: [openstack-dev] [nova]Libvirt error code for failing volume in nova

2016-05-19 Thread Daniel P. Berrange
On Wed, May 18, 2016 at 07:57:17PM +, Radhakrishnan, Siva wrote: > Hi All! > Currently I am working on this bug > https://bugs.launchpad.net/nova/+bug/1168011 which says we have to change > error message displayed when attaching a volume fails. Currently it catches > all operation errors

Re: [openstack-dev] Wiki

2016-05-11 Thread Daniel P. Berrange
On Tue, May 10, 2016 at 12:59:41PM -0400, Anita Kuno wrote: > On 05/10/2016 12:48 PM, Dan Smith wrote: > >>> Hmm... that's unfortunate, as we were trying to get some of our less > >>> ephemeral items out of random etherpads and into the wiki (which has the > >>> value of being google indexed). > >

Re: [openstack-dev] [nova] next min libvirt?

2016-05-03 Thread Daniel P. Berrange
On Fri, Apr 29, 2016 at 03:16:56PM -0500, Matt Riedemann wrote: > On 4/29/2016 10:28 AM, Daniel P. Berrange wrote: > >On Fri, Apr 29, 2016 at 10:13:42AM -0500, Sean Dague wrote: > >>We've just landed the libvirt min to bump us up to 1.2.1 required. It's > >>pr

Re: [openstack-dev] [nova] next min libvirt?

2016-05-03 Thread Daniel P. Berrange
On Sat, Apr 30, 2016 at 10:28:23AM -0500, Thomas Bechtold wrote: > Hi, > > On Fri, Apr 29, 2016 at 10:13:42AM -0500, Sean Dague wrote: > > We've just landed the libvirt min to bump us up to 1.2.1 required. It's > > probably a good time consider the appropriate bump for Otaca. > > > > By that

Re: [openstack-dev] [Nova] Libvirt version requirement

2016-05-03 Thread Daniel P. Berrange
On Mon, May 02, 2016 at 11:27:01AM +0800, ZhiQiang Fan wrote: > Hi Nova cores, > > There is a spec[1] submitted to Telemetry project for Newton release, > mentioned that a new feature requires libvirt >= 1.3.4 , I'm not sure if > this will have bad impact to Nova service, so I open this thread

Re: [openstack-dev] [Nova] Live Migration: Austin summit update

2016-05-03 Thread Daniel P. Berrange
On Fri, Apr 29, 2016 at 10:32:09PM +, Murray, Paul (HP Cloud) wrote: > The following summarizes status of the main topics relating to live migration > after the Newton design summit. Please feel free to correct any inaccuracies > or add additional information. > Post copy > > The spec to add

Re: [openstack-dev] [Nova] Live Migration: Austin summit update

2016-05-04 Thread Daniel P. Berrange
On Tue, May 03, 2016 at 04:16:43PM -0600, Chris Friesen wrote: > On 05/03/2016 03:14 AM, Daniel P. Berrange wrote: > > >There are currently many options for live migration with QEMU that can > >assist in completion > > > > >Given this I've spent the last week c

Re: [openstack-dev] [tc] License for specs repo

2016-05-05 Thread Daniel P. Berrange
On Thu, May 05, 2016 at 12:03:38PM -0400, Ben Swartzlander wrote: > It appears that many of the existing specs repos contain a confusing mixture > of Apache 2.0 licensed code and Creative Commons licensed docs. > > The official cookie-cutter for creating new specs repos [1] appears to also >

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

2016-04-19 Thread Daniel P. Berrange
On Tue, Apr 19, 2016 at 09:57:56AM -0500, Dean Troyer wrote: > On Tue, Apr 19, 2016 at 9:06 AM, Adam Young wrote: > > > I wonder how much of that is Token caching. In a typical CLI use patter, > > a new token is created each time a client is called, with no passing of a > >

<    2   3   4   5   6   7   8   >