Re: [openstack-dev] [TC][Keystone] Rehashing the Pecan/Falcon/other WSGI debate

On 05/01/2015 09:16 PM, Jamie Lennox wrote: > Hi all, > > At around the time Barbican was applying for incubation there was a > discussion about "supported" WSGI frameworks. From memory the decision > at the time was that Pecan was to be the only supported framework and > that for incubation Barb

Re: [openstack-dev] [swift] Go! Swift!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/30/2015 08:06 PM, John Dickinson wrote: > >> On Apr 30, 2015, at 9:52 AM, Jay Pipes >> wrote: >> >> On 04/30/2015 12:40 PM, John Dickinson wrote: >>> Swift is a scalable and durable storage engine for storing >>> unstructured data. It's bee

Re: [openstack-dev] [magnum] New fedora 21 Atomic images available for testing

On 04/26/2015 02:21 PM, Gregory Haynes wrote: > Excerpts from Steven Dake (stdake)'s message of 2015-04-23 23:27:00 +: >> Hi folks, >> >> I have spent the last couple of days trying to bring some sanity to the >> image building process for Magnum. >> >> I have found a tool which the Atomic ups

Re: [openstack-dev] [pbr] support for 'python setup.py install'

On 04/25/2015 11:46 AM, Monty Taylor wrote: > On 04/25/2015 11:33 AM, Dave Walker wrote: >> I'm not going to pretend it is graceful... but is there a situation >> where _" isn't correct? > > Ooh. This is a worthy avenue to explore ... Ok. After some chatti

Re: [openstack-dev] [pbr] support for 'python setup.py install'

p(name='foobar', > version='1.0', > description='Foobar', > ) > > > -- > Kind Regards, > Dave Walker > > > On 25 April 2015 at 15:27, Monty Taylor wrote: >> On 04/25/2015 09:49 AM, Jeremy Stanley wrote: >>

Re: [openstack-dev] [pbr] support for 'python setup.py install'

On 04/25/2015 09:49 AM, Jeremy Stanley wrote: > On 2015-04-25 12:12:15 +1200 (+1200), Robert Collins wrote: > [...] >> I'd like to make that a little more official: >> - put it in our docs >> - stop testing python setup.py install. > [...] > > And emit a clear error message? (Even if that just m

Re: [openstack-dev] [pbr] support for 'python setup.py install'

On 04/24/2015 08:12 PM, Robert Collins wrote: > In our pbr integration tests we ensure that 'python setup.py install' > works, as well as ensuring that 'pip install' works. But see > http://lists.openstack.org/pipermail/openstack-dev/2013-September/015525.html > - for the last 18 months in pbr we'v

Re: [openstack-dev] [all] Question for the TC candidates

On 04/24/2015 06:28 PM, David Medberry wrote: > On Fri, Apr 24, 2015 at 2:14 AM, Chris Dent wrote: > >> >> What can and should the TC at large, and you specifically, do to ensure >> quality improves for the developers, end-users and operators of >> OpenStack as a full system, both as a project be

Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work]

On 04/18/2015 10:44 AM, Fox, Kevin M wrote: > Replying inline. > >> -Original Message- From: Monty Taylor >> [mailto:mord...@inaugust.com] Sent: Friday, April 17, 2015 7:53 PM >> To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] >> [Nov

Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work]

