Re: [openstack-dev] [all] config options not correctly deprecated

On Mon, Nov 10, 2014 at 09:45:02AM +, Derek Higgins wrote: > Tl;dr oslo.config wasn't logging warnings about deprecated config > options, do we need to support them for another cycle? AFAIK, there has not been any change in olso.config behaviour in the Juno release, as compared to previous rel

Re: [openstack-dev] [stable] New config options, no default change

On Tue, Nov 11, 2014 at 10:24:41AM +, Dave Walker wrote: > Hi, > > Looking at a stable/juno cinder proposed change[0], I came across one > that introduces a new config option. > > The default is a noop change for the behaviour, so no bad surprises on > upgrade. > > These sort of changes fee

Re: [openstack-dev] [Nova][Neutron][NFV][Third-party] CI for NUMA, SR-IOV, and other features that can't be tested on current infra.

On Wed, Nov 12, 2014 at 03:48:47PM -0500, Russell Bryant wrote: > On 11/12/2014 02:11 PM, Steve Gordon wrote: > > NUMA > > > > > > We still need to identify some hardware to run third party CI for the > > NUMA-related work, and no doubt other things that will come up. It's > > expected that t

Re: [openstack-dev] mixing vif drivers e1000 and virtio

On Thu, Nov 13, 2014 at 07:37:33AM -0800, Srini Sundararajan wrote: > Hi, > When i create an instance with more than 1 vif, how can i pick and > choose/configure which driver (e1000/virtio) i can assign ? The vif driver is is customizable at a per-image level using the hw_vif_model metadata p

Re: [openstack-dev] [Nova][Neutron][NFV][Third-party] CI for NUMA, SR-IOV, and other features that can't be tested on current infra.

On Thu, Nov 13, 2014 at 09:28:01AM -0800, Dan Smith wrote: > > Yep, it is possible to run the tests inside VMs - the key is that when > > you create the VMs you need to be able to give them NUMA topology. This > > is possible if you're creating your VMs using virt-install, but not if > > you're cre

Re: [openstack-dev] [Nova][Neutron][NFV][Third-party] CI for NUMA, SR-IOV, and other features that can't be tested on current infra.

On Thu, Nov 13, 2014 at 09:36:18AM -0800, Dan Smith wrote: > > That sounds like something worth exploring at least, I didn't know > > about that kernel build option until now :-) It sounds like it ought > > to be enough to let us test the NUMA topology handling, CPU pinning > > and probably huge pa

Re: [openstack-dev] [Nova][Neutron][NFV][Third-party] CI for NUMA, SR-IOV, and other features that can't be tested on current infra.

On Thu, Nov 13, 2014 at 05:43:14PM +, Daniel P. Berrange wrote: > On Thu, Nov 13, 2014 at 09:36:18AM -0800, Dan Smith wrote: > > > That sounds like something worth exploring at least, I didn't know > > > about that kernel build option until now :-) It sounds like it o

Re: [openstack-dev] [nova][libvirt] - 'nova reboot' causes console-log truncated

On Thu, Nov 13, 2014 at 01:55:06PM -0800, Surojit Pathak wrote: > Hi all, > > [Issue observed] > If we issue 'nova reboot ', we get to have the console output of the > latest bootup of the server only. The console output of the previous boot > for the same server vanishes due to truncation[1]. If

Re: [openstack-dev] [all] config options not correctly deprecated

On Thu, Nov 13, 2014 at 05:20:47PM -0600, Ben Nemec wrote: > On 11/10/2014 05:00 AM, Daniel P. Berrange wrote: > > On Mon, Nov 10, 2014 at 09:45:02AM +, Derek Higgins wrote: > >> Tl;dr oslo.config wasn't logging warnings about deprecated config > >> options

Re: [openstack-dev] [nova] mapping of hypervisor support matrix to driver functions - agenda?

On Fri, Nov 14, 2014 at 05:26:44PM +0100, Markus Zoeller wrote: > In preparation to the blueprint "libvirt-kvm-systemz" [1] we made an > analysis of the mapping of the driver functions to the hypervisor > support matrix features [2]. We could provide that information for the > wiki page. Should w

Re: [openstack-dev] [nova] RT/Scheduler summit summary and Kilo development plan

On Mon, Nov 17, 2014 at 10:58:52AM -0500, Jay Pipes wrote: > Good morning Stackers, > > At the summit in Paris, we put together a plan for work on the Nova resource > tracker and scheduler in the Kilo timeframe. A large number of contributors > across many companies are all working on this particu

Re: [openstack-dev] [nova] policy on old / virtually abandoned patches

