openstack team mailing list archive

[Cole <coleton@xxxxxxxxx>]

gfs2/rgmanager works reliably for kvm so i don't see why gluster wouldn't.

On Mon, Jun 6, 2011 at 5:20 AM, Shehjar Tikoo <shehjart@xxxxxxxxxxx> wrote:

> My understanding is that the --instances_path will be the share to which
> the VM state will be synced on the source hypervisor. This synced image will
> then be used to restart the VM at  the destination hypervisor. Ideally, I'd
> like to avoid having a local copy of the VM state in order to provide
> persistence in VMs so that if the hypervisor fails or crashes, etc. the VM
> state on a Gluster volume can be used to restart it. I am not sure whether
> this is possible in OpenStack yet or if KVM will even support using a shared
> mount as a VM state storage. This is something I will be looking into. Of
> course, some references to docs, emails will be nice . Thanks.
>
>
> ________________________________________
> From: masumotok@xxxxxxxxxxxxx [masumotok@xxxxxxxxxxxxx]
> Sent: Monday, June 06, 2011 6:23 AM
> To: Shehjar Tikoo
> Cc: openstack@xxxxxxxxxxxxxxxxxxx; soren@xxxxxxxxxxx
> Subject: RE: [Openstack] Integrating GlusterFS with OpenStack
>
> Hi,
>
> > When doing live migration, we could let KVM migrate the
> > VM state and somehow tell gluster to migrate the disk image to the new
> > host (to maintain locality between the virtual machine and its storage).
> > Gluster already has the means to do live rebalancing, but I don't believe
> > an API to specify "I'd like for this particular file to reside on this
> > particular brick. Please make it so". That would *rock*.
>
> In current openstack live migration feature, a flag --instances_path
> specifies the path which has to be on shared storage. Live re-balancing
> sounds like good idea, and I think at least, just "--instances_path is on
> the glusterFS" is good option to users.
> If you want any help, my colleague and me would love to do ^^;
>
>
> > -----Original Message-----
> > From: openstack-bounces+masumotok=nttdata.co.jp@xxxxxxxxxxxxxxxxxxx
> > [mailto:openstack-bounces+masumotok=nttdata.co.jp@xxxxxxxxxxxxxxxxxx
> > t] On Behalf Of Soren Hansen
> > Sent: Monday, June 06, 2011 7:40 AM
> > To: Shehjar Tikoo
> > Cc: openstack@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Openstack] Integrating GlusterFS with OpenStack
> >
> > 2011/6/3 Shehjar Tikoo <shehjart@xxxxxxxxxxx>:
> > > We're aiming to integrate Gluster with Openstack in a way that allows
> > > GlusterFS to be used as the storage for application volumes as well
> > as VMs.
> > > I am interested in hearing your ideas on how such an integration can
> > > be performed. Being the openstack experts, could you please share some
> > > issues I should be considering, the problems I may run into or
> > > anything else you think I should know.
> >
> > One thing I'd love to be able to do is store my virtual disks on a
> gluster
> > filesystem that is shared across my compute nodes. The data would be
> > stored on the host that is actually running the virtual machine (think
> > NUFA scheduler). When doing live migration, we could let KVM migrate the
> > VM state and somehow tell gluster to migrate the disk image to the new
> > host (to maintain locality between the virtual machine and its storage).
> > Gluster already has the means to do live rebalancing, but I don't believe
> > an API to specify "I'd like for this particular file to reside on this
> > particular brick. Please make it so". That would *rock*.
> >
> > --
> > Soren Hansen        | http://linux2go.dk/ Ubuntu Developer    |
> > http://www.ubuntu.com/ OpenStack Developer | http://www.openstack.org/
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack
> > Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>