On Thu, 5 Feb 2015, Lindsay Mathieson wrote:
> On 5 February 2015 at 07:22, Sage Weil wrote:
> > Is the snapshoting performed by ceph or by the fs? Can we
> switch to
> > xfs and have the same capabilities: instant snapshot + instant
> boot
> > from snapshot?
>
>
We want to use this script as a service for start/stop (but it wasn't
tested yet):
#!/bin/bash
# chkconfig: - 50 90
# description: make a journal for osd.0 in ram
start () {
-f /dev/shm/osd.0.journal || ceph-osd -i 0 --mkjournal
}
stop () {
service ceph stop osd.0 && ceph-osd -i osd.0 --flush-j
On 5 February 2015 at 07:22, Sage Weil wrote:
> > Is the snapshoting performed by ceph or by the fs? Can we switch to
> > xfs and have the same capabilities: instant snapshot + instant boot
> > from snapshot?
>
> The feature set and capabilities are identical. The difference is that on
> btrfs w
Hi Cristian,
> We will try to report back, but I'm not sure our use case is relevant.
> We are trying to use every dirty trick to speed up the VMs.
we have the same use-case.
> The second pool is for the tests machines and has the journal in ram,
> so this part is very volatile. We don't really
Thank you for the clarifications.
We will try to report back, but I'm not sure our use case is relevant.
We are trying to use every dirty trick to speed up the VMs.
We have only 1 replica, and 2 pools.
One pool with journal on disk, where the original instance exists (we
want to keep this one sa
On Wed, 4 Feb 2015, Cristian Falcas wrote:
> Hi,
>
> We have an openstack installation that uses ceph as the storage backend.
>
> We use mainly snapshot and boot from snapshot from an original
> instance with a 200gb disk. Something like this:
> 1. import original image
> 2. make volume from imag
Hi,
We have an openstack installation that uses ceph as the storage backend.
We use mainly snapshot and boot from snapshot from an original
instance with a 200gb disk. Something like this:
1. import original image
2. make volume from image (those 2 steps were done only once, when we
installed ope
