Re: [openstack-dev] [neutron] Cross-server locking for neutron server

2014-07-30 Thread Morgan Fainberg
many rows were affected. Feel free to hit me up if I can help in any way on this. Cheers, Morgan  — Morgan Fainberg ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Keystone] Survey on Token Provider Usage

2014-07-29 Thread Morgan Fainberg
Hi! The Keystone team is looking for feedback from the community on what type of Keystone Token is being used in your OpenStack deployments. This is to help us understand the use of the different providers and get information on the reasoning (if possible) that that token provider is being

Re: [openstack-dev] [Keystone] Feasibility of adding global restrictions at trust creation time

2014-07-23 Thread Morgan Fainberg
On Wednesday, July 23, 2014, Russell Bryant rbry...@redhat.com wrote: On 07/22/2014 11:00 PM, Nathan Kinder wrote: On 07/22/2014 06:55 PM, Steven Hardy wrote: On Tue, Jul 22, 2014 at 05:20:44PM -0700, Nathan Kinder wrote: Hi, I've had a few discussions recently related to Keystone

Re: [openstack-dev] [devstack][keystone] Devstack, auth_token and keystone v3

2014-07-17 Thread Morgan Fainberg
that are not on this list (or are truly transparent to the end-user and deployer). Cheers, Morgan Fainberg ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [devstack][keystone] Devstack, auth_token and keystone v3

2014-07-16 Thread Morgan Fainberg
On Wednesday, July 16, 2014, Joe Gordon joe.gord...@gmail.com wrote: On Tue, Jul 15, 2014 at 7:20 AM, Morgan Fainberg morgan.fainb...@gmail.com wrote: On Tuesday, July 15, 2014, Steven Hardy sha...@redhat.com wrote: On Mon, Jul 14, 2014 at 02:43:19PM -0400, Adam Young wrote: On 07/14/2014

Re: [openstack-dev] [devstack][keystone] Devstack, auth_token and keystone v3

2014-07-16 Thread Morgan Fainberg
I apologize for the very mixed up/missed quoting in that response, looks like my client ate a bunch of the quotes when writing up the email.  — Morgan Fainberg -- From: Morgan Fainberg morgan.fainb...@gmail.com Reply: Morgan Fainberg

Re: [openstack-dev] [devstack][keystone] Devstack, auth_token and keystone v3

2014-07-16 Thread Morgan Fainberg
: July 16, 2014 at 02:27:42 To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Subject:  Re: [openstack-dev] [devstack][keystone] Devstack, auth_token and keystone v3 On Tue, Jul 15, 2014 at 7:20 AM, Morgan Fainberg wrote: On Tuesday, July

Re: [openstack-dev] [devstack][keystone] (98)Address already in use: make_sock: could not bind to address [::]:5000 0.0.0.0:5000

2014-07-16 Thread Morgan Fainberg
-- From: Rich Megginson rmegg...@redhat.com Reply: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: July 16, 2014 at 08:08:00 To: openstack-dev@lists.openstack.org

Re: [openstack-dev] [devstack][keystone] Devstack, auth_token and keystone v3

2014-07-15 Thread Morgan Fainberg
On Tuesday, July 15, 2014, Steven Hardy sha...@redhat.com wrote: On Mon, Jul 14, 2014 at 02:43:19PM -0400, Adam Young wrote: On 07/14/2014 11:47 AM, Steven Hardy wrote: Hi all, I'm probably missing something, but can anyone please tell me when devstack will be moving to keystone v3,

Re: [openstack-dev] [devstack][keystone] Devstack, auth_token and keystone v3

2014-07-15 Thread Morgan Fainberg
Thanks for the info - any chance you can provide links to the relevant reviews here? If so I'll be happy to pull them and locally test to ensure our issues will be addressed :) Sure! https://review.openstack.org/#/c/106819/ is the change for the keystonemiddleware package (where the

Re: [openstack-dev] [devstack][keystone] Devstack, auth_token and keystone v3

2014-07-15 Thread Morgan Fainberg
Thanks for the info - any chance you can provide links to the relevant reviews here? If so I'll be happy to pull them and locally test to ensure our issues will be addressed :) Sure! https://review.openstack.org/#/c/106819/ is the change for the keystonemiddleware package

[openstack-dev] [Keystone][devstack] Keystone is now gating (Juno and beyond) on Apache + mod_wsgi deployed Keystone

2014-07-11 Thread Morgan Fainberg
The Keystone team is happy to announce that as of yesterday (July 10th 2014), with the merge of https://review.openstack.org/#/c/100747/ Keystone is now gating on Apache + mod_wsgi based deployment. This also has moved the default for devstack to deploy Keystone under apache. This is in-line

[openstack-dev] [Keystone] HTTP Get and HEAD requests mismatch on resulting HTTP status (proposed REST API Response Status Changes)

2014-07-01 Thread Morgan Fainberg
deploy via devstack under Apache (and gate upon it). Please let me know if anyone has significant issues with this change / concerns as I would like to finish up this road to mod_wsgi based Keystone as early in the Juno cycle as possible. Cheers, Morgan Fainberg — Morgan Fainberg

[openstack-dev] [Keystone] Announcing Keystone Middleware Project

2014-06-24 Thread Morgan Fainberg
The Keystone team would like to announce the official split of python-keystoneclient and the Keystone middleware code. Over time the middleware (auth_token, s3_token, ec2_token) has developed into a fairly expansive code base and includes dependencies that are not necessarily appropriate for the

Re: [openstack-dev] horizon failing on icehouse 100%, currently blocking all patches

2014-06-21 Thread Morgan Fainberg
The issue with the login page simply refreshing was due to a change in Keystone that updated the type of Token issued by default from PKI to PKIZ (compressed PKI/ASN1). The update to the django auth module was intended to correct that specific issue with Keystone and Horizon (Juno). The bug fix

Re: [openstack-dev] horizon failing on icehouse 100%, currently blocking all patches

2014-06-21 Thread Morgan Fainberg
django_openstack_auth versions, I currently have a patch up to restore the strange import in openstack_auth https://review.openstack.org/#/c/101715/ once that merges I will release django_openstack_auth 1.1.7 and all gates should work again. David From: Morgan Fainberg morgan.fainb...@gmail.com

Re: [openstack-dev] horizon failing on icehouse 100%, currently blocking all patches

2014-06-21 Thread Morgan Fainberg
...@gmail.com wrote: I'm afraid we have to revert the PKIZ change since devstack is not support django_openstack_auth now and all patches blocked including David's fix. 发自我的 iPhone 在 Jun 22, 2014,5:39,Morgan Fainberg morgan.fainb...@gmail.com javascript:; 写道: Great. This looks like your fix

Re: [openstack-dev] [hacking] rules for removal

2014-06-20 Thread Morgan Fainberg
+1 across the board for this change. H803 is ignored by a large number of projects after a rather extensive conversation on the ML last year (as I recall). The other two changes seem quite reasonable. Cheers, Morgan — Morgan Fainberg From: Sean Dague s...@dague.net Reply: OpenStack

Re: [openstack-dev] Fwd: Fwd: Debian people don't like bash8 as a project name (Bug#748383: ITP: bash8 -- bash script style guide checker)

2014-06-12 Thread Morgan Fainberg
(rather than just silly) about the naming? I just don’t see how if we don’t namespace collide on the executable side, how there can be any real confusion (python-bash8, sure pypi is a little different) over what is being installed. Cheers, Morgan — Morgan Fainberg From: Thomas Goirand z

Re: [openstack-dev] masking X-Auth-Token in debug output - proposed consistency

