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

2014-03-04 Thread Vishvananda Ishaya
On Mar 3, 2014, at 11:32 AM, Jay Pipes jaypi...@gmail.com wrote: On Mon, 2014-03-03 at 11:09 -0800, Vishvananda Ishaya wrote: On Mar 3, 2014, at 6:48 AM, Jay Pipes jaypi...@gmail.com wrote: On Sun, 2014-03-02 at 12:05 -0800, Morgan Fainberg wrote: Having done some work with MySQL

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

2014-03-04 Thread Morgan Fainberg
On March 4, 2014 at 10:45:02, Vishvananda Ishaya (vishvana...@gmail.com) wrote: On Mar 3, 2014, at 11:32 AM, Jay Pipes jaypi...@gmail.com wrote:  On Mon, 2014-03-03 at 11:09 -0800, Vishvananda Ishaya wrote:  On Mar 3, 2014, at 6:48 AM, Jay Pipes jaypi...@gmail.com wrote:    On Sun, 2014-03-02

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

2014-03-03 Thread Jay Pipes
On Sun, 2014-03-02 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

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

2014-03-03 Thread Dolph Mathews
On Mon, Mar 3, 2014 at 8:48 AM, Jay Pipes jaypi...@gmail.com wrote: On Sun, 2014-03-02 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

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

2014-03-03 Thread Vishvananda Ishaya
On Mar 3, 2014, at 6:48 AM, Jay Pipes jaypi...@gmail.com wrote: On Sun, 2014-03-02 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

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

2014-03-03 Thread Mark Washenberger
On Sat, Mar 1, 2014 at 12:51 PM, Jay Pipes jaypi...@gmail.com wrote: On Fri, 2014-02-28 at 15:25 -0800, Mark Washenberger wrote: I believe we have some agreement here. Other openstack services should be able to use a strongly typed identifier for users. I just think if we want to go that

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

2014-03-03 Thread Jay Pipes
On Mon, 2014-03-03 at 11:09 -0800, Vishvananda Ishaya wrote: On Mar 3, 2014, at 6:48 AM, Jay Pipes jaypi...@gmail.com wrote: On Sun, 2014-03-02 at 12:05 -0800, Morgan Fainberg wrote: Having done some work with MySQL (specifically around similar data sets) and discussing the changes with

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

2014-03-03 Thread Jay Pipes
On Mon, 2014-03-03 at 11:18 -0800, Mark Washenberger wrote: On Sat, Mar 1, 2014 at 12:51 PM, Jay Pipes jaypi...@gmail.com wrote: On Fri, 2014-02-28 at 15:25 -0800, Mark Washenberger wrote: I believe we have some agreement here. Other openstack services should

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

2014-03-03 Thread Adam Young
On 03/03/2014 02:32 PM, Jay Pipes wrote: On Mon, 2014-03-03 at 11:09 -0800, Vishvananda Ishaya wrote: On Mar 3, 2014, at 6:48 AM, Jay Pipes jaypi...@gmail.com wrote: On Sun, 2014-03-02 at 12:05 -0800, Morgan Fainberg wrote: Having done some work with MySQL (specifically around similar data

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

2014-03-03 Thread Clint Byrum
Excerpts from Adam Young's message of 2014-03-03 23:06:58 -0800: On 03/03/2014 02:32 PM, Jay Pipes wrote: On Mon, 2014-03-03 at 11:09 -0800, Vishvananda Ishaya wrote: On Mar 3, 2014, at 6:48 AM, Jay Pipes jaypi...@gmail.com wrote: On Sun, 2014-03-02 at 12:05 -0800, Morgan Fainberg wrote:

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

2014-03-02 Thread Sean Dague
On 03/01/2014 08:00 PM, Clint Byrum wrote: Excerpts from Robert Collins's message of 2014-03-01 14:26:57 -0800: On 1 March 2014 13:28, Clint Byrum cl...@fewbar.com wrote: +1. A Keystone record belongs to Keystone, and it should have a Keystone ID. External records that are linked should be

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] [all][keystone] Increase of USER_ID length maximum from 64 to 255

2014-03-01 Thread Jay Pipes
On Fri, 2014-02-28 at 15:25 -0800, Mark Washenberger wrote: I believe we have some agreement here. Other openstack services should be able to use a strongly typed identifier for users. I just think if we want to go that route, we probably need to create a new field to act as the proper user

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

2014-03-01 Thread Robert Collins
On 1 March 2014 13:28, Clint Byrum cl...@fewbar.com wrote: +1. A Keystone record belongs to Keystone, and it should have a Keystone ID. External records that are linked should be linked separately. It may not be obvious to everyone, but MySQL uses B-trees for indexes. B-trees cannot have

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

2014-03-01 Thread Clint Byrum
Excerpts from Robert Collins's message of 2014-03-01 14:26:57 -0800: On 1 March 2014 13:28, Clint Byrum cl...@fewbar.com wrote: +1. A Keystone record belongs to Keystone, and it should have a Keystone ID. External records that are linked should be linked separately. It may not be

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

2014-02-28 Thread Mark Washenberger
On Wed, Feb 26, 2014 at 5:25 AM, Dolph Mathews dolph.math...@gmail.comwrote: On Tue, Feb 25, 2014 at 2:38 PM, Jay Pipes jaypi...@gmail.com wrote: On Tue, 2014-02-25 at 11:47 -0800, Morgan Fainberg wrote: For purposes of supporting multiple backends for Identity (multiple LDAP, mix of LDAP

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

2014-02-28 Thread Henry Nash
Hi Mark, So we would not modify any existing IDs, so no migration required. Henry On 28 Feb 2014, at 17:38, Mark Washenberger mark.washenber...@markwash.net wrote: On Wed, Feb 26, 2014 at 5:25 AM, Dolph Mathews dolph.math...@gmail.com wrote: On Tue, Feb 25, 2014 at 2:38 PM, Jay

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

2014-02-28 Thread Mark Washenberger
On Fri, Feb 28, 2014 at 10:39 AM, Henry Nash hen...@linux.vnet.ibm.comwrote: Hi Mark, So we would not modify any existing IDs, so no migration required. Okay, I just want to be painfully clear--we're not proposing changing any of the current restrictions on the user-id field. We will not:

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

2014-02-28 Thread Jay Pipes
On Fri, 2014-02-28 at 13:10 -0800, Mark Washenberger wrote: On Fri, Feb 28, 2014 at 10:39 AM, Henry Nash hen...@linux.vnet.ibm.com wrote: Hi Mark, So we would not modify any existing IDs, so no migration required. Okay, I just want to be

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

2014-02-28 Thread Mark Washenberger
On Fri, Feb 28, 2014 at 2:26 PM, Jay Pipes jaypi...@gmail.com wrote: On Fri, 2014-02-28 at 13:10 -0800, Mark Washenberger wrote: On Fri, Feb 28, 2014 at 10:39 AM, Henry Nash hen...@linux.vnet.ibm.com wrote: Hi Mark, So we would not modify any existing IDs, so no

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

2014-02-28 Thread Clint Byrum
Excerpts from Jay Pipes's message of 2014-02-28 14:26:26 -0800: On Fri, 2014-02-28 at 13:10 -0800, Mark Washenberger wrote: On Fri, Feb 28, 2014 at 10:39 AM, Henry Nash hen...@linux.vnet.ibm.com wrote: Hi Mark, So we would not modify any existing

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

2014-02-27 Thread Henry Nash
So a couple of things about this: 1) Today (and also true for Grizzly and Havana), the user can chose what LDAP attribute should be returned as the user or group ID. So it is NOT a safe assumption today (ignoring any support for domain-specific LDAP support) that the format of a user or group

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

2014-02-27 Thread Jay Pipes
On Thu, 2014-02-27 at 16:13 +, Henry Nash wrote: So a couple of things about this: 1) Today (and also true for Grizzly and Havana), the user can chose what LDAP attribute should be returned as the user or group ID. So it is NOT a safe assumption today (ignoring any support for

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

2014-02-27 Thread Henry Nash
On 27 Feb 2014, at 17:52, Jay Pipes jaypi...@gmail.com wrote: On Thu, 2014-02-27 at 16:13 +, Henry Nash wrote: So a couple of things about this: 1) Today (and also true for Grizzly and Havana), the user can chose what LDAP attribute should be returned as the user or group ID. So it

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

