Affects Version/s: None
Fix Version/s: 0.9.0.0
Vagrant has been getting a lot of pickup in the tech communities. I have found it very useful for development and testing and working with a few clients now using it to help virtualize their environments in repeatable ways.
Using Vagrant to get up and running.
For 0.8.0 I have a patch on github https://github.com/stealthly/kafka
In the main kafka folder
1) ./sbt update
2) ./sbt package
3) ./sbt assembly-package-dependency
4) vagrant up
once this is done
- Zookeeper will be running 192.168.50.5
- Broker 1 on 192.168.50.10
- Broker 2 on 192.168.50.20
- Broker 3 on 192.168.50.30
When you are all up and running you will be back at a command brompt.
If you want you can login to the machines using vagrant shh <machineName> but you don't need to.
You can access the brokers and zookeeper by their IP
bin/kafka-console-producer.sh --broker-list 192.168.50.10:9092,192.168.50.20:9092,192.168.50.30:9092 --topic sandbox
bin/kafka-console-consumer.sh --zookeeper 192.168.50.5:2181 --topic sandbox --from-beginning