-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Be able to deploy into VPC #134
Comments
sounds like it'll be frustrating to work about but 👍 very important |
The simplest thing to do:
bin/storm jar events-0.0.1-SNAPSHOT-STANDALONE.jar streamparse.commands.submit_topology events.clj Please let us know if that doesn't work. |
Ah, I forgot one thing. You'll also need to have virtualenvs setup on all of your machines containing all of the Python prereqs you need. They will need to be located in the path indicated in your Once #99 is addressed, this step will no longer be necessary. |
You could also try a bit of ssh magic. This is all hypothetical because I don't have a test setup to try it on. Add Update your
If you don't have a common subdomain you'll have to list all of the hosts individually.
Setup your streamparse config to use all of the hosts normally (without bastion host). |
Thanks @codywilbourn. I knew I should have just asked you. 😄 |
Yeah +1 for SSH config as a way to manage this. We've had great success with this approach. |
I've got a Storm setup that I'd like to deploy within a VPC on AWS. As is pretty standard in VPC setups, there's a bastion server that you SSH into first, and then get into the instances. I can't find a way to get
sparse submit
to work with this setup, though. It'd be nice if the deploy script could work with this.Sidenote: one idea I had was to
lein uberjar
everything, then manuallyscp
that up to the servers. When I do that, though, and runbin/storm jar 0.0.1-STANDALONE.jar MAINCLASS
, I'm not sure what to put for MAINCLASS. My project.clj isdefproject events "0.0.1-SNAPSHOT"
, butevents
doesn't work. Any thoughts on that? Is the only option to run it throughlein
?I think it'd make sense to update the documentation to reflect these sort of outlying scenarios.
The text was updated successfully, but these errors were encountered: