Closed mfeldheim closed 9 years ago
Is the intent to setup multiple nodes on the same box? Otherwise I would think you would still need all the other pieces (binaries, init.d script, etc...)
I am using the recipe on Amazon opsworks, where I have two events. setup and configure. Setup is run once on each new instance, configure is run on all instances when one instance starts or stops. With the configure event I can update the zoo.cfg on all zoo instances. a configure recipe would be helpful here. Not sure about traditional chef deployments.
Sorry to not get back to you earlier. Since Chef tries to be idempotent I think you could just use the default recipe in both cases and each configure
event should just make any changes necessary but not re-install zookeeper. I'm closing this for now but feel free to re-open if you disagree or create a pull.
when running in a multi-node setup, I don't want to repeat the whole setup recipe for all nodes in order to add a new node. A separate configure recipe would be sufficient