Re: [openstack-dev] [glance] proposed priorities for Mitaka

2015-09-14 Thread Monty Taylor
On 09/15/2015 02:06 AM, Clint Byrum wrote: Excerpts from Doug Hellmann's message of 2015-09-14 13:46:16 -0700: Excerpts from Clint Byrum's message of 2015-09-14 13:25:43 -0700: Excerpts from Doug Hellmann's message of 2015-09-14 12:51:24 -0700: Excerpts from Flavio Percoco's message of

Re: [openstack-dev] [glance] tasks (following "proposed priorities for Mitaka")

2015-09-14 Thread Monty Taylor
On 09/14/2015 04:58 PM, Brian Rosmaita wrote: Apologies for forking the thread, but there was way too much in Doug's email (and Flavio's response) and I only want to make a few points about tasks. Please read Doug's original email and Flavio's reply at some point, preferably before you read

Re: [openstack-dev] OpenStack support for Amazon Concepts - was Re: cloud-init IPv6 support

2015-09-06 Thread Monty Taylor
On 09/05/2015 06:19 PM, Sean M. Collins wrote: On Fri, Sep 04, 2015 at 04:20:23PM EDT, Kevin Benton wrote: Right, it depends on your perspective of who 'owns' the API. Is it cloud-init or EC2? At this point I would argue that cloud-init is in control because it would be a large undertaking to

[openstack-dev] This is what disabled-by-policy should look like to the user

2015-09-04 Thread Monty Taylor
mordred@camelot:~$ neutron net-create test-net-mt Policy doesn't allow create_network to be performed. Thank you neutron. Excellent job. Here's what that looks like at the REST layer: DEBUG: keystoneclient.session RESP: [403] date: Fri, 04 Sep 2015 13:55:47 GMT connection: close content-type:

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

2015-09-04 Thread Monty Taylor
On 09/04/2015 10:55 AM, Morgan Fainberg wrote: On Sep 4, 2015, at 07:04, Monty Taylor <mord...@inaugust.com> wrote: mordred@camelot:~$ neutron net-create test-net-mt Policy doesn't allow create_network to be performed. Thank you neutron. Excellent job. Here's what that look

Re: [openstack-dev] This is what disabled-by-policy should look like to the user

2015-09-04 Thread Monty Taylor
On 09/04/2015 01:42 PM, John Griffith wrote: On Fri, Sep 4, 2015 at 11:35 AM, Mathieu Gagné <mga...@internap.com> wrote: On 2015-09-04 12:50 PM, Monty Taylor wrote: On 09/04/2015 10:55 AM, Morgan Fainberg wrote: Obviously the translation of errors would be more difficult if the en

Re: [openstack-dev] [api] [wsme] [ceilometer] Replacing WSME with _____ ?

2015-08-28 Thread Monty Taylor
On 08/28/2015 08:32 AM, Julien Danjou wrote: On Fri, Aug 28 2015, Chris Dent wrote: This morning I kicked off a quick spec for replacing WSME in Ceilometer with ... something: https://review.openstack.org/#/c/218155/ This is because not only is WSME not that great, it also results in

Re: [openstack-dev] [api] [wsme] [ceilometer] Replacing WSME with _____ ?

2015-08-28 Thread Monty Taylor
On 08/28/2015 08:32 AM, Julien Danjou wrote: On Fri, Aug 28 2015, Chris Dent wrote: This morning I kicked off a quick spec for replacing WSME in Ceilometer with ... something: https://review.openstack.org/#/c/218155/ This is because not only is WSME not that great, it also results in

Re: [openstack-dev] [api] [wsme] [ceilometer] Replacing WSME with _____ ?

2015-08-28 Thread Monty Taylor
On 08/28/2015 07:36 AM, Lucas Alvares Gomes wrote: Hi, If you just want to shoot the breeze please respond here. If you have specific comments on the spec please response there. I have been thinking about doing it for Ironic as well so I'm looking for options. IMHO after using WSME I would

Re: [openstack-dev] [Neutron] netaddr and abbreviated CIDR format

