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

2014-08-22 Thread Rochelle.RochelleGrober
/flame-on Ok, this is funny to some of us in the community. The general populace of this community is so against the idea of management that they will use the term for a despotic dictator as a position name rather than manager. Sorry, but this needed to be said. /flame-off Specific comments

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

2014-08-25 Thread Rochelle.RochelleGrober
Zane Bitter wrote: On 22/08/14 21:02, Anne Gentle wrote: I'm with Rocky on the anti-czar-as-a-word camp. We all like clever names to shed the corporate stigma but this word ain't it. Liaison or lead? +1. The only time you hear the word 'czar' in regular life (outside of references to

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

2014-08-25 Thread Rochelle.RochelleGrober
Zane Bitter [August 25, 2014 1:38 PM] wrote: . . . snip I'd say we've done fairly well, but I would attribute that at least in part to the fact that we've treated the PTL as effectively the temporary release management contact more than the guy who will resolve disputes for us. In other

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

2014-08-26 Thread Rochelle.RochelleGrober
On August 26, 2014, Anne Gentle wrote: On Mon, Aug 25, 2014 at 8:36 AM, Sean Dague s...@dague.netmailto:s...@dague.net 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

Re: [openstack-dev] [all] Design Summit reloaded

2014-08-27 Thread Rochelle.RochelleGrober
On August 27, 2014 3:26 PM Clint Byrum wrote: Excerpts from Thierry Carrez's message of 2014-08-27 05:51:55: Hi everyone, I've been thinking about what changes we can bring to the Design Summit format to make it more productive. I've heard the feedback from the mid-cycle meetups and would

Re: [openstack-dev] [all] Design Summit reloaded

2014-08-27 Thread Rochelle.RochelleGrober
From: Chris Jones [mailto:c...@tenshu.net] Hi Anita Your impromptu infra-clue-dissemination talks sound interesting (I'd like to see the elastic recheck fingerprint one, for example). Would it make sense to amplify your reach, by making some short screencasts of these sorts of things?

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

2014-09-10 Thread Rochelle.RochelleGrober
-Original Message- From: Daniel P. Berrange [mailto:berra...@redhat.com] Sent: Wednesday, September 10, 2014 1:45 AM On Tue, Sep 09, 2014 at 05:14:43PM -0700, Stefano Maffulli wrote: To me, this means you don't really want a sin bin where you dump drivers and tell them not to come

Re: [openstack-dev] [all] OpenStack bootstrapping hour - Friday Sept 19th - 3pm EST

2014-09-15 Thread Rochelle.RochelleGrober
+1000 This is *great*. Not only for newbies, but refreshers, learning different approaches, putting faces to the signatures, etc. And Mock best practices is a brilliant starting place for developers. I'd like to vote for a few others: - Development environment (different ones: PyCharms,

[openstack-dev] Log Rationalization -- Bring it on!

2014-09-17 Thread Rochelle.RochelleGrober
TL;DR: I consider the poor state of log consistency a major impediment for more widespread adoption of OpenStack and would like to volunteer to own this cross-functional process to begin to unify and standardize logging messages and attributes for Kilo while dealing with the most egregious

Re: [openstack-dev] [Nova] [All] API standards working group (was: Some ideas for micro-version implementation)

2014-09-23 Thread Rochelle.RochelleGrober
jaypi...@gmail.commailto:jaypi...@gmail.com on Tuesday, September 23, 2014 9:09 AM wrote: _Snip I'd like to say finally that I think there should be an OpenStack API working group whose job it is to both pull together a set of OpenStack API

Re: [openstack-dev] [Fwd: Change in openstack/neutron[master]: Kill dnsmasq and ns-meta softly]

2014-01-28 Thread Rochelle.RochelleGrober
+1 anyway. Sometimes I feel like we've lost the humor in our work, but at least I see it on IRC and now here. Thanks for the humanity check! --Rocky From: Salvatore Orlando [mailto:sorla...@nicira.com] Sent: Tuesday, January 28, 2014 1:05 PM To: OpenStack Development Mailing List (not for

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

2014-02-05 Thread Rochelle.RochelleGrober
On Wed, Feb 5, 2014 at 12:05 PM, Russell Bryant rbry...@redhat.commailto:rbry...@redhat.com wrote: On 02/05/2014 11:22 AM, 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

Re: [openstack-dev] [Nova] RFC: Generate API sample files from API schemas

2014-02-06 Thread Rochelle.RochelleGrober
+1 Really lots more than just +1 This leads to so many more efficiencies and increase in effectiveness. --Rocky -Original Message- From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] Sent: Thursday, February 06, 2014 10:17 AM To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [openstack-qa] Graduation Requirements + Scope of Tempest

2014-03-20 Thread Rochelle.RochelleGrober
-Original Message- From: Malini Kamalambal [mailto:malini.kamalam...@rackspace.com] Sent: Thursday, March 20, 2014 12:13 PM 'project specific functional testing' in the Marconi context is treating Marconi as a complete system, making Marconi API calls verifying the response -

Re: [openstack-dev] [openstack-qa] Graduation Requirements + Scope of Tempest

2014-03-21 Thread Rochelle.RochelleGrober
From: Malini Kamalambal [mailto:malini.kamalam...@rackspace.com] snip We are talking about different levels of testing, 1. Unit tests - which everybody agrees should be in the individual project itself 2. System Tests - 'System' referring to ( limited to), all the components that make

Re: [openstack-dev] [RFC] Tempest without branches

2014-04-04 Thread Rochelle.RochelleGrober
(easier to insert my questions at top of discussion as they are more general) How would test deprecations work in a branchless Tempest? Right now, there is the discussion on removing the XML tests from Tempest, yet they are still valid for Havana and Icehouse. If they get removed, will they

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

2014-07-30 Thread Rochelle.RochelleGrober
From: Gary Kotton [mailto:gkot...@vmware.com] On 7/30/14, 8:22 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote: On Wed, 2014-07-30 at 09:01 +0200, Flavio Percoco wrote: As a stable-maint, I'm always hesitant to review patches I've no understanding on, hence I end up just

Re: [openstack-dev] [Neutron][LBaaS] SSL re-encryption scenario question

2014-04-18 Thread Rochelle.RochelleGrober
+1 for the discussion Remember, a cloud does not always have all its backend co-located. There are sometimes AZs and often other hidden network hops. And, to ask the obvious, what do you think the response is when you whisper NSA in a crowded Google data center? --Rocky -Original

Re: [openstack-dev] [qa] QA Summit Meet-up Atlanta

2014-04-30 Thread Rochelle.RochelleGrober
+1 but I don't get in until late Sunday :-( Any chance you could do this sometime Monday? I'd like to meet the people behind the IRC names and email addresses. --Rocky -Original Message- From: Ken'ichi Ohmichi [mailto:ken1ohmi...@gmail.com] Sent: Wednesday, April 30, 2014 6:29 AM

Re: [openstack-dev] [Ironic] handling drivers that will not be third-party tested

2014-05-21 Thread Rochelle.RochelleGrober
+1 for community contribs and a common place for them to be sourced. From: Devananda van der Veen [mailto:devananda@gmail.com] Sent: Wednesday, May 21, 2014 5:03 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [Ironic] handling drivers that will not be third-party tested

Re: [openstack-dev] [oslo] logging around olso lockutils

2014-09-25 Thread Rochelle.RochelleGrober
+1 Exactly what I was thinking. Semaphore races and deadlocks are important to be able to trace, but the normal production cloud doesn't want to see those messages. What might be even better would be to also put a counter on the semaphores so that if they ever are 1 or 0 they report an

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

2014-09-26 Thread Rochelle.RochelleGrober
Robert Collins on Friday, September 26, 2014 3:33 PM wrote: On 27 September 2014 09:43, Jay Pipes jaypi...@gmail.com wrote: Hi James, thanks for the corrections/explanations. A comment inline (and a further question) :) Oh, good to know. Sorry, my information about Triple-O's undercloud

Re: [openstack-dev] [tempest] [devstack] Generic scripts for Tempest configuration

2014-10-24 Thread Rochelle.RochelleGrober
Hi, Timur. Check out [1]. Boris Pavlovic has been working towards what you want for more than a full release cycle. There are still major issues to be conquered, but having something that gets us part of the way there and can identify what can’t be determined so that the humans have only a