Ya, that would be the ideal, make it more modular so that nosql engines could be hooked in (if applicable).
It might also provide someone an opportunity to re-factor https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py which seems hairy (4000 lines??) On 9/23/11 3:10 PM, "Debo Dutta (dedutta)" <dedu...@cisco.com> wrote: This is a good idea. Actually it might be a very good idea to think of scalable/distributed nosql engines to interface with nova and other Openstack projects. Regards debo From: openstack-bounces+dedutta=cisco....@lists.launchpad.net [mailto:openstack-bounces+dedutta=cisco....@lists.launchpad.net] On Behalf Of Joshua Harlow Sent: Friday, September 23, 2011 2:40 PM To: openstack Subject: [Openstack] Database replacement? Howdy all, congrats on the diablo release! Has there been any thought on having a nova-db service that responds to requests for information from the db (or something like a db). This could be useful for companies that don't necessarily want to have a limiting factor being a database. Since when u scale past a certain number of compute nodes the database connections themselves may become a bottleneck (especially the heartbeat mechanism which updates a table every X seconds). It would be interesting if these types of request could go to the message queue instead and then the db backing could be swapped out with something more scalable (or still use mysql/sqlite...). Any thoughts? -Josh
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