2015-08-22 Thread Monty Taylor
On 08/21/2015 03:33 PM, Jay Pipes wrote: On 08/21/2015 02:34 PM, Sean M. Collins wrote: So - the tl;dr is that I don't think that we should accept inputs like the following: x - 192 x/y - 10/8 x.x/y - 192.168/16 x.x.x/y - 192.168.0/24 which are equivalent to:: x.0.0.0/y -

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

2015-07-31 Thread Monty Taylor
On 08/01/2015 03:40 AM, Mike Perez wrote: On Fri, Jul 31, 2015 at 8:56 AM, Joshua Harlow harlo...@outlook.com wrote: ...random thought here, skip as needed... in all honesty orchestration solutions like mesos (http://mesos.apache.org/assets/img/documentation/architecture3.jpg), map-reduce

Re: [openstack-dev] OPENSTACK with CEPH storage backend cant down size an instance

2015-07-24 Thread Monty Taylor
On 07/24/2015 12:47 PM, Clint Byrum wrote: Excerpts from James Galvin's message of 2015-07-24 09:08:36 -0700: Hi All I am having some trouble with down sizing an instance, I can resize the instance from say small flavour to medium flavour but when trying to resize the instance back from

Re: [openstack-dev] [all] Setting epoch in setup.cfg??

2015-07-14 Thread Monty Taylor
On 07/14/2015 11:08 AM, Ian Cordasco wrote: On 7/13/15, 16:19, Joshua Harlow harlo...@outlook.com wrote: Ian Cordasco wrote: On 7/13/15, 15:09, Dave Walkerem...@daviey.com wrote: On 13 Jul 2015 8:52 pm, Ian Cordascoian.corda...@rackspace.com wrote: On 7/13/15, 03:38, Thierry

[openstack-dev] OpenStack Mitaka (三鷹) - Our next release name has been selected

2015-07-14 Thread Monty Taylor
Hi everybody! Ok. There is nothing more actually useful I can say that isn't in the subject line. As I mentioned previously, the preliminary results from our name election are here: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4983776e190c8dbc As you are all probably aware by now, as a

Re: [openstack-dev] [testing] moving testrepository *outside* the tox venv

2015-07-10 Thread Monty Taylor
On 07/10/2015 07:19 PM, Robert Collins wrote: On 10 July 2015 at 01:59, Morgan Fainberg morgan.fainb...@gmail.com wrote: Or a database per python major version (or at least gracefully handle the incompatibility). So that would partition the data, and the whole point of test *repository* is

Re: [Openstack] [openstack-community] [openstack-dev] OpenStack Meiji (明治) - Our next release name has been selected

2015-07-08 Thread Monty Taylor
to anything. Cheers Tristan *From:* Jaesuk Ahn [mailto:bluejay@gmail.com] *Sent:* Wednesday, 8 July 2015 2:41 PM *To:* OpenStack Development Mailing List; Openstack Users; Monty Taylor; Community User Groups, OpenStack *Subject:* Re: [openstack-community] [openstack-dev] OpenStack

[Openstack] Rescinding the M name decision

2015-07-08 Thread Monty Taylor
Hi everyone! In light of issues raised concerning the initially selected name for the M release (Meiji), that name will not be used. It turns out fully open community and fully inclusive collaboration is a hard thing to get right. On the one hand, we do not want to exclude anyone's input or

[openstack-dev] OpenStack Meiji (明治) - Our next release name has been selected

2015-07-06 Thread Monty Taylor
Hi everybody! Ok. There is nothing more actually useful I can say that isn't in the subject line. As I mentioned previously, the preliminary results from our name election are here: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4983776e190c8dbc As a follow on step, the OpenStack Foundation

[Openstack] OpenStack Meiji (明治) - Our next release name has been selected

2015-07-06 Thread Monty Taylor
Hi everybody! Ok. There is nothing more actually useful I can say that isn't in the subject line. As I mentioned previously, the preliminary results from our name election are here: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4983776e190c8dbc As a follow on step, the OpenStack Foundation

Re: [openstack-dev] [TripleO] diskimage-builder 1.0.0

2015-06-29 Thread Monty Taylor
On 06/29/2015 08:44 AM, Gregory Haynes wrote: Hello all, DIB has come a long way and we seem to have a fairly stable interface for the elements and the image creation scripts. As such, I think it's about time we commit to a major version release. Hopefully this can give our users the

Re: [openstack-dev] [cinder][glance][nova] Python 3 coming!

2015-06-26 Thread Monty Taylor
On 06/26/2015 04:26 AM, Victor Stinner wrote: Hi, The Python 3.4 gate (py34) of cinder, glance and nova just became voting. You now have to write Python code compatible with Python 2.7 and 3.4. WOOHOO! Well done! If the py34 check job fails on your patch, you may try to rebase it to get

Re: [openstack-dev] [all] Any other downstream developers having problems with pbr?

2015-06-26 Thread Monty Taylor
On 06/26/2015 07:24 AM, Clark Boylan wrote: On Fri, Jun 26, 2015, at 04:01 AM, Matthew Booth wrote: I wrote this: https://review.openstack.org/#/c/195983/1/tools/de-pbr.py,cm Ideally we'd fix PBR, but this seems to be expected behaviour. Thoughts? Use the PBR_VERSION env var [1], it exists

Re: [openstack-dev] Scheduler hints, API and Objects

2015-06-25 Thread Monty Taylor
On 06/25/2015 10:22 AM, Andrew Laski wrote: I have been growing concerned recently with some attempts to formalize scheduler hints, both with API validation and Nova objects defining them, and want to air those concerns and see if others agree or can help me see why I shouldn't worry.

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-25 Thread Monty Taylor
On 06/25/2015 01:35 PM, Devananda van der Veen wrote: Sean's point and Dmitri's are similar. There are APIs for projects which do not have official team or program names. And some teams may produce more than one forward-facing service. Naming the API based in the team name doesn't make

Re: [openstack-dev] [devstack] apache wsgi application support

2015-06-24 Thread Monty Taylor
On 06/24/2015 02:05 PM, Sean Dague wrote: On 06/24/2015 01:51 PM, Brant Knudson wrote: On Wed, Jun 24, 2015 at 7:27 AM, Chris Dent chd...@redhat.com mailto:chd...@redhat.com wrote: On Wed, 24 Jun 2015, Sean Dague wrote: On 06/24/2015 07:57 AM, Chris Dent wrote:

Re: [openstack-dev] [cinder][stable] Cinder client broken in Juno

2015-06-23 Thread Monty Taylor
On 06/23/2015 11:49 AM, Mike Perez wrote: There was a bug raised [1] from some large deployments that the Cinder client 1.2.0 and beyond is not working because of version discovery. Unfortunately it's not taking into account of deployments that have a proxy. Cinder client asks Keystone to

Re: [openstack-dev] [Fuel][Fuel-library] Using librarian-puppet to manage upstream fuel-library modules

2015-06-23 Thread Monty Taylor
On 06/23/2015 01:51 PM, Alex Schultz wrote: Hello everyone, I took some time this morning to write out a document[0] that outlines one possible ways for us to manage our upstream modules in a more consistent fashion. I know we've had a few emails bouncing around lately around this topic of

Re: [openstack-dev] [all][requirements] requirements reviews falling behind

2015-06-22 Thread Monty Taylor
On 06/22/2015 02:49 PM, Doug Hellmann wrote: We have quite a long list of patches to the openstack/requirements repository, many of which are straightforward changes to increase the minimums for libraries we develop within the community (meaning we are holding up projects from using new

[Openstack] M Naming Poll ended - results still need to clear legal

2015-06-22 Thread Monty Taylor
Hey all! The M naming poll has concluded. I'd say and the winner is ... except we still need to get the winning choice(s) vetted for legal entanglements. Feel free to go and look at the results, they are publicly available - but please DON'T start making t-shirts or having parties (ok, have as

[openstack-dev] M Naming Poll ended - results still need to clear legal

2015-06-22 Thread Monty Taylor
Hey all! The M naming poll has concluded. I'd say and the winner is ... except we still need to get the winning choice(s) vetted for legal entanglements. Feel free to go and look at the results, they are publicly available - but please DON'T start making t-shirts or having parties (ok, have as

Re: [openstack-dev] [Stackalytics] Complementary projects

2015-06-19 Thread Monty Taylor
On 06/19/2015 11:40 AM, Jay Pipes wrote: On 06/19/2015 10:31 AM, Joe Gordon wrote: On Jun 19, 2015 3:56 PM, Jay Pipes jaypi...@gmail.com mailto:jaypi...@gmail.com wrote: On 06/19/2015 09:19 AM, Ilya Shakhat wrote: Some reasons of having complementary projects in Stackalytics: *

Re: [openstack-dev] [Neutron][DevStack] Standing on the shoulders of giants - Linux Bridge testing at the gate

2015-06-19 Thread Monty Taylor
On 06/19/2015 03:20 AM, Sean M. Collins wrote: Hi, I wanted to give a quick update on the new experimental job for testing the Linux Bridge mechanism driver for Neutron. I believe that there is only one patch that needs to be merged, in order to get the job to a point where we could move

Re: [openstack-dev] [all] setup.py executable bit

2015-06-18 Thread Monty Taylor
On 06/17/2015 03:24 PM, Ian Cordasco wrote: On 6/17/15, 13:53, Jeremy Stanley fu...@yuggoth.org wrote: On 2015-06-17 14:47:48 -0400 (-0400), Doug Hellmann wrote: +1 both to using -x and to removing the shebang. Agreed. We don't want anyone directly invoking this file as an executable

Re: [openstack-dev] [puppet][murano] Developing puppet module for Murano

2015-06-17 Thread Monty Taylor
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/17/2015 08:53 AM, Emilien Macchi wrote: Hi Serg, On 06/17/2015 05:35 AM, Serg Melikyan wrote: Hi Emilien, I would like to answer your question regarding stackforge/puppet-murano repository asked in different thread: Someone from

[openstack-dev] Starting the M Release Name Poll

2015-06-14 Thread Monty Taylor
Hey everybody! I've started the poll for the M release. By now, you should have gotten an email with a link to the vote. If you did not and think that you should have, please let me know (directly, not to the mailing list please) and I can re-send and/or fix as necessary. Please remember that

[openstack-dev] Please Merge patches titled Merge Tag ...

2015-06-09 Thread Monty Taylor
Hi! When we cut a release, we do so on a branch. This means that the tag for the release is not in the master branch of the repo, which means git can produce unexpected output in some cases. To solve this, we have the proposal bot propose a null-merge of the tag back in to master. The patch in

Re: [openstack-dev] [Ironic] When to bump the microversion?

2015-06-04 Thread Monty Taylor
On 06/04/2015 11:27 AM, Dmitry Tantsur wrote: On 06/04/2015 05:03 PM, Sean Dague wrote: On 06/04/2015 10:50 AM, Dmitry Tantsur wrote: On 06/04/2015 04:40 PM, Ruby Loo wrote: Hi, In Kilo, we introduced microversions but it seems to be a work-in-progress. There is an effort now to add

[Openstack] Release naming for M open for nominations

2015-06-02 Thread Monty Taylor
Hey everyone! It's time to pick a name for the M release. If you have a name you'd like us to vote on, please add it here: https://wiki.openstack.org/wiki/Release_Naming/M_Proposals The nominations will be open until 2015-06-07 23:59:59 UTC. If you don't remember the rules, they're here:

[openstack-dev] Release naming for M open for nominations

2015-06-02 Thread Monty Taylor
Hey everyone! It's time to pick a name for the M release. If you have a name you'd like us to vote on, please add it here: https://wiki.openstack.org/wiki/Release_Naming/M_Proposals The nominations will be open until 2015-06-07 23:59:59 UTC. If you don't remember the rules, they're here:

Re: [openstack-dev] [nova] usefulness of device parameter at volumeAttachment

2015-05-28 Thread Monty Taylor
On 05/28/2015 11:25 PM, Jay Pipes wrote: On 05/26/2015 03:13 AM, Daniel P. Berrange wrote: On Sat, May 23, 2015 at 11:00:32AM +0200, Géza Gémes wrote: Hi, When someone calls nova volume-attach or the block-device-mapping parameter at boot, it is possible to specify a device name for the

Re: [openstack-dev] [Ironic] [TC] Discussion: changing Ironic's release model

2015-05-28 Thread Monty Taylor
On 05/28/2015 12:41 PM, Devananda van der Veen wrote: Hi all, tl;dr; At the summit, the Ironic team discussed the challenges we've had with the current release model and came up with some ideas to address them. I had a brief follow-up conversation with Doug and Thierry, but I'd like this

Re: [openstack-dev] [new][app-catalog] App Catalog next steps

2015-05-27 Thread Monty Taylor
On 05/27/2015 06:35 PM, Keith Bray wrote: Joe, regarding apps-catalog for any app deployable on OpenStack (regardless of deployment technology), my two cents is that is a good idea. I also believe, however, that the app-catalog needs to evolve first with features that make it super simple to

Re: [openstack-dev] [nova][api] Allow passing body for more API methods

2015-05-11 Thread Monty Taylor
On 05/11/2015 02:05 PM, Dean Troyer wrote: On Mon, May 11, 2015 at 11:44 AM, Rosa, Andrea (HP Cloud Services) andrea.r...@hp.com wrote: Agreed. Violating the HTTP spec is something that should be avoided. Actually it is not violating the HTTP spec, from RFC: A payload within a DELETE

Re: [openstack-dev] [all] who is the ptl of trove?

2015-05-08 Thread Monty Taylor
On 05/08/2015 03:45 AM, Nikhil Manchanda wrote: Comments and answers inline. Li Tianqing writes: [...] 1) why we put the trove vm into user's tenant, not the trove's tenant? User can login on that vm, and that vm must connect to rabbitmq. It is quite insecure. what's

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

2015-05-04 Thread Monty Taylor
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/04/2015 08:47 PM, Emilien Macchi wrote: On 05/04/2015 10:37 PM, Rich Megginson wrote: On 05/04/2015 07:52 PM, Mathieu Gagné wrote: On 2015-05-04 9:15 PM, Rich Megginson wrote: On 05/04/2015 06:03 PM, Mathieu Gagné wrote: On 2015-05-04

Re: [openstack-dev] [pbr] regular releases, and path to 1.0

2015-05-04 Thread Monty Taylor
On 05/04/2015 03:53 PM, Robert Collins wrote: Hi, I'd like to talk about how often we can and should release pbr, and what criteria we should use for 1.0. tl;dr: release weekly [outside of organisation-wide-freezes], do a 1.0 immediately. pbr, like all our libraries affects everything

Re: [openstack-dev] [pbr] regular releases, and path to 1.0

2015-05-04 Thread Monty Taylor
On 05/04/2015 04:15 PM, Robert Collins wrote: On 5 May 2015 at 08:12, Monty Taylor mord...@inaugust.com wrote: On 05/04/2015 03:53 PM, Robert Collins wrote: I'm fine with that in principle - I tend to release personal libraries pretty much as soon as something interesting hits them. I have

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

2015-05-02 Thread Monty Taylor
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 Barbican

Re: [OpenStack-Infra] Questions with respect to packaging

2015-05-01 Thread Monty Taylor
On 04/29/2015 02:19 AM, Steve Kowalik wrote: On 29/04/15 04:41, Monty Taylor wrote: On 04/28/2015 02:02 PM, Clark Boylan wrote: On Mon, Apr 27, 2015, at 11:13 PM, Steve Kowalik wrote: [snip] * Decide if we host full upstream sources, or if we point at a remote site with tarballs

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

2015-04-30 Thread Monty Taylor
-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 jaypi...@gmail.com 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

Re: [OpenStack-Infra] PuppetBoard

2015-04-27 Thread Monty Taylor
On 04/26/2015 08:08 PM, Spencer Krum wrote: Hi All, The primary maintainer of puppetboard is stepping aside: https://github.com/puppet-community/puppetboard/issues/132. We use puppetboard to display facts from machines and reports of puppet runs. We can expect to continue to have this need

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

2015-04-26 Thread Monty Taylor
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 upstream

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

2015-04-25 Thread Monty Taylor
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 means

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

2015-04-25 Thread Monty Taylor
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've

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

2015-04-25 Thread Monty Taylor
April 2015 at 15:27, Monty Taylor mord...@inaugust.com wrote: 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

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

2015-04-25 Thread Monty Taylor
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 chatting with fungi in IRC - I've got this: https

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

2015-04-24 Thread Monty Taylor
On 04/24/2015 06:28 PM, David Medberry wrote: On Fri, Apr 24, 2015 at 2:14 AM, Chris Dent chd...@redhat.com 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

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

2015-04-18 Thread Monty Taylor
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] [Nova][Neutron] Linuxbridge as the default

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

2015-04-17 Thread Monty Taylor
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 ?

2015-04-16 Thread Monty Taylor
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], the

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

2015-04-15 Thread Monty Taylor
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 in

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

2015-04-14 Thread Monty Taylor
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 make

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

2015-04-12 Thread Monty Taylor
On 04/12/2015 08:01 PM, James Polley wrote: On Mon, Apr 13, 2015 at 9:12 AM, Monty Taylor mord...@inaugust.com 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_requires. Upstream

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

2015-04-12 Thread Monty Taylor
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 import

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

2015-04-12 Thread Monty Taylor
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 Development Mailing List (not for usage questions); openstack-d

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

2015-04-11 Thread Monty Taylor
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

[OpenStack-Infra] A proposal to use phabricator for issue tracking

2015-04-03 Thread Monty Taylor
As a follow up to my previous email about thinking about ceasing to use storyboard, I have done some work towards investigating using phabricator. phabricator came out of Facebook, but has been spun out completely and is now managed as an Open Source project. There is a company that has formed

Re: [OpenStack-Infra] A proposal to use phabricator for issue tracking

2015-04-03 Thread Monty Taylor
On 04/03/2015 11:54 AM, Sean Dague wrote: On 04/03/2015 11:00 AM, Monty Taylor wrote: As a follow up to my previous email about thinking about ceasing to use storyboard, I have done some work towards investigating using phabricator. phabricator came out of Facebook, but has been spun out

Re: [OpenStack-Infra] A proposal to use phabricator for issue tracking

2015-04-03 Thread Monty Taylor
On 04/03/2015 12:06 PM, Jeremy Stanley wrote: On 2015-04-03 11:54:00 -0400 (-0400), Sean Dague wrote: [...] 2) is there an event stream of changes (either real time or rss) that can be consumed by said tools? Having the change stream would be really helpful. Which relates to a feature

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