On 04/17/2015 06:48 PM, Rochelle Grober wrote: > I know the DevStack issue seems to be solved, but I had to > respond.inline > > From: Fox, Kevin M [mailto:kevin@pnnl.gov] Sent: Friday, April > 17, 2015 12:28 To: OpenStack Development Mailing List (not for usage > questions) Subject: Re: [

Re: [openstack-dev] [wsme] [ironic] [ceilometer] [magnum] [kite] [tuskar] WSME unmaintained ?

On 04/16/2015 07:41 AM, Lucas Alvares Gomes wrote: > Hi, > > We have a couple of Openstack projects that uses WSME for their REST > APIs[1], but WSME project looks abandoned. The review stats are not good, > for the last 40 days the project didn't have a single review from a core > reviewer[2], th

Re: [openstack-dev] [all] QPID incompatible with python 3 and untested in gate -- what to do?

On 04/14/2015 08:21 PM, Chris Dent wrote: > On Tue, 14 Apr 2015, Sean Dague wrote: > >> It's time to be honest about the level of support that comes with those >> other backends, deprecate the plugability, and move on to more >> interesting problems. We do have plenty of them to solve. :) Perhaps

Re: [openstack-dev] [all] QPID incompatible with python 3 and untested in gate -- what to do?

On 04/14/2015 01:22 PM, Clint Byrum wrote: > Hello! There's been some recent progress on python3 compatibility for > core libraries that OpenStack depends on[1], and this is likely to open > the flood gates for even more python3 problems to be found and fixed. > > Recently a proposal was made to m

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 04/12/2015 08:01 PM, James Polley wrote: > On Mon, Apr 13, 2015 at 9:12 AM, Monty Taylor wrote: > >> On 04/12/2015 06:43 PM, Robert Collins wrote: >>> Right now we do something that upstream pip considers wrong: we make >>> our requirements.txt be our install_re

Re: [openstack-dev] [all][pbr] splitting our deployment vs install dependencies

On 04/12/2015 06:43 PM, Robert Collins wrote: > Right now we do something that upstream pip considers wrong: we make > our requirements.txt be our install_requires. > > Upstream there are two separate concepts. > > install_requirements, which are meant to document what *must* be > installed to im

Re: [openstack-dev] [OpenStack-docs] What's Up Doc? Apr 10 2015

tack world than an official installation guide; no need to > expose newbies including myself to the complexity of v2. > > Bernd > > -----Original Message- > From: Monty Taylor [mailto:mord...@inaugust.com] > Sent: Sunday, April 12, 2015 6:22 AM > To: OpenStack Develop

Re: [openstack-dev] What's Up Doc? Apr 10 2015

Sorry for top posting - I wasn't subscribed to the doc list before clarkb told me about this thread. Warning ... rage coming ... if you don't want to read rage on a Saturday, I recommend skipping this email. a) There may be a doc bug here, but I'm not 100% convinced it's a doc bug - I'll try to ch

Re: [openstack-dev] [Keystone] SQLite support (migrations, work-arounds, and more), is it worth it?

On 04/03/2015 08:55 PM, Morgan Fainberg wrote: > I am looking forward to the Liberty cycle and seeing the special > casing we do for SQLite in our migrations (and elsewhere). My > inclination is that we should (similar to the deprecation of > eventlet) deprecate support for SQLite in Keystone. In L

Re: [openstack-dev] [Infra] Use of heat for CI of OpenStack

On 04/03/2015 08:55 AM, Maish Saidel-Keesing wrote: > I was wondering.. > > Is the OpenStack CI/CD Infra using Heat in any way? Do the commits > trigger a new build of DevStack/OpenStack that is based on a Heat > Template or just the provisioning of a regular instance and then > deployment of code

Re: [openstack-dev] [all][oslo][clients] Let's speed up start of OpenStack libs and clients by optimizing imports with profimp

On 04/02/2015 06:22 PM, Brant Knudson wrote: > On Thu, Apr 2, 2015 at 4:52 PM, Boris Pavlovic wrote: > >> Hi stackers, >> >> Recently, I started working on speeding up Rally cli. >> >> What I understand immediately is that I don't understand why it takes >> 700-800ms >> to just run "rally versio

Re: [openstack-dev] The Evolution of core developer to maintainer?

On 04/01/2015 05:41 AM, Thierry Carrez wrote: > Joe Gordon wrote: >> I am starting this thread based on Thierry's feedback on [0]. Instead >> of writing the same thing twice, you can look at the rendered html from >> that patch [1]. Neutron tried to go from core to maintainer but after >> input fr

Re: [openstack-dev] [kolla][tripleo] Optional Ansible deployment coming

On 03/31/2015 03:30 PM, Steven Dake (stdake) wrote: > Hey folks, > > One of our community members submitted a review to add optional Ansible > support to deploy OpenStack using Ansible and the containers within Kolla. > Our main objective remains: for third party deployment tools to use Kolla a

Re: [openstack-dev] [infra] What do people think of YAPF (like gofmt, for python)?

On 03/27/2015 07:21 AM, Sean Dague wrote: > On 03/26/2015 06:46 PM, Robert Collins wrote: >> On 27 March 2015 at 09:14, Ryan Brown >> wrote: >> >>> Ooof, that's huge. If we can configure it to be less >>> aggressive I love the *idea* of having everything formatted >>> semantically, but that's a

Re: [openstack-dev] [infra] What do people think of YAPF (like gofmt, for python)?

On 03/25/2015 05:50 PM, Maru Newby wrote: > I am excited by the release of YAPF [1], a gofmt-like too for python. > I think it has the potential to simplify style enforcement, and as > much as I appreciate our current hacking checks, I’d be much happier > not requiring developers to manually confor

Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))

On 03/24/2015 06:05 PM, Kyle Mestery wrote: > On Tue, Mar 24, 2015 at 9:56 AM, Doug Hellmann > wrote: > >> Excerpts from Mark McClain's message of 2015-03-24 10:25:31 -0400: >>> >>> Echoing both Thierry and John. I support Mike’s decision to enforce the >> requirement. Maintaining drivers in the

Re: [openstack-dev] [nova] how to handle vendor-specific API microversions?

On 03/21/2015 01:21 AM, Chris Friesen wrote: > Hi, > > I've recently been playing around a bit with API microversions and I > noticed something that may be problematic. > > The way microversions are handled, there is a monotonically increasing > MAX_API_VERSION value in "nova/api/openstack/api_ve

Re: [openstack-dev] [all] requirements-py{2, 3} and universal wheels

On 03/17/2015 09:07 AM, Monty Taylor wrote: > On 03/16/2015 08:32 PM, Robert Collins wrote: >> On 17 March 2015 at 13:22, Doug Hellmann wrote: >>> Excerpts from Robert Collins's message of 2015-03-17 12:54:00 +1300: >>>> I've raised this in reviews 15

Re: [openstack-dev] [all] requirements-py{2, 3} and universal wheels

On 03/16/2015 08:32 PM, Robert Collins wrote: > On 17 March 2015 at 13:22, Doug Hellmann wrote: >> Excerpts from Robert Collins's message of 2015-03-17 12:54:00 +1300: >>> I've raised this in reviews 157135 and 153966, but I think it deserves >>> a thread of its own. >>> >>> I think universal whee

Re: [openstack-dev] [Glance] [all] python-glanceclient release 0.16.1

On 03/05/2015 12:02 AM, Nikhil Komawar wrote: > The python-glanceclient release management team is pleased to announce: > python-glanceclient version 0.16.1 has been released on Thursday, Mar 5th > around 04:56 UTC. > > For more information, please find the details at: > > > https://lau

Re: [openstack-dev] Removal of copyright statements above the Apache 2.0 license header

On 02/17/2015 07:58 AM, Daniel P. Berrange wrote: > On Tue, Feb 17, 2015 at 01:16:46PM +0100, Christian Berendt wrote: >> On 02/17/2015 12:05 PM, Daniel P. Berrange wrote: >>> In section 4.(c) the LICENSE text says >>> >>> (c) You must retain, in the Source form of any Derivative Works >>>

Re: [openstack-dev] [Glance][Artifacts] Object Version format: SemVer vs pep440

On 02/10/2015 10:28 AM, Alexander Tivelkov wrote: > Hi folks, > > One of the key features that we are adding to Glance with the > introduction of Artifacts is the ability to have multiple versions of > the same object in the repository: this gives us the possibility to > query for the latest versi

Re: [openstack-dev] [horizon] JavaScript docs?

On 02/04/2015 12:48 PM, Michael Krotscheck wrote: > I agree. StoryBoard's storyboard-webclient project has a lot of existing > code already that's pretty well documented, but without knowing what > documentation system we were going to settle on we never put any rule > enforcement in place. If some

Re: [openstack-dev] [nova][cinder][neutron][security] Rootwrap on root-intensive nodes

On 02/04/2015 06:57 AM, Daniel P. Berrange wrote: > On Wed, Feb 04, 2015 at 11:58:03AM +0100, Thierry Carrez wrote: >> The first one is performance -- each call would spawn a Python >> interpreter which would then call the system command. This was fine when >> there were just a few calls here and t

Re: [openstack-dev] [oslo.db] PyMySQL review

On 01/28/2015 06:33 PM, Johannes Erdfelt wrote: > On Wed, Jan 28, 2015, Mike Bayer wrote: >> I can envision turning this driver into a total monster, adding >> C-speedups where needed but without getting in the way of async >> patching, adding new APIs for explicit async, and everything else. >> H

Re: [openstack-dev] [all][tc] SQL Schema Downgrades and Related Issues

On 01/29/2015 11:06 AM, Morgan Fainberg wrote: > As a quick preface, today there is the assumption you can upgrade and > downgrade your SQL Schema. For the most part we do our best to test all of > this in our unit tests (do upgrades and downgrades land us in the same > schema). What isn’t clear