2014-06-11 Thread Morgan Fainberg
, tokens are only marginally less exposure than a password in a log file. I firmly believe that we should avoid putting information that conveys authorization (e.g. username/password or bearer token id) in the logs. — Morgan Fainberg From: Sean Dague s...@dague.net Reply: OpenStack Development Mailing

Re: [openstack-dev] masking X-Auth-Token in debug output - proposed consistency

2014-06-11 Thread Morgan Fainberg
}%(token)s’ instead of specifying a specific obscuring algorithm. This means that if we ever update the way we obscure the data in the future, we’re not lying about what was done in the log. The proposed approach can be found here: https://review.openstack.org/#/c/99432 Cheers, Morgan — Morgan

Re: [openstack-dev] Fwd: Fwd: Debian people don't like bash8 as a project name (Bug#748383: ITP: bash8 -- bash script style guide checker)

2014-06-11 Thread Morgan Fainberg
On 06/11/2014 02:01 PM, Sean Dague wrote: Honestly, I kind of don't care. :) +1 :-) +1 yep. that about covers it.___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [All] Disabling Pushes of new Gerrit Draft Patchsets

2014-05-31 Thread Morgan Fainberg
that won’t ever be submitted to the main repositories). I, for one am very pleased that Drafts are now disabled. I never liked the feature (it felt like it was missing a chunk of functionality to be really useful). Cheers, Morgan — Morgan Fainberg From: Clark Boylan clark.boy...@gmail.com Reply

Re: [openstack-dev] [All] Disabling Pushes of new Gerrit Draft Patchsets

2014-05-31 Thread Morgan Fainberg
2. Since a patch is very much WIP, there is concern about consuming CI  resources with needless testing.  3. The code is “example”, “toy”, or “exploratory” (not planning to  submit to the project, but not private/proprietary)    The general advice I give to people is to post the patches

Re: [openstack-dev] [Keystone] [Blazar] [Ironic] Py26/27 gates failing because of keystoneclient-0.9.0

2014-05-30 Thread Morgan Fainberg
the required fields, etc):  https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/fixture/v3.py#L48  for example. — Morgan Fainberg From: Doug Hellmann doug.hellm...@dreamhost.com Reply: OpenStack Development Mailing List (not for usage questions) openstack-dev

Re: [openstack-dev] [keystone] Redesign of Keystone Federation

2014-05-29 Thread Morgan Fainberg
will help us address any concerns with the proposal/redesign as we move into implementation. Cheers, Morgan — Morgan Fainberg From: Adam Young ayo...@redhat.com Reply: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: May 28, 2014 at 09:24:26

Re: [openstack-dev] Oslo logging eats system level tracebacks by default

2014-05-28 Thread Morgan Fainberg
+1 Providing service crashing information is very valuable. In general we need to provide as much information about why the service exited (critically/traceback/unexpectedly) for our operators. —Morgan — Morgan Fainberg From: Jay Pipes jaypi...@gmail.com Reply: OpenStack Development Mailing

Re: [openstack-dev] Concerns about the ballooning size of keystone tokens

2014-05-21 Thread Morgan Fainberg
The keystone team is also looking at ways to reduce the data contained in the token. Coupled with the compression, this should get the tokens back down to a reasonable size. Cheers, Morgan Sent via mobile On Wednesday, May 21, 2014, Adam Young ayo...@redhat.com wrote: On 05/21/2014 11:09 AM,

Re: [openstack-dev] Concerns about the ballooning size of keystone tokens

2014-05-21 Thread Morgan Fainberg
This is part of what I was referencing in regards to lightening the data stored in the token. Ideally, we would like to see an ID only token that only contains the basic information to act. Some initial tests show these tokens should be able to clock in under 1k in size. However all the details

[openstack-dev] [keystone] Catalog Backend in Deployments (Templated, SQL, etc)

2014-04-22 Thread Morgan Fainberg
) backends, limiting enhancements and new development done on the templated catalog backend. Please feel free to respond via the survey below or via email to the mailing list. Keystone Catalog Backend Usage Survey: https://www.surveymonkey.com/s/3DL7FTY Cheers, Morgan — Morgan Fainberg Principal

[openstack-dev] TC Candidacy

2014-04-14 Thread Morgan Fainberg
Hi everyone! I would like to announce my candidacy for the Technical Committee election. About Me I’m Morgan Fainberg. I am a software engineer working for a startup focused on deploying OpenStack in a private cloud configuration for a number of organizations. I’ve been an active

Re: [openstack-dev] [keystone] [oslo] Using oslo.cache in keystoneclient.middleware.auth_token

2014-03-31 Thread Morgan Fainberg
I’ve been working on (albeit slowly) getting the keystone implementation of dogpile.cache into oslo.cache. It’s been slow due to other demands, but I’m hoping to get back to it in the near future here so we can make moves like this more easily. — Morgan Fainberg Principal Software Engineer Core

Re: [openstack-dev] [nova] Thought exercise for a V2 only world

2014-03-04 Thread Morgan Fainberg
propose changing the topic of this thread slightly: In a V2 only world, how do we know if something is used? How do we understand how it is used and when? Lets answer that instead. — Morgan Fainberg Principal Software Engineer Core Developer, Keystone m...@metacloud.com On March 4, 2014 at 02:09:51

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

2014-03-04 Thread Morgan Fainberg
at 12:05 -0800, Morgan Fainberg wrote:  Having done some work with MySQL (specifically around similar data  sets) and discussing the changes with some former coworkers (MySQL  experts) I am inclined to believe the move from varchar to binary  absolutely would increase performance like

Re: [openstack-dev] [Nova] Concrete Proposal for Keeping V2 API

2014-03-04 Thread Morgan Fainberg
On March 4, 2014 at 16:13:45, Dan Smith (d...@danplanet.com) wrote: What I'd like to do next is work through a new proposal that includes  keeping both v2 and v3, but with a new added focus of minimizing the  cost. This should include a path away from the dual code bases and to  something like

Re: [openstack-dev] [nova] Thought exercise for a V2 only world

2014-03-03 Thread Morgan Fainberg
Hi Joe, I think that in a V2 only world a 2 cycle deprecation model would be sufficient for any extension. I don’t foresee any complaints on that front, especially if there is work to supersede or obsolete the need for the extension. Cheers, Morgan  — Morgan Fainberg Principal Software

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

2014-03-02 Thread Morgan Fainberg
Having done some work with MySQL (specifically around similar data sets) and discussing the changes with some former coworkers (MySQL experts) I am inclined to believe the move from varchar to binary absolutely would increase performance like this. However, I would like to get some real

Re: [openstack-dev] Toward SQLAlchemy 0.9.x compatibility everywhere for Icehouse

2014-03-01 Thread Morgan Fainberg
Hi Thomas, I’ll take a look at that tonight and see if it’s an easy solve. Hopefully I can have something posted by Monday for you. —Morgan — Morgan Fainberg Principal Software Engineer Core Developer, Keystone m...@metacloud.com On March 1, 2014 at 20:06:54, Thomas Goirand (z...@debian.org

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

2014-02-27 Thread Morgan Fainberg
On Thursday, February 27, 2014, Dolph Mathews dolph.math...@gmail.com wrote: On Thu, Feb 27, 2014 at 11:52 AM, Jay Pipes jaypi...@gmail.comjavascript:_e(%7B%7D,'cvml','jaypi...@gmail.com'); wrote: On Thu, 2014-02-27 at 16:13 +, Henry Nash wrote: So a couple of things about this:

[openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

2014-02-25 Thread Morgan Fainberg
with this change to USER_ID format, please respond so that the issues/concerns can be addressed.  Again, the plan is not to change current USER_IDs but that new ones could be up to 255 characters in length. Cheers, Morgan Fainberg — Morgan Fainberg Principal Software Engineer Core Developer, Keystone m

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-24 Thread Morgan Fainberg
and the community. TL;DR, “don’t break the contract”. If we are seriously making incompatible changes (and we will be regardless of the direction) the only reasonable option is a new major version. — Morgan Fainberg Principal Software Engineer Core Developer, Keystone m...@metacloud.com On February

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-24 Thread Morgan Fainberg
, consumer, and developer) this means we should keep V2, and work on benefiting from the lessons learned in developing V3 while moving to correct the issues we have in a maintainable / friendly way (to developers, deployers, and consumers). — Morgan Fainberg Principal Software Engineer Core Developer

[openstack-dev] [Keystone] IRC Channel Venue Change for Keystone Development topics

2014-02-18 Thread Morgan Fainberg
team will still be in #openstack-dev so that we can catch Keystone and Identity related questions (just as before). Cheers, Morgan Fainberg — Morgan Fainberg Principal Software Engineer Core Developer, Keystone m...@metacloud.com___ OpenStack-dev

[openstack-dev] [wsme] Undefined attributes in WSME

2014-01-18 Thread Morgan Fainberg
Yes, this feature is used in real deployments just as Yuriy described. I really want to avoid a new API version since we're just now getting solidly into V3 being used more extensively. Is it unreasonable to have wsme allow extra values in some manner? (I think that is the crux, is it something

Re: [openstack-dev] [oslo.config] Centralized config management

2014-01-09 Thread Morgan Fainberg
I agree with Doug’s question, but also would extend the train of thought to ask why not help to make Chef or Puppet better and cover the more OpenStack use-cases rather than add yet another competing system? Cheers, Morgan On January 9, 2014 at 10:24:06, Doug Hellmann

Re: [openstack-dev] [openstack][keystone] Is the user password too simple?

2014-01-01 Thread Morgan Fainberg
Brant, That is fine for some cases but we provide non-ldap backends, and a read/write backend. If we continue to provide a keystone specific idp (likely we need to), these features are a must-have in the long run. Just my view (and requests from real customers). It's all well and good to

Re: [openstack-dev] [Keystone] policy has no effect because of hard coded assert_admin?

2013-12-12 Thread Morgan Fainberg
the protection occurs likely warrants a deeper discussion (perhaps in Atlanta?). Cheers, Morgan Fainberg On December 12, 2013 at 10:32:40, Dolph Mathews (dolph.math...@gmail.com) wrote: The policy file is protecting v3 API calls at the controller layer, but you're calling the v2 API. The policy

Re: [openstack-dev] Incubation Request for Barbican

2013-12-12 Thread Morgan Fainberg
On December 12, 2013 at 14:32:36, Dolph Mathews (dolph.math...@gmail.com) wrote: On Thu, Dec 12, 2013 at 2:58 PM, Adam Young ayo...@redhat.com wrote: On 12/04/2013 08:58 AM, Jarret Raim wrote: While I am all for adding a new program, I think we should only add one if we rule out all existing

Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33

2013-12-10 Thread Morgan Fainberg
Hi Chmouel, I think the correct way to sync is to run the update.py script and submit a review (I don’t think it’s changed recently).   Cheers, Morgan On December 9, 2013 at 23:58:42, Chmouel Boudjnah (chmo...@enovance.com) wrote: On Fri, Dec 6, 2013 at 4:30 PM, Dolph Mathews

Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33

2013-12-05 Thread Morgan Fainberg
message From: Morgan Fainberg  Date:12/04/2013 6:17 PM (GMT-08:00)  To: Jamie Lennox ,OpenStack Development Mailing List (not for usage questions)  Subject: Re: [openstack-dev] [Keystoneclient] [Keystone] [Solum] Last released version of keystoneclient does not work with python33

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

2013-11-24 Thread Morgan Fainberg
I hear a concerted effort to get this bootstrapped in Keystone. We can do this if it is the voice of the majority. If we do: Keep KDS configuration separate from the Keystone configuration: the fact that they both point to the same host and port is temporary. In fact, we should probably

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

2013-11-24 Thread Morgan Fainberg
Hi Thomas, How pressing is this issue? I know there is work being done to unify token/auth implementation across the clients. I want to have an idea of the heat here so we can look at addressing this directly in novaclient if it can't wait until the unification work to come down the line.

Re: [openstack-dev] tenant or project

2013-11-23 Thread Morgan Fainberg
, and deprecation of keystone v2 API). Cheers, --Morgan Fainberg On Saturday, November 23, 2013, Caitlin Bestler wrote: I have seen several people request that their users be members of two projects and that they be allow to publish objects that are Shared by multiple projects. For some