2015-04-03 Thread Monty Taylor
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 on

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

2015-04-03 Thread Monty Taylor
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

Re: [OpenStack-Infra] A proposal to use phabricator for issue tracking

2015-04-03 Thread Monty Taylor
On 04/03/2015 11:16 AM, Thierry Carrez wrote: Monty Taylor wrote: As a follow up to my previous email about thinking about ceasing to use storyboard, I have done some work towards investigating using phabricator. [...] For the record, I'll repost some of the analysis I did for mordred

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

2015-04-02 Thread Monty Taylor
On 04/02/2015 06:22 PM, Brant Knudson wrote: On Thu, Apr 2, 2015 at 4:52 PM, Boris Pavlovic bo...@pavlovic.me 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

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

2015-04-01 Thread Monty Taylor
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 from the

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

2015-03-29 Thread Monty Taylor
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 rybr...@redhat.com 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

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

2015-03-25 Thread Monty Taylor
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 conform

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

2015-03-24 Thread Monty Taylor
On 03/24/2015 06:05 PM, Kyle Mestery wrote: On Tue, Mar 24, 2015 at 9:56 AM, Doug Hellmann d...@doughellmann.com 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

Re: [OpenStack-Infra] Better Corporate CLA management

2015-03-23 Thread Monty Taylor
On 03/23/2015 04:15 PM, Clark Boylan wrote: On Fri, Mar 13, 2015, at 11:06 AM, Jimmy Mcarthur wrote: Hi all - The OpenStack Foundation has already worked up at least a portion of this solution by allowing one or more users with an OpenStackID to be set as a CCLA Admin for their

[OpenStack-Infra] Biting the bullet on issue tracking

2015-03-23 Thread Monty Taylor
Hi everybody, First, some background: A year and a half ago, Infra started down the road of of writing a replacement for the pieces of Launchpad that OpenStack continues to use. There were several reasons, but notable amongst them are: - Desire to use the forthcoming openstackid OpenID/Oauth as

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

2015-03-21 Thread Monty Taylor
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

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

2015-03-17 Thread Monty Taylor
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 d...@doughellmann.com 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

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

2015-03-17 Thread Monty Taylor
On 03/16/2015 08:32 PM, Robert Collins wrote: On 17 March 2015 at 13:22, Doug Hellmann d...@doughellmann.com 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

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

2015-03-05 Thread Monty Taylor
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:

Re: [OpenStack-Infra] We're going to make a cloud, it needs a name

2015-03-05 Thread Monty Taylor
On 03/05/2015 05:26 PM, Clint Byrum wrote: And the results: https://www.surveymonkey.com/results/SM-W6R6K2T7/ It would appear that 'infra cloud' is far enough ahead of the others, including a wide margin in front of discuss further that I think we can declare it the winner of this very

Re: [OpenStack-Infra] Thoughts on evolving Zuul

2015-02-26 Thread Monty Taylor
On 02/26/2015 05:41 PM, Zaro wrote: Thanks Jim. This makes a lot of sense and will hopefully make things simpler and more robust. Just a few questions: I am not Jim - but I'm going to answer anyway ... 1. It looks like zuul can request a specific set of nodes for a job. Do you envision

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

2015-02-17 Thread Monty Taylor
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 that

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

2015-02-10 Thread Monty Taylor
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 version of

Re: [OpenStack-Infra] Cross-Repo Dependencies in Zuul

2015-02-10 Thread Monty Taylor
On 02/10/2015 05:26 PM, Boris Pavlovic wrote: James, Awesome! Amazing! You guys rock!=) Thanks Boris! Just trying to keep up with all of the awesome developers we have out there! On Wed, Feb 11, 2015 at 1:26 AM, James E. Blair cor...@inaugust.com wrote: Hi, We have added support for

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

2015-02-04 Thread Monty Taylor
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 someone

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

2015-02-04 Thread Monty Taylor
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 there,

Re: [OpenStack-Infra] [infra] Nominating Elizabeth K. Joseph for infra-core and root

2015-01-31 Thread Monty Taylor
On 01/30/2015 12:20 PM, James E. Blair wrote: Hi, The Infrastructure program has a unique three-tier team structure: contributors (that's all of us!), core members (people with +2 ability on infra projects in Gerrit) and root members (people with administrative access). Read all about it

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

2015-01-30 Thread Monty Taylor
On 01/28/2015 06:33 PM, Johannes Erdfelt wrote: On Wed, Jan 28, 2015, Mike Bayer mba...@redhat.com 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

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

2015-01-29 Thread Monty Taylor
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 clearly

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

2015-01-28 Thread Monty Taylor
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/2015 04:50 PM, Monty

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

2015-01-28 Thread Monty Taylor
On 01/27/2015 10:35 PM, James E. Blair wrote: Lauren Sell lau...@openstack.org 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

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

2015-01-28 Thread Monty Taylor
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 would imagine that if any of them

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

2015-01-27 Thread Monty Taylor
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

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

2015-01-27 Thread Monty Taylor
On 01/27/2015 06:05 PM, Jonathan Bryce wrote: On Jan 27, 2015, at 3:50 PM, Monty Taylor mord...@inaugust.com 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 opposite of what a community

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

2015-01-17 Thread Monty Taylor
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 that it

Re: [OpenStack-Infra] Stackforge projects: Manila Image Project and licensing considerations

2015-01-15 Thread Monty Taylor
On 01/14/2015 07:28 AM, Csaba Henk wrote: Hi, I hope I'm addressing the right list -- if not, please point me where it's appropriate. We (Manila developers) plan to start a new side-project that would be hosted on Stackforge. It's tentatively named Manila Image Project, although it would

<    1   2   3   4   5   6   7   8   9   10   >