Martin Kleppmann created SAMZA-189:
--------------------------------------
Summary: Move Vagrant setup out of hello-samza
Key: SAMZA-189
URL: https://issues.apache.org/jira/browse/SAMZA-189
Project: Samza
Issue Type: Improvement
Components: hello-samza
Reporter: Martin Kleppmann
As discussed [on the mailing
list|http://mail-archives.apache.org/mod_mbox/incubator-samza-dev/201402.mbox/%3C1B43C7411DB20E47AB0FB62E7262B80179BA9981%40ESV4-MBX01.linkedin.biz%3E],
we want to have just one way of running hello-samza, namely with bin/grid as
described [in the website
docs|http://samza.incubator.apache.org/startup/hello-samza/0.7.0/]. At the
moment, the hello-samza README gives different instructions for running Samza
with Vagrant. It's confusing that there are two conflicting sets of
instructions.
At the moment the Vagrant setup basically prepares the VM, and then runs
bin/grid inside it. As long as the bin/grid script is part of hello-samza, it's
difficult to move the current Vagrant setup into a separate repo. But perhaps a
better approach would be to use a configuration management tool such as Puppet,
Chef or Ansible for setting up the Vagrant VM — that could also provide a
useful blueprint for people wanting to set up a real multi-machine deployment.
[Wirbelsturm|http://www.michael-noll.com/blog/2014/03/17/wirbelsturm-one-click-deploy-storm-kafka-clusters-with-vagrant-puppet/]
does something like this for Storm, and might be a good starting point.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