2014-02-27 Thread Dolph Mathews
On Thu, Feb 27, 2014 at 11:52 AM, Jay Pipes jaypi...@gmail.com wrote: On Thu, 2014-02-27 at 16:13 +, Henry Nash wrote: So a couple of things about this: 1) Today (and also true for Grizzly and Havana), the user can chose what LDAP attribute should be returned as the user or group

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:

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

2014-02-27 Thread Miller, Mark M (EB SW Cloud - RD - Corvallis)
Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255 On Thursday, February 27, 2014, Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com wrote: On Thu, Feb 27, 2014 at 11:52 AM, Jay Pipes

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

2014-02-27 Thread Adam Young
On 02/27/2014 12:52 PM, Jay Pipes wrote: On Thu, 2014-02-27 at 16:13 +, Henry Nash wrote: So a couple of things about this: 1) Today (and also true for Grizzly and Havana), the user can chose what LDAP attribute should be returned as the user or group ID. So it is NOT a safe assumption

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

2014-02-27 Thread Jay Pipes
On Thu, 2014-02-27 at 17:02 -0500, Adam Young wrote: On 02/27/2014 12:52 PM, Jay Pipes wrote: On Thu, 2014-02-27 at 16:13 +, Henry Nash wrote: So a couple of things about this: 1) Today (and also true for Grizzly and Havana), the user can chose what LDAP attribute should be

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

2014-02-26 Thread Marco Fargetta
Hi Morgan, On Tue, Feb 25, 2014 at 11:47:43AM -0800, Morgan Fainberg wrote: For purposes of supporting multiple backends for Identity (multiple LDAP, mix of LDAP and SQL, federation, etc) Keystone is planning to increase the maximum size of the USER_ID field from an upper limit of 64 to an

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

2014-02-26 Thread Dolph Mathews
On Wed, Feb 26, 2014 at 4:23 AM, Marco Fargetta marco.farge...@ct.infn.itwrote: Hi Morgan, On Tue, Feb 25, 2014 at 11:47:43AM -0800, Morgan Fainberg wrote: For purposes of supporting multiple backends for Identity (multiple LDAP, mix of LDAP and SQL, federation, etc) Keystone is planning

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

2014-02-26 Thread Dolph Mathews
On Tue, Feb 25, 2014 at 2:38 PM, Jay Pipes jaypi...@gmail.com wrote: On Tue, 2014-02-25 at 11:47 -0800, Morgan Fainberg wrote: For purposes of supporting multiple backends for Identity (multiple LDAP, mix of LDAP and SQL, federation, etc) Keystone is planning to increase the maximum size

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

2014-02-26 Thread Adam Young
On 02/26/2014 08:25 AM, Dolph Mathews wrote: On Tue, Feb 25, 2014 at 2:38 PM, Jay Pipes jaypi...@gmail.com mailto:jaypi...@gmail.com wrote: On Tue, 2014-02-25 at 11:47 -0800, Morgan Fainberg wrote: For purposes of supporting multiple backends for Identity (multiple LDAP, mix of

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

2014-02-25 Thread Morgan Fainberg
For purposes of supporting multiple backends for Identity (multiple LDAP, mix of LDAP and SQL, federation, etc) Keystone is planning to increase the maximum size of the USER_ID field from an upper limit of 64 to an upper limit of 255. This change would not impact any currently assigned USER_IDs

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

2014-02-25 Thread Jay Pipes
On Tue, 2014-02-25 at 11:47 -0800, Morgan Fainberg wrote: For purposes of supporting multiple backends for Identity (multiple LDAP, mix of LDAP and SQL, federation, etc) Keystone is planning to increase the maximum size of the USER_ID field from an upper limit of 64 to an upper limit of 255.

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

2014-02-25 Thread Steven Hardy
On Tue, Feb 25, 2014 at 11:47:43AM -0800, Morgan Fainberg wrote: For purposes of supporting multiple backends for Identity (multiple LDAP, mix of LDAP and SQL, federation, etc) Keystone is planning to increase the maximum size of the USER_ID field from an upper limit of 64 to an upper limit