Hello
I think, that changes that I made can be used by you "ZaitcevFS" all you
need for this is just add support for it to LFS middleware or build your
own middleware. And your middleware may use special hooks
(setup_partition) for prepare file system for files.
17.07.2012 20:40, Pete Zaitcev пишет:
On Mon, 16 Jul 2012 22:45:48 +0000
Victor Rodionov<victor.rodio...@nexenta.com> wrote:
Most of patch code was restructured, most of logic was moved to middleware
level and use hooks in Swift code. I create separate project (LFS middleware
https://github.com/nexenta/lfs) for now there are only 2 supported file system
types (XFS and ZFS) there. Also this middleware provide API for getting file
system status information (for example, for ZFS it's current pool status, etc).
It sounds strange to make Swift aware of the specific LFS. One day I come
up with ZaitcevFS and what happens then? Patching Swift again I presume.
I wish Gluster people would stop delaying their competing LFS proposal
and finally submit it. Their code was out for a year, but they apparently
are content to carry a fork forever:
http://review.gluster.com/805<==== for 1.4.5
http://review.gluster.com/3118<==== for 1.4.8
-- Pete
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
