Thanks
-Original Message-
From: Christian Schwede [mailto:cschw...@redhat.com]
Sent: Thursday, January 05, 2017 1:29 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [TripleO] Fixing Swift rings when
upscaling/replacing nodes in TripleO deployments
On 05.01.2017 17
rcloud operational by
> definition, so I think this is probably OK?
>
> Steve
>>
>> -Original Message-
>> From: Christian Schwede [mailto:cschw...@redhat.com]
>> Sent: Thursday, January 05, 2017 6:14 AM
>> To: OpenStack Development Mailing List <openstac
K?
Steve
>
> -Original Message-
> From: Christian Schwede [mailto:cschw...@redhat.com]
> Sent: Thursday, January 05, 2017 6:14 AM
> To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org>
> Subject: [openstack-dev] [TripleO] Fixing Swift rings when
>
To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [TripleO] Fixing Swift rings when upscaling/replacing
nodes in TripleO deployments
Hello everyone,
there was an earlier discussion on $subject last year [1] regarding a bug when
ups
Hello everyone,
there was an earlier discussion on $subject last year [1] regarding a
bug when upscaling or replacing nodes in TripleO [2].
Shortly summarized: Swift rings are built on each node separately, and
if adding or replacing nodes (or disks) this will break the rings
because they are no
