On Nov 8, 2017 7:33 AM, "Vasu Kulkarni" wrote:
On Tue, Nov 7, 2017 at 11:38 AM, Sage Weil wrote:
> On Tue, 7 Nov 2017, Alfredo Deza wrote:
>> On Tue, Nov 7, 2017 at 7:09 AM, kefu chai wrote:
>> > On Fri, Jun 9, 2017 at 3:37 AM, Sage Weil wrote:
>> >> At CDM yesterday we talked about removing t
On Tue, Nov 7, 2017 at 11:38 AM, Sage Weil wrote:
> On Tue, 7 Nov 2017, Alfredo Deza wrote:
>> On Tue, Nov 7, 2017 at 7:09 AM, kefu chai wrote:
>> > On Fri, Jun 9, 2017 at 3:37 AM, Sage Weil wrote:
>> >> At CDM yesterday we talked about removing the ability to name your ceph
>> >> clusters. The
On Tue, 7 Nov 2017, Alfredo Deza wrote:
> On Tue, Nov 7, 2017 at 7:09 AM, kefu chai wrote:
> > On Fri, Jun 9, 2017 at 3:37 AM, Sage Weil wrote:
> >> At CDM yesterday we talked about removing the ability to name your ceph
> >> clusters. There are a number of hurtles that make it difficult to full
On Tue, Nov 7, 2017 at 7:09 AM, kefu chai wrote:
> On Fri, Jun 9, 2017 at 3:37 AM, Sage Weil wrote:
>> At CDM yesterday we talked about removing the ability to name your ceph
>> clusters. There are a number of hurtles that make it difficult to fully
>> get rid of this functionality, not the leas
On Fri, Jun 9, 2017 at 3:37 AM, Sage Weil wrote:
> At CDM yesterday we talked about removing the ability to name your ceph
> clusters. There are a number of hurtles that make it difficult to fully
> get rid of this functionality, not the least of which is that some
> (many?) deployed clusters mak
On Fri, Jun 9, 2017 at 12:30 PM, Sage Weil wrote:
> On Fri, 9 Jun 2017, Erik McCormick wrote:
>> On Fri, Jun 9, 2017 at 12:07 PM, Sage Weil wrote:
>> > On Thu, 8 Jun 2017, Sage Weil wrote:
>> >> Questions:
>> >>
>> >> - Does anybody on the list use a non-default cluster name?
>> >> - If so, do
On 06/08/17 21:37, Sage Weil wrote:
> Questions:
>
> - Does anybody on the list use a non-default cluster name?
> - If so, do you have a reason not to switch back to 'ceph'?
>
> Thanks!
> sage
Will it still be possible for clients to use multiple clusters?
Also how does this affect rbd mirroring
On Fri, 9 Jun 2017, Dan van der Ster wrote:
> On Fri, Jun 9, 2017 at 5:58 PM, Vasu Kulkarni wrote:
> > On Fri, Jun 9, 2017 at 6:11 AM, Wes Dillingham
> > wrote:
> >> Similar to Dan's situation we utilize the --cluster name concept for our
> >> operations. Primarily for "datamover" nodes which do
On Fri, Jun 9, 2017 at 5:58 PM, Vasu Kulkarni wrote:
> On Fri, Jun 9, 2017 at 6:11 AM, Wes Dillingham
> wrote:
>> Similar to Dan's situation we utilize the --cluster name concept for our
>> operations. Primarily for "datamover" nodes which do incremental rbd
>> import/export between distinct clus
On Fri, 9 Jun 2017, Erik McCormick wrote:
> On Fri, Jun 9, 2017 at 12:07 PM, Sage Weil wrote:
> > On Thu, 8 Jun 2017, Sage Weil wrote:
> >> Questions:
> >>
> >> - Does anybody on the list use a non-default cluster name?
> >> - If so, do you have a reason not to switch back to 'ceph'?
> >
> > It
On Fri, Jun 9, 2017 at 12:07 PM, Sage Weil wrote:
> On Thu, 8 Jun 2017, Sage Weil wrote:
>> Questions:
>>
>> - Does anybody on the list use a non-default cluster name?
>> - If so, do you have a reason not to switch back to 'ceph'?
>
> It sounds like the answer is "yes," but not for daemons. Seve
On Thu, 8 Jun 2017, Sage Weil wrote:
> Questions:
>
> - Does anybody on the list use a non-default cluster name?
> - If so, do you have a reason not to switch back to 'ceph'?
It sounds like the answer is "yes," but not for daemons. Several users use
it on the client side to connect to multiple
On Fri, Jun 9, 2017 at 6:11 AM, Wes Dillingham
wrote:
> Similar to Dan's situation we utilize the --cluster name concept for our
> operations. Primarily for "datamover" nodes which do incremental rbd
> import/export between distinct clusters. This is entirely coordinated by
> utilizing the --clust
Similar to Dan's situation we utilize the --cluster name concept for our
operations. Primarily for "datamover" nodes which do incremental rbd
import/export between distinct clusters. This is entirely coordinated by
utilizing the --cluster option throughout.
The way we set it up is that all cluster
On Thu, Jun 8, 2017 at 3:54 PM, Sage Weil wrote:
> On Thu, 8 Jun 2017, Bassam Tabbara wrote:
>> Thanks Sage.
>>
>> > At CDM yesterday we talked about removing the ability to name your ceph
>> > clusters.
>>
>> Just to be clear, it would still be possible to run multiple ceph
>> clusters on the sam
On 06/09/2017 06:41 AM, Benjeman Meekhof wrote:
> Hi Sage,
>
> We did at one time run multiple clusters on our OSD nodes and RGW
> nodes (with Jewel). We accomplished this by putting code in our
> puppet-ceph module that would create additional systemd units with
> appropriate CLUSTER=name enviro
We have an internal management service that works at a higher layer
upstream on top of multiple Ceph clusters. It needs a way to
differentiate and connect separately to each of those clusters.
Presently making that distinction is relatively easy since we create
those connections based on /etc/conf/
Hi Sage,
We do use cluster names, we do not use ceph-deploy or ceph-ansible so in
the short term it is not an issue. We have scripts that call cli
commands with the --cluster XX parameter, would that still work ? What
time frame do you have in mind for removing this ?
Cheers /Maged
On 2017-06
Hi Sage,
We did at one time run multiple clusters on our OSD nodes and RGW
nodes (with Jewel). We accomplished this by putting code in our
puppet-ceph module that would create additional systemd units with
appropriate CLUSTER=name environment settings for clusters not named
ceph. IE, if the modu
Hi Sage,
We need named clusters on the client side. RBD or CephFS clients, or
monitoring/admin machines all need to be able to access several clusters.
Internally, each cluster is indeed called "ceph", but the clients use
distinct names to differentiate their configs/keyrings.
Cheers, Dan
On J
On Thu, 8 Jun 2017, Bassam Tabbara wrote:
> Thanks Sage.
>
> > At CDM yesterday we talked about removing the ability to name your ceph
> > clusters.
>
> Just to be clear, it would still be possible to run multiple ceph
> clusters on the same nodes, right?
Yes, but you'd need to either (1) use
Thanks Sage.
> At CDM yesterday we talked about removing the ability to name your ceph
> clusters.
Just to be clear, it would still be possible to run multiple ceph clusters on
the same nodes, right?
___
ceph-users mailing list
ceph-users@lists.ce
At CDM yesterday we talked about removing the ability to name your ceph
clusters. There are a number of hurtles that make it difficult to fully
get rid of this functionality, not the least of which is that some
(many?) deployed clusters make use of it. We decided that the most we can
do at th
23 matches
Mail list logo