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

2014-08-11 Thread Mark McLoughlin
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 that we don't CI on in the gate. Is it naive to think that a possible

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

2014-08-12 Thread Mark McLoughlin
On Mon, 2014-08-11 at 15:25 -0700, Joe Gordon wrote: On Sun, Aug 10, 2014 at 11:59 PM, Mark McLoughlin mar...@redhat.com 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

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

2014-08-12 Thread Mark McLoughlin
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 approach situations like this. Here's my attempt at documenting what I think we're expecting the procedure to be:

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

2014-08-12 Thread Mark McLoughlin
On Wed, 2014-07-30 at 15:34 -0700, Clark Boylan wrote: On Wed, Jul 30, 2014, at 03:23 PM, Jeremy Stanley wrote: On 2014-07-30 13:21:10 -0700 (-0700), Joe Gordon wrote: While forcing people to move to a newer version of libvirt is doable on most environments, do we want to do that now?

Re: [openstack-dev] [Nova] Nominating Jay Pipes for nova-core

2014-08-12 Thread Mark McLoughlin
On Wed, 2014-07-30 at 14:02 -0700, Michael Still wrote: Greetings, I would like to nominate Jay Pipes for the nova-core team. Jay has been involved with nova for a long time now. He's previously been a nova core, as well as a glance core (and PTL). He's been around so long that there are

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

2014-08-13 Thread Mark McLoughlin
On Tue, 2014-08-05 at 18:03 +0200, Thierry Carrez wrote: Hi everyone, With the incredible growth of OpenStack, our development community is facing complex challenges. How we handle those might determine the ultimate success or failure of OpenStack. With this cycle we hit new limits in our

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

2014-08-13 Thread Mark McLoughlin
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 before it lightens our load to the point where we get more breathing

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

2014-08-13 Thread Mark McLoughlin
On Fri, 2014-08-08 at 15:36 -0700, Devananda van der Veen wrote: On Tue, Aug 5, 2014 at 10:02 AM, Monty Taylor mord...@inaugust.com wrote: Yes. Additionally, and I think we've been getting better at this in the 2 cycles that we've had an all-elected TC, I think we need to learn how to

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

2014-08-13 Thread Mark McLoughlin
On Tue, 2014-08-12 at 14:26 -0400, 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 how much work they think they can actually do (less than the available number of blueprints), and then blueprints

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

2014-08-13 Thread Mark McLoughlin
On Tue, 2014-08-12 at 14:12 -0700, Joe Gordon wrote: Here is the full nova proposal on Blueprint in Kilo: Runways and Project Priorities https://review.openstack.org/#/c/112733/ http://docs-draft.openstack.org/33/112733/4/check/gate-nova-docs/5f38603/doc/build/html/devref/runways.html

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

2014-08-13 Thread Mark McLoughlin
On Wed, 2014-08-13 at 10:26 +0100, Daniel P. Berrange wrote: On Tue, Aug 12, 2014 at 10:09:52PM +0100, Mark McLoughlin wrote: On Wed, 2014-07-30 at 15:34 -0700, Clark Boylan wrote: On Wed, Jul 30, 2014, at 03:23 PM, Jeremy Stanley wrote: On 2014-07-30 13:21:10 -0700 (-0700), Joe Gordon

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

2014-08-13 Thread Mark McLoughlin
On Tue, 2014-07-29 at 14:04 +0200, Thierry Carrez wrote: Ihar Hrachyshka a écrit : On 29/07/14 12:15, Daniel P. Berrange wrote: 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

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

2014-08-13 Thread Mark McLoughlin
On Wed, 2014-08-13 at 12:05 -0700, James E. Blair wrote: cor...@inaugust.com (James E. Blair) writes: Sean Dague s...@dague.net writes: This has all gone far enough that someone actually wrote a Grease Monkey script to purge all the 3rd Party CI content out of Jenkins UI. People are

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

2014-08-14 Thread Mark McLoughlin
On Tue, 2014-08-12 at 15:56 +0100, 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 approach situations like this. Here's my attempt at documenting

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

2014-08-14 Thread Mark McLoughlin
On Tue, 2014-08-12 at 15:56 +0100, 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 approach situations like this. Here's my attempt at documenting

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

2014-08-18 Thread Mark McLoughlin
On Mon, 2014-08-18 at 14:23 +0200, Thierry Carrez wrote: Clint Byrum wrote: Here's why folk are questioning Ceilometer: Nova is a set of tools to abstract virtualization implementations. Neutron is a set of tools to abstract SDN/NFV implementations. Cinder is a set of tools to abstract

Re: [openstack-dev] [all] [ptls] The Czar system, or how to scale PTLs

2014-08-22 Thread Mark McLoughlin
On Fri, 2014-08-22 at 11:01 -0400, Zane Bitter wrote: I don't see that as something the wider OpenStack community needs to dictate. We have a heavyweight election process for PTLs once every cycle because that used to be the process for electing the TC. Now that it no longer serves this