Re: [openstack-dev] [tc] Take back the naming process

On 01/28/2015 01:29 AM, Thierry Carrez wrote: > Monty Taylor wrote: >> You'll notice that I did say in my suggestion that ANYONE should be able >> to propose a name - I believe that would include non-dev people. Since >> the people in question are marketing people, I

Re: [openstack-dev] [tc] Take back the naming process

ry careful with decisions, however well meaning, that take place outside of the public context. So please accept my apology for my language - and please engage with me in the discussion around how to make sure people don't inadvertently begin to feel disenfranchised. Thanks, Monty On 01/27/

Re: [openstack-dev] [OpenStack Foundation] [tc] Take back the naming process

On 01/27/2015 10:35 PM, James E. Blair wrote: > Lauren Sell writes: > >> Hey Monty, >> >> I’d like to weigh in here, because I think there have been some >> misunderstandings around Lemming-gate. I’m glad you raised your >> concerns; it’s a good test of release naming for us all to discuss and >>

Re: [openstack-dev] [tc] Take back the naming process

On 01/27/2015 06:05 PM, Jonathan Bryce wrote: > >> On Jan 27, 2015, at 3:50 PM, Monty Taylor wrote: >> >> I do not like how we are selecting names for our releases right now. >> The current process is autocratic and opaque and not fun - which is the >> exact oppo

[openstack-dev] [tc] Take back the naming process

I do not like how we are selecting names for our releases right now. The current process is autocratic and opaque and not fun - which is the exact opposite of what a community selected name should be. I propose: * As soon as development starts on release X, we open the voting for the name of rele

Re: [openstack-dev] [all] "All rights reserved" V.S. "Apache license"

On 01/17/2015 03:27 AM, ZhiQiang Fan wrote: > Hi, developers > > I have observed that some source code files in our projects have been > announced as "Copyright xxx, All rights reserved", and then followed by a > "Apache License" > > Is this right? any conflict? > > And if one company claims tha

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

On 12/09/2014 03:39 AM, Sean Dague wrote: > I'd like to propose that for hacking 1.0 we drop 2 groups of rules entirely. > > 1 - the entire H8* group. This doesn't function on python code, it > functions on git commit message, which makes it tough to run locally. It > also would be a reason to pre

Re: [openstack-dev] [docs] Older Developer documentation Icehouse? Havana?

On 12/02/2014 06:14 AM, Russell Sim wrote: > Hi, > > From what I can see it seems like the developer documentation available > on the OpenStack website is generated from the git repositories. > > http://docs.openstack.org/developer/openstack-projects.html > > Are older versions of this documenta

Re: [openstack-dev] [NFV][Telco] pxe-boot

On 11/25/2014 05:33 PM, Angelo Matarazzo wrote: > > Hi all, > my team and I are working on pxe boot feature very similar to the > "Discless VM" one in Active blueprint list[1] > The blueprint [2] is no longer active and we created a new spec [3][4]. > > Nova core reviewers commented our spec and

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 11/25/2014 03:40 PM, Richard Jones wrote: > On Wed Nov 26 2014 at 3:36:27 AM Thomas Goirand wrote: > >> On 11/21/2014 08:31 PM, Donald Stufft wrote: >>> On Nov 21, 2014, at 3:59 AM, Thomas Goirand wrote: > > I'm not sure I understand the meaning behind this question. "bower

Re: [openstack-dev] [cinder] Anyone Using the Open Solaris ZFS Driver?

On 11/24/2014 10:14 AM, Drew Fisher wrote: > > > On 11/17/14 10:27 PM, Duncan Thomas wrote: >> Is the new driver drop-in compatible with the old one? IF not, can >> existing systems be upgraded to the new driver via some manual steps, or >> is it basically a completely new driver with similar fun

Re: [openstack-dev] [all] removing XML testing completely from Tempest

On 11/24/2014 12:36 PM, Lance Bragstad wrote: > We are in the process of removing XML support from Keystone [1] and have > provided > configuration options to Tempest for testing XML in older releases [2]. > However, the > identity client is still tightly coupled to XML test cases. We can either >

Re: [openstack-dev] [oslo] Add a new aiogreen executor for Oslo Messaging

On 11/23/2014 06:13 PM, Robert Collins wrote: > On 24 November 2014 at 11:01, victor stinner > wrote: >> Hi, >> >> I'm happy to announce you that I just finished the last piece of the puzzle >> to add support for trollius coroutines in Oslo Messaging! See my two changes: >> >> * Add a new aiogree

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 11/12/2014 02:40 AM, Richard Jones wrote: > On 12 November 2014 18:17, Matthias Runge wrote: > >> On 11/11/14 10:53, Jiri Tomasek wrote: >>> Hey, >>> >>> Thanks for writing this up! >> The Storyboard project has successfully integrated these tools into the OpenStack CI environment. >

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 11/12/2014 02:17 AM, Matthias Runge wrote: > On 11/11/14 10:53, Jiri Tomasek wrote: >> Hey, >> >> Thanks for writing this up! > >>> The Storyboard project has successfully integrated these tools into >>> the OpenStack CI environment. > > OpenStack CI and distributors are different, because Ope

Re: [openstack-dev] MOS Infra weekly report (29 Oct 2014 - 31 Oct 2014)

On 10/31/2014 05:03 PM, Sergey Lukjanov wrote: > Heh, wrong mailing list :( Now I know your sekrits... > On Fri, Oct 31, 2014 at 7:02 PM, Sergey Lukjanov > wrote: > >> Hi colleagues, >> >> here you can find the weekly report for MOS Infra activity - >> https://mirantis.jira.com/wiki/display/MOS

Re: [openstack-dev] [All] Finalizing cross-project design summit track

After looking over the > etherpad of proposed cross project sessions I think there is one glaring > omission: the SDK. In the "Kilo Cycle Goals Exercise" thread [0] having a > real SDK was one of the top answers. Many folks had great responses that > clearly explained the i

Re: [openstack-dev] TC election by the numbers

On 10/30/2014 04:45 AM, Clint Byrum wrote: > Excerpts from Jeremy Stanley's message of 2014-10-29 18:37:42 -0700: >> On 2014-10-29 18:27:48 -0700 (-0700), Clint Byrum wrote: >>> IIRC, there is no method for removing foundation members. So there >>> are likely a number of people listed who have move

Re: [openstack-dev] FreeBSD host support

On 10/27/2014 06:39 AM, Michael Still wrote: > On Tuesday, October 21, 2014, Roman Bogorodskiy > wrote: > >> On Mon, Oct 20, 2014 at 10:19 PM, Joe Gordon > > wrote: >>> On Sat, Oct 18, 2014 at 10:04 AM, Roman Bogorodskiy < >> rbogorods...@mirantis.com > wrote: >> > > [snip] > > High level

Re: [openstack-dev] [DevStack] Proposal - add support for Markdown for docs

On 10/21/2014 10:37 AM, Collins, Sean wrote: > I do see mentions of gh-pages in the build_docs.sh script - is > devstack.org redirect to GitHub? > Nope - it used to be. It's now built and published like the rest of openstack docs. Now - I don't want to get in the way of the work you're wanting t

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

On 10/20/2014 07:11 PM, Devananda van der Veen wrote: > Hi all, > > I was reminded in the Ironic meeting today that the words "hardware > discovery" are overloaded and used in different ways by different > people. Since this is something we are going to talk about at the > summit (again), I'd like

Re: [openstack-dev] Usage of @author tags in the header of Python files

On 10/08/2014 10:45 AM, John Griffith wrote: > On Wed, Oct 8, 2014 at 11:15 AM, David Lyle wrote: > >> I don't see any need nor benefit from the tags. We should remove them if >> convenient. >> >> David >> On Oct 8, 2014 3:02 AM, "Duncan Thomas" wrote: >> >>> On 8 October 2014 10:39, Ihar Hrachy

Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading

Regards >> >> Chaoyi Huang ( joehuang ) >> ________ >> From: Joshua Harlow [harlo...@outlook.com] >> Sent: 07 October 2014 12:21 >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-dev]

[openstack-dev] TC candidacy

Hi everybody! I'd like to announce my candidacy for re-election to the TC. tl;dr - Vote for me or vote for someone else you prefer I've been around the project for quite a while, having been on the phone calls where we were discussing the name OpenStack - although I'll admit I had absolutely zer

Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack cascading

On 09/30/2014 12:07 PM, Tim Bell wrote: >> -Original Message- >> From: John Garbutt [mailto:j...@johngarbutt.com] >> Sent: 30 September 2014 15:35 >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenS

Re: [openstack-dev] [infra] Nominating Sean Dague for project-config-core

