BD is in and of itself a separate block device, not file
> system). I would imagine OpenStack works in a similar fashion.
>
> --
> *From: *"hp cre"
> *To: *"Gregory Farnum"
> *Cc: *ceph-users@lists.ceph.com
> *Sent: *Tuesday, November
On Tue, Nov 18, 2014 at 1:43 PM, hp cre wrote:
> Ok thanks Greg.
> But what openstack does, AFAIU, is use rbd devices directly, one for each
> Vm instance, right? And that's how it supports live migrations on KVM,
> etc.. Right? Openstack and similar cloud frameworks don't need to create vm
>
shion.
- Original Message -
From: "hp cre"
To: "Gregory Farnum"
Cc: ceph-users@lists.ceph.com
Sent: Tuesday, November 18, 2014 4:43:07 PM
Subject: Re: [ceph-users] Concurrency in ceph
Ok thanks Greg.
But what openstack does, AFAIU, is use rbd devices directly, one for each
Ok thanks Greg.
But what openstack does, AFAIU, is use rbd devices directly, one for each
Vm instance, right? And that's how it supports live migrations on KVM,
etc.. Right? Openstack and similar cloud frameworks don't need to create vm
instances on filesystems, am I correct?
On 18 Nov 2014 23
On Tue, Nov 18, 2014 at 1:26 PM, hp cre wrote:
> Hello everyone,
>
> I'm new to ceph but been working with proprietary clustered filesystem for
> quite some time.
>
> I almost understand how ceph works, but have a couple of questions which
> have been asked before here, but i didn't understand t
Hello everyone,
I'm new to ceph but been working with proprietary clustered filesystem for
quite some time.
I almost understand how ceph works, but have a couple of questions which
have been asked before here, but i didn't understand the answer.
In the closed source world, we use clustered fi