Re: [openstack-dev] [oslo] Launchpad tracking of oslo projects

2014-08-26 Thread Mark McLoughlin
On Fri, 2014-08-22 at 11:59 +0200, Thierry Carrez wrote: TL;DR: Let's create an Oslo projectgroup in Launchpad to track work across all Oslo libraries. In library projects, let's use milestones connected to published versions rather than the common milestones. Sounds good to me, Thierry.

Re: [openstack-dev] [oslo] usage patterns for oslo.config

2014-08-26 Thread Mark McLoughlin
On Mon, 2014-08-11 at 15:06 -0400, Doug Hellmann wrote: On Aug 8, 2014, at 7:22 PM, Devananda van der Veen devananda@gmail.com wrote: On Fri, Aug 8, 2014 at 12:41 PM, Doug Hellmann d...@doughellmann.com wrote: That’s right. The preferred approach is to put the register_opt() in

Re: [openstack-dev] [oslo] usage patterns for oslo.config

2014-08-27 Thread Mark McLoughlin
On Tue, 2014-08-26 at 10:00 -0400, Doug Hellmann wrote: On Aug 26, 2014, at 6:30 AM, Mark McLoughlin mar...@redhat.com wrote: On Mon, 2014-08-11 at 15:06 -0400, Doug Hellmann wrote: On Aug 8, 2014, at 7:22 PM, Devananda van der Veen devananda@gmail.com wrote: On Fri, Aug 8, 2014

Re: [openstack-dev] [oslo.messaging] Request to include AMQP 1.0 support in Juno-3

2014-08-28 Thread Mark McLoughlin
On Thu, 2014-08-28 at 13:24 +0200, Flavio Percoco wrote: On 08/27/2014 03:35 PM, Ken Giusti wrote: Hi All, I believe Juno-3 is our last chance to get this feature [1] included into olso.messaging. I honestly believe this patch is about as low risk as possible for a change that

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

2014-08-30 Thread Mark McLoughlin
Hey The libvirt version_cap debacle continues to come up in conversation and one perception of the whole thing appears to be: A controversial patch was ninjaed by three Red Hat nova-cores and then the same individuals piled on with -2s when a revert was proposed to allow further

Re: [openstack-dev] [Zaqar] Zaqar graduation (round 2) [was: Comments on the concerns arose during the TC meeting]

2014-09-12 Thread Mark McLoughlin
On Wed, 2014-09-10 at 14:51 +0200, Thierry Carrez wrote: Flavio Percoco wrote: [...] Based on the feedback from the meeting[3], the current main concern is: - Do we need a messaging service with a feature-set akin to SQS+SNS? [...] I think we do need, as Samuel puts it, some sort of

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

2014-09-12 Thread Mark McLoughlin
On Wed, 2014-09-10 at 12:46 -0700, Monty Taylor wrote: On 09/09/2014 07:04 PM, Samuel Merritt wrote: On 9/9/14, 4:47 PM, Devananda van der Veen wrote: The questions now before us are: - should OpenStack include, in the integrated release, a messaging-as-a-service component? I

Re: [openstack-dev] Thoughts on OpenStack Layers and a Big Tent model

2014-09-22 Thread Mark McLoughlin
Hey On Thu, 2014-09-18 at 11:53 -0700, Monty Taylor wrote: Hey all, I've recently been thinking a lot about Sean's Layers stuff. So I wrote a blog post which Jim Blair and Devananda were kind enough to help me edit. http://inaugust.com/post/108 Lots of great stuff here, but too much to

Re: [openstack-dev] TransportURL and virtualhost/exchnage (was Re: [Oslo] Layering olso.messaging usage of config)

2013-12-09 Thread Mark McLoughlin
Hi Gordon, On Fri, 2013-12-06 at 18:36 +, Gordon Sim wrote: On 11/18/2013 04:44 PM, Mark McLoughlin wrote: On Mon, 2013-11-18 at 11:29 -0500, Doug Hellmann wrote: IIRC, one of the concerns when oslo.messaging was split out was maintaining support for existing deployments

Re: [openstack-dev] [olso] [cinder] upgrade issues in lock_path in cinder after oslo utils sync

2013-12-09 Thread Mark McLoughlin
On Mon, 2013-12-09 at 11:11 -0600, Ben Nemec wrote: On 2013-12-09 10:55, Sean Dague wrote: On 12/09/2013 11:38 AM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2013-12-09 08:17:45 -0800: On 12/06/2013 05:40 PM, Ben Nemec wrote: On 2013-12-06 16:30, Clint Byrum wrote:

Re: [openstack-dev] Retiring reverify no bug

