On Wed, Apr 25, 2012 at 6:04 PM, Andrew Bogott abog...@wikimedia.orgwrote:
On 4/25/12 4:48 PM, Nathanael Burton wrote:
On Thu, Mar 8, 2012 at 11:53 AM, Andrew Bogottabog...@wikimedia.org
wrote:
I'm working on an API and implementation to support the creation of
filesystems that are
On Thu, Mar 8, 2012 at 11:53 AM, Andrew Bogott abog...@wikimedia.org wrote:
I'm working on an API and implementation to support the creation of
filesystems that are shared among Nova instances.
http://wiki.openstack.org/SharedFS
My hope is to keep this API isolated from core Nova code,
On 4/25/12 4:48 PM, Nathanael Burton wrote:
On Thu, Mar 8, 2012 at 11:53 AM, Andrew Bogottabog...@wikimedia.org wrote:
I'm working on an API and implementation to support the creation of
filesystems that are shared among Nova instances.
http://wiki.openstack.org/SharedFS
My hope is
On Wed, Apr 25, 2012 at 6:04 PM, Andrew Bogott abog...@wikimedia.org wrote:
Nate --
The short answer is: I'm sure that it's straightforward to create a
'private' table which doesn't collide with existing nova tables, but I have
yet to do so.
The longer answer is: Everything about that
Has there been any investigation into using already existing plugin frameworks
and just use those (and/or make those better)?
Just from a quick google search:
http://wehart.blogspot.com/2009/01/python-plugin-frameworks.html
It might be useful to see if we can find one that is generic and
On Thu, Mar 08, 2012, Andrew Bogott abog...@wikimedia.org wrote:
1) DB support
I need a database table to keep track of some filesystem
metadata. My current implementation adds the table via
nova/db/sqlalchemy/migrate_repo... but is it really necessary to
coordinate this table with
6 matches
Mail list logo
