root
/
kafka
mirror of https://github.com/apache/kafka.git
1
0
Fork 0
Code Issues Actions 2 Packages Projects Releases Wiki Activity

KAFKA-8344; Fix vagrant-up.sh to work with AWS properly 

For now, `vagrant/vagrant-up.sh --aws` fails because
the `vagrant hostmanager` command in that script lacks
the `--aws` option. This PR adds it.

I ran `vagrant/vagrant-up.sh --aws` with and without
`--no-parallel` option and confirmed both worked
as expected.

Author: Kengo Seki <sekikn@apache.org>

Reviewers: Gwen Shapira

Closes #6703 from sekikn/KAFKA-8344
This commit is contained in:
Kengo Seki 2019-05-09 22:48:23 -07:00 committed by Gwen Shapira
parent 96096cebe1
commit c638235dbc
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
vagrant/vagrant-up.sh
View File

@ -220,7 +220,7 @@ function bring_up_aws {
# We still have to bring up zookeeper/broker nodes serially
echo "Bringing up zookeeper/broker machines serially"
vagrant up --provider=aws --no-parallel --no-provision $zk_broker_machines $debug
vagrant hostmanager
vagrant hostmanager --provider=aws
vagrant provision
fi
@ -231,11 +231,11 @@ function bring_up_aws {
local vagrant_rsync_temp_dir=$(mktemp -d);
TMPDIR=$vagrant_rsync_temp_dir vagrant_batch_command "vagrant up $debug --provider=aws" "$worker_machines" "$max_parallel"
rm -rf $vagrant_rsync_temp_dir
vagrant hostmanager
vagrant hostmanager --provider=aws
fi
else
vagrant up --provider=aws --no-parallel --no-provision $debug
vagrant hostmanager
vagrant hostmanager --provider=aws
vagrant provision
fi