Re: [openstack-dev] [keystone][py3] Usage of httpretty

2013-11-20 Thread Morgan Fainberg
Chuck, The reason to use httpretty is that it handles everything at the socket layer, this means if we change out urllib for requests or some other transport to make HTTP requests to we don't need to refactor every one of the mock/mox subouts to match the exact set of parameters to be passed.

Re: [openstack-dev] [keystone][py3] Usage of httpretty

2013-11-20 Thread Morgan Fainberg
I'd be more willing to toss in and help to maintain/fix appropriately on StackForge if that is needed. Though I am very much hoping upstream can be used. Cheers, Morgan Fainberg On Wed, Nov 20, 2013 at 7:21 PM, Chuck Short chuck.sh...@canonical.com wrote: Hi, So maybe if it gets to the point

Re: [openstack-dev] [Solum] Some initial code copying for db/migration

2013-11-18 Thread Morgan Fainberg
to understand). I think the plus of avoiding decorating things isn't really a huge win, and actually i think takes clarity away. --Morgan Fainberg ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman

Re: [openstack-dev] Split of the openstack-dev list (summary so far)

2013-11-17 Thread Morgan Fainberg
A couple of quick points. 1) I think that splitting the list is the wrong approach. 2) Perhaps we need to look at adding a mechanism that enforces the use of tags in the subject line (send a nice sorry, but you need to indicate the topic(s) you are mailing about error back if it doesn't exist,

Re: [openstack-dev] Congress: an open policy framework

2013-11-14 Thread Morgan Fainberg
to unwind that). There might be some value to seeing some work being done to provide more information to Keystone, but I think this will become more apparent as Congress develops. Thoughts? Tim Cheers, Morgan Fainberg ___ OpenStack-dev mailing list

Re: [openstack-dev] RFC: reverse the default Gerrit sort order

2013-11-10 Thread Morgan Fainberg
was a little short to convey that. --Morgan Fainberg On Sunday, November 10, 2013, Robert Collins wrote: On 9 November 2013 01:51, Morgan Fainberg m...@metacloud.com javascript:; wrote: I agree this would be interesting but if it isn't configurable (e.g. A mechanism to support current behavior

Re: [openstack-dev] RFC: reverse the default Gerrit sort order

2013-11-08 Thread Morgan Fainberg
to support current behavior) I think this would very much disrupt the workflow I use. If configurable, I'd be open to it, if not configurable I have to say -1 to this idea. Cheers, Morgan Fainberg ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org

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

2013-10-30 Thread Morgan Fainberg
on the topic. Cheers, Morgan Fainberg ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] distibuted caching system in front of mysql server for openstack transactions

2013-10-28 Thread Morgan Fainberg
In light of what Dolph said with regards to Keystone, we are using dogpile.cache to implement memoization in front of our driver calls. It it has the ability to cache directly as well, but it has been effective (so far) for our use-case. That being said, I am unsure if caching in front of MySQL

Re: [openstack-dev] excessively difficult to support both iso8601 0.1.4 and 0.1.8 as deps

2013-10-24 Thread Morgan Fainberg
It seems like adopting 0.1.8 is the right approach. If it doesn't work with other projects, we should work to help those projects get updated to work with it. --Morgan On Thursday, October 24, 2013, Zhi Yan Liu wrote: Hi all, Adopt 0.1.8 as iso8601 minimum version:

Re: [openstack-dev] Remove vim modelines?

2013-10-24 Thread Morgan Fainberg
+1 and likely this should be added to hacking so they don't sneak back in by accident / reviewers missing the line since we've had them for do long. On Thursday, October 24, 2013, Flavio Percoco wrote: On 24/10/13 13:38 +0100, Joe Gordon wrote: Since the beginning of OpenStack we have had vim

Re: [openstack-dev] [keystone] design summit session proposal deadline

2013-10-16 Thread Morgan Fainberg
I agree that likely extensions and internal API discussions can become one session. I think the API side of that won't need to fill a whole session. On Wednesday, October 16, 2013, Adam Young wrote: On 10/16/2013 12:23 PM, Dolph Mathews wrote: I'll be finalizing the design summit schedule [1]

[openstack-dev] [Keystone] stabilizing internal APIs

2013-10-15 Thread Morgan Fainberg
of things. Cheers, Morgan Fainberg IRC: morganfainberg ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Keystone] stabilizing internal APIs

2013-10-15 Thread Morgan Fainberg
On Tue, Oct 15, 2013 at 5:05 PM, Doug Hellmann doug.hellm...@dreamhost.comwrote: Making updates easier would be nice, and the abstract base class work should help with that. On the other hand, as a deployer who has had to rewrite our custom integration a few times in the past 6 months or so,

Re: [openstack-dev] [Nova] UpgradeImpact commit message tag

2013-10-14 Thread Morgan Fainberg
I think this could be a significant win for all projects (I'd like to see it adopted beyond nova). This should help ferret out the upgrade impacts that sometimes sneak up on us (and cause issues later on). +1 from me. Cheers, Morgan Fainberg IRC: morganfainberg On Mon, Oct 14, 2013 at 4:51

[openstack-dev] TC Candidacy

2013-10-05 Thread Morgan Fainberg
usability and ease of deployment for all of OpenStack. I would be honored to also serve as a member of the TC, collaborating, and helping to guide the technical direction of the project as a whole. Cheers, Morgan Fainberg ___ OpenStack-dev mailing list

Re: [openstack-dev] Client and Policy

2013-09-20 Thread Morgan Fainberg
On Fri, Sep 20, 2013 at 3:20 PM, Monty Taylor mord...@inaugust.com wrote: What if we rethought the organization just a little bit. Instead of having oslo-incubator from which we copy code, and then oslo.* that we consume as libraries, what if: - we split all oslo modules into their own

Re: [openstack-dev] [requirements] Review request for adding ordereddict

2013-09-19 Thread Morgan Fainberg
there. Also is there a minimum version that you require? I think getting the packagers involved (and know if there is a minimum version requirement) is the best way to know if it should be accepted. Cheers, Morgan Fainberg IRC: morganfainberg On Thu, Sep 19, 2013 at 2:08 PM, Mark Washenberger

Re: [openstack-dev] When will we stop adding new Python modules to requirements

2013-09-15 Thread Morgan Fainberg
for packaging ?if it requires packaging). With that being said, I agree that it make sense for other (non-openstack) libraries to be added carefully late in the cycle. Perhaps the best would be to limit additions to prior to the release Feature-Freeze. Cheers, Morgan Fainberg On Sunday, September 15

Re: [openstack-dev] Backwards incompatible migration changes - Discussion

2013-09-12 Thread Morgan Fainberg
in place because other things changed? At a certain point restore from backup is really the only sane option. That threshold isn't exactly a long period of time. Cheers, Morgan Fainberg IRC: morganfainberg On Wed, Sep 11, 2013 at 10:30 PM, Robert Collins robe...@robertcollins.netwrote: I think

Re: [openstack-dev] [Keystone][Devstack] is dogpile.cache a requirement?

