[ https://issues.apache.org/jira/browse/KAFKA-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215589#comment-14215589 ]
Joe Stein edited comment on KAFKA-1173 at 11/18/14 1:47 AM: ------------------------------------------------------------ [~ewencp] The aws parts are further along and servers are spinning up with the code and configs installed but still getting issue. All of the DNS hosts are on the public IP but my default security group is only setup for 22 on the outside and only the internal security group for inside. Can this change to use the private IP instead of the public address? should I have set ec2_associate_public_ip = false I ran vagrant outside the VPC but maybe I should change it to false though the comment above that line is the reason I didn't? Maybe something else but right now the servers can only communicate with each on the internal private IP but hosts spin up on public ip (however we fix that) thanks! was (Author: joestein): [~ewencp] The aws parts are further along and servers are spinning up with the code and configs installed but still getting issue. All of the DNS hosts are on the public IP but my default security group is only setup for 22 on the outside and only the internal security group for inside. Can this change to use the private IP instead of the public address? should I have set ec2_associate_public_ip = false I ran vagrant outside the VPC but maybe I should change it to false though the comment above that line is the reason I didn't? > 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.8.3 > > Attachments: 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 > > > 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)