Rundeck VS Apache ZooKeeper

Have a look at rundeck.org

Firstly, I tried Rundeck and Apache Airflow. They are complete overkill for what I want to do. Then I found Cronicle which is light enough, besides it can pull double duty as a general purpose scheduler.

Yesterday we posted a Security Advisory to Github for a critical vulnerability in Rundeck Community and Rundeck Enterprise Docker images, versions 4.0 and earlier. Those Docker images contained a pre-generated SSH key pair in the default file path. If that key was used to configure SSH access to hosts, they would allow access to anyone with the exposed private key.

Never used it myself (we're currently working on deploying Tower) but I've heard that Rundeck is the goto for your exact use case: "Tower, but less heavy". I looked at it when evaluating for my current job and it looks like a good middle of the road solution and looks way easier to deploy than AWX. The tradeoff is that since it's not custom built for Ansible you can automate lots of other things with it (like just bash scripts and the like) but you get less of the Ansible-specific integrations and tooling that Tower offers.

Hi! This fix solves the bug, is ready to be included in the next release. Regards.

There is already an open GitHub issue on this, but I wanted to mention it here as it can cause some nasty surprises for those unaware.

Compare to rundeck after they were acquired by Pagerduty

https://github.com/rundeck/rundeck/graphs/contributors

You can install Kafka from https://kafka.apache.org/quickstart. Because Druid and Kafka both use Apache Zookeeper, I opted to use the Zookeeper deployment that comes with Druid, so didn’t start it with Kafka. Once running, I created two topics for me to post the data into, and for Druid to ingest from:

Please note that we use Zookeeper as the Governance Center.

Next, review deployment complexity such as DB-less versus database-backed deployments. For example, Kong does require running Cassandra or Postgres. Apigee requires Cassandra, Zookeeper, and Postgres to run, while other solutions like Express Gateway and Tyk only require Redis. Apache APISIX uses etcd as its data store, it stores and manages routing-related and plugin-related configurations in etcd in the Data Plane.

ZooKeeper, a system for coordinating distributed nodes, similar to Google's Chubby

ElasticJob achieves distributed coordination through ZooKeeper. In practical scenarios, users may start multiple jobs in the same project simultaneously, all of which use the same Apache Curator client. There are certain risks due to the nature of ZooKeeper and the callback method of Curator in a single event thread.

For now we just need to know that Kafka will be running n brokers acting as a cluster. The Kafka cluster will use Zookeeper to orchestrate the brokers.

We spin up a Zookeeper instance at port 2181 internally within the Docker network (i.e. not accessible from the host)

To solve this issue we can use a distributed system manager such as Zookeeper which can provide distributed synchronization. Zookeeper can maintain multiple ranges for our servers.

Support the deployment of the ZooKeeper cluster through Bitnami.