Hello, Eric Swift is actually an object store rather then volume store. It is used for storing any types of objects as files in underlying file system. This files can be anything, including binary images of block volumes. HTTP is used for transporting objects to and from the store. Nova-volume service is totally different. It allows to attach virtual block devices to VMs by providing correct parameters for nova-compute's 'attach_volume' method. It has a number of drivers that can manage different storage back-ends (Linux LVs, SAN virtual disks, distributed storage systems), but all these back-ends must be able to provide a virtual block device to VMs, which Swift is not capable of. Primary integration point between Swift and nova-volume is a way to store snapshots of virtual volumes to Swift store as files: https://blueprints.launchpad.net/nova/+spec/store-snapshots-to-swift. Status of work on this blueprint is unknown to me.
-- Best regards, Oleg On Sat, Apr 28, 2012 at 10:15 AM, Eric Luo <nextf...@gmail.com> wrote: > Hello ,all > I am a little confused about the nova-volumes service and the swift.I know > both are about the volume store,but > what's the relationship between them ?Can some one please explain it to me > please :) > Thanks! > > Eric Luo > 2012-04-28 > > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp