Re: [openstack-dev] [TripleO][Nova][Neutron] multiple hypervisors on one compute host - neutron agent and compute hostnames

On Tue, Aug 5, 2014 at 4:17 PM, Robert Collins wrote: > Hi! > > James has run into an issue implementing the multi-hypervisor spec > ( > http://git.openstack.org/cgit/openstack/tripleo-specs/tree/specs/juno/tripleo-juno-deploy-cloud-hypervisor-type.rst > ) > which we're hoping to use to reduce in

Re: [openstack-dev] [qa][ceilometer] swapping the roles of mongodb and sqlalchemy for ceilometer in Tempest

On Sat, Aug 9, 2014 at 6:29 AM, Eoghan Glynn wrote: > > > > > Hi Folks, > > > > > > Dina Belova has recently landed some infra patches[1,2] to create > > > an experimental mongodb-based Tempest job. This effectively just > > > overrides the ceilometer storage backend config so that mongodb > > >

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

On Sun, Aug 10, 2014 at 11:59 PM, Mark McLoughlin wrote: > On Fri, 2014-08-08 at 09:06 -0400, Russell Bryant wrote: > > On 08/07/2014 08:06 PM, Michael Still wrote: > > > It seems to me that the tension here is that there are groups who > > > would really like to use features in newer libvirts th

Re: [openstack-dev] [qa][ceilometer] swapping the roles of mongodb and sqlalchemy for ceilometer in Tempest

On Mon, Aug 11, 2014 at 3:07 PM, Eoghan Glynn wrote: > > > > Ignoring the question of is it ok to say: 'to run ceilometer in any sort > of > > non-trivial deployment you must manager yet another underlying service, > > mongodb' I would prefer not adding an addition gate variant to all > projects.

Re: [openstack-dev] [qa][ceilometer] swapping the roles of mongodb and sqlalchemy for ceilometer in Tempest

On Mon, Aug 11, 2014 at 3:53 PM, Devananda van der Veen < devananda@gmail.com> wrote: > On Mon, Aug 11, 2014 at 3:27 PM, Joe Gordon wrote: > > > > > > > > On Mon, Aug 11, 2014 at 3:07 PM, Eoghan Glynn wrote: > >> > >> > >> > &g

Re: [openstack-dev] [all] The future of the integrated release

On Fri, Aug 8, 2014 at 6:58 AM, Kyle Mestery wrote: > On Thu, Aug 7, 2014 at 1:26 PM, Joe Gordon wrote: > > > > > > > > On Tue, Aug 5, 2014 at 9:03 AM, Thierry Carrez > > wrote: > >> > >> Hi everyone, > >> > >> With the inc

Re: [openstack-dev] [nova] Retrospective veto revert policy

On Tue, Aug 12, 2014 at 8:46 AM, Jay Pipes wrote: > On 08/12/2014 10:56 AM, Mark McLoughlin wrote: > >> Hey >> >> (Terrible name for a policy, I know) >> >> From the version_cap saga here: >> >>https://review.openstack.org/110754 >> >> I think we need a better understanding of how to approac

Re: [openstack-dev] [all] The future of the integrated release

On Tue, Aug 12, 2014 at 11:08 AM, Doug Hellmann wrote: > > On Aug 12, 2014, at 1:44 PM, Dolph Mathews > wrote: > > > On Tue, Aug 12, 2014 at 12:30 AM, Joe Gordon > wrote: > >> >> >> >> On Fri, Aug 8, 2014 at 6:58 AM, Kyle Mestery wrote: &

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

On Tue, Aug 12, 2014 at 12:23 AM, Mark McLoughlin wrote: > On Mon, 2014-08-11 at 15:25 -0700, Joe Gordon wrote: > > > > > > > > On Sun, Aug 10, 2014 at 11:59 PM, Mark McLoughlin > > wrote: > > On Fri, 2014-08-08 at 09:06 -0400, Russell Bryant wrot

Re: [openstack-dev] [all] The future of the integrated release

On Wed, Aug 13, 2014 at 2:01 AM, Nikola Đipanov wrote: > On 08/13/2014 04:05 AM, Michael Still wrote: > > On Wed, Aug 13, 2014 at 4:26 AM, Eoghan Glynn wrote: > >> > >>> It seems like this is exactly what the slots give us, though. The core > review > >>> team picks a number of slots indicating

Re: [openstack-dev] [all] The future of the integrated release

On Wed, Aug 13, 2014 at 5:13 AM, Mark McLoughlin wrote: > On Thu, 2014-08-07 at 09:30 -0400, Sean Dague wrote: > > > While I definitely think re-balancing our quality responsibilities back > > into the projects will provide an overall better release, I think it's > > going to take a long time bef

Re: [openstack-dev] Which program for Rally

On Wed, Aug 13, 2014 at 2:48 PM, Duncan Thomas wrote: > On 13 August 2014 13:57, Matthew Treinish wrote: > > On Tue, Aug 12, 2014 at 01:45:17AM +0400, Boris Pavlovic wrote: > >> Keystone, Glance, Cinder, Neutron and Heat are running rally performance > >> jobs, that can be used for performance t

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Wed, Aug 13, 2014 at 8:31 PM, Michael Still wrote: > On Thu, Aug 14, 2014 at 1:24 PM, Jay Pipes wrote: > > > Just wanted to quickly weigh in with my thoughts on this important > topic. I > > very much valued the face-to-face interaction that came from the > mid-cycle > > meetup in Beaverton (

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Thu, Aug 14, 2014 at 1:47 AM, Daniel P. Berrange wrote: > On Thu, Aug 14, 2014 at 09:24:36AM +1000, Michael Still wrote: > > On Thu, Aug 14, 2014 at 3:09 AM, Dan Smith wrote: > > >> I'm not questioning the value of f2f - I'm questioning the idea of > > >> doing f2f meetings sooo many times a

Re: [openstack-dev] [all] The future of the integrated release

On Wed, Aug 13, 2014 at 12:24 PM, Doug Hellmann wrote: > > On Aug 13, 2014, at 3:05 PM, Eoghan Glynn wrote: > > > > >>> At the end of the day, that's probably going to mean saying No to more > >>> things. Everytime I turn around everyone wants the TC to say No to > >>> things, just not to their

Re: [openstack-dev] Enabling silent Docker tests for Nova?

Running a silent check on > >> changes to Nova is the first step in establishing that history. > >> > >> Joe Gordon suggests we need a spec to bring the driver back into Nova. > >> Besides the fact that specs are closed and there is no intention of > >>

Re: [openstack-dev] [all] The future of the integrated release

On Fri, Aug 15, 2014 at 8:17 AM, Sandy Walsh wrote: > On 8/14/2014 6:42 PM, Doug Hellmann wrote: > > > On Aug 14, 2014, at 4:41 PM, Joe Gordon wrote: > > > > > On Wed, Aug 13, 2014 at 12:24 PM, Doug Hellmann > wrote: > >> >> On Aug 13, 2014, at 3:

Re: [openstack-dev] [all] The future of the integrated release

On Thu, Aug 14, 2014 at 4:02 PM, Eoghan Glynn wrote: > > > > Additional cross-project resources can be ponied up by the large > > > contributor companies, and existing cross-project resources are not > > > necessarily divertable on command. > > > > Sure additional cross-project resources can and

Re: [openstack-dev] [all] The future of the integrated release

On Thu, Aug 14, 2014 at 4:02 PM, Eoghan Glynn wrote: > > > > Additional cross-project resources can be ponied up by the large > > > contributor companies, and existing cross-project resources are not > > > necessarily divertable on command. > > > > Sure additional cross-project resources can and

Re: [openstack-dev] [specs] script to help with spec reviews to convert them in html or pdf

On Aug 16, 2014 10:37 AM, "Jeremy Stanley" wrote: > > On 2014-08-16 04:01:25 +0200 (+0200), Chmouel Boudjnah wrote: > > If like me you find it difficult to read a large text file like > > the rst specs inside gerrit diff interface viewer, I have created > > a script that gets rst files in a review

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Mon, Aug 18, 2014 at 3:18 AM, Thierry Carrez wrote: > Doug Hellmann wrote: > > On Aug 13, 2014, at 4:42 PM, Russell Bryant wrote: > >> Let me try to say it another way. You seemed to say that it wasn't much > >> to ask given the rate at which things happen in OpenStack. I would > >> argue t

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Mon, Aug 18, 2014 at 8:18 AM, Russell Bryant wrote: > On 08/18/2014 06:18 AM, Thierry Carrez wrote: > > Doug Hellmann wrote: > >> On Aug 13, 2014, at 4:42 PM, Russell Bryant wrote: > >>> Let me try to say it another way. You seemed to say that it wasn't > much > >>> to ask given the rate at

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Mon, Aug 18, 2014 at 5:22 AM, Daniel P. Berrange wrote: > On Mon, Aug 18, 2014 at 12:18:16PM +0200, Thierry Carrez wrote: > > Doug Hellmann wrote: > > > On Aug 13, 2014, at 4:42 PM, Russell Bryant > wrote: > > >> Let me try to say it another way. You seemed to say that it wasn't > much > > >

Re: [openstack-dev] [All] LOG.warning/LOG.warn

On Sun, Aug 17, 2014 at 9:24 AM, Jay Bryant wrote: > +2 > > I prefer the LOG.warning format and support that given the documentation > you shared. > > If there is agreement I would create a hacking check. > I think a better approach is to just not care which i used here. IMHO mixing up LOG.warn

Re: [openstack-dev] [Nova][VMware] Minesweeper status

On Tue, Aug 19, 2014 at 4:22 AM, Gary Kotton wrote: > Hi, > Minesweeper is back up and running – this is now called “Vmware NSX CI”. > A patch for the deprecation of the ESX driver resulted in endless > Minesweeper failures (https://review.openstack.org/#/c/108854/). These > were resolved by a n

Re: [openstack-dev] [TripleO] Specs and approvals

On Tue, Aug 19, 2014 at 8:47 AM, Daniel P. Berrange wrote: > On Tue, Aug 19, 2014 at 09:31:48PM +1200, Robert Collins wrote: > > Hey everybody - https://wiki.openstack.org/wiki/TripleO/SpecReviews > > seems pretty sane as we discussed at the last TripleO IRC meeting. > > > > I'd like to propose t

Re: [openstack-dev] [TripleO][Nova] Specs and approvals

On Tue, Aug 19, 2014 at 8:23 AM, Russell Bryant wrote: > On 08/19/2014 05:31 AM, Robert Collins wrote: > > Hey everybody - https://wiki.openstack.org/wiki/TripleO/SpecReviews > > seems pretty sane as we discussed at the last TripleO IRC meeting. > > > > I'd like to propose that we adopt it with t

Re: [openstack-dev] [Nova] Scheduler split wrt Extensible Resource Tracking

On Aug 19, 2014 10:45 AM, "Day, Phil" wrote: > > > -Original Message- > > From: Nikola Đipanov [mailto:ndipa...@redhat.com] > > Sent: 19 August 2014 17:50 > > To: openstack-dev@lists.openstack.org > > Subject: Re: [openstack-dev] [Nova] Scheduler split wrt Extensible Resource > > Tracking

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Aug 20, 2014 10:56 AM, "John Garbutt" wrote: > > On 18 August 2014 11:18, Thierry Carrez wrote: > > Doug Hellmann wrote: > >> On Aug 13, 2014, at 4:42 PM, Russell Bryant wrote: > >>> Let me try to say it another way. You seemed to say that it wasn't much > >>> to ask given the rate at which

Re: [openstack-dev] Adding GateFailureFix tag to commit messages

On Fri, Aug 22, 2014 at 2:11 AM, Daniel P. Berrange wrote: > On Thu, Aug 21, 2014 at 09:02:17AM -0700, Armando M. wrote: > > Hi folks, > > > > According to [1], we have ways to introduce external references to commit > > messages. > > > > These are useful to mark certain patches and their relevan

Re: [openstack-dev] [heat] "heat.conf.sample is not up to date"

On Aug 24, 2014 9:04 AM, "Morgan Fainberg" wrote: > > > > On Sunday, August 24, 2014, Anne Gentle wrote: >> >> I'm following this as well since I have the exact same problem in a docstring patch for heat. >> > > Keystone saw an oddity with the new sample config generator (changing how options are

Re: [openstack-dev] [qa] In-tree functional test vision

On Mon, Aug 4, 2014 at 3:29 AM, Chris Dent wrote: > > In the "Thoughts on the patch test failure rate and moving forward" > thread[1] there's discussion of moving some of the burden for > functional testing to the individual projects. This seems like a good > idea to me, but also seems like it co

Re: [openstack-dev] [qa] In-tree functional test vision

On Mon, Aug 25, 2014 at 2:50 PM, Chris Dent wrote: > On Mon, 25 Aug 2014, Joe Gordon wrote: > > [Other stuff snipped, thanks for that, good to have some pointers.] > > > Why can't you run devstack locally? Maybe there are some changes we can >> make so its easier

Re: [openstack-dev] [TripleO] Specs and approvals

On Tue, Aug 19, 2014 at 11:57 AM, James Slagle wrote: > On Tue, Aug 19, 2014 at 1:58 PM, Joe Gordon wrote: > > > > While I cannot speak for the dynamics of the tripleo team, if this were > to > > be adopted in nova I would not +2 any blueprints as I don't think I ca

Re: [openstack-dev] [OpenStack][Nova]May be performance issues of connect_volume in Nova

On Tue, Aug 26, 2014 at 5:36 AM, Wang Shen wrote: > Hi, All > I have done some work to test the performance of LUN scanning, use > "iscsiadm" with "--rescan" like what Nova dose. In my test, a host > connected with a lot of LUNs , more than 1000 LUNs. Because "--rescan" > will cause kernel to sca

Re: [openstack-dev] [all] The future of the integrated release

On Mon, Aug 25, 2014 at 6:36 AM, Sean Dague wrote: > On 08/20/2014 12:37 PM, Zane Bitter wrote: > > On 11/08/14 05:24, Thierry Carrez wrote: > >> So the idea that being (and remaining) in the integrated release should > >> also be judged on technical merit is a slightly different effort. It's > >

Re: [openstack-dev] [all] The future of the integrated release

On Wed, Aug 20, 2014 at 2:25 AM, Eoghan Glynn wrote: > > > > > > Additional cross-project resources can be ponied up by the large > > > > contributor companies, and existing cross-project resources are not > > > > necessarily divertable on command. > > > > > > Sure additional cross-project resour

Re: [openstack-dev] [rally] Introduction to feature request mechanism in Rally

On Tue, Aug 26, 2014 at 5:31 AM, Boris Pavlovic wrote: > Hi stackers, > > > It goes without saying that end users, that are actually using your > tool/project/service, usually don't have enough time to join community, > understand all technical details and road map of project and after that > con

Re: [openstack-dev] [infra] [neutron] [tc] Neutron Incubator workflow

On Wed, Aug 27, 2014 at 12:30 PM, James E. Blair wrote: > Kevin Benton writes: > > > From what I understand, the intended projects for the incubator can't > > operate without neutron because they are just extensions/plugins/drivers. > > I could have phrased that better. What I meant was that th

Re: [openstack-dev] [all] gate debugging

On Thu, Aug 28, 2014 at 10:17 AM, Sean Dague wrote: > On 08/28/2014 12:48 PM, Doug Hellmann wrote: > > > > On Aug 27, 2014, at 5:56 PM, Sean Dague wrote: > > > >> On 08/27/2014 05:27 PM, Doug Hellmann wrote: > >>> > >>> On Aug 27, 2014, at 2:54 PM, Sean Dague wrote: > >>> > Note: thread in

Re: [openstack-dev] [all] gate debugging

On Thu, Aug 28, 2014 at 5:17 AM, Thierry Carrez wrote: > David Kranz wrote: > > On 08/27/2014 03:43 PM, Sean Dague wrote: > >> On 08/27/2014 03:33 PM, David Kranz wrote: > >>> Race conditions are what makes debugging very hard. I think we are in > >>> the process of experimenting with such an ide

Re: [openstack-dev] [nova] Is the BP approval process broken?

On Thu, Aug 28, 2014 at 2:40 AM, Daniel P. Berrange wrote: > On Thu, Aug 28, 2014 at 01:04:57AM +, Dugger, Donald D wrote: > > I'll try and not whine about my pet project but I do think there > > is a problem here. For the Gantt project to split out the scheduler > > there is a crucial BP th

Re: [openstack-dev] [nova] Is the BP approval process broken?

On Thu, Aug 28, 2014 at 2:43 PM, Alan Kavanagh wrote: > I share Donald's points here, I believe what would help is to clearly > describe in the Wiki the process and workflow for the BP approval process > and build in this process how to deal with discrepancies/disagreements and > build timeframes

[openstack-dev] [nova] Kilo Specs Schedule

We just finished discussing when to open up Kilo specs at the nova meeting today [0], and Kilo specs will open right after we cut Juno RC1 (around Sept 25th [1]). Additionally, the spec template will most likely be revised. We still have a huge amount of work to do for Juno and the nova team is mo

Re: [openstack-dev] [nova] Is the BP approval process broken?

On Thu, Aug 28, 2014 at 3:27 PM, Chris Friesen wrote: > On 08/28/2014 04:01 PM, Joe Gordon wrote: > >> >> >> >> On Thu, Aug 28, 2014 at 2:43 PM, Alan Kavanagh >> mailto:alan.kavan...@ericsson.com>> wrote: >> >> I share Donald's

Re: [openstack-dev] [nova] Is the BP approval process broken?

On Aug 29, 2014 10:42 AM, "Dugger, Donald D" wrote: > > Well, I think that there is a sign of a broken (or at least bent) process and that's what I'm trying to expose. Especially given the ongoing conversations over Gantt it seems wrong that ultimately it was rejected due to silence. Maybe rejec

[openstack-dev] Kilo Cycle Goals Exercise

goal of this exercise is to help us see if our individual world views align with the greater community, and to get the ball rolling on a larger discussion of where as a project we should be focusing more time. best, Joe Gordon [0] http://lists.openstack.org/pipermail/openstack-dev/2014-August

Re: [openstack-dev] [infra][qa][neutron] Neutron full job, advanced services, and the integrated gate

On Tue, Aug 26, 2014 at 4:47 PM, Salvatore Orlando wrote: > TL; DR > A few folks are proposing to stop running tests for neutron advanced > services [ie: (lb|vpn|fw)aas] in the integrated gate, and run them only on > the neutron gate. > > Reason: projects like nova are 100% orthogonal to neutron

Re: [openstack-dev] [nova] libvirt version_cap, a postmortem

t; https://review.openstack.org/102643 > > where upgrading to Ubuntu Trusty meant the libvirt version in use in the > gate went from 0.9.8 to 1.2.2, which caused the "live snapshot" code > paths in Nova for the first time, which appeared to be related to some > serious

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

On Wed, Sep 3, 2014 at 2:50 AM, Nikola Đipanov wrote: > On 09/02/2014 09:23 PM, Michael Still wrote: > > On Tue, Sep 2, 2014 at 1:40 PM, Nikola Đipanov > wrote: > >> On 09/02/2014 08:16 PM, Michael Still wrote: > >>> Hi. > >>> > >>> We're soon to hit feature freeze, as discussed in Thierry's rec

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

On Wed, Sep 3, 2014 at 8:57 AM, Solly Ross wrote: > > I will follow up with a more detailed email about what I believe we are > > missing, once the FF settles and I have applied some soothing creme to > > my burnout wounds, but currently my sentiment is: > > > > Contributing features to Nova nowa

Re: [openstack-dev] [Nova] [feature freeze exception] Move to oslo.db

for a feature freeze exception for porting nova to use > >> oslo.db. > >> > >> This change not only removes 3k LOC, but fixes 4 bugs(see commit message > >> for more details) and provides relevant, stable common db code. > >> > >> Main maintain

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

On Thu, Sep 4, 2014 at 2:23 AM, John Garbutt wrote: > Sorry for another top post, but I like how Nikola has pulled this > problem apart, and wanted to respond directly to his response. > > On 3 September 2014 10:50, Nikola Đipanov wrote: > > The reason many features including my own may not make

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

On Thu, Sep 4, 2014 at 3:24 AM, Daniel P. Berrange wrote: > Position statement > == > > Over the past year I've increasingly come to the conclusion that > Nova is heading for (or probably already at) a major crisis. If > steps are not taken to avert this, the project is likely to

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

On Fri, Sep 5, 2014 at 4:05 AM, Nikola Đipanov wrote: > On 09/04/2014 10:25 PM, Solly Ross wrote: > > Anyway, I think it would be useful to have some sort of page where people > > could say "I'm an SME in X, ask me for reviews" and then patch > submitters could go > > and say, "oh, I need an some

Re: [openstack-dev] [Nova][FFE] Feature Freeze exception for juno-slaveification

On Fri, Sep 5, 2014 at 9:11 AM, Mike Wilson wrote: > Hi all, > > I am requesting an exception for the juno-slaveification blueprint. There > is a single outstanding patch [1] which has already been approved before, > but needed to be re-spun due to gate failures which then necessitated a > rebase

[openstack-dev] memory usage in devstack-gate (the oom-killer strikes again)

Hi All, We have recently started seeing assorted memory issues in the gate including the oom-killer [0] and libvirt throwing memory errors [1]. Luckily we run ps and dstat on every devstack run so we have some insight into why we are running out of memory. Based on the output from job taken at ran

Re: [openstack-dev] Kilo Cycle Goals Exercise

On Wed, Sep 3, 2014 at 8:37 AM, Joe Gordon wrote: > As you all know, there has recently been several very active discussions > around how to improve assorted aspects of our development process. One idea > that was brought up is to come up with a list of cycle goals/project > priorit

Re: [openstack-dev] [zaqar] Juno Performance Testing (Round 2)

On Tue, Sep 9, 2014 at 12:19 PM, Kurt Griffiths < kurt.griffi...@rackspace.com> wrote: > Hi folks, > > In this second round of performance testing, I benchmarked the new Redis > driver. I used the same setup and tests as in Round 1 to make it easier to > compare the two drivers. I did not test Red

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 11, 2014 at 2:18 AM, Daniel P. Berrange wrote: > On Thu, Sep 11, 2014 at 09:23:34AM +1000, Michael Still wrote: > > On Thu, Sep 11, 2014 at 8:11 AM, Jay Pipes wrote: > > > > > a) Sorting out the common code is already accounted for in Dan B's > original > > > proposal -- it's a prere

Re: [openstack-dev] [Nova] What's holding nova development back?

On Sep 15, 2014 8:31 PM, "Jay Pipes" wrote: > > On 09/15/2014 08:07 PM, Jeremy Stanley wrote: >> >> On 2014-09-15 17:59:10 -0400 (-0400), Jay Pipes wrote: >> [...] >>> >>> Sometimes it's pretty hard to determine whether something in the >>> E-R check page is due to something in the infra scripts,

Re: [openstack-dev] [zaqar] Juno Performance Testing (Round 2)

hough not graphed), but in the > former case only one “project” was used. > multiple Tenant/Project-IDs > > From: Joe Gordon > Reply-To: OpenStack Dev > Date: Friday, September 12, 2014 at 1:45 PM > To: OpenStack Dev > Subject: Re: [openstack-dev] [zaqar] Juno Performance T

[openstack-dev] [Zaqar] Zaqar and SQS Properties of Distributed Queues

Hi All, My understanding of Zaqar is that it's like SQS. SQS uses distributed queues, which have a few unusual properties [0]: Message Order Amazon SQS makes a best effort to preserve order in messages, but due to the distributed nature of the queue, we cannot guarantee you will receive messages

Re: [openstack-dev] PostgreSQL jobs slow in the gate

Postgres is also logging a lot of errors: http://logs.openstack.org/63/122263/1/check/check-tempest-dsvm-postgres-full/2f27252/logs/postgres.txt.gz On Wed, Sep 17, 2014 at 4:49 PM, Clark Boylan wrote: > Hello, > > Recent sampling of test run times shows that our tempest jobs run > against clouds

Re: [openstack-dev] [Nova] Its time to start identifying release critical bugs

On Tue, Sep 16, 2014 at 2:58 AM, Michael Still wrote: > Hi. > > Is time to start identifying (and working on) release critical bugs in > nova before we ship RC1. > > My initial position is that any critical bug is release critical. > There are currently critical bugs not targeted to rc1, but that

Re: [openstack-dev] [Zaqar] Zaqar and SQS Properties of Distributed Queues

On Thu, Sep 18, 2014 at 9:02 AM, Devananda van der Veen < devananda@gmail.com> wrote: > On Thu, Sep 18, 2014 at 7:55 AM, Flavio Percoco wrote: > > On 09/18/2014 04:24 PM, Clint Byrum wrote: > >> Great job highlighting what our friends over at Amazon are doing. > >> > >> It's clear from these

Re: [openstack-dev] [Zaqar] Zaqar and SQS Properties of Distributed Queues

On Thu, Sep 18, 2014 at 7:45 AM, Flavio Percoco wrote: > On 09/18/2014 04:09 PM, Gordon Sim wrote: > > On 09/18/2014 12:31 PM, Flavio Percoco wrote: > >> On 09/17/2014 10:36 PM, Joe Gordon wrote: > >>> My understanding of Zaqar is that it's like SQS. SQS uses d

[openstack-dev] Top Gate Bugs

ename:"console.html" Title: test_network_basic_ops fails waiting for network to become available Project: Status neutron: In Progress swift: Invalid tempest: Invalid Hits FAILURE: 42 Bug: https://bugs.launchpad.net/bugs/1218391 => message:"Cannot 'createImage'" AND filename:&qu

Re: [openstack-dev] The recent gate performance and how it affects you

Dims, we think https://review.openstack.org/#/c/57509/ will fix 125178 . On Wed, Nov 20, 2013 at 3:58 PM, Davanum Srinivas wrote: > Anita, Joe, > > I need help with adding debug message in: > https://review.openstack.org/#/c/56316/ > > to track down: > Bug: h

Re: [openstack-dev] [openstack][nova][social-apects] Social aspects shouldn't impact on dev process

this BP, but I will properly respond to that tommorow. Also I am not sure what you mean with the subject line. > >> > >> And made patch that makes this work. > >> But only because our BP wasn't approved we got -2 from Joe Gordon. > >> (https://review.openstac

Re: [openstack-dev] [openstack][nova][social-apects] Social aspects shouldn't impact on dev process

moment we don't have any working >> way to purge DB... so admins should make it by hand. >> >> >> And we made this BP (in october) >> https://blueprints.launchpad.net/nova/+spec/db-purge-engine >> >> And made patch that makes this work.

Re: [openstack-dev] [Nova] Proposal to add Matt Riedemann to nova-core

+1 On Fri, Nov 22, 2013 at 2:41 PM, Christopher Yeoh wrote: > > > +1 > > > On Sat, Nov 23, 2013 at 7:23 AM, Russell Bryant wrote: > >> Greetings, >> >> I would like to propose adding Matt Riedemann to the nova-core review >> team. >> >> Matt has been involved with nova for a long time, taking o

Re: [openstack-dev] Gate failures

sent on the go On Nov 23, 2013 9:02 AM, "Davanum Srinivas" wrote: > > Gary, > > There's a blow-by-blow account in this etherpad - > https://etherpad.openstack.org/p/critical-patches-gatecrash-November-2013 > > On Sat, Nov 23, 2013 at 11:12 AM, Gary Kotton wrote: > > Hi, > > To whoever fixed the g

[openstack-dev] Unwedging the gate

e are working on the next steps to prevent this from happening again. The two most immediate changes are: - Doing a better job of triaging gate bugs ( http://lists.openstack.org/pipermail/openstack-dev/2013-November/020048.html ). - In the next few days we will remove '

Re: [openstack-dev] Unwedging the gate

known set of nondeterministic issues down to 0 and keep it > there. > Yes! In fact we are already working towards that. See http://lists.openstack.org/pipermail/openstack-dev/2013-November/020048.html > > -Rob > > On 25 November 2013 18:00, Joe Gordon wrote: > > Hi All, > &g

Re: [openstack-dev] [Nova] Remove ratelimits from nova v3 api

On Mon, Nov 25, 2013 at 4:38 AM, David Hill wrote: > Hi Alex, > >Is removing the ratelimiting code part of the roadmap? I fear that if > it's removed now, it may have to be re-implemented in the future as the > cloud deployments become more mainstream ... Without ratelimit, some evil > users

Re: [openstack-dev] EC2 Filter

On Mon, Nov 25, 2013 at 6:22 AM, Sebastian Porombka < porom...@uni-paderborn.de> wrote: > Hi Folks. > > I stumbled over the lacking of EC2 Api filter support on Openstack and > justinsb¹s (and the other people I forgot to mention here) attempt [1] to > implement this against diabolo. > > I¹m highl

Re: [openstack-dev] [qa] Plan for failing "successful" tempest jobs when new ERRORs appear in logs

On Mon, Nov 18, 2013 at 2:58 PM, David Kranz wrote: > So we are close to being able to start doing this. The current whitelist > is here https://github.com/openstack/tempest/blob/master/etc/ > whitelist.yaml. I have a "find-errors" script that watches for successful > builds and pulls out the non

Re: [openstack-dev] [qa] Plan for failing "successful" tempest jobs when new ERRORs appear in logs

On Mon, Nov 25, 2013 at 11:06 AM, Joe Gordon wrote: > > > > On Mon, Nov 18, 2013 at 2:58 PM, David Kranz wrote: > >> So we are close to being able to start doing this. The current whitelist >> is here https://github.com/openstack/tempest/blob/master/etc/ >> whit

Re: [openstack-dev] [nova] python-novaclient: uses deprecated keyring.backend.$keyring

On Mon, Nov 25, 2013 at 2:48 AM, Thomas Goirand wrote: > On 11/25/2013 03:57 AM, Morgan Fainberg wrote: > > Hi Thomas, > > > > How pressing is this issue? > > It seems it's blocking some python package transition from Sid to > Jessie, and impacting the Gnome guys, so it's quite annoying for Debia

Re: [openstack-dev] Unwedging the gate

On Sun, Nov 24, 2013 at 10:48 PM, Robert Collins wrote: > On 25 November 2013 19:25, Joe Gordon wrote: > > > > > > > > On Sun, Nov 24, 2013 at 9:58 PM, Robert Collins < > robe...@robertcollins.net> > > wrote: > >> > >> I have a

Re: [openstack-dev] [all project] Treating recently seen recheck bugs as critical across the board

On Nov 26, 2013 8:48 AM, "Dolph Mathews" wrote: > > > On Tue, Nov 26, 2013 at 5:23 AM, Thierry Carrez wrote: >> >> Dolph Mathews wrote: >> > On Mon, Nov 25, 2013 at 8:12 PM, Robert Collins >> > mailto:robe...@robertcollins.net>> wrote: >> > >> > So my proposal is that we make it part of the b

Re: [openstack-dev] [Nova] Proposal to re-add Dan Prince to nova-core

On Nov 26, 2013 11:37 AM, "Russell Bryant" wrote: > > Greetings, > > I would like to propose that we re-add Dan Prince to the nova-core > review team. > > Dan Prince has been involved with Nova since early in OpenStack's > history (Bexar timeframe). He was a member of the nova-core review team >

Re: [openstack-dev] EC2 Filter

: porom...@uni-paderborn.de > Tel.: 05251/60-5999 > Fax: 05251/60-48-5999 > Raum: N5.314 > > > Q: Why is this email five sentences or less? > A: http://five.sentenc.es > > Please consider the environment before printing this emai

[openstack-dev] [nova][libvirt] Gate bug 'libvirtError: Unable to read from monitor: Connection reset by peer'

Hi Daniel, all This morning I noticed we are seeing libvirt stacktrace in the gate occasionally. https://bugs.launchpad.net/nova/+bug/1255624 Since your are a libvirt maintainer I was hoping you could take a look at this one. best, Joe P.S. We also have a second libvirt gate bug https://bug

Re: [openstack-dev] [all project] Time to fail tempest gate jobs when new log errors appear

On Nov 27, 2013 11:06 AM, "Jay Pipes" wrote: > > On 11/27/2013 01:53 PM, David Kranz wrote: >> >> tl;dr Soon, perhaps next week, tempest gate jobs will start failing if >> there are any ERROR lines in the logs that are not matched by an entry >> in https://github.com/openstack/tempest/blob/master/

Re: [openstack-dev] cinder related gate failures

On Nov 27, 2013 11:58 AM, "John Griffith" wrote: > > Hey Everyone. > > There's been discussions about all sorts of things regarding getting > visibility to intermittent issues in the gates etc. including special > tags for bugs, making them critical etc. Regardless of what the > outcome of those

Re: [openstack-dev] [Neutron] Stop logging non-exceptional conditions as ERROR

On Dec 2, 2013 3:39 AM, "Maru Newby" wrote: > > > On Dec 2, 2013, at 2:07 AM, Anita Kuno wrote: > > > Great initiative putting this plan together, Maru. Thanks for doing > > this. Thanks for volunteering to help, Salvatore (I'm thinking of asking > > for you to be cloned - once that becomes avail

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 6:06 AM, Russell Bryant wrote: > On 12/02/2013 08:53 AM, Doug Hellmann wrote: > > > > > > > > On Mon, Dec 2, 2013 at 8:46 AM, Doug Hellmann > > mailto:doug.hellm...@dreamhost.com>> > wrote: > > > > > > > > > > On Mon, Dec 2, 2013 at 8:36 AM, Russell Bryant >

Re: [openstack-dev] [nova] why are we backporting low priority v3 api fixes to v2?

On Sat, Nov 30, 2013 at 2:25 PM, Christopher Yeoh wrote: > > On Sun, Dec 1, 2013 at 8:02 AM, Matt Riedemann > wrote: > >> I've seen a few bugs/reviews like this [1] lately which are essentially >> backporting fixes from the nova openstack v3 API to the v2 API. While this >> is goodness for the v

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 6:37 AM, Doug Hellmann wrote: > > > > On Mon, Dec 2, 2013 at 9:22 AM, Joe Gordon wrote: > >> >> >> >> On Mon, Dec 2, 2013 at 6:06 AM, Russell Bryant wrote: >> >>> On 12/02/2013 08:53 AM, Doug Hellmann wrote: >&g

Re: [openstack-dev] [ceilometer][qa] Punting ceilometer from whitelist

On Fri, Nov 29, 2013 at 11:07 AM, David Kranz wrote: > In preparing to fail builds with log errors I have been trying to make > things easier for projects by maintaining a whitelist. But these bugs in > ceilometer are coming in so fast that I can't keep up. So I am just > putting ".*" in the whi

Re: [openstack-dev] request-id in API response

On Sun, Dec 1, 2013 at 7:04 PM, John Dickinson wrote: > Just to add to the story, Swift uses "X-Trans-Id" and generates it in the > outer-most "catch_errors" middleware. > > Swift's catch errors middleware is responsible for ensuring that the > transaction id exists on each request, and that all

Re: [openstack-dev] [oslo] maintenance policy for code graduating from the incubator

On Mon, Dec 2, 2013 at 7:26 AM, Doug Hellmann wrote: > > > > On Mon, Dec 2, 2013 at 10:05 AM, Joe Gordon wrote: > >> >> >> >> On Mon, Dec 2, 2013 at 6:37 AM, Doug Hellmann < >> doug.hellm...@dreamhost.com> wrote: >> >>

Re: [openstack-dev] [Neutron][qa] Parallel testing update

On Dec 2, 2013 9:04 PM, "Salvatore Orlando" wrote: > > Hi, > > As you might have noticed, there has been some progress on parallel tests for neutron. > In a nutshell: > * Armando fixed the issue with IP address exhaustion on the public network [1] > * Salvatore has now a patch which has a 50% succ

Re: [openstack-dev] [Neutron] Stop logging non-exceptional conditions as ERROR

On Mon, Dec 2, 2013 at 1:55 PM, Maru Newby wrote: > > On Dec 2, 2013, at 10:19 PM, Joe Gordon wrote: > > > > > On Dec 2, 2013 3:39 AM, "Maru Newby" wrote: > > > > > > > > > On Dec 2, 2013, at 2:07 AM, Anita Kuno wrote: > > >

[openstack-dev] Tool for detecting commonly misspelled words

HI all, Recently I have seen a few patches fixing a few typos. I would like to point out a really nifty tool to detect commonly misspelled words. So next time you want to fix a typo, instead of just fixing a single one you can go ahead and fix a whole bunch. https://github.com/lyda/misspell-che

Re: [openstack-dev] Incubation Request for Barbican

On Dec 3, 2013 6:45 PM, "Jarret Raim" wrote: > > > >With the introduction of programs (think: official teams), all > >incubated/integrated projects must belong to an official program... So > >when a project applies for incubation but is not part of an official > >program yet, it de-facto also appl

Re: [openstack-dev] [Keystone] Store quotas in Keystone

On Dec 3, 2013 6:49 PM, "John Dickinson" wrote: > > > On Dec 3, 2013, at 8:05 AM, Jay Pipes wrote: > > > On 12/03/2013 10:04 AM, John Dickinson wrote: > >> How are you proposing that this integrate with Swift's account and container quotas (especially since there may be hundreds of thousands of a

Re: [openstack-dev] Tool for detecting commonly misspelled words

On Tue, Dec 3, 2013 at 10:46 AM, John Griffith wrote: > On Tue, Dec 3, 2013 at 11:38 AM, Russell Bryant > wrote: > > On 12/03/2013 09:22 AM, Joe Gordon wrote: > >> HI all, > >> > >> Recently I have seen a few patches fixing a few typos. I would like t

  1   2   3   4   5   6   7   8   9   >