2013-12-09 Thread Mark McLoughlin
On Mon, 2013-12-09 at 10:49 -0800, James E. Blair wrote: Hi, On Wednesday December 11, 2013 we will remove the ability to use reverify no bug to re-trigger gate runs for changes that have failed tests. This was previously discussed[1] on this list. There are a few key things to keep in

Re: [openstack-dev] [Nova][TripleO] Nested resources

2013-12-09 Thread Mark McLoughlin
On Tue, 2013-12-10 at 09:40 +1300, Robert Collins wrote: On 6 December 2013 14:11, Fox, Kevin M kevin@pnnl.gov wrote: I think the security issue can be handled by not actually giving the underlying resource to the user in the first place. So, for example, if I wanted a bare metal

Re: [openstack-dev] [Oslo] First steps towards amqp 1.0

2013-12-09 Thread Mark McLoughlin
On Mon, 2013-12-09 at 16:05 +0100, Flavio Percoco wrote: Greetings, As $subject mentions, I'd like to start discussing the support for AMQP 1.0[0] in oslo.messaging. We already have rabbit and qpid drivers for earlier (and different!) versions of AMQP, the proposal would be to add an

Re: [openstack-dev] [Tripleo] Core reviewer update Dec

2013-12-09 Thread Mark McLoughlin
On Tue, 2013-12-10 at 13:31 +1300, Robert Collins wrote: We have a bit of a bug in OpenStack today, IMO, in that there is more focus on being -core than on being a good effective reviewer. IMO that's backwards: the magic switch that lets you set +2 and -2 is a responsibility, and that has

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

2013-12-12 Thread Mark McLoughlin
On Wed, 2013-12-11 at 13:33 +0100, Jiří Stránský wrote: Hi all, TL;DR: I believe that As an infrastructure administrator, Anna wants a CLI for managing the deployment providing the same fundamental features as UI. With the planned architecture changes (making tuskar-api thinner and

Re: [openstack-dev] [oslo][glance] Oslo.cfg resets not really resetting the CONF

2013-12-16 Thread Mark McLoughlin
a bug on the oslo end. Yes, that's working as designed. Those two options are registered by __call__() so reset() unregisters only them. The idea is that you can register lots and then do __call__() and reset() without affecting the registered options. Mark. On Tue, Dec 17, 2013 at 5:27 AM, Mark

Re: [openstack-dev] [governance] Becoming a Program, before applying for incubation

2013-12-17 Thread Mark McLoughlin
On Tue, 2013-12-17 at 11:25 +0100, Thierry Carrez wrote: Mark McLoughlin wrote: I'm not totally convinced we need such formality around the TC expressing its support for an early-stage program/project/effort/team. This is a difficult balance. You want to help a number of projects

Re: [openstack-dev] [governance] Becoming a Program, before applying for incubation

2013-12-17 Thread Mark McLoughlin
On Tue, 2013-12-17 at 13:44 +0100, Thierry Carrez wrote: Mark McLoughlin wrote: How about if we had an emerging projects page where the TC feedback on each project would be listed? That would give visibility to our feedback, without making it a yes/no blessing. Ok, whether to list any

Re: [openstack-dev] Less option (was: [oslo.config] Centralized config management)

2014-01-10 Thread Mark McLoughlin
On Thu, 2014-01-09 at 16:34 -0800, Joe Gordon wrote: On Thu, Jan 9, 2014 at 3:01 PM, Jay Pipes jaypi...@gmail.com wrote: On Thu, 2014-01-09 at 23:56 +0100, Julien Danjou wrote: On Thu, Jan 09 2014, Jay Pipes wrote: Hope you don't mind, I'll jump in here :) On Thu, 2014-01-09

Re: [openstack-dev] pep8 gating fails due to tools/config/check_uptodate.sh

2014-02-04 Thread Mark McLoughlin
On Mon, 2014-01-13 at 16:49 +, Sahid Ferdjaoui wrote: Hello all, It looks 100% of the pep8 gate for nova is failing because of a bug reported, we probably need to mark this as Critical. https://bugs.launchpad.net/nova/+bug/1268614 Ivan Melnikov has pushed a patchset waiting for

Re: [openstack-dev] pep8 gating fails due to tools/config/check_uptodate.sh

2014-02-04 Thread Mark McLoughlin
On Wed, 2014-02-05 at 01:19 +0900, Sean Dague wrote: On 02/05/2014 12:37 AM, Mark McLoughlin wrote: On Mon, 2014-01-13 at 16:49 +, Sahid Ferdjaoui wrote: Hello all, It looks 100% of the pep8 gate for nova is failing because of a bug reported, we probably need to mark

Re: [openstack-dev] [Openstack-docs] Conventions on naming

2014-02-05 Thread Mark McLoughlin
On Wed, 2014-02-05 at 11:52 +0100, Thierry Carrez wrote: Steve Gordon wrote: From: Anne Gentle anne.gen...@rackspace.com Based on today's Technical Committee meeting and conversations with the OpenStack board members, I need to change our Conventions for service names at

Re: [openstack-dev] [PTL] Designating required use upstream code

2014-02-05 Thread Mark McLoughlin
On Wed, 2014-02-05 at 17:22 +0100, Thierry Carrez wrote: (This email is mostly directed to PTLs for programs that include one integrated project) The DefCore subcommittee from the OpenStack board of directors asked the Technical Committee yesterday about which code sections in each

Re: [openstack-dev] why do we put a license in every file?

2014-02-05 Thread Mark McLoughlin
On Wed, 2014-02-05 at 16:29 +, Greg Hill wrote: I'm new, so I'm sure there's some history I'm missing, but I find it bizarre that we have to put the same license into every single file of source code in our projects. In my past experience, a single LICENSE file at the root-level of the

Re: [openstack-dev] supported dependency versioning and testing

2014-02-21 Thread Mark McLoughlin
On Thu, 2014-02-20 at 10:31 -0800, Joe Gordon wrote: Hi All, I discussion recently came up inside of nova about what it means supported version for a dependency means. in libvirt we gate on the minimal version that we support but for all python dependencies we gate on the highest version

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-19 Thread Mark McLoughlin
On Wed, 2014-03-19 at 10:17 +1300, Robert Collins wrote: So this came up briefly at the tripleo sprint, and since I can't seem to find a /why/ document (https://wiki.openstack.org/wiki/Marconi/Incubation#Raised_Questions_.2B_Answers and https://wiki.openstack.org/wiki/Marconi#Design don't

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Mark McLoughlin
On Thu, 2014-03-20 at 01:28 +, Joshua Harlow wrote: Proxying from yahoo's open source director (since he wasn't initially subscribed to this list, afaik he now is) on his behalf. From Gil Yehuda (Yahoo’s Open Source director). I would urge you to avoid creating a dependency between

Re: [openstack-dev] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Mark McLoughlin
On Wed, 2014-03-19 at 12:37 -0700, Devananda van der Veen wrote: Let me start by saying that I want there to be a constructive discussion around all this. I've done my best to keep my tone as non-snarky as I could while still clearly stating my concerns. I've also spent a few hours reviewing

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Mark McLoughlin
On Thu, 2014-03-20 at 12:07 +0100, Thierry Carrez wrote: Monty Taylor wrote: On 03/20/2014 01:30 AM, Radcliffe, Mark wrote: The problem with AGPL is that the scope is very uncertain and the determination of the consequences are very fact intensive. I was the chair of the User Committee

Re: [openstack-dev] Multiple patches in one review

2014-03-25 Thread Mark McLoughlin
On Mon, 2014-03-24 at 10:49 -0400, Russell Bryant wrote: Gerrit support for a patch series could certainly be better. There has long been talking about gerrit getting topic review functionality, whereby you could e.g. approve a whole series of patches from a topic view. See:

Re: [openstack-dev] OpenStack vs. SQLA 0.9

2014-03-25 Thread Mark McLoughlin
FYI, allowing 0.9 recently merged into openstack/requirements: https://review.openstack.org/79817 This is a good example of how we should be linking gerrit and mailing list discussions together more. I don't think the gerrit review was linked in this thread nor was the mailing list discussion

Re: [openstack-dev] [depfreeze] [horizon] Exception request: python-keystoneclient=0.7.0

2014-03-27 Thread Mark McLoughlin
On Thu, 2014-03-27 at 13:53 +, Julie Pichon wrote: Hi, I would like to request a depfreeze exception to bump up the keystone client requirement [1], in order to reenable the ability for users to update their own password with Keystone v3 in Horizon in time for Icehouse [2]. This

[openstack-dev] oslo.messaging 1.3.0 released

2014-04-01 Thread Mark McLoughlin
Hi oslo.messaging 1.3.0 is now available on pypi and should be available in our mirror shortly. Full release notes are available here: http://docs.openstack.org/developer/oslo.messaging/ The master branch will soon be open for Juno targeted development and we'll publish 1.4.0aN beta releases

Re: [openstack-dev] [oslo] use of the oslo namespace package

2014-04-08 Thread Mark McLoughlin
On Mon, 2014-04-07 at 15:24 -0400, Doug Hellmann wrote: We can avoid adding to the problem by putting each new library in its own package. We still want the Oslo name attached for libraries that are really only meant to be used by OpenStack projects, and so we need a naming convention. I'm not

Re: [openstack-dev] [Oslo] Change ListOpt and DictOpt default values

