I had good experiences using the vagrant setup as it is on a mac, but did had to change some things. We are using docker now. I'm not sure about the general preference, but I would like a docker compose over the vagrant setup. Don't know if you really want it Kafka itself, and to give it support through.
On Mon, Mar 21, 2016 at 9:43 PM Ewen Cheslack-Postava (JIRA) < j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/KAFKA-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205083#comment-15205083 > ] > > Ewen Cheslack-Postava commented on KAFKA-1173: > ---------------------------------------------- > > [~gwenshap] Maybe? I had been thinking of our Vagrantfile as a tool for > Kafka developers. Technically I guess it gets shipped with the source > version. It doesn't get shipped with the binary versions afaik, which may > be confusing. > > I guess it's also a question of whether we want to treat it as > "supported"... > > > Using Vagrant to get up and running with Apache Kafka > > ----------------------------------------------------- > > > > Key: KAFKA-1173 > > URL: https://issues.apache.org/jira/browse/KAFKA-1173 > > Project: Kafka > > Issue Type: Improvement > > Reporter: Joe Stein > > Assignee: Ewen Cheslack-Postava > > Fix For: 0.9.0.0 > > > > Attachments: KAFKA-1173-JMX.patch, KAFKA-1173.patch, > KAFKA-1173_2013-12-07_12:07:55.patch, KAFKA-1173_2014-11-11_13:50:55.patch, > KAFKA-1173_2014-11-12_11:32:09.patch, KAFKA-1173_2014-11-18_16:01:33.patch > > > > > > 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 > > 1) Install Vagrant [ > http://www.vagrantup.com/](http://www.vagrantup.com/) > > 2) Install Virtual Box [ > https://www.virtualbox.org/](https://www.virtualbox.org/) > > 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 > > e.g. > > 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 > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