On Tue, Nov 18, 2014 at 07:06:59AM -0500, Sean Dague wrote: > Nova currently has 197 patches that have seen no activity in the last 4 > weeks (project:openstack/nova age:4weeks status:open). > > Of these > * 108 are currently Jenkins -1 (project:openstack/nova age:4weeks > status:open label:Verif

Re: [openstack-dev] [nova] policy on old / virtually abandoned patches

On Tue, Nov 18, 2014 at 07:33:54AM -0500, Sean Dague wrote: > On 11/18/2014 07:29 AM, Daniel P. Berrange wrote: > > On Tue, Nov 18, 2014 at 07:06:59AM -0500, Sean Dague wrote: > >> Nova currently has 197 patches that have seen no activity in the last 4 > >> weeks (projec

Re: [openstack-dev] [nova][libvirt] Block migrations and Cinder volumes

On Wed, Jun 18, 2014 at 11:09:33PM -0700, Rafi Khardalian wrote: > I am concerned about how block migration functions when Cinder volumes are > attached to an instance being migrated. We noticed some unexpected > behavior recently, whereby attached generic NFS-based volumes would become > entirely

Re: [openstack-dev] [nova] Do any hyperviors allow disk reduction as part of resize ?

-dev] [nova] Do any hyperviors allow disk reduction > > as part of resize ? > > > > On 18 June 2014 21:57, Jay Pipes wrote: > > > On 06/17/2014 05:42 PM, Daniel P. Berrange wrote: > > >> > > >> On Tue, Jun 17, 2014 at 04:32:36PM +0

Re: [openstack-dev] [nova] top gate bug is libvirt snapshot

On Thu, Jun 26, 2014 at 07:00:32AM -0400, Sean Dague wrote: > While the Trusty transition was mostly uneventful, it has exposed a > particular issue in libvirt, which is generating ~ 25% failure rate now > on most tempest jobs. > > As can be seen here - > https://github.com/openstack/nova/blob/mas

Re: [openstack-dev] [all] 3rd Party CI vs. Gerrit

On Fri, Jun 27, 2014 at 07:40:51AM -0400, Sean Dague wrote: > It's clear that lots of projects want 3rd Party CI information on > patches. But it's also clear that 6 months into this experiment with a > lot of 3rd Party CI systems, the Gerrit UI is really not great for this. That's an understateme

Re: [openstack-dev] [all] 3rd Party CI vs. Gerrit

On Sat, Jun 28, 2014 at 08:26:44AM -0500, Matt Riedemann wrote: > > > On 6/27/2014 7:35 AM, Daniel P. Berrange wrote: > >On Fri, Jun 27, 2014 at 07:40:51AM -0400, Sean Dague wrote: > >>It's clear that lots of projects want 3rd Party CI information on > >&

Re: [openstack-dev] [Nova] [Gantt] Scheduler split status

On Thu, Jul 03, 2014 at 03:30:06PM -0400, Russell Bryant wrote: > On 07/03/2014 01:53 PM, Sylvain Bauza wrote: > > Hi, > > > > == > > tl; dr: A decision has been made to split out the scheduler to a > > separate project not on a feature parity basis with nova-scheduler, your > > comments are welco

Re: [openstack-dev] [Nova] [Gantt] Scheduler split status

On Mon, Jul 07, 2014 at 09:28:16AM +0200, Sylvain Bauza wrote: > Le 04/07/2014 10:41, Daniel P. Berrange a écrit : > > On Thu, Jul 03, 2014 at 03:30:06PM -0400, Russell Bryant wrote: > >> On 07/03/2014 01:53 PM, Sylvain Bauza wrote: > >>> That doesn't mean Ga

Re: [openstack-dev] [Nova] [Gantt] Scheduler split status

On Mon, Jul 07, 2014 at 02:38:57PM +, Dugger, Donald D wrote: > Well, my main thought is that I would prefer to see the gantt split > done sooner rather than later. The reality is that we've been trying > to split out the scheduler for months and we're still not there. Until > we bite the bul

Re: [openstack-dev] [nova][libvirt] Suspend via virDomainSave() rather than virDomainManagedSave()

On Sun, Jul 06, 2014 at 10:22:44PM -0700, Rafi Khardalian wrote: > Hi All -- > > It seems as though it would be beneficial to use virDomainSave rather than > virDomainManagedSave for suspending instances. The primary benefit of > doing so would be to locate the save files within the instance's de

Re: [openstack-dev] [nova] top gate bug is libvirt snapshot

On Tue, Jul 08, 2014 at 02:50:40PM -0700, Joe Gordon wrote: > > > But for right now, we should stop the bleeding, so that nova/libvirt > > > isn't blocking everyone else from merging code. > > > > Agreed, we should merge the hack and treat the bug as release blocker > > to be resolve prior to Juno

Re: [openstack-dev] [nova] top gate bug is libvirt snapshot

On Wed, Jul 09, 2014 at 08:58:02AM +1000, Michael Still wrote: > On Wed, Jul 9, 2014 at 8:21 AM, Sean Dague wrote: > > > This is also why I find it unlikely to be a qemu bug, because that's not > > shared state between guests. If qemu just randomly wedges itself, that > > would be detectable much

Re: [openstack-dev] [olso] olso incubator logging issues

ah, I saw that last week and already sent a fix to oslo for that which is merged, so projects need to re-sync to oslo, or cherry pick this: commit 33afb20cc0e6790ae82e1bfe211d47f34c22ff91 Author: Daniel P. Berrange Date: Mon Jun 30 16:25:01 2014 +0100 Fix broken formatting of process

Re: [openstack-dev] [olso] olso incubator logging issues

On Wed, Jul 09, 2014 at 07:39:39AM -0400, Sean Dague wrote: > On 07/03/2014 01:52 PM, Doug Hellmann wrote: > >> oslo code, by definition, is going to be used a lot, inside of tight > >> loops. Which means extremely verbose. Actually > >> nova.openstack.common.policy currently represents ~40% of all

Re: [openstack-dev] [nova] top gate bug is libvirt snapshot

On Wed, Jul 09, 2014 at 08:34:06AM -0400, Sean Dague wrote: > On 07/09/2014 03:58 AM, Daniel P. Berrange wrote: > > On Tue, Jul 08, 2014 at 02:50:40PM -0700, Joe Gordon wrote: > >>>> But for right now, we should stop the bleeding, so that nova/libvirt > >>>

Re: [openstack-dev] [nova] top gate bug is libvirt snapshot

On Wed, Jul 09, 2014 at 06:23:27PM -0400, Sean Dague wrote: > The libvirt logs needed are huge, so we can't run them all the time. And > realistically, I don't think they provided us the info we needed. There > has been at least one fail on Dan's log hack patch for this scenario > today, so maybe i

Re: [openstack-dev] [nova] top gate bug is libvirt snapshot

On Thu, Jul 10, 2014 at 08:32:37AM -0400, Sean Dague wrote: > On 07/10/2014 05:03 AM, Daniel P. Berrange wrote: > > On Wed, Jul 09, 2014 at 06:23:27PM -0400, Sean Dague wrote: > >> The libvirt logs needed are huge, so we can't run them all the time. And > >> r

Re: [openstack-dev] [Containers] Nova virt driver requirements

On Thu, Jul 10, 2014 at 05:36:59PM +0400, Dmitry Guryanov wrote: > I have a question about mounts - in OpenVZ project each container has its own > filesystem in an image file. So to start a container we mount this filesystem > in host OS (because all containers share the same linux kernel). Is it

Re: [openstack-dev] [Containers] Nova virt driver requirements

On Thu, Jul 10, 2014 at 05:57:46PM +0400, Dmitry Guryanov wrote: > On Tuesday 08 July 2014 14:10:25 Michael Still wrote: > > Joe has a good answer, but you should also be aware of the hypervisor > > support matrix (https://wiki.openstack.org/wiki/HypervisorSupportMatrix), > > which hopefully comes

Re: [openstack-dev] [Containers] Nova virt driver requirements

On Thu, Jul 10, 2014 at 06:18:52PM +0400, Dmitry Guryanov wrote: > On Thursday 10 July 2014 14:47:11 Daniel P. Berrange wrote: > > On Thu, Jul 10, 2014 at 05:36:59PM +0400, Dmitry Guryanov wrote: > > > I have a question about mounts - in OpenVZ project each container has its &g

Re: [openstack-dev] [Containers] Nova virt driver requirements

On Thu, Jul 10, 2014 at 08:19:36AM -0700, James Bottomley wrote: > On Thu, 2014-07-10 at 14:47 +0100, Daniel P. Berrange wrote: > > On Thu, Jul 10, 2014 at 05:36:59PM +0400, Dmitry Guryanov wrote: > > > I have a question about mounts - in OpenVZ project each container

Re: [openstack-dev] [nova][vmware] Convert to rescue by adding the rescue image and booting from it

On Fri, Jul 11, 2014 at 12:30:19PM +0100, John Garbutt wrote: > On 10 July 2014 16:52, Matthew Booth wrote: > > Currently we create a rescue instance by creating a new VM with the > > original instance's image, then adding the original instance's first > > disk to it, and booting. This means we ha

Re: [openstack-dev] [Containers] Nova virt driver requirements

On Fri, Jul 11, 2014 at 09:53:47AM -0400, Eric Windisch wrote: > > > > > > > Actually, there's a hidden assumption here that makes this statement not > > > necessarily correct for containers. You're assuming the container has > > > to have raw access to the device it's mounting. For hypervisors,

Re: [openstack-dev] Python 2.6 being dropped in K? What does that entail?

On Fri, Jul 11, 2014 at 08:45:07AM -0500, Matt Riedemann wrote: > I'm hearing that python 2.6 will no longer be support in the K release but > not sure if there is an official statement about that somewhere (wiki?). > > I realize this means turning off the 2.6 unit test jobs, but what other > runt

Re: [openstack-dev] [nova][vmware] Convert to rescue by adding the rescue image and booting from it

On Mon, Jul 14, 2014 at 10:48:17AM +0100, Matthew Booth wrote: > > That's interesting. I didn't realise that other drivers had the same > limitations. Does anybody understand the original thinking which lead to > this design? The single VM approach seems intuitively correct to me, so > presumably

Re: [openstack-dev] [nova][all] Old review expiration

On Mon, Jul 14, 2014 at 11:01:17AM -0500, Kevin L. Mitchell wrote: > On Sat, 2014-07-12 at 12:46 -0400, Jay Pipes wrote: > > > Given that we have so many old reviews hanging around on nova (and > > > probably other projects), should we consider setting something like that > > > back up? With nova,

Re: [openstack-dev] [specs] how to continue spec discussion

On Wed, Jul 16, 2014 at 11:57:33AM +, Tim Bell wrote: > As we approach Juno-3, a number of specs have been correctly marked > as abandoned since they are not expected to be ready in time for the > release. > > Is there a mechanism to keep these specs open for discussion even > though there is

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Wed, Jul 16, 2014 at 04:15:40PM +0200, Sean Dague wrote: > Recently the main gate updated from Ubuntu 12.04 to 14.04, and in doing > so we started executing the livesnapshot code in the nova libvirt > driver. Which fails about 20% of the time in the gate, as we're bringing > computes up and down

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Wed, Jul 16, 2014 at 08:12:47AM -0700, Clark Boylan wrote: > On Wed, Jul 16, 2014 at 7:50 AM, Daniel P. Berrange > wrote: > > On Wed, Jul 16, 2014 at 04:15:40PM +0200, Sean Dague wrote: > >> Recently the main gate updated from Ubuntu 12.04 to 14.04, and in doing > &g

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Wed, Jul 16, 2014 at 08:29:26AM -0700, Dan Smith wrote: > >> Based on these experiences, libvirt version differences seem to be as > >> substantial as major hypervisor differences. > > > > I think that is a pretty dubious conclusion to draw from just a > > couple of bugs. The reason they really

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Thu, Jul 17, 2014 at 08:46:12AM +1000, Michael Still wrote: > Top posting to the original email because I want this to stand out... > > I've added this to the agenda for the nova mid cycle meetup, I think > most of the contributors to this thread will be there. So, if we can > nail this down he

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Wed, Jul 16, 2014 at 12:38:44PM -0600, Chris Friesen wrote: > On 07/16/2014 11:59 AM, Monty Taylor wrote: > >On 07/16/2014 07:27 PM, Vishvananda Ishaya wrote: > > >>This is a really good point. As someone who has to deal with packaging > >>issues constantly, it is odd to me that libvirt is one

Re: [openstack-dev] [specs] how to continue spec discussion

On Wed, Jul 16, 2014 at 03:30:56PM +0100, John Garbutt wrote: > My intention was that once the specific project is open for K specs, > people will restore their original patch set, and move the spec to the > K directory, thus keeping all the history. > > For Nova, the open reviews, with a -2, are

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Thu, Jul 17, 2014 at 10:59:27AM +0200, Sean Dague wrote: > We've talked about the 'CI the world plan' for a while, which this would > be part of. That's a ton of work that no one is signed up for. > > But more importantly setting up and running the tests is < 10% of the > time cost. Triage and

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Wed, Jul 16, 2014 at 09:44:55AM -0700, Johannes Erdfelt wrote: > On Wed, Jul 16, 2014, Mark McLoughlin wrote: > > No, there are features or code paths of the libvirt 1.2.5+ driver that > > aren't as well tested as the "class A" designation implies. And we have > > a proposal to make sure these

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Thu, Jul 17, 2014 at 12:13:13PM -0700, Johannes Erdfelt wrote: > On Thu, Jul 17, 2014, Russell Bryant wrote: > > On 07/17/2014 02:31 PM, Johannes Erdfelt wrote: > > > It kind of helps. It's still implicit in that you need to look at what > > > features are enabled at what version and determine

Re: [openstack-dev] [gate] Automatic elastic rechecks

On Fri, Jul 18, 2014 at 09:06:45AM -0500, Matt Riedemann wrote: > > > On 7/17/2014 9:01 AM, Matthew Booth wrote: > >Elastic recheck is a great tool. It leaves me messages like this: > > > >=== > >I noticed jenkins failed, I think you hit bug(s): > > > >check-devstack-dsvm-cells: https://bugs.laun

Re: [openstack-dev] Virtio-scsi settings nova-specs exception

On Mon, Jul 21, 2014 at 10:21:20AM +1000, Michael Still wrote: > I just want to check my understanding -- it seems to me that this > depends on a feature that's very new to libvirt (merged there 22 May > 2014). Is that right? > > http://libvirt.org/git/?p=libvirt.git;a=commit;h=d950494129513558a30

Re: [openstack-dev] [nova] Configuring libivrt VIF driver

On Wed, Jul 23, 2014 at 07:38:05PM +0300, Itzik Brown wrote: > Hi, > > I see that the option to specify vif_driver in nova.conf for libvirt is > deprecated for Juno release. Hmm, that is not right. There's no intention to remove the vif_driver parameter itself. We were supposed to merely deprecat

Re: [openstack-dev] [nova] threading in nova (greenthreads, OS threads, etc.)

On Wed, Jul 23, 2014 at 10:41:06AM -0600, Chris Friesen wrote: > > Hi all, > > I was wondering if someone could point me to a doc describing the threading > model for nova. > > I know that we use greenthreads to map multiple threads of execution onto a > single native OS thread. And the python

Re: [openstack-dev] [nova] Configuring libivrt VIF driver

On Wed, Jul 23, 2014 at 09:53:55AM -0700, Dan Smith wrote: > > Hmm, that is not right. There's no intention to remove the vif_driver > > parameter itself. We were supposed to merely deprecate the various > > legacy VIF driver implementations in Nova, not remove the ability > > to use 3rd party ones

Re: [openstack-dev] [nova] Configuring libivrt VIF driver

On Wed, Jul 23, 2014 at 10:09:37AM -0700, Dan Smith wrote: > > I don't see an issue with allowing people to configure 3rd party impl > > for the VIF driver, provided we don't claim that the VIF driver API > > contract is stable, same way we don't claim virt driver API is stable. > > It lets users h

Re: [openstack-dev] [Nova][Spec freeze exception] Controlled shutdown of GuestOS

On Wed, Jul 23, 2014 at 06:08:52PM +, Day, Phil wrote: > Hi Folks, > > I'd like to propose the following as an exception to the spec freeze, on the > basis that it addresses a potential data corruption issues in the Guest. > > https://review.openstack.org/#/c/89650 > > We were pretty close

Re: [openstack-dev] [nova] Configuring libivrt VIF driver

On Wed, Jul 23, 2014 at 10:52:54AM -0700, Dan Smith wrote: > > If we're going to do that, then we should be consistent. eg there is > > a volume_drivers parameter that serves the same purpose as > > vif_driver > > There are lots of them. We've had a bit of a background task running to > remove the

Re: [openstack-dev] vhost-scsi support in Nova

On Wed, Jul 23, 2014 at 10:32:44PM -0700, Nicholas A. Bellinger wrote: > *) vhost-scsi doesn't support migration > > Since it's initial merge in QEMU v1.5, vhost-scsi has a migration blocker > set. This is primarily due to requiring some external orchestration in > order to setup the necessary vh

Re: [openstack-dev] Thoughts on the patch test failure rate and moving forward

On Wed, Jul 23, 2014 at 02:39:47PM -0700, James E. Blair wrote: > ==Future changes== > ===Fixing Faster=== > > We introduce bugs to OpenStack at some constant rate, which piles up > over time. Our systems currently treat all changes as equally risky and > important to the health of the system, w

Re: [openstack-dev] [gate] Automatic elastic rechecks

On Thu, Jul 24, 2014 at 04:31:05PM +, Jeremy Stanley wrote: > On 2014-07-18 15:09:34 +0100 (+0100), Daniel P. Berrange wrote: > [...] > > If there were multiple failures and only some were identified, it would > > be reasonable to *not* automatically recheck. > [...] >

Re: [openstack-dev] Thoughts on the patch test failure rate and moving forward

On Thu, Jul 24, 2014 at 04:01:39PM -0400, Sean Dague wrote: > On 07/24/2014 12:40 PM, Daniel P. Berrange wrote: > > On Wed, Jul 23, 2014 at 02:39:47PM -0700, James E. Blair wrote: > > > >> ==Future changes== > > > >> ===Fixing Faster=== > >> >

Re: [openstack-dev] vhost-scsi support in Nova

On Fri, Jul 25, 2014 at 01:18:33AM -0700, Nicholas A. Bellinger wrote: > On Thu, 2014-07-24 at 11:06 +0100, Daniel P. Berrange wrote: > > On Wed, Jul 23, 2014 at 10:32:44PM -0700, Nicholas A. Bellinger wrote: > > > *) vhost-scsi doesn't support migration > > > &

Re: [openstack-dev] Virtio-scsi settings nova-specs exception

On Wed, Jul 23, 2014 at 09:09:52AM +1000, Michael Still wrote: > Ok, I am going to take Daniel and Dan's comments as agreement that > this spec freeze exception should go ahead, so the exception is > approved. The exception is in the form of another week to get the spec > merged, so quick iteration

Re: [openstack-dev] [infra] "recheck no bug" and comment

On Fri, Jul 25, 2014 at 06:38:29AM -0400, Sean Dague wrote: > On 07/25/2014 01:18 AM, Ian Wienand wrote: > > On 07/16/2014 11:15 PM, Alexis Lee wrote: > >> What do you think about allowing some text after the words "recheck no > >> bug"? > > > > I think this is a good idea; I am often away from a

Re: [openstack-dev] [infra] "recheck no bug" and comment

On Fri, Jul 25, 2014 at 07:09:56AM -0400, Sean Dague wrote: > On 07/25/2014 06:53 AM, Daniel P. Berrange wrote: > > On Fri, Jul 25, 2014 at 06:38:29AM -0400, Sean Dague wrote: > >> On 07/25/2014 01:18 AM, Ian Wienand wrote: > >>> On 07/16/2014 11:15 PM, Alexis Lee w

Re: [openstack-dev] [infra] "recheck no bug" and comment

