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. Sent from my really tiny device... On Mar 28, 2014, at 7:11 AM, "Kekane, Abhishek" <abhishek.kek...@nttdata.com<mailto:abhishek.kek...@nttdata.com>> wrote: Hello everyone, Currently I am working on adding persistence layer for create_volume api using taskflow. Could you please give your opinions on whether is it a good idea to add taskflow tables in existing cinder database or to create a new database for taskflow. Thanks & Regards, Abhishek Kekane ______________________________________________________________________ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