On 09/26/2014 08:35 AM, James E. Blair wrote: > I'm pleased to nominate Sean Dague to the project-config core team. > > The project-config repo is a constituent of the Infrastructure Program > and has a core team structured to be a superset of infra-core with > additional reviewers who specialize

Re: [openstack-dev] [infra] Nominating Andreas Jaeger for project-config-core

On 09/26/2014 08:35 AM, James E. Blair wrote: > I'm pleased to nominate Andreas Jaeger to the project-config core team. > > The project-config repo is a constituent of the Infrastructure Program > and has a core team structured to be a superset of infra-core with > additional reviewers who special

Re: [openstack-dev] [infra] Nominating Anita Kuno for project-config-core

On 09/26/2014 08:34 AM, James E. Blair wrote: > I'm pleased to nominate Anito Kuno to the project-config core team. > > The project-config repo is a constituent of the Infrastructure Program > and has a core team structured to be a superset of infra-core with > additional reviewers who specialize

Re: [openstack-dev] [neutron] [infra] Python 2.6 tests can't possibly be passing in neutron

On 09/22/2014 10:58 AM, Kevin L. Mitchell wrote: > On Mon, 2014-09-22 at 10:32 -0700, Armando M. wrote: >> What about: >> >> https://github.com/openstack/neutron/blob/master/test-requirements.txt#L12 > > Pulling in ordereddict doesn't do anything if your code doesn't use it > when OrderedDict isn'

Re: [openstack-dev] [Neutron] - what integration with Keystone is allowed?

On 09/21/2014 10:57 PM, Nader Lahouti wrote: > Thanks Kevin for bring it up in the ML, I was looking for a guideline or > any document to clarify issues on this subject. > > I was told, even using keystone API in neutron is not permitted. I recognize that I'm potentially without context for neutr

Re: [openstack-dev] [all] In defence of faking

On 09/22/2014 08:58 AM, Matthew Booth wrote: > If you missed the inaugural OpenStack Bootstrapping Hour, it's here: > http://youtu.be/jCWtLoSEfmw . I think this is a fantastic idea and big > thanks to Sean, Jay and Dan for doing this. I liked the format, the > informal style and the content. Unfort

Re: [openstack-dev] [Heat][Zaqar] Integration plan moving forward

On 09/19/2014 03:42 PM, Zane Bitter wrote: > On 19/09/14 14:34, Clint Byrum wrote: >> Excerpts from Flavio Percoco's message of 2014-09-19 02:37:08 -0700: >>> On 09/18/2014 11:51 AM, Angus Salkeld wrote: On 18/09/2014 7:11 PM, "Flavio Percoco" >>> > wrote: >

Re: [openstack-dev] usability anti-pattern, part 2

> We may not want a BDFL, but we NEED someone to say NO when necessary for > the sake of the entire project. Jeez, now I'm sounding all enterprisey. > > On Fri, Sep 19, 2014 at 9:01 PM, Monty Taylor wrote: > >> except exc.Unauthorized: >>

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

On 09/19/2014 10:50 AM, Vishvananda Ishaya wrote: > > On Sep 19, 2014, at 10:14 AM, John Dickinson wrote: > >> >> On Sep 19, 2014, at 5:46 AM, John Griffith >> wrote: >> >>> >>> >>> On Fri, Sep 19, 2014 at 4:33 AM, Thierry Carrez >>> wrote: >>> Vishvananda Ishaya wrote: Great writeup. I

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

On 09/19/2014 10:14 AM, John Dickinson wrote: > > On Sep 19, 2014, at 5:46 AM, John Griffith > wrote: > >> >> >> On Fri, Sep 19, 2014 at 4:33 AM, Thierry Carrez >> wrote: Vishvananda Ishaya wrote: >>> Great writeup. I think there are some great concrete suggestions >>> here. >>> >>> A couple

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

On 09/19/2014 03:29 AM, Thierry Carrez wrote: > Monty Taylor wrote: >> 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 &g

[openstack-dev] usability anti-pattern, part 2

except exc.Unauthorized: raise exc.CommandError("Invalid OpenStack credentials.") except exc.AuthorizationFailure: raise exc.CommandError("Unable to authorize user") This is pervasive enough that both of those exceptions come from openstack.common. Anyone?

[openstack-dev] usability anti-pattern

Hey, Not to name names, but some of our client libs do this: client.Client(API_VERSION, os_username, ... ) I'm pretty sure they got the idea from python-glanceclient, so I blame Brian Waldon, since he left us for CoreOS. PLEASE STOP DOING THIS - IT CAUSES BABIES TO CRY. MORE. As a developer,

