[jira] [Created] (CASSSIDECAR-275) Implement cluster-wide config change orchestration in Sidecar

["Isaac Reath (Jira)" <ji...@apache.org>]

Isaac Reath created CASSSIDECAR-275:
---------------------------------------

             Summary: Implement cluster-wide config change orchestration in Sidecar
                 Key: CASSSIDECAR-275
                 URL: https://issues.apache.org/jira/browse/CASSSIDECAR-275
             Project: Sidecar for Apache Cassandra
          Issue Type: Improvement
            Reporter: Isaac Reath


In https://issues.apache.org/jira/browse/CASSSIDECAR-273, we propose adding the ability to manage configurations for a single Cassandra node via Sidecar. This ticket builds on that work to introduce new endpoints in Sidecar that can automate the rollout of configuration changes across the cluster. This rollout mechanism should support:
 * Rollout strategies that define how quickly the configuration change can be rolled out (e.g., one node at a time, percentage of a rack at a time, time to wait between steps).
 * Visibility into the status of the configuration rollout.
 * Pausing an in-progress rollout.
 * Aborting an in-progress rollout.
 * Rolling back the configuration change.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org