2013-09-04 Thread Morgan Fainberg
import is likely going to take a significant amount of refactoring. My guess is that it's going to be a bit late in the cycle, but we will see what comes up. --Morgan Fainberg IRC: morganfainberg On Wed, Sep 4, 2013 at 8:21 AM, Dolph Mathews dolph.math...@gmail.comwrote: On Wed, Sep 4, 2013

Re: [openstack-dev] upgrade tox - now with less slowness!

2013-09-04 Thread Morgan Fainberg
NICE!! On Wed, Sep 4, 2013 at 11:05 AM, Dan Smith d...@danplanet.com wrote: Because we landed a patch to tox upstream to use setup.py develop instead of sdist+install like our run_tests.sh scripts do - this means that with the new tox config changes, tox runs should be just as quick as

Re: [openstack-dev] [neutron] Why does nova.network.neutronv2.get_client(context, admin=True) drop auth_token?

2013-08-28 Thread Morgan Fainberg
for. It would still require lookups to the backend for a number of reasons (not listed, as I don't think it is relevant for this conversation). -- Morgan Fainberg IRC: morganfainberg ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http

[openstack-dev] [keystone] driver/pluggable base classes and ABCMeta

2013-08-21 Thread Morgan Fainberg
(and similar pluggable systems) a bit more clear. Cheers! -- Morgan Fainberg Sr. Software Architect | Metacloud, Inc Email: m...@metacloud.com IRC: morganfainberg ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin

Re: [openstack-dev] Dropping or weakening the 'only import modules' style guideline - H302

2013-08-06 Thread Morgan Fainberg
to review, I am going to agree with Sean here, it is a boon on large changes. I am against lessening/removing H302; but I understand why people desire it eased up. Cheers, Morgan Fainberg IRC: morganfainberg On Tue, Aug 6, 2013 at 1:18 PM, Christopher Armstrong chris.armstr...@rackspace.com

Re: [openstack-dev] Motion to start using Gerrit for TC votes

2013-08-06 Thread Morgan Fainberg
. This would be a very nice level of transparency (not that the TC hides anything) and makes it much easier to see what is/has been going on and how we got there. It also ensures we have the comments recorded along the way. Cheers, Morgan Fainberg IRC: morganfainberg

[openstack-dev] [Neutron][API Doc] Easy way to generate JSON output for doc?

2013-08-01 Thread Morgan Fainberg
=keystone.token.providers.uuid.Provider In older versions I believe the option (still in the [token] section) is: token_format=UUID I hope this info helps you out some. Cheers, Morgan Fainberg Sent from my iPhone (please excuse the brevity) 31/07/2013, Paul Michali : Yeah I was playing

Re: [openstack-dev] [Keystone] Alembic support

2013-07-25 Thread Morgan Fainberg
of Icehouse (barring any major issue) the point in which we move to Alembric. We can be selective in taking extension modifications that add migration repos if it is a major concern that moving to Alembric is going to be really painful. Cheers, Morgan Fainberg On Thu, Jul 25, 2013 at 7:35 PM, Adam

Re: [openstack-dev] [Keystone] Memcache user token index and PKI tokens

2013-07-16 Thread Morgan Fainberg
for my company, but I want to move to the memcache driver soon. Cheers, Morgan Fainberg ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [keystone] sqlite doesn't support migrations

2013-07-16 Thread Morgan Fainberg
in IRC I had offered to help with the effort of moving away from SQLite migration testing; if the nova-way is the way we want to go, I'll be happy to help contribute to that. Cheers, Morgan Fainberg ___ OpenStack-dev mailing list OpenStack-dev

Re: [openstack-dev] [keystone] sqlite doesn't support migrations

2013-07-15 Thread Morgan Fainberg
another approach should be taken. If this is a legitimate issue, maybe we should look at what Neutron is doing, as they are using alembric for migrations already. Cheers, Morgan Fainberg -- Sent from my iPhone (please excuse the brevity and any typos

<    1   2   3   4   5