On Fri, Jul 25, 2014 at 07:35:52AM -0400, Sean Dague wrote: > On 07/25/2014 07:17 AM, Daniel P. Berrange wrote: > > On Fri, Jul 25, 2014 at 07:09:56AM -0400, Sean Dague wrote: > >> On 07/25/2014 06:53 AM, Daniel P. Berrange wrote: > >>> On Fri, Jul 25, 2014 at 06:3

Re: [openstack-dev] Thoughts on the patch test failure rate and moving forward

On Mon, Jul 28, 2014 at 02:28:56PM +0200, Thierry Carrez wrote: > James E. Blair wrote: > > [...] > > Most of these bugs are not failures of the test system; they are real > > bugs. Many of them have even been in OpenStack for a long time, but are > > only becoming visible now due to improvements

Re: [openstack-dev] [Nova] Boot from ISO feature status

On Mon, Jul 28, 2014 at 09:30:24AM -0700, Vishvananda Ishaya wrote: > I think we should discuss adding/changing this functionality. I have had > many new users assume that booting from an iso image would give them a > root drive which they could snapshot. I was hoping that the new block > device ma

[openstack-dev] [nova] stable branches & failure to handle review backlog

Looking at the current review backlog I think that we have to seriously question whether our stable branch review process in Nova is working to an acceptable level On Havana - 43 patches pending - 19 patches with a single +2 - 1 patch with a -1 - 0 patches wit a -2 - Stalest waiting 111

