When I was at Target, we had a lot of success with Rundeck.  It was a quick
way to push out changes to hundreds of clusters.
https://www.rundeck.com/open-source


On Mon, Oct 18, 2021 at 12:19 PM Yakir Gibraltar <yaki...@gmail.com> wrote:

> We manage via Puppet:  https://github.com/voxpupuli/puppet-cassandra
>
> On Mon, Oct 18, 2021 at 7:19 PM Elliott Sims <elli...@backblaze.com>
> wrote:
>
>> Ansible here as well with a similar setup.  A play at the end of the
>> playbook that waits until all nodes in the cluster are "UN" before moving
>> on to the next node to change.
>>
>> On Mon, Oct 18, 2021 at 10:01 AM vytenis silgalis <vsilga...@gmail.com>
>> wrote:
>>
>>> Yep, also use Ansible with configs living in git here.
>>>
>>> On Fri, Oct 15, 2021 at 5:19 PM Bowen Song <bo...@bso.ng> wrote:
>>>
>>>> We have Cassandra on bare-metal servers, and we manage our servers via
>>>> Ansible. In this use case, we create an Ansible playbook to update the
>>>> servers one by one, change the cassandra.yaml file, restart Cassandra, and
>>>> wait for it to finish the restart, and then wait for a few minutes before
>>>> moving on to the next server.
>>>> On 15/10/2021 22:42, ZAIDI, ASAD wrote:
>>>>
>>>>
>>>>
>>>> Hello Folks,
>>>>
>>>>
>>>>
>>>> Can you guys please suggest tool or approach  to update  cassandra.yaml
>>>> file in multi-dc environment with large number of nodes efficiently.
>>>>
>>>>
>>>>
>>>> Thank you.
>>>>
>>>> Asad
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>
> --
> *בברכה,*
> *יקיר גיברלטר*
>

Reply via email to