Thank you John. I really appreciate your help!
Best regards,
Cody
On Tue, Oct 23, 2018 at 12:39 PM John Fulton wrote:
>
> On Tue, Oct 23, 2018 at 12:22 PM Cody wrote:
> >
> > Hi John,
> >
> > Thank you so much for the explanation.
> >
> > Now I am clear that I need to include the same previously
On Tue, Oct 23, 2018 at 12:22 PM Cody wrote:
>
> Hi John,
>
> Thank you so much for the explanation.
>
> Now I am clear that I need to include the same previously used
> environment file(s) for every subsequent scaling or upgrades in order
> to keep the settings. But, what about those changes made
Hi John,
Thank you so much for the explanation.
Now I am clear that I need to include the same previously used
environment file(s) for every subsequent scaling or upgrades in order
to keep the settings. But, what about those changes made via ceph
commands during daily operation since the last dep
On Mon, Oct 22, 2018 at 8:51 PM Cody wrote:
>
> Thank you John for the reply.
>
> I am unsure to what extent I should include in an environment file
> when it comes to scale a Ceph cluster. Should I include every
> customization done to the cluster since previous deployment? In my
> case, I have a
Thank you John for the reply.
I am unsure to what extent I should include in an environment file
when it comes to scale a Ceph cluster. Should I include every
customization done to the cluster since previous deployment? In my
case, I have altered the CRUSH hierarchy, changed failure domains, and
c
No, I don't see why it would hurt the existing settings, provided you
continue to pass the CRUSH data environment files.
John
On Sun, Oct 21, 2018, 10:08 PM Cody wrote:
> Hello folks,
>
> I have made some changes to a Ceph cluster initially deployed with
> OpenStack using TripleO. Specificall
Hello folks,
I have made some changes to a Ceph cluster initially deployed with
OpenStack using TripleO. Specifically, I have changed the CRUSH map
and failure domain for the pools used by the overcloud. Now, if I
attempt to add new storage nodes (with identical specs) to the cluster
simply by inc
