Quoting Morgan Fainberg (2015-04-04 02:55:59)
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
On 4/6/15 2:52 PM, Morgan Fainberg wrote:
On Apr 6, 2015, at 11:41, Mike Bayer mba...@redhat.com
mailto:mba...@redhat.com wrote:
On 4/6/15 12:49 PM, David Stanek wrote:
Exactly. This is the direction I have been going. Functional tests
are written using the public APIs using the
On Apr 6, 2015, at 11:41, Mike Bayer mba...@redhat.com wrote:
On 4/6/15 12:49 PM, David Stanek wrote:
Exactly. This is the direction I have been going. Functional tests are
written using the public APIs using the client.
I would also add that I don't like that the Keystone unit
On 4/6/15 12:49 PM, David Stanek wrote:
Exactly. This is the direction I have been going. Functional tests are
written using the public APIs using the client.
I would also add that I don't like that the Keystone unit tests are so
database heavy. I would not want MySQL or ant RDBMS to be a
On Mon, Apr 6, 2015 at 2:41 PM, Mike Bayer mba...@redhat.com wrote:
On 4/6/15 12:49 PM, David Stanek wrote:
Exactly. This is the direction I have been going. Functional tests are
written using the public APIs using the client.
I would also add that I don't like that the Keystone unit
,
Dave Chen
From: Rodrigo Duarte [mailto:rodrigodso...@gmail.com]
Sent: Sunday, April 05, 2015 2:47 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Keystone] SQLite support (migrations,
work-arounds, and more), is it worth it?
yes please [2
On Apr 6, 2015, at 09:20, Mike Bayer mba...@redhat.com wrote:
On 4/6/15 12:06 PM, Clint Byrum wrote:
Excerpts from Boris Bobrov's message of 2015-04-03 18:29:08 -0700:
On Saturday 04 April 2015 03:55:59 Morgan Fainberg wrote:
I am looking forward to the Liberty cycle and seeing the
On 4/6/15 12:06 PM, Clint Byrum wrote:
Excerpts from Boris Bobrov's message of 2015-04-03 18:29:08 -0700:
On Saturday 04 April 2015 03:55:59 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
Exactly. This is the direction I have been going. Functional tests are
written using the public APIs using the client.
I would also add that I don't like that the Keystone unit tests are so
database heavy. I would not want MySQL or ant RDBMS to be a requirement for
running the tests.
On Mon, Apr
Excerpts from Boris Bobrov's message of 2015-04-03 18:29:08 -0700:
On Saturday 04 April 2015 03:55:59 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
I totally agree, since this is not used in production and make the dev job
more complicated.
@Henry If you want help with this, I would be glad to work with you to make
this clean up.
On Sat, Apr 4, 2015 at 2:55 AM Henry Nash hen...@linux.vnet.ibm.com wrote:
Fully support this. I, for one,
yes please [2]
On Sat, Apr 4, 2015 at 1:07 PM, Raildo Mascena rail...@gmail.com wrote:
I totally agree, since this is not used in production and make the dev job
more complicated.
@Henry If you want help with this, I would be glad to work with you to
make this clean up.
On Sat, Apr 4,
On Saturday 04 April 2015 03:55:59 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
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 Liberty we will have a full functional test suite
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
Fully support this. I, for one, volunteer to take on a lot of the work needed
to clean up any our tests/environment to allow this to a happen. Hardly a month
goes by without a fix having to be re-applied to our sql code to get round some
problem that didn’t show up in original testing because
16 matches
Mail list logo