Mostly empty projects for adding Storm. Seeded with the jars from storm-0.9.2-incubating (unmodified)
Barely-working version of Storm in Blue Coffee. As far as I can see Nimbus and Supervisor start, but my attempt at using a Log4j config file failed so it looks like I do indeed need a logback config file instead.
Add support for Logback configuration files, and change Storm to use that. Now Storm seems to be working and logging nicely.
Plumb storm.local.dir through so I can explicitly specify the directory.
Add a Console appender class to Logback, and use that in Storm.
Two main changes:
1. Enable Storm UI.
2. Enhance Storm's unit test to submit a topology to the cluster.
Make the Storm test a terminating contained unit test by outputting the output from the topology into a file and making sure that file gets the expected output.
Fill out StormNodeBase to be able to deploy Storm to Azure. Not tested yet.
Add a fairly empty test service that runs Storm (Nimbus and Supervisor) and Kafka roles with a ZooKeeper role to support them.
Upgrade the PowerShell deployer script to work with the new Azure PowerShell
Start making the Storm test service richer and juicier:
1. Add a Java project to start putting an interesting Storm topology. Right now it's a simple one, next it'll be richer.
2. Plumb that project as a resource in the Nimbus role in my test service, and submit that along with running the Storm UI on that node.
Make my test topology for Storm a bit more interesting by adding an output-to-Azure Trident function in there.
Make my Storm topology even juicier: route things to/from Kafka!
More fixes to my deployment script after my previous fix broke it.
Fixes needed to get my Storm test service to work correctly in Azure:
1. Open Firewall ports.
2. Accomodate the different name I gave the ZooKeeper role.
Ignore the Storm test by default.
Version bump