Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Priming kafka-manager with 'zkhosts' of a known set of kafka clusters #37

Open
vvutharkar opened this issue Mar 16, 2015 · 3 comments · May be fixed by #42
Open

Priming kafka-manager with 'zkhosts' of a known set of kafka clusters #37

vvutharkar opened this issue Mar 16, 2015 · 3 comments · May be fixed by #42

Comments

@vvutharkar
Copy link

Hi,

We want to automate some of the kafka management by

  • deploying a few kafka-manager instances via automation (puppet etc)
  • Each instance of kafka-manager is responsible for only a known set of kafka clusters (a bare bones compartmentalization)
  • We also intend to disable the 'add cluster' feature so that our customers cannot modify the scope of a given kafka-manager (what clusters you can manage via that particular instance)

To achieve this, we also need to be able to prime (pre-populate) a kafka-manager instance with a set of kafka clusters' 'zkhost' lists. We intend to provide the list via the application conf (As a list of lists) and set that value in the conf during puppet install of the kafka-manager.

But I am struggling a bit to find a nice 'bootstrap' (Startup) point in the lifecycle of the kafka-manager app to insert a populate_kafka_clusters() method. May be because I am very new to Scala and Play. Can you please point me to such a location or if there is none, can it be added so that other such initializations can be added by others at that interception point? Also can you point me to the code that takes the 'zkhosts' for a cluster and adds them to the backend store (kafka-manager's Zookeeper namespace /kafka-manager I presume)

@patelh
Copy link
Collaborator

patelh commented Mar 19, 2015

We may be able to introduce a way to make the kafka manager "read-only" in terms of adding/modifying/deleting clusters. And for bootstrap, we can just bundle a CLI utility which you can use to define a new cluster.

@vvutharkar vvutharkar linked a pull request Mar 28, 2015 that will close this issue
@sherzberg
Copy link

I would like a way to specify the clusters in the application.conf as well. It would also be nice to have a read only option too.

@miketheman
Copy link

I believe this effort has started inh ttps://github.com/yahoo/kafka-manager/commit/18d370dd60896100927dc17ced766bd358b56645 and has been getting updates as needed.
The conf file has an entry for "enabled features", so an admin of KM can choose behaviors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants