Open Stack

On 05/18/2013 06:57 PM, Davanum Srinivas wrote:
> Gary,
>
> We are at a stalemate between your -1 and Dolph Mathews's -1 on what
> the naming of the group in session.py [1]

I'd say that we are between a rock and a hard place :)

Below is a partial mapping on how the projects have the section and key 
names for the SQL database:

Nova: Section - DEFAULT; Key - sql_connection
Cinder: Section - DEFAULT; Key - sql_connection
Glance: Section - DEFAULT; Key - sql_connection
Quantum: Section - DATABASE; key - sql_connection
Keystone: Section - SQL; key - connection

My concern is the upgrade process and being backward compatible to the 
existing configuration. The code that you have done works great for 
Nova, Cinder and Glance. Problem is that it does not work for Quantum 
and Keystone.

Is there anyway of ensuring that the Quantum and Keystone configurations 
are also supported. I am not sure that the common configuration module 
supports more than one deprecated section and key name. If so great.

I am really impartial to the section name. I prefer database but can be 
easily swayed as it is not something that is written in stone. But What 
I really do think is important is that we do not break things when going 
from Grizzly to Havana.

Thanks
Gary

> So throwing it out where...what should it be? "database" or
> "sqlalchemy"? We need to pick one and i'll change the review
>
> thanks,
> dims
>
> [1] https://review.openstack.org/#/c/27345/9/openstack/common/db/sqlalchemy/session.py,unified
>
> On Thu, May 16, 2013 at 1:04 AM, Gary Kotton<gkotton at redhat.com>  wrote:
>> Hi,
>> Any chance on getting a review for https://review.openstack.org/#/c/27345/.
>> This is blocking the OSLO DB usage of Quantum. It would be nice to be able
>> to get this in by H-1.
>> Thanks
>> Gary
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>