Re: [ANN] A framework for deploying Octopus using cephadm in the cloud
On Sat, Aug 1, 2020 at 5:50 AM Marc Roos <M.Roos@f1-outsourcing.eu> wrote:
I can understand the benefits of having a CO, I am still testing with mesos. However what is the benefit of having ceph daemons running in CO environment?
As I said in my original post, I use this for testing CephFS. There's no reason why you can't also use Ceph as a storage system in the cloud though. It just may not be as cost effective as the native cloud storage offering (like S3).
Except for your mds, mrg and radosgw, your osd daemons are bound to the hardware / disks they are running on. It is not like if osd.121 goes down, you can start it on some random node.
Why not? -- Patrick Donnelly, Ph.D. He / Him / His Principal Software Engineer Red Hat Sunnyvale, CA GPG: 19F28A586F808C2402351B93C3301A3E258DD79D
Except for your mds, mrg and radosgw, your osd daemons are bound to the hardware / disks they are running on. It is not like if osd.121 goes down, you can start it on some random node.
Why not?
The data stays on the old node not? If you did automate destroy/create of a new osd, that would also mean that the cluster has to replicate data to this 'new' osd.121, if there is even storage available on that node. And if there is indeed storage available and not used at that node, why not use it in the first place for an osd.122?
participants (2)
-
Marc Roos
-
Patrick Donnelly