[SAMZA-189] Move Vagrant setup out of hello-samza

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: hello-samza
• Assignee: Unassigned
• Reporter: Martin Kleppmann
• Created: 18/Mar/14 01:10
• Updated: 31/Mar/15 16:24

Description

As discussed on the mailing list, we want to have just one way of running hello-samza, namely with bin/grid as described in the website docs. 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 does something like this for Storm, and might be a good starting point.

Issue Links

• relates to: SAMZA-451 Vagrant hello-samza is broken