Skip to content
This repository
branch: master

Dec 11, 2013

  1. Antoni Batchelli

    Merge pull request #50 from lorcan/updatezookeeper

    Updated zookeeper to latest stable (3.3.6)
    tbatchelli authored

Dec 09, 2013

  1. Lorcan Coyle

    Updated zookeeper to latest stable (3.3.6)

    The specified zookeeper version must be available here:
    http://www.apache.org/dist/zookeeper/
    However 3.3.5 is no longer available from there, which causes a
    deployment failure. This problem was [first highlighted by Lorin
    Kobashigawa on the storm-user mailing
    list](https://groups.google.com/d/msg/storm-user/i0x3WFgW36k/dd5vufPkFj4
    J).
    lorcan authored

Nov 14, 2013

  1. Antoni Batchelli

    Merge pull request #48 from lorcan/customlein

    lein1 is used for deploying storm <0.9.0, otherwise lein2 is used.
    tbatchelli authored

Nov 07, 2013

  1. Lorcan Coyle

    BugFix: storm pre 0.9.0 requires lein1.

    We test which branch is being used - if it is <0.9.0 we use lein2
    (currently 2.3.2), otherwise we use lein1 (currently 1.5.2). This
    addresses a bug reported by Ryan Ebanks on the mailing list:
    https://groups.google.com/forum/#!topic/storm-user/5qOUkMfXkj4
    lorcan authored
  2. Lorcan Coyle

    Moved the branch functions into their own namespace

    To facilitate reuse.
    lorcan authored

Nov 02, 2013

  1. Antoni Batchelli

    Merge pull request #47 from lorcan/fixB

    BugFix: --branch was being ignored in storm-deploy due to typo
    tbatchelli authored
  2. Lorcan Coyle

    BugFix: --branch was being ignored in storm-deploy due to typo

    Value of variable `branch` was not being used, rather git was searching
    for the branch called "branch".
    lorcan authored

Oct 23, 2013

  1. Antoni Batchelli

    Merge pull request #45 from lorcan/checkoutcommit

    Allows storm-deploy more flexibility - checkout branches and SHA1s
    tbatchelli authored
  2. Antoni Batchelli

    Merge pull request #40 from xpe/issue-39

    Fix for #39.
    tbatchelli authored

Oct 03, 2013

  1. Lorcan Coyle

    Allows storm-deploy to select both a storm branch and a SHA1 commit

    The storm `--release` model is very unclear and not all that useful.
    Currently there is a choice of passing a no release, in which case you
    get a version of storm based on the latest commit from master or you
    get to pass a release which gets you the latest commit from that
    branch, e.g.,
    
        lein deploy-storm --start --name mycluster --release 0.9.0
    
    gets you storm 0.9.0wip16 (roughly, actually it gets you commit
    (d12c335, which is between 0.9.0-wip16
    and 0.9.0-wip17)
    
    and
    
        lein deploy-storm --start --name mycluster
    
    gets you the latest commit from master. It's not possible to get
    anything inbetween.
    
    This commit drops the `--release` argument in favour of a `--branch`
    argument (equivalent to `--release`) and a `--commit` argument, which
    takes a SHA1. If a commit is passed then we attempt to checkout that
    SHA1 into a new branch and use that. This gives us much more
    flexibility, e.g., to checkout storm 0.9.0-rc2 you would run
    
            lein deploy-storm --start --name mycluster --branch master
    --commit 32098d5
    
    If you want the latest version from a specific branch (say 0.8.3) you
    can execute
    
            lein deploy-storm --start --name mycluster --branch 0.8.3
    
    and if you want the bleeding edge you can still execute this get the
    latest commit from master
    
            lein deploy-storm --start --name mycluster
    
    The diff on this commit is bigger than it might have been because i
    deliberately changed `release` to `branch` wherever possible. I think
    now that storm has both releases (since 0.9.9-rc1) and branches we
    should make the code closer to what's actually happening (i.e.,
    checking out branches rather than releases).
    lorcan authored

Jul 24, 2013

  1. David James

    Likely fix for #39.

    I think that the upgrade from jClouds 1.4.2 to 1.5.1 in the previous
    commit (9d6e47b) made a change in how `.createSecurityGroupInRegion`
    works (see security.clj).
    xpe authored