2013-10-10 Thread Mark McLoughlin
Hi Flavio, On Thu, 2013-10-10 at 14:40 +0200, Flavio Percoco wrote: Greetings, I'd like to propose to change both ListOpt and DictOpt default values to [] and {} respectively. These values are, IMHO, saner defaults than None for this 2 options and behavior won't be altered - unles `is not

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-21 Thread Mark McLoughlin
On Mon, 2013-10-21 at 10:28 -0700, Clint Byrum wrote: Excerpts from Robert Collins's message of 2013-10-20 02:25:43 -0700: On 20 October 2013 02:35, Monty Taylor mord...@inaugust.com wrote: However, even as a strong supporter of accurate license headers, I would like to know more about

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-21 Thread Mark McLoughlin
On Tue, 2013-10-22 at 01:55 +0800, Thomas Goirand wrote: On 10/21/2013 09:28 PM, Mark McLoughlin wrote: In other words, what exactly is a list of copyright holders good for? At least avoid pain and reject when uploading to the Debian NEW queue... I'm sorry, that is downstream Debian pain

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-21 Thread Mark McLoughlin
On Tue, 2013-10-22 at 01:45 +0800, Thomas Goirand wrote: On 10/20/2013 09:00 PM, Jeremy Stanley wrote: On 2013-10-20 22:20:25 +1300 (+1300), Robert Collins wrote: [...] OTOH registering one's nominated copyright holder on the first patch to a repository is probably a sustainable overhead.

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-22 Thread Mark McLoughlin
On Tue, 2013-10-22 at 01:09 +0100, Monty Taylor wrote: The last thing we need to do is validate in any manner that somehow the CLA makes our Apache Licensed Free Software more Free or more Valid than if we did not have our useless CLA. Agree with this. My simplified way of thinking about this

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-22 Thread Mark McLoughlin
On Tue, 2013-10-22 at 14:09 +0800, Thomas Goirand wrote: On 10/22/2013 04:55 AM, Mark McLoughlin wrote: Talk to the Trove developers and politely ask them whether the copyright notices in their code reflects what they see as the reality. I'm sure it would help them if you pointed out

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-22 Thread Mark McLoughlin
On Tue, 2013-10-22 at 14:19 +0800, Thomas Goirand wrote: On 10/22/2013 04:48 AM, Mark McLoughlin wrote: On Tue, 2013-10-22 at 01:55 +0800, Thomas Goirand wrote: On 10/21/2013 09:28 PM, Mark McLoughlin wrote: In other words, what exactly is a list of copyright holders good for? At least

Re: [openstack-dev] RFC: Filtering boring commit subjects from ChangeLog

2013-10-28 Thread Mark McLoughlin
On Sun, 2013-10-27 at 21:50 -0400, Monty Taylor wrote: Hey all! We're adding a little bit of code to pbr to make the auto-generated ChangeLog files a bit more useful. Currently, they are just the git changelog, which is kinda useless. So we wrote this:

Re: [openstack-dev] When is it okay for submitters to say 'I don't want to add tests' ?

2013-10-31 Thread Mark McLoughlin
On Thu, 2013-10-31 at 15:37 +1300, Robert Collins wrote: This is a bit of a social norms thread I've been consistently asking for tests in reviews for a while now, and I get the occasional push-back. I think this falls into a few broad camps: A - there is no test suite at all, adding

Re: [openstack-dev] welcoming new committers (was Re: When is it okay for submitters to say 'I don't want to add tests' ?)

2013-10-31 Thread Mark McLoughlin
On Thu, 2013-10-31 at 11:49 -0700, Stefano Maffulli wrote: Another idea that Tom suggested is to use gerrit automation to send back to first time committers something in addition to the normal 'your patch is waiting for review' message. The message could be something like: thank you for

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

2013-11-11 Thread Mark McLoughlin
to track more complex affiliations. Our affiliation databases are all keyed off email addresses right now, so how about if we allowed for encoding affiliation/sponsorship in addresses? e.g. Author: Mark McLoughlin markmc+...@redhat.com and we could register that address as work done by Mark on behalf

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

2013-11-11 Thread Mark McLoughlin
On Mon, 2013-11-11 at 11:41 -0500, Russell Bryant wrote: On 11/11/2013 10:57 AM, Mark McLoughlin wrote: Hi Nick, On Mon, 2013-11-11 at 15:20 +0100, Nicolas Barcet wrote: Dear TC members, Our companies are actively encouraging our respective customers to have the patches

Re: [openstack-dev] Bad review patterns

2013-11-11 Thread Mark McLoughlin
On Fri, 2013-11-08 at 09:32 +1300, Robert Collins wrote: On 7 November 2013 13:15, Day, Phil philip@hp.com wrote: Core reviewers look for the /comments/ from people, not just the votes. A +1 from someone that isn't core is meaningless unless they are known to be a thoughtful

Re: [openstack-dev] Bad review patterns

2013-11-11 Thread Mark McLoughlin
/able to set up such filtering.) I know you're discounting filtering here, but FWIW I filter on the email body containing: Gerrit-Reviewer: Mark McLoughlin so that I have all email related to reviews I'm subscribed to in a single folder. I try hard to stay on top of this folder to avoid being

Re: [openstack-dev] [Nova] Configuration validation

2013-11-11 Thread Mark McLoughlin
Hi Nikola, On Mon, 2013-11-11 at 12:44 +0100, Nikola Đipanov wrote: Hey all, During the summit session on the the VMWare driver roadmap, a topic of validating the passed configuration prior to starting services came up (see [1] for more detail on how it's connected to that specific topic).

Re: [openstack-dev] [nova] Do we have some guidelines for mock, stub, mox when writing unit test?

2013-11-11 Thread Mark McLoughlin
On Mon, 2013-11-11 at 12:07 +, John Garbutt wrote: On 11 November 2013 10:27, Rosa, Andrea (HP Cloud Services) andrea.r...@hp.com wrote: Hi Generally mock is supposed to be used over mox now for python 3 support. That is my understanding too +1 But I don't think we should

Re: [openstack-dev] [Nova] New API requirements, review of GCE

2013-11-15 Thread Mark McLoughlin
On Fri, 2013-11-15 at 11:28 -0500, Russell Bryant wrote: Greetings, We've talked a lot about requirements for new compute drivers [1]. I think the same sort of standards shold be applied for a new third-party API, such as the GCE API [2]. Before we can consider taking on a new API, it

Re: [openstack-dev] [Nova] New API requirements, review of GCE

2013-11-15 Thread Mark McLoughlin
On Fri, 2013-11-15 at 12:19 -0500, Russell Bryant wrote: On 11/15/2013 12:01 PM, Mark McLoughlin wrote: On Fri, 2013-11-15 at 11:28 -0500, Russell Bryant wrote: Greetings, We've talked a lot about requirements for new compute drivers [1]. I think the same sort of standards shold

Re: [openstack-dev] [RFC] Straw man to start the incubation / graduation requirements discussion

2013-11-15 Thread Mark McLoughlin
On Wed, 2013-11-13 at 06:57 -0500, Sean Dague wrote: (Apologies, this started on the TC list, and really should have started on -dev, correctly posting here now for open discussion) There were a few chats at summit about this, mostly on the infra / devstack / qa side of the house. Consider

Re: [openstack-dev] [Neutron] Neutron Tempest code sprint - 2nd week of January, Montreal, QC, Canada

2013-11-15 Thread Mark McLoughlin
On Fri, 2013-11-15 at 12:47 -0500, Anita Kuno wrote: On 11/15/2013 12:34 PM, Russell Bryant wrote: On 11/15/2013 12:16 PM, Kyle Mestery (kmestery) wrote: On Nov 15, 2013, at 11:04 AM, Dan Smith d...@danplanet.com wrote: Thanks for weighing in, I do hope to keep the conversation going. Add

Re: [openstack-dev] [Oslo] Layering olso.messaging usage of config

2013-11-18 Thread Mark McLoughlin
Hi Julien, On Mon, 2013-11-18 at 11:05 +0100, Julien Danjou wrote: Hi Oslo developers, It seems my latest patch¹ on oslo.messaging scared Mark, so I'll try to discuss it a bit on this mailing list as it is more convenient. Scared, heh :) I've created a blueprint² as requested by Mark.

Re: [openstack-dev] [Oslo] Layering olso.messaging usage of config

2013-11-18 Thread Mark McLoughlin
On Mon, 2013-11-18 at 17:37 +0100, Julien Danjou wrote: On Mon, Nov 18 2013, Mark McLoughlin wrote: I'm struggling to care about this until I have some insight into why it's important. And it's a bit frustrating to have to guess the rationale for this. Like commit messages, blueprints

Re: [openstack-dev] [Oslo] Layering olso.messaging usage of config

2013-11-18 Thread Mark McLoughlin
Hey Doug, On Mon, 2013-11-18 at 11:29 -0500, Doug Hellmann wrote: On Mon, Nov 18, 2013 at 5:05 AM, Julien Danjou jul...@danjou.info wrote: Hi Oslo developers, It seems my latest patch¹ on oslo.messaging scared Mark, so I'll try to discuss it a bit on this mailing list as it is more

Re: [openstack-dev] [Nova][db] Changing migrations

2013-11-18 Thread Mark McLoughlin
On Mon, 2013-11-18 at 18:46 +0100, Nikola Đipanov wrote: Dear OpenStack devs, A recent review [1] dragged into spotlight how damaging improper use of external code inside migrations can be. Basically in my mind the incident raises 2 issues that I think we should look into: 1) How can

Re: [openstack-dev] [Oslo] Layering olso.messaging usage of config

2013-11-18 Thread Mark McLoughlin
On Mon, 2013-11-18 at 18:22 +, Joshua Harlow wrote: I see it as important (and not theoretical). I'd like to use oslo.messaging (and oslo.messaging.rpc) in taskflow (to prototype how a distributed engine would work using it) and bringing in a library which requires global configuration

Re: [openstack-dev] [Cinder][Glance] OSLO update

2013-11-18 Thread Mark McLoughlin
On Mon, 2013-11-18 at 17:24 +, Duncan Thomas wrote: Random OSLO updates with no list of what changed, what got fixed etc are unlikely to get review attention - doing such a review is extremely difficult. I was -2ing them and asking for more info, but they keep popping up. I'm really not

Re: [openstack-dev] Incubation request for Manila

2013-11-18 Thread Mark McLoughlin
Hi, On Thu, 2013-10-10 at 15:00 +, Swartzlander, Ben wrote: Please consider our formal request for incubation status of the Manila project: https://wiki.openstack.org/wiki/Manila_Overview Note that the Manila application was discussed at last week's TC meeting. I tried to take some

Re: [openstack-dev] Propose project story wiki idea

2013-11-21 Thread Mark McLoughlin
On Thu, 2013-11-21 at 10:43 +0100, Thierry Carrez wrote: Stefano Maffulli wrote: On 11/19/2013 09:33 PM, Boris Pavlovic wrote: The idea of this proposal is that every OpenStack project should have story wiki page. It means to publish every week one short message that contains most

Re: [openstack-dev] [Keystone][Oslo] Future of Key Distribution Server, Trusted Messaging

2013-11-22 Thread Mark McLoughlin
On Fri, 2013-11-22 at 11:04 +0100, Thierry Carrez wrote: Russell Bryant wrote: [...] I'm not thrilled about the prospect of this going into a new project for multiple reasons. - Given the priority and how long this has been dragging out, having to wait for a new project to make its

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

2013-11-22 Thread Mark McLoughlin
On Fri, 2013-11-22 at 15:53 -0500, 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 on a wide range of tasks. He writes good code. He's very engaged with the development

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

2013-11-26 Thread Mark McLoughlin
On Tue, 2013-11-26 at 14:32 -0500, 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] [nova] [QA] Triaging Bugs during Review

2013-11-26 Thread Mark McLoughlin
On Tue, 2013-11-26 at 13:06 -0800, Vishvananda Ishaya wrote: Hi Everyone, I tend to follow merges and look for valuable havana backports. A few bug fixes have merged recently where the associated bug is untriaged (i.e. the severity is listed as 'Unknown'). I assume that reviewers of a bugfix

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

2013-11-26 Thread Mark McLoughlin
On Tue, 2013-11-26 at 12:29 -0800, Joe Gordon wrote: On Nov 26, 2013 8:48 AM, Dolph Mathews dolph.math...@gmail.com wrote: On Tue, Nov 26, 2013 at 5:23 AM, Thierry Carrez thie...@openstack.org wrote: Dolph Mathews wrote: On Mon, Nov 25, 2013 at 8:12 PM, Robert Collins

Re: [openstack-dev] [Oslo] Improving oslo-incubator update.py

2013-11-26 Thread Mark McLoughlin
On Fri, 2013-11-22 at 12:39 -0500, Doug Hellmann wrote: On Fri, Nov 22, 2013 at 4:11 AM, Flavio Percoco fla...@redhat.com wrote: Greetings, Based on the recent discussion that came out about not having enough information in the commit message when syncing oslo-incubator modules, I was

Re: [openstack-dev] [Oslo] Improving oslo-incubator update.py

2013-11-26 Thread Mark McLoughlin
On Fri, 2013-11-22 at 16:24 +, Duncan Thomas wrote: On 22 November 2013 14:59, Ben Nemec openst...@nemebean.com wrote: One other thought I had was to add the ability to split one Oslo sync up into multiple commits, either one per module, or even one per Oslo commit for some really

Re: [openstack-dev] How to best make User Experience a priority in every project

2013-11-26 Thread Mark McLoughlin
On Wed, 2013-11-20 at 11:06 -0600, Dean Troyer wrote: On Wed, Nov 20, 2013 at 9:09 AM, Thierry Carrez thie...@openstack.orgwrote: However, as was apparent in the Technical Committee meeting discussion about it yesterday, most of us are not convinced that establishing and blessing a

Re: [openstack-dev] [Oslo] Improving oslo-incubator update.py

2013-11-27 Thread Mark McLoughlin
On Wed, 2013-11-27 at 11:50 +0100, Flavio Percoco wrote: On 26/11/13 22:54 +, Mark McLoughlin wrote: On Fri, 2013-11-22 at 12:39 -0500, Doug Hellmann wrote: On Fri, Nov 22, 2013 at 4:11 AM, Flavio Percoco fla...@redhat.com wrote: 1) Store the commit sha from which the module

Re: [openstack-dev] [oslo] rpc concurrency control rfc

2013-11-27 Thread Mark McLoughlin
Hi, On Wed, 2013-11-27 at 14:45 +, Edward Hope-Morley wrote: Moving this to the ml as requested, would appreciate comments/thoughts/feedback. Thanks, I too would appreciate input from others. So, I recently proposed a small patch to the oslo rpc code (initially in oslo-incubator then

Re: [openstack-dev] [TripleO] Summit session wrapup

2013-11-27 Thread Mark McLoughlin
Hi Jarda, On Wed, 2013-11-27 at 14:39 +0100, Jaromir Coufal wrote: I think here is the main point where I disagree and which leads to different approaches. I don't think, that user of TripleO cares *only* about deploying infrastructure without any knowledge where the things go. This is

Re: [openstack-dev] [Keystone][Oslo] Future of Key Distribution Server, Trusted Messaging

2013-11-29 Thread Mark McLoughlin
Hey Anyone got an update on this? The keystone blueprint for KDS was marked approved on Tuesday: https://blueprints.launchpad.net/keystone/+spec/key-distribution-server and a new keystone review was added on Sunday, but it must be a draft since I can't access it:

Re: [openstack-dev] When should things get added to Oslo.Incubator

2013-12-03 Thread Mark McLoughlin
On Tue, 2013-12-03 at 22:07 +, Joshua Harlow wrote: Process for process sake imho has been a problem for oslo. It's been reiterated many times, but again - the only purpose of oslo-incubator is as a place to evolve an API until we're ready to make a commitment to API stability. It's often

Re: [openstack-dev] When should things get added to Oslo.Incubator

2013-12-03 Thread Mark McLoughlin
On Wed, 2013-12-04 at 10:42 +1300, Robert Collins wrote: Hey - https://review.openstack.org/#/c/57022/7//COMMIT_MSG - I strongly suggested here that reusing the Nova object code is the first step towards an objects library, and that we should be putting it in olso; there are some reasonable

Re: [openstack-dev] When should things get added to Oslo.Incubator

2013-12-03 Thread Mark McLoughlin
. On 12/3/13 2:25 PM, Mark McLoughlin mar...@redhat.com wrote: On Tue, 2013-12-03 at 22:07 +, Joshua Harlow wrote: Process for process sake imho has been a problem for oslo. It's been reiterated many times, but again - the only purpose of oslo-incubator is as a place to evolve an API

Re: [openstack-dev] creating a default for oslo config variables within a project?

2013-12-03 Thread Mark McLoughlin
On Tue, 2013-12-03 at 16:23 -0600, Ben Nemec wrote: On 2013-12-03 15:56, Sean Dague wrote: This cinder patch - https://review.openstack.org/#/c/48935/ Is blocked on failing upgrade because the updated oslo lockutils won't function until there is a specific configuration variable added to

Re: [openstack-dev] When should things get added to Oslo.Incubator

2013-12-03 Thread Mark McLoughlin
to commit to API stability. Mark. On 12/3/13 2:25 PM, Mark McLoughlin mar...@redhat.com wrote: On Tue, 2013-12-03 at 22:07 +, Joshua Harlow wrote: Process for process sake imho has been a problem for oslo. It's been reiterated many times, but again - the only purpose

Re: [openstack-dev] [Olso][DB] Remove eventlet from oslo.db

2013-12-03 Thread Mark McLoughlin
On Mon, 2013-12-02 at 16:02 +0200, Victor Sergeyev wrote: Hi folks! At the moment I and Roman Podoliaka are working on splitting of openstack.common.db code into a separate library. And it would be nice to drop dependency on eventlet before oslo.db is released. Currently, there is only

Re: [openstack-dev] [openstack-tc] [barbican] Curious about oslo.messaging (from Incubation Request for Barbican)

2013-12-04 Thread Mark McLoughlin
On Wed, 2013-12-04 at 05:01 +, John Wood wrote: Hello folks, I was curious if there is an OpenStack project that would be a good example to follow as we convert Barbican over to oslo messaging. I've been examining existing OpenStack projects such as Ceilometer and Keystone to see how

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

2013-12-05 Thread Mark McLoughlin
On Mon, 2013-12-02 at 11:00 -0500, Doug Hellmann wrote: I have updated the Oslo wiki page with these details and would appreciate feedback on the wording used there. https://wiki.openstack.org/wiki/Oslo#Graduation Thanks Doug, that sounds perfect to me. Mark.

Re: [openstack-dev] [Nova][TripleO] Nested resources

2013-12-05 Thread Mark McLoughlin
Hi Kevin, On Mon, 2013-12-02 at 12:39 -0800, Fox, Kevin M wrote: Hi all, I just want to run a crazy idea up the flag pole. TripleO has the concept of an under and over cloud. In starting to experiment with Docker, I see a pattern start to emerge. * As a User, I may want to allocate a

  1   2   3   >