----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27735/#review64949 -----------------------------------------------------------
vagrant/README.md <https://reviews.apache.org/r/27735/#comment107788> Will need to add an Apache license header. - Jun Rao On Nov. 19, 2014, 12:01 a.m., Ewen Cheslack-Postava wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/27735/ > ----------------------------------------------------------- > > (Updated Nov. 19, 2014, 12:01 a.m.) > > > Review request for kafka. > > > Bugs: KAFKA-1173 > https://issues.apache.org/jira/browse/KAFKA-1173 > > > Repository: kafka > > > Description > ------- > > Add basic EC2 support, cleaner Vagrantfile, README cleanup, etc. > > > Better naming, hostmanager for routable VM names, vagrant-cachier to reduce > startup cost, cleanup provisioning scripts, initial support for multiple > zookeepers, general cleanup. > > > Don't sync a few directories that aren't actually required on the server. > > > Add generic worker node support. > > > Default # of workers should be 0 > > > Add support for Zookeeper clusters. > > This requires us to split up allocating VMs and provisioning because Vagrant > will run the provisioner for the first node before all nodes are allocated. > This > leaves the first node running Zookeeper with unroutable peer hostnames which > it, > for some reason, caches as unroutable. The cluster never properly finishes > forming since the nodes are unable to open connections to nodes booted later > than they were. The simple solution is to make sure all nodes are booted > before > starting configuration so we have all the addresses and hostnames available > and > routable. > > Fix AWS provider commands in Vagrant README. > > > Addressing Joe's comments. > > > Add support for EC2 VPC settings. > > > Update Vagrant README to use --no-parallel when using EC2. > > There's an issue that causes Vagrant to hang when running in > parallel. The last message is from vagrant-hostmanager, but it's not > clear if it is the actual cause. > > Only setup private static IP addresses under VirtualBox. > > > Diffs > ----- > > .gitignore 99b32a6770e3da59bc0167d77d45ca339ac3dbbd > README.md 9aca90664b2a80a37125775ddbdea06ba6c53644 > Vagrantfile PRE-CREATION > vagrant/README.md PRE-CREATION > vagrant/base.sh PRE-CREATION > vagrant/broker.sh PRE-CREATION > vagrant/zk.sh PRE-CREATION > > Diff: https://reviews.apache.org/r/27735/diff/ > > > Testing > ------- > > > Thanks, > > Ewen Cheslack-Postava > >
