-
Notifications
You must be signed in to change notification settings - Fork 148
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
storm-deploy for "new generation" ec2 hardware #57
Comments
This is almost certainly because the version of jclouds storm-deploy is using does not know about those. Unfortunately, I think at this point storm-deploy can't come up to the latest version of jclouds without first upgrading to pallet 0.8.0. |
Sorry to be newb about this - but what would the upgrade of pallet to 0.8.0 entail? |
A lot. Many things changed between 0.7.x and 0.8.x, so it's by no means straightforward. |
The pallet-jclouds library that wraps jclouds is compatible with both 0.7 and 0.8 of pallet, so an upgrade to pallet 0.8 is not required, although largely overdue. Having said this, pallet-jclouds might need an update if the APIs have changed from jclouds 1.5.5. One quick way to test is to directly upgrade the jclouds dependencies 1.6 or whichever is the jclouds version that has support for the new instances (see below) We’ll be looking into putting out a newer version of pallet-jclouds soon. Toni. The libraries to add into project.clj in storm-deploy in order to force an update to jclouds are: [org.jclouds/jclouds-all ~jclouds-ver] where ~jclouds-ver is the version of jclouds that you want. Also, you might want to update the pallet-jclouds dependency to 1.5.3 (currently 1.5.1) tbatchelli On February 13, 2014 at 9:17:33 AM, G Gordon Worley III ([email protected]) wrote:
|
Got me really excited --- however, still issues: --- project.clj --- :repositories { :dependencies [
:dev-dependencies [[swank-clojure "1.2.1"] Exception in thread "main" java.io.FileNotFoundException: Could not locate clojure/reflect__init.class or clojure/reflect.clj on classpath: (jclouds.clj:1) |
I was only able to go as high as pallet-jclouds 1.5.1 and jclouds 1.5.2 when I was actively working on my storm-deploy fork. Haven't revisited since then. |
So even with pallet-jclouds 1.5.1 and jclouds 1.5.2 it doesn't work for me... |
I have pushed a branch 'update-clojure-jclouds` that uses the latest jclouds version (1.7.1), and this should allow using all the newer hardware in AWS. Give it a try and report back if you find any issues so I can proceed to merge it into master. |
I'm looking to deploy storm (and zookeeper) into our VPC with the new i2 and c3 hardware that has recently come available to see if it makes sense for our setup.
I know there may be some issues with VPC and having to set up an IPSEC VPN, and I'm fully okay with that, however I cannot find a way (since I'm new to leiningen and storm-deploy) to get these new generation machines up and running.
When I try to deploy, I obviously get these errors:
The text was updated successfully, but these errors were encountered: