Greg,
IMO the most critical risks when running Ceph are bugs that affect
daemon stability and the upgrade process.
Due to the speed of releases in the Ceph project, I feel having separate
physical hardware is the safer way to go, especially in light of your
mention of an SLA for your production services.
A separate non-production cluster will allow you to test and validate
new versions (including point releases within a stable series) before
you attempt to upgrade your production cluster.
Cheers,
Mike Dawson
Co-Founder & Director of Cloud Architecture
Cloudapt LLC
6330 East 75th Street, Suite 170
Indianapolis, IN 46250
On 7/31/2013 10:47 AM, Greg Poirier wrote:
Does anyone here have multiple clusters or segment their single cluster
in such a way as to try to maintain different SLAs for production vs
non-production services?
We have been toying with the idea of running separate clusters (on the
same hardware, but reserve a portion of the OSDs for the production
cluster), but I'd rather have a single cluster in order to more evenly
distribute load across all of the spindles.
Thoughts or observations from people with Ceph in production would be
greatly appreciated.
Greg
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