Jul 14, 2013

  1. Antoni Batchelli

    Force the process to exit once it is done. Fixes #37.

    This is issue in Clojure explains is related: http://dev.clojure.org/jira/browse/CLJ-959
    tbatchelli authored
  2. Antoni Batchelli

    Update jclouds dependencies. Fixes #36

    tbatchelli authored

Apr 02, 2013

  1. Jason Jackson

    Merge pull request #29 from adsummos/upgrade-pallet-to-0.7.3

    Upgrade to pallet 0.7.3.
    jasonjckn authored
  2. Upgrade to pallet 0.7.3.

    Gordon Worley authored

Mar 31, 2013

  1. Jason Jackson

    Merge pull request #17 from travis/master

    Update to lein 2
    jasonjckn authored

Mar 25, 2013

  1. Travis Vachon

    Merge branch 'master' of github.com:nathanmarz/storm-deploy

    Conflicts:
    	project.clj
    travis authored

Mar 23, 2013

  1. Jason Jackson

    Merge pull request #26 from guarly/aws_auth_error

    Fix AWS error: InvalidPlacementGroup.Unknown
    jasonjckn authored

Feb 15, 2013

  1. Jason Jackson

    Merge pull request #27 from guarly/ubuntu_missing_apaches_mod_php

    Ganglia UI missing mod_php in apache
    jasonjckn authored

Feb 11, 2013

  1. guarly

    Ganglia UI missing mod_php in apache

    Add the libapache2-mod-php5 package to
    fix missing php handler in apache
    guarly authored
  2. guarly

    Fix AWS error: InvalidPlacementGroup.Unknown

    AWS's call to AuthorizeSecurityGroupIngress doesn't
    like being called specifying the same UserID as the
    current user.
    guarly authored

Feb 06, 2013

  1. Jason Jackson

    Merge pull request #23 from petermelias/master

    Fixed IP Address Output to properly list all the IPs for the various nodes
    jasonjckn authored

Feb 01, 2013

  1. Peter M. Elias

    fixed IP address output to properly list ALL ips for given node types.

    petermelias authored

Jan 31, 2013

  1. Peter M. Elias

    false alarm, no booting issues

    petermelias authored

Jan 30, 2013

  1. Jason Jackson

    Merge pull request #20 from petermelias/master

    Fixed two SEVERE bugs (build breakers in fact) in the storm build portion of deploy script
    jasonjckn authored
  2. Peter M. Elias

    refactored get-release to use bound symbols instead of some hackish d…

    …ef statements
    petermelias authored
  3. Peter M. Elias

    fixed bash execution environment for storm build and fixed pallet par…

    …sing for release parameter
    petermelias authored

Jan 29, 2013

  1. Kasper Grud Skat Madsen

    fixed typo

    KasperMadsen authored
  2. Kasper Grud Skat Madsen

    Download release is now based on github branch, not zipped release.

    KasperMadsen authored

Jan 23, 2013

  1. Kasper Grud Skat Madsen

    Update to Ubuntu 12.04 64bit AMI

    KasperMadsen authored

Jan 20, 2013

  1. Kasper Grud Skat Madsen

    Solve missing dependencies.

    Ensure JNA is not read from system, but from included lib.
    KasperMadsen authored
  2. Kasper Grud Skat Madsen

    Cleaned up readme

    KasperMadsen authored
  3. Kasper Grud Skat Madsen

    Merge pull request #12 from barkbarkuk/master

    Updates pallet to 0.72 (jclouds 1.4.2)
    KasperMadsen authored

Nov 17, 2012

  1. Travis Vachon

    Update to lein 2

    Note that this changes the deploy command from
    
    lein run :deploy --start --name mycluster --release {release version}
    
    to
    
    lein deploy-storm --start --name mycluster --release {release version}
    travis authored

Sep 28, 2012

  1. Peter Hibbert

    Changes to make storm-deploy work with more recent versions of pallet…

    …/jclouds:
    
      - Pulls in changes from rummble to allow functioning in different regions.
      - Updates dependencies in project.clj
      - Updated jclouds namespace references to new versions (with a '2')
      - Updated use of nodes-with-tag to new nodes-in-group function.
      - Fixed warnings about use of deprecated functions.
      - Changes ganglia.clj as librrd2-dev wasn't available in test deployment and caused failure.
      - Made use of log4j to capture everything in one file which was helping me diagnose issues.
    barkbarkuk authored
Something went wrong with that request. Please try again.