Re: [openstack-dev] [nova] stable branches & failure to handle review backlog

On Tue, Jul 29, 2014 at 02:04:42PM +0200, Thierry Carrez wrote: > Ihar Hrachyshka a écrit : > At the dawn of time there were no OpenStack stable branches, each > distribution was maintaining its own stable branches, duplicating the > backporting work. At some point it was suggested (mostly by RedHa

Re: [openstack-dev] [nova] stable branches & failure to handle review backlog

On Tue, Jul 29, 2014 at 08:30:09AM -0700, Jay Pipes wrote: > On 07/29/2014 06:13 AM, Daniel P. Berrange wrote: > >On Tue, Jul 29, 2014 at 02:04:42PM +0200, Thierry Carrez wrote: > >>Ihar Hrachyshka a écrit : > >>At the dawn of time there were no OpenStack stable branches

Re: [openstack-dev] [nova] bug discussion at mid cycle meet up

On Tue, Jul 29, 2014 at 02:48:12PM -0400, Russell Bryant wrote: > On 07/29/2014 11:43 AM, Tracy Jones wrote: > > 3. We have bugs that are really not bugs but features, or performance > > issues. They really should be a BP not a bug, but we don’t want these > > things to fall off the radar so they

Re: [openstack-dev] [nova] stable branches & failure to handle review backlog

On Wed, Jul 30, 2014 at 11:16:00AM +0200, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 29/07/14 18:12, Daniel P. Berrange wrote: > > On Tue, Jul 29, 2014 at 08:30:09AM -0700, Jay Pipes wrote: > >> On 07/29/2014 06:13 AM, Daniel P. B

Re: [openstack-dev] [ALL] Removing the tox==1.6.1 pin

On Fri, Jul 25, 2014 at 02:38:49PM -0700, Clark Boylan wrote: > Hello, > > The recent release of tox 1.7.2 has fixed the {posargs} interpolation > issues we had with newer tox which forced us to be pinned to tox==1.6.1. > Before we can remove the pin and start telling people to use latest tox > we

Re: [openstack-dev] [ALL] Removing the tox==1.6.1 pin

On Fri, Jul 25, 2014 at 02:38:49PM -0700, Clark Boylan wrote: > New tox sets a random PYTHONHASHSEED value by default. Arguably this is > a good thing as it forces you to write code that handles unknown hash > seeds, but unfortunately many projects' unittests don't currently deal > with this very w

Re: [openstack-dev] [oslo.messaging][infra] Adding support for AMQP 1.0 Messaging to Oslo.Messaging and infra/config

On Wed, Jul 30, 2014 at 08:54:01AM -0400, Ken Giusti wrote: > Greetings, > > Apologies for the cross-post: this should be of interest to both infra > and olso.messaging developers. > > The blueprint [0] that adds support for version 1.0 of the AMQP messaging > protocol is blocked due to CI test f

Re: [openstack-dev] [nova] so what do i do about libvirt-python if i'm on precise?

On Wed, Jul 30, 2014 at 06:39:56AM -0700, Matt Riedemann wrote: > This change: > > https://review.openstack.org/#/c/105501/ > > Tries to pull in libvirt-python >= 1.2.5 for testing. > > I'm on Ubuntu Precise for development which has libvirt 0.9.8. > > The latest libvirt-python appears to requi

Re: [openstack-dev] [nova][libvirt] Should file injection work for boot from volume images?

On Wed, Sep 25, 2013 at 12:02:03PM +0200, Thierry Carrez wrote: > Christopher Yeoh wrote: > > On Mon, Sep 23, 2013 at 10:56 PM, Russell Bryant > > wrote: > > I agree with Monty and Thierry that ideally file injection should DIAF > > everywhere. On that note, hav

Re: [openstack-dev] [Nova] [Libvirt] Virtio-Serial support for Nova libvirt driver

On Thu, Sep 26, 2013 at 03:05:16AM +, P Balaji-B37839 wrote: > Hi Ravi, > > We did this as part of PoC few months back. > > Daniel can give us more comments on this as he is the lead for Libvirt > support in Nova. Just adding the ability to expose virtio-serial devices to the guest doesn't d

Re: [openstack-dev] Nova Migrate/Resize Libvirt Methods

On Fri, Sep 27, 2013 at 02:11:36PM -0400, Solly Ross wrote: > Hello Fellow OpenStackers, > > I was working on a bug (https://bugzilla.redhat.com/show_bug.cgi?id=975014) > involving the Nova resize functionality in the libvirt driver. So, it > turns out that the bug is caused by nova code trying t

Re: [openstack-dev] [Nova] [Libvirt] Virtio-Serial support for Nova libvirt driver

On Mon, Sep 30, 2013 at 08:32:51AM +, P Balaji-B37839 wrote: > Hi Daniel, > > Thanks for comments and examples. > > As you already know that for any application running on Host platform > can communicate with Guest through Virtio-Serial device. What we are > looking at is the security provide

Re: [openstack-dev] [Nova] [Libvirt] Virtio-Serial support for Nova libvirt driver

On Mon, Sep 30, 2013 at 08:59:47AM +, P Balaji-B37839 wrote: > On Mon, Sep 30, 2013 at 08:32:51AM +, P Balaji-B37839 wrote: > > Hi Daniel, > > > > Thanks for comments and examples. > > > > As you already know that for any application running on Host platform > > can communicate with Gues

Re: [openstack-dev] [Nova] [Libvirt] Virtio-Serial support for Nova libvirt driver

On Mon, Sep 30, 2013 at 11:31:58AM +, P Balaji-B37839 wrote: > > > > Hi Daniel, > > > > > > > > Thanks for comments and examples. > > > > > > > > As you already know that for any application running on Host > > > > platform can communicate with Guest through Virtio-Serial device. > > > > What w

Re: [openstack-dev] [Nova] [Libvirt] Virtio-Serial support for Nova libvirt driver

On Mon, Sep 30, 2013 at 09:46:02AM -0700, Ravi Chunduru wrote: > Let me present an use case. > Today Nova enables to launch guests of different types. For real > deployments we would need appliances from various vendors to run as > instances. Appliances can be Loadbalancer, Firewall, IPsec, Route

Re: [openstack-dev] [Nova] [Libvirt] Virtio-Serial support for Nova libvirt driver

On Mon, Sep 30, 2013 at 02:25:30PM -0700, Ravi Chunduru wrote: > Alessandro, > I agree with you. I created a Blueprint. Let us collaborate and achieve > this on all types of hypervisors. > > All, > > Here is the link for the BP as discussed. > https://blueprints.launchpad.net/nova/+spec/applianc

Re: [openstack-dev] [Nova] [Libvirt] Virtio-Serial support for Nova libvirt driver

On Wed, Oct 02, 2013 at 11:07:23AM -0700, Ravi Chunduru wrote: > Hi Daniel, > I will modify the blueprint as per your suggestions. Actually, we can use > state_path in nova.conf if set or the default location. This set of config vars: - Enable unix channels - No of Unix Channels - Target

Re: [openstack-dev] How does the libvirt domain XML get created?

On Tue, Oct 15, 2013 at 11:07:38PM -0500, Clark Laughlin wrote: > > I can see in config.py where VNC gets added (the element), > but I can't find any place where a element gets added. In > fact, I've grepped the entire nova tree for "cirrus" or "video" and > can only find it here: It is added

Re: [openstack-dev] Hyper-V meeting Minutes

Alessandro, please fix your email program so that it does not send HTML email to the list, and correctly quotes text you are replying to with '> '. Your reply comes out looking like this which makes it impossible to see who wrote what: On Wed, Oct 16, 2013 at 10:42:45AM +, Alessandro Pilotti w

Re: [openstack-dev] Hyper-V meeting Minutes

On Wed, Oct 16, 2013 at 12:59:26PM +, Alessandro Pilotti wrote: > > When somebody (especially a core reviewer) puts a -1 and a new patch is > committed to address it, > I noticed that other reviewers wait for the guy that put the -1 to say > something before +1/+2 it. I think that depends

Re: [openstack-dev] Hyper-V meeting Minutes

On Wed, Oct 16, 2013 at 06:51:50AM -0700, Dan Smith wrote: > > +1 - I think we really want to have a strong preference for a stable > > api if we start separating parts out > > So, as someone who is about to break the driver API all to hell over the > next six months (er, I mean, make some signif

Re: [openstack-dev] Gerrit tools

On Sun, Oct 20, 2013 at 05:01:23AM +, Joshua Harlow wrote: > I created some gerrit tools that I think others might find useful. > > https://github.com/harlowja/gerrit_view > > The neat one there is a curses based real time gerrit review receiver > that uses a similar mechanism as the gerrit i

Re: [openstack-dev] Gerrit tools

On Wed, Oct 23, 2013 at 03:05:32PM +, James E. Blair wrote: > "Daniel P. Berrange" writes: > > > Actually, from my POV, the neat one there is the qgerrit script - I had > > no idea you could query this info so easily. > > FYI the query syntax for SSH and th

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

On Wed, Oct 30, 2013 at 10:35:59AM +, Joe Gordon wrote: > On Wed, Oct 30, 2013 at 8:31 AM, Alex Glikson wrote: > > > Russell Bryant wrote on 30/10/2013 10:20:34 AM: > > > > > On 10/30/2013 03:13 AM, Alex Glikson wrote: > > > > Maybe a more appropriate approach could be to have a tool/script

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

On Wed, Oct 30, 2013 at 04:20:34AM -0400, Russell Bryant wrote: > On 10/30/2013 03:13 AM, Alex Glikson wrote: > > Maybe a more appropriate approach could be to have a tool/script that > > does it, as a one time thing. > > For example, it could make sense in a scenario when Nova DB gets lost or > >

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

On Wed, Oct 30, 2013 at 11:51:01AM -0400, Mike Spreitzer wrote: > Swapnil Kulkarni wrote on 10/30/2013 > 02:36:37 AM: > > > I had a discussion with russellb regarding this for yesterday, I > > would like to discuss this with the team regarding the blueprint > > mentioned in subject. > > > >

Re: [openstack-dev] [nova] changing old migrations is verboten

On Fri, Nov 01, 2013 at 07:20:19AM -0400, Sean Dague wrote: > On 11/01/2013 06:27 AM, John Garbutt wrote: > >On 31 October 2013 16:57, Johannes Erdfelt wrote: > >>On Thu, Oct 31, 2013, Sean Dague wrote: > >>>So there is a series of patches starting with - > >>>https://review.openstack.org/#/c/534

Re: [openstack-dev] Bad review patterns

On Thu, Nov 07, 2013 at 12:21:38AM +, Day, Phil wrote: > > > > Leaving a mark. > > === > > > > You review a change and see that it is mostly fine, but you feel that since > > you > > did so much work reviewing it, you should at least find > > *something* wrong. So you find some n

Re: [openstack-dev] [Nova] Enabling libvirt feature: pass-through of QEMU command line args

On Mon, Nov 11, 2013 at 01:43:59PM +0530, Rahul M R wrote: > Hi all, > > I'm new to this mailing list :) > > I am currently working on the Snabbswitch project < > https://github.com/SnabbCo/snabbswitch/wiki >. We are developing an OpenStack > Neutron plugin (targeting Icehouse release). Snabbsw

Re: [openstack-dev] Proposal to recognize indirect contributions to our code base

On Mon, Nov 11, 2013 at 12:27:35PM -0500, Russell Bryant wrote: > On 11/11/2013 12:09 PM, Anne Gentle wrote: > > What about something with attribution in the docs for the feature? Can > > we play around with that a while? Attribution is going to have to be > > incorporated better into the docs for

Re: [openstack-dev] Proposal to recognize indirect contributions to our code base

On Mon, Nov 11, 2013 at 03:20:20PM +0100, Nicolas Barcet wrote: > Dear TC members, > > Our companies are actively encouraging our respective customers to have the > patches they mission us to make be contributed back upstream. In order to > encourage this behavior from them and others, it would b

Re: [openstack-dev] [Nova] Recent change breaks manual control of service enabled / disabled status - suggest it is backed out and re-worked

On Mon, Nov 11, 2013 at 11:34:10AM +, Day, Phil wrote: > Hi Folks, > > I'd like to get some eyes on a bug I just filed: > https://bugs.launchpad.net/nova/+bug/1250049 > > A recent change (https://review.openstack.org/#/c/52189/9 ) introduced the > automatic disable / re-enable of nova-comp

<    1   2   3   4   5   6   7   8   9   >