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

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 > >

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

There have been threads in the past about the slowness of the "openstack" client tool such as this one by Sean last year: http://lists.openstack.org/pipermail/openstack-dev/2015-April/061317.html Sean mentioned a 1.5s fixed overhead on openstack client, and mentions it is significantly slower

Re: [openstack-dev] Nova hook

On Thu, Apr 14, 2016 at 03:15:42PM +0800, Kenny Ji-work wrote: > Hi all,​ > The nova hooks facility will be removed in the future, now > what's the recommended method to add custom code into the nova's > internal APIs? Thank you for answer! The point of removing it is that we do *not* want

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

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] FYI: Removing default flavors from nova

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] Minimal secure identification of a new VM

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] FPGA as a resource

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] Minimal secure identification of a new VM

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

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] post-copy live migration

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

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] KVM Forum 2016: Call For Participation

= 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] nova hooks - document & test or deprecate?

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] nova hooks - document & test or deprecate?

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?

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?

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?

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] [nova] nova hooks - document & test or deprecate?

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] [all] A proposal to separate the design summit

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] [all] A proposal to separate the design summit

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

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-compute blocking main thread under heavy disk IO

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

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] [Kuryr] will we use os-vif in kuryr

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? >

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

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] [all][tc] Proposal: Separate design summits from OpenStack conferences

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] Migration progress

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

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

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

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] [glance][ironic][cinder][nova] 'tar' as an image disk_format

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] [glance][ironic][cinder][nova] 'tar' as an image disk_format

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] [all][tc] Stabilization cycles: Elaborating on the idea to move it forward

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

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

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] [nova][infra] Ability to run newer QEMU in Gate jobs

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] Proposal: copyright-holders file in each project, or copyright holding forced to the OpenStack Foundation

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

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

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

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

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][Glance] Nova + Glance_v2 = Love

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

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] Testing concerns around boot from UEFI spec

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

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

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

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

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

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

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] [cinder][nova]Move encryptors to os-brick

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

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

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

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

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] [cinder][nova]Move encryptors to os-brick

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

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] [Infra] Remove .mailmap files from OpenStack repos

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][infra] Getting a bleeding edge libvirt gate job running

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] [glance] [nova] Image Signature Verification

On Tue, Nov 17, 2015 at 02:09:42PM -0300, Flavio Percoco wrote: > On 13/11/15 09:35 +0000, Daniel P. Berrange wrote: > >On Thu, Nov 12, 2015 at 08:30:53PM +, Poulos, Brianna L. wrote: > >>Hello, > >> > >>There has recently been additional discussion ab

Re: [openstack-dev] [glance] [nova] Image Signature Verification

On Thu, Nov 12, 2015 at 08:30:53PM +, Poulos, Brianna L. wrote: > Hello, > > There has recently been additional discussion about the best way to handle > image signature verification in glance and nova [1]. There are two > options being discussed for the signature (the examples below using >

Re: [openstack-dev] [nova] hackathon day

On Thu, Nov 12, 2015 at 11:15:09AM +, Rosa, Andrea (HP Cloud Services) wrote: > Hi > > I knew that people in China had a 3 days hackathon few months ago I was > thinking to have a similar thing in Europe. > My original idea was to propose to add an extra day after the mid-cycle but I > am

Re: [openstack-dev] [Openstack-operators] [tc][all][osprofiler] OSprofiler is dead, long live OSprofiler

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

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

On Fri, Nov 06, 2015 at 05:08:59PM +1100, Tony Breeds wrote: > Hello all, > I came across [1] which is notionally an ironic bug in that horizon > presents > VM operations (like suspend) to users. Clearly these options don't make sense > to ironic which can be confusing. > > There is a

Re: [openstack-dev] [nova] Proposal to add Sylvain Bauza to nova-core

On Fri, Nov 06, 2015 at 03:32:00PM +, John Garbutt wrote: > Hi, > > I propose we add Sylvain Bauza[1] to nova-core. > > Over the last few cycles he has consistently been doing great work, > including some quality reviews, particularly around the Scheduler. > > Please respond with comments,

Re: [openstack-dev] [nova] Proposal to add Alex Xu to nova-core

On Fri, Nov 06, 2015 at 03:32:04PM +, John Garbutt wrote: > Hi, > > I propose we add Alex Xu[1] to nova-core. > > Over the last few cycles he has consistently been doing great work, > including some quality reviews, particularly around the API. > > Please respond with comments, +1s, or

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

On Fri, Nov 06, 2015 at 07:09:59AM -0500, Sean Dague wrote: > On 11/06/2015 04:49 AM, Daniel P. Berrange wrote: > > > > I think that exposing hypervisor_type is very much the *wrong* approach > > to this problem. The set of allowed actions varies based on mu

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

On Tue, Oct 13, 2015 at 05:08:29PM -0700, Zaro wrote: > Hello All, > > The openstack-infra team would like to upgrade from our Gerrit 2.8 to > Gerrit 2.11. We are proposing to do the upgrade shortly after the > Mitaka summit. The main motivation behind the upgrade is to allow us > to take

Re: [openstack-dev] [infra][all] Reviews with a prio label?

On Tue, Oct 20, 2015 at 06:09:51PM +0200, Markus Zoeller wrote: > In ML post [1] I wondered if it would be possible to introduce a new > "prio" label in Gerrit which could help in focusing review efforts to > increase the throughput. With this new post I'd like to discuss if we > think this could

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

On Wed, Oct 07, 2015 at 03:54:29PM -0600, Chris Friesen wrote: > On 10/07/2015 03:14 AM, Daniel P. Berrange wrote: > > >For suspended instances, the scenario is really the same as with completely > >offline instances. The only extra step is that you need to migrate the saved &

Re: [openstack-dev] [tc] naming N and O releases nowish

On Wed, Oct 07, 2015 at 02:57:59PM +0200, Thierry Carrez wrote: > Sean Dague wrote: > > We're starting to make plans for the next cycle. Long term plans are > > getting made for details that would happen in one or two cycles. > > > > As we already have the locations for the N and O summits I

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

On Tue, Oct 06, 2015 at 11:43:52AM -0600, Chris Friesen wrote: > On 10/06/2015 11:27 AM, Paul Carlton wrote: > > > > > >On 06/10/15 17:30, Chris Friesen wrote: > >>On 10/06/2015 08:11 AM, Daniel P. Berrange wrote: > >>>On Tue, Oct 06, 2015 at 02:54:2

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

On Wed, Oct 07, 2015 at 10:26:05AM +0100, Paul Carlton wrote: > I'd be happy to take this on in Mitaka Ok, first step would be to re-propose the old Kilo spec against Mitaka and we should be able to fast-approve it. > >>>So my reading of this is the issue could be addressed in Mitaka by >

Re: [openstack-dev] [nova] revisiting minimum libvirt version

On Wed, Oct 07, 2015 at 06:32:53AM -0400, Sean Dague wrote: > The following review https://review.openstack.org/#/c/171098 attempts to > raise the minimum libvirt version to 1.0.3. > > In May that was considered a no go - >

Re: [openstack-dev] [nova] Min libvirt for Mitaka is 0.10.2 and suggest Nxxx uses 1.1.1

On Wed, Oct 07, 2015 at 07:17:09AM -0400, Sean Dague wrote: > On 10/07/2015 07:02 AM, Daniel P. Berrange wrote: > > On Wed, Oct 07, 2015 at 06:55:44AM -0400, Sean Dague wrote: > >> Isn't RHEL 7.1 just an update stream on RHEL 7.0? It seems a little > >> weird to kee

[openstack-dev] [nova] FYI: Updated Mitaka specs template

FYI anyone who is pushing specs for review against Mitaka should be aware that yesterday we merged a change to the spec template. Specifically we have removed the "Project priority" section of the template, since it has been a source of much confusion, cannot be filled out until after the summit

[openstack-dev] [nova] Min libvirt for Mitaka is 0.10.2 and suggest Nxxx uses 1.1.1

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

Re: [openstack-dev] [nova] Min libvirt for Mitaka is 0.10.2 and suggest Nxxx uses 1.1.1

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

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

On Tue, Oct 06, 2015 at 06:27:12PM +0100, Paul Carlton wrote: > > > On 06/10/15 17:30, Chris Friesen wrote: > >On 10/06/2015 08:11 AM, Daniel P. Berrange wrote: > >>On Tue, Oct 06, 2015 at 02:54:21PM +0100, Paul Carlton wrote: > >>>https://review.openstack.

Re: [openstack-dev] [Openstack-operators] [nova] Min libvirt for Mitaka is 0.10.2 and suggest Nxxx uses 1.1.1

On Wed, Oct 07, 2015 at 11:46:58AM +0100, 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 > Mitaka will required 0.10.2 > > This mail is a reminder that

Re: [openstack-dev] [Openstack-operators] [nova] Min libvirt for Mitaka is 0.10.2 and suggest Nxxx uses 1.1.1

On Wed, Oct 07, 2015 at 11:13:12AM +, Tim Bell wrote: > > Although Red Hat is no longer supporting RHEL 6 after Icehouse, a number of > users such as GoDaddy and CERN are using Software Collections to run the > Python 2.7 code. Do you have any educated guess as to when you might switch to

Re: [openstack-dev] [tc] naming N and O releases nowish

On Wed, Oct 07, 2015 at 07:47:31AM -0400, Sean Dague wrote: > We're starting to make plans for the next cycle. Long term plans are > getting made for details that would happen in one or two cycles. > > As we already have the locations for the N and O summits I think we > should do the naming

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

On Tue, Oct 06, 2015 at 02:54:21PM +0100, Paul Carlton wrote: > https://review.openstack.org/#/c/85048/ was raised to address the > migration of instances that are not running but people did not warm to > the idea of bringing a stopped/suspended instance to a paused state to > migrate it. Is

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

On Fri, Oct 02, 2015 at 04:38:30PM -0400, Mathieu Gagné wrote: > On 2015-10-02 4:18 PM, Pavel Boldin wrote: > > > > You have to pass device names from /dev/, e.g., if a VM has > > ephemeral disk > > attached at /dev/vdb you need to pass in 'vdb'. Format expected by > >

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

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] [Openstack-operators] [cinder] [all] The future of Cinder API v1

On Wed, Sep 30, 2015 at 08:10:43AM -0400, Sean Dague wrote: > On 09/30/2015 07:29 AM, Ivan Kolodyazhny wrote: > > Sean, > > > > openstack client supports Cinder API v2 since Liberty. What it the right > > way ti fix grenade? > > Here's the thing. > > With this change: Rally doesn't work,

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On Fri, Sep 25, 2015 at 11:05:09AM -0400, Doug Hellmann wrote: > git tools such as git log and git show indent the commit message in > their output, so you don't actually have the full 79/80 character width > to work with. That's where the 72 comes from. It is also commonly done because so that

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

On Wed, Sep 23, 2015 at 01:48:17PM +0100, Paul Carlton wrote: > > > On 22/09/15 16:44, Daniel P. Berrange wrote: > >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 > >&

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

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

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

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

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] [nova][neutron][SR-IOV] Hardware changes and shifting PCI addresses

On Mon, Sep 14, 2015 at 09:34:31PM -0400, Jay Pipes wrote: > On 09/10/2015 05:23 PM, Brent Eagles wrote: > >Hi, > > > >I was recently informed of a situation that came up when an engineer > >added an SR-IOV nic to a compute node that was hosting some guests that > >had VFs attached. Unfortunately,

Re: [openstack-dev] [nova][neutron][SR-IOV] Hardware changes and shifting PCI addresses

On Thu, Sep 10, 2015 at 06:53:06PM -0230, Brent Eagles wrote: > Hi, > > I was recently informed of a situation that came up when an engineer > added an SR-IOV nic to a compute node that was hosting some guests that > had VFs attached. Unfortunately, adding the card shuffled the PCI > addresses

Re: [openstack-dev] [Nova] What is the no_device flag for in block device mapping?

On Tue, Sep 08, 2015 at 05:32:29PM +, Murray, Paul (HP Cloud) wrote: > Hi All, > > I'm wondering what the "no_device" flag is used for in the block device > mappings. I had a dig around in the code but couldn't figure out why it > is there. The name suggests an obvious meaning, but I've

Re: [openstack-dev] [nova] testing for setting the admin password via the libvirt driver

On Tue, Aug 25, 2015 at 09:14:33AM -0500, Matt Riedemann wrote: Support to change the admin password on an instance via the libvirt driver landed in liberty [1] but the hypervisor support matrix wasn't updated [2]. There is a version restriction in the driver that it won't work unless you're

Re: [openstack-dev] [nova] should we allow overcommit for a single VM?

On Mon, Aug 17, 2015 at 01:22:28PM -0600, Chris Friesen wrote: I tried bringing this up on the irc channel, but nobody took the bait. Hopefully this will generate some discussion. I just filed bug 1485631. Nikola suggested one way of handling it, but there are some complications that I

Re: [openstack-dev] [openstack][nova] Streamlining of config options in nova

On Wed, Aug 12, 2015 at 07:20:24PM +0200, Markus Zoeller wrote: Another thing which makes it hard to understand the impact of the config options is, that it's not clear how the interdependency to other config options is. As an example, the serial_console.base_url has a dependency to

Re: [openstack-dev] Hyper-V 2008 R2 support

On Tue, Aug 04, 2015 at 02:34:19PM +, Alessandro Pilotti wrote: Hi guys, Just a quick note on the Windows editions support matrix updates for the Nova Hyper-V driver and Neutron networking-hyperv ML2 agent: We are planning to drop legacy Windows Server / Hyper-V Server 2008 R2

Re: [openstack-dev] [openstack][nova] Streamlining of config options in nova

On Fri, Jul 24, 2015 at 09:48:15AM +0100, Daniel P. Berrange wrote: On Thu, Jul 23, 2015 at 05:55:36PM +0300, mhorban wrote: Hi all, During development process in nova I faced with an issue related with config options. Now we have lists of config options and registering options mixed

Re: [openstack-dev] [openstack][nova] Streamlining of config options in nova

On Thu, Jul 23, 2015 at 05:55:36PM +0300, mhorban wrote: Hi all, During development process in nova I faced with an issue related with config options. Now we have lists of config options and registering options mixed with source code in regular files. From one side it can be convenient: to

Re: [openstack-dev] [openstack][nova] Streamlining of config options in nova

On Thu, Jul 23, 2015 at 11:57:01AM -0500, Michael Still wrote: In fact, I did an example of what I thought it would look like already: https://review.openstack.org/#/c/205154/ I welcome discussion on this, especially from people who couldn't make it to the mid-cycle. Its up to y'all if

<    1   2   3   4   5   6   7   8   >