Re: [openstack-dev] [nova] Expand resource name allowed characters

On 09/17/2014 10:44 AM, Day, Phil wrote: >> -Original Message- >> From: Jay Pipes [mailto:jaypi...@gmail.com] >> Sent: 12 September 2014 19:37 >> To: openstack-dev@lists.openstack.org >> Subject: Re: [openstack-dev] [nova] Expand resource name allowed >> characters >> >> Had to laugh about

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

On 09/18/2014 01:12 PM, Dean Troyer wrote: > On Thu, Sep 18, 2014 at 1:53 PM, Monty Taylor wrote: > >> 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. >>

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

On 09/17/2014 08:48 PM, John Dickinson wrote: > > On Sep 17, 2014, at 8:43 PM, Jay Faulkner wrote: > >> Comments inline. >> >>> -Original Message- >>> From: Monty Taylor [mailto:mord...@inaugust.com] >>> Sent: Wednesday,

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

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 Enjoy. Monty ___ OpenStack-dev mailing list OpenStack-dev@lists.

Re: [openstack-dev] pbr alpha and dev version handling

On 09/17/2014 03:09 PM, Doug Hellmann wrote: > Earlier today we discovered a problem with the way pbr is generating > dev version numbers for commits following tags using alpha > pre-version suffixes [1]. Basically what’s happening is a commit > following a tag like 1.3.0.0a3 is coming out as a 1.3

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

On 09/17/2014 04:42 PM, Rochelle.RochelleGrober wrote: > 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 at

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

On 09/10/2014 10:29 AM, Stefano Maffulli wrote: On 09/05/2014 12:36 PM, Tim Bell wrote: How can the average deployer know whether a stackforge is a. An early prototype which has completed (such as some of the early LBaaS packages) b. A project which has lost its initial steam and fur

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

On 09/09/2014 07:04 PM, Samuel Merritt wrote: On 9/9/14, 4:47 PM, Devananda van der Veen wrote: On Tue, Sep 9, 2014 at 4:12 PM, Samuel Merritt wrote: On 9/9/14, 12:03 PM, Monty Taylor wrote: [snip] So which is it? Because it sounds like to me it's a thing that actually does NOT ne

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

On 09/04/2014 01:30 AM, Clint Byrum wrote: Excerpts from Flavio Percoco's message of 2014-09-04 00:08:47 -0700: Greetings, Last Tuesday the TC held the first graduation review for Zaqar. During the meeting some concerns arose. I've listed those concerns below with some comments hoping that it w

Re: [openstack-dev] [tripleo] Puppet elements support

On 09/08/2014 04:11 PM, Emilien Macchi wrote: Hi TripleO community, I would be really interested by helping to bring Puppet elements support in TripleO. So far I've seen this work: https://github.com/agroup/tripleo-puppet-elements/tree/puppet_dev_heat which is a very good bootstrap but really ou

Re: [openstack-dev] how to provide tests environments for python things that require C extensions

On 09/05/2014 07:21 AM, Monty Taylor wrote: On 09/05/2014 06:32 AM, Sean Dague wrote: While reviewing this zookeeper service group fix in Nova - https://review.openstack.org/#/c/102639/ it was exposed that the zookeeper tests aren't running in infra. The crux of the issue is that zook

Re: [openstack-dev] Standard virtualenv for docs building

On 09/08/2014 11:59 AM, Joshua Harlow wrote: Hi all, I just wanted to get some feedback on a change that I think will make the docs building process more understood, Currently there is a script @ https://github.com/openstack-infra/config/blob/master/modules/openstack_project/files/slave_scrip

Re: [openstack-dev] Kilo Cycle Goals Exercise

On 09/03/2014 08: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 priorities for Kilo [0]. To that end

[openstack-dev] Mirror changes

Hey all! A few of quick notes about PyPI mirrors and the gate. Firstly - today we just rolled out per-cloud-region mirrors. Hopefully this eliminate issues we have from time to time with connections to PyPI timing out. We have a selector script running on node creation, so nodes in, say, Rack

[openstack-dev] [nova][neutron] default allow security group

Hi! I've decided that as I have problems with OpenStack while using it in the service of Infra, I'm going to just start spamming the list. Please make something like this: neutron security-group-create default --allow-every-damn-thing Right now, to make security groups get the hell out of ou

Re: [openstack-dev] how to provide tests environments for python things that require C extensions

On 09/05/2014 06:32 AM, Sean Dague wrote: While reviewing this zookeeper service group fix in Nova - https://review.openstack.org/#/c/102639/ it was exposed that the zookeeper tests aren't running in infra. The crux of the issue is that zookeeper python modules are C extensions. So you have to e

Re: [openstack-dev] Announcing Gertty 1.0.0: A console interface to Gerrit

On 09/04/2014 04:17 PM, James E. Blair wrote: Announcing Gertty 1.0.0 Gertty is a console-based interface to the Gerrit Code Review system. If that doesn't sound interesting to you, then just skip right on to the next message. This mailing list gets a lot of traffic, and it's going to take you

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

On 08/05/2014 09:03 AM, 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 processes, tools

Re: [openstack-dev] [Nova][Neutron][Technical Committee] nova-network -> Neutron. Throwing a wrench in the Neutron gap analysis

On 08/05/2014 09:34 AM, Mike Spreitzer wrote: Monty Taylor wrote on 08/05/2014 12:27:14 PM: On 08/05/2014 09:18 AM, Jay Pipes wrote: Hello stackers, TC, Neutron contributors, At the Nova mid-cycle meetup last week in Oregon, during the discussion about the future of nova-network, the

Re: [openstack-dev] [Nova][Neutron][Technical Committee] nova-network -> Neutron. Throwing a wrench in the Neutron gap analysis

On 08/05/2014 09:18 AM, Jay Pipes wrote: Hello stackers, TC, Neutron contributors, At the Nova mid-cycle meetup last week in Oregon, during the discussion about the future of nova-network, the topic of nova-network -> Neutron migration came up. For some reason, I had been clueless about the det

Re: [openstack-dev] [nova][libvirt][baremetal] Nova Baremetal's Usage of Components from Libvirt

On 08/04/2014 03:54 PM, Solly Ross wrote: Hello All, So, I'm working on https://review.openstack.org/#/c/111459/, and have encountered an issue. It seems that the Nova Baremetal driver uses the ImageCacheManager from the Libvirt driver. For various reasons (see the commit), the ImageCacheMan

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

On 07/30/2014 03:34 PM, 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? What is the benefit

Re: [openstack-dev] [gate] The gate: a failure analysis

On 07/28/2014 02:32 PM, Angus Lees wrote: On Mon, 28 Jul 2014 10:22:07 AM Doug Hellmann wrote: On Jul 28, 2014, at 2:52 AM, Angus Lees wrote: On Mon, 21 Jul 2014 04:39:49 PM David Kranz wrote: On 07/21/2014 04:13 PM, Jay Pipes wrote: On 07/21/2014 02:03 PM, Clint Byrum wrote: Thanks Matthew

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

On 07/16/2014 07:27 PM, Vishvananda Ishaya wrote: > > On Jul 16, 2014, at 8:28 AM, Daniel P. Berrange wrote: > >> On Wed, Jul 16, 2014 at 08:12:47AM -0700, Clark Boylan wrote: >> >>> I am worried that we would just regress to the current process because >>> we have tried something similar to thi

Re: [openstack-dev] [TripleO] pypi-mirror is now unsupported - what do we do now?

On 07/10/2014 02:44 PM, Richard Jones wrote: > On 10 July 2014 23:27, Mulcahy, Stephen wrote: >> When I last tested bandersnatch, it didn’t work well behind a proxy (in > fact most of the existing pypi mirroring tools suffered from the same > problem) – pypi-mirror has worked extremely well for mi

Re: [openstack-dev] [OpenStack-Dev] Commit messages and lawyer speak

On 07/07/2014 08:18 PM, Anne Gentle wrote: > Hi John, > There's a thread started on the legal-discuss list: > http://lists.openstack.org/pipermail/legal-discuss/2014-July/000304.html > Probably want to follow along there. Hi! a) I agree with Anne - so I have responded there. b) I agree with Robe

Re: [openstack-dev] [infra][oslo][neutron] Need help getting oslo.messaging 1.4.0.0a2 in global requirements

On 06/30/2014 02:28 PM, Mark McLoughlin wrote: > On Mon, 2014-06-30 at 16:52 +, Paul Michali (pcm) wrote: >> I have out for review 103536 to add this version to global >> requirements, so that Neutron has an oslo fix (review 102909) for >> encoding failure, which affects some gate runs. This re

<    1   2   3   4   5   6   7   8   9   >