[openstack-dev] [Cinder]Persistance layer for cinder + taskflow

Joshua Harlow harlowja at yahoo-inc.com
Fri Mar 28 20:32:31 UTC 2014


That'd work to, allowing for trying out/deploying/using this feature in different ways if it's wanted.

Hopefully not to many issues, if so, u know where to find us ;-)

-Josh

From: Jay Pipes <jaypipes at gmail.com<mailto:jaypipes at gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Friday, March 28, 2014 at 12:52 PM
To: "openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [Cinder]Persistance layer for cinder + taskflow

On Fri, 2014-03-28 at 18:16 +0000, Duncan Thomas wrote:
On 28 March 2014 14:38, Joshua Harlow <harlowja at yahoo-inc.com<mailto:harlowja at yahoo-inc.com>> wrote:
> An idea that might be good to do is to start off using SQLite as the
> taskflow persistence backend.
>
> Get that working using SQLite files (which should be fine as a persistence
> method for most usages) and then after this works there can be discussion
> around moving those tables to something like MySQL and the
> benefits/drawbacks of doing that.
>
> What do u think?
>
> Start small then grow seems to be a good approach.
I'd say at tables to the existing database first, it adds the smallest
number of new moving parts, then look at a new database if and only if
there seems to be evidence that one is needed. As a systems operator,
it is hard enough managing one db let alone N local dbs...

My suggestion would be to add a new CONF option
(persistent_db_connection?) that would default to the value of
CONF.db.connection). That way you default to using the same DB as the
main Cinder tables, but automagically provide the deployer with the
ability to handle the taskflow tables separately if they want.

best,
-jay


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140328/f050f73b/attachment-0001.html>


More information about the OpenStack-dev mailing list