As written in this post, I developed a tool for constructing storm cluster more easily. When you want to add new features or investigate some bugs issued by others, this tool will be useful. Usually this kind of tools can only construct a cluster with released packages. storm-devenv enables us to construct storm cluster with your own storm code on your local machine. Vagrant and VirtualBox make is possible. I think that we can apply same process to AWS EC2 instances by using Vagrant. So I choose Vagrant as constructing tool. And as provisioning tool, I wrote chef cookbooks which is a de fact tool for configuration tool. I’d like to introduce storm-devenv mode detail in this post.
storm-devenv repository is here. If you are familiar with Vagrant and Chef cookbooks, you can easily understand all codebase.
storm-devenv uses Vagrant and Chef therefore first you have to install these software.
Chef packages are listed in
Gemfile so first restore rubygems.
$ cd storm-devenv $ bundle install
Build your own storm code
storm-devenv is for development of storm code itself. So if you have no storm code as tar format, I recommend you to build it.
You can see how to build in DEVELOPER.md. Or if you want to try with
released package, please download from official link. These packages should be put on
At last, all you have to do is a command.
$ vagrant up
It will take about 10 minutes. Of course this time depends on your environment and machine spec. You can confirm the state of this cluster from http://192.168.50.4:8080, if you don’t change your nimbus host ip.
storm-devenv has several improvement points.
- Storm cookbook should be under one version controle separately
- Support AWS EC2
- Make it easy to construct selfmade storm
I’d like to debug and develop improvements with storm-devenv from now. If you have any idea and opinion please let me know. Thank you.