openstack team mailing list archive

[Gabe Westmaas <gabe.westmaas@xxxxxxxxxxxxx>]

Maybe a good topic for next design summit is to define our next set of goals with migrations as the projects get larger and the usage of the projects increases in scale.  

Are migrations intended for all environments?  Dev, initial rollouts, small clouds, "enterprise" clouds?
Should data and schema migrations be maintained separately? More generally, how can migrations be written and maintained to allow for seamless upgrades?
Should we really require that we run all 68+ migrations to go from first install to current code? (No)
What is the line on database optimization?  How can we communicate that some optimizations will speed up the OpenStack projects long term, but will have a very serious performance impact on an already operating cloud during the migration?

And so on.  I'm sure there are lots more, and better questions.

Gabe

-----Original Message-----
From: openstack-bounces+gabe.westmaas=rackspace.com@xxxxxxxxxxxxxxxxxxx [mailto:openstack-bounces+gabe.westmaas=rackspace.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jay Pipes
Sent: Tuesday, January 10, 2012 8:53 PM
To: Monty Taylor
Cc: openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] Unique key is case-sensitive or *in*sensitive?

Fair enough :)

On Tue, Jan 10, 2012 at 8:48 PM, Monty Taylor <mordred@xxxxxxxxxxxx> wrote:
> I think we manage enough of the schema via sqlalchemy that expecting a 
> DBA to do this is unexpected. Also, it's nova,keystone and glance that 
> want to ensure a behavior of key matching - if we leave this up to 
> deployers, they will be more likely to get it wrong (and there isn't 
> really a great argument as to why they'd ever want to do it the other 
> way)
>
> I think it's possible to get sqlalchemy to do db-engine specific 
> properties in the case of the use of that engine...
>
> On 01/10/2012 05:16 PM, Jay Pipes wrote:
>> Not sure I would think that a migrate patch is the right approach 
>> here... I kind of feel like this is a DBA or sysops responsibility.
>>
>> Thoughts?
>>
>> -jay
>>
>> On Tue, Jan 10, 2012 at 4:43 PM, Nachi Ueno 
>> <ueno.nachi@xxxxxxxxxxxxxxxxxxxx> wrote:
>>> Hi Jay
>>>
>>> Thanks
>>> Is it possible to do it on sqlalchemy.migration ?
>>>
>>>
>>> 2012/1/10 Jay Pipes <jaypipes@xxxxxxxxx>:
>>>> +1 for Case Sensitive. For MySQL, this is a configuration issue. 
>>>> +The
>>>> default character set and collation should use the *_cs variants. 
>>>> For existing MySQL installations, an ALTER TABLE ... MODIFY COLUMN ...
>>>> CHARACTER SET ... COLLATION ... *_cs would need to be done for 
>>>> affected tables.
>>>>
>>>> -jay
>>>>
>>>> On Tue, Jan 10, 2012 at 4:15 PM, Nachi Ueno 
>>>> <ueno.nachi@xxxxxxxxxxxxxxxxxxxx> wrote:
>>>>> Hi folks
>>>>>
>>>>> Nova,Keystone,Glance uses RDBMS and they use unique key constraints.
>>>>> Nowadays, we can use Mysql,Sqlite,Postgresql.
>>>>> Unfortunately, the unique key behaviors of each DB are different.
>>>>>
>>>>> - Mysql : case-insensitive
>>>>> - Sqlite : case-sensitive
>>>>> - Postgresql : case-sensitive
>>>>>
>>>>> I wanna know the spec of OpenStack.
>>>>> Unique key is case-sensitive or *in*sensitive?
>>>>>
>>>>> Cheers
>>>>> Nati
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~openstack Post to     : 
>>>>> openstack@xxxxxxxxxxxxxxxxxxx Unsubscribe : 
>>>>> https://launchpad.net/~openstack More help   : 
>>>>> https://help.launchpad.net/ListHelp
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack Post to     : 
>> openstack@xxxxxxxxxxxxxxxxxxx Unsubscribe : 
>> https://launchpad.net/~openstack More help   : 
>> https://help.launchpad.net/ListHelp
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack Post to     : 
> openstack@xxxxxxxxxxxxxxxxxxx Unsubscribe : 
> https://launchpad.net/~openstack More help   : 
> https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp