Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.5.0
    • Component/s: None
    • Labels:
      None

      Description

      jclouds now supports a "bring your own nodes" (BYON) provider (http://code.google.com/p/jclouds/issues/detail?id=452), which would be useful to take advantage of in Whirr. One use case is deploying Whirr services to local VMs during development and testing.

        Issue Links

          Activity

          Hide
          Tom White added a comment -

          A lot of the code is in WHIRR-239 - it just needs some generalization to support both cases.

          Show
          Tom White added a comment - A lot of the code is in WHIRR-239 - it just needs some generalization to support both cases.
          Hide
          Andrei Savu added a comment -

          This is going to be really useful when implementing new services. I'm thinking virtualbox + snapshotting + revert to clean state = easy & fast.

          Show
          Andrei Savu added a comment - This is going to be really useful when implementing new services. I'm thinking virtualbox + snapshotting + revert to clean state = easy & fast.
          Hide
          Tom White added a comment -

          I got the ZooKeeper integration test working with this patch, running against two VMs.

          Given that this is primarily for development, it's probably good enough to go in. It would be really nice to have some supporting scripts to control VMware or VirtualBox VMs, as it's pretty fiddly otherwise. Also, the Java installation phase is fairly slow; doing some work to improve this would help the dev feedback loop (WHIRR-88? WHIRR-266?).

          Here was the config I used:

          nodes:
              - id: ubuntu1
                hostname: 192.168.54.160
                os_arch: x86
                os_family: ubuntu
                os_description: ubuntu
                os_version: 10.04
                group: whirr
                username: tom
                credential: xxx
                sudo_password: xxx
              - id: ubuntu2
                hostname: 192.168.54.161
                os_arch: x86
                os_family: ubuntu
                os_description: ubuntu
                os_version: 10.04
                group: whirr
                username: tom
                credential: xxx
                sudo_password: xxx
          
          mvn verify -Pintegration -DargLine="-Dwhirr.test.provider=byon -Dwhirr.test.identity=blah -Dwhirr.test.credential=blah -Dconfig=.whirr-test.properties"
          

          And .whirr-test.properties contained the following:

          whirr.service-name=byon
          whirr.provider=byon
          jclouds.byon.endpoint=file:///Users/tom/whirr-byon.yaml
          
          Show
          Tom White added a comment - I got the ZooKeeper integration test working with this patch, running against two VMs. Given that this is primarily for development, it's probably good enough to go in. It would be really nice to have some supporting scripts to control VMware or VirtualBox VMs, as it's pretty fiddly otherwise. Also, the Java installation phase is fairly slow; doing some work to improve this would help the dev feedback loop ( WHIRR-88 ? WHIRR-266 ?). Here was the config I used: nodes: - id: ubuntu1 hostname: 192.168.54.160 os_arch: x86 os_family: ubuntu os_description: ubuntu os_version: 10.04 group: whirr username: tom credential: xxx sudo_password: xxx - id: ubuntu2 hostname: 192.168.54.161 os_arch: x86 os_family: ubuntu os_description: ubuntu os_version: 10.04 group: whirr username: tom credential: xxx sudo_password: xxx mvn verify -Pintegration -DargLine="-Dwhirr.test.provider=byon -Dwhirr.test.identity=blah -Dwhirr.test.credential=blah -Dconfig=.whirr-test.properties" And .whirr-test.properties contained the following: whirr.service-name=byon whirr.provider=byon jclouds.byon.endpoint=file: ///Users/tom/whirr-byon.yaml
          Hide
          Tom White added a comment -

          Unless anyone has any objections, I'd like to commit this in the next few days.

          Show
          Tom White added a comment - Unless anyone has any objections, I'd like to commit this in the next few days.
          Hide
          Adrian Cole added a comment -

          Hi, Tom.

          I think the default should indeed include trivial nodemetadata for localhost, using the assumption that you are on linux or osx and will login with the current username with default ssh keys from the home dir. Otherwise, looks sensible!

          -Adrian

          Show
          Adrian Cole added a comment - Hi, Tom. I think the default should indeed include trivial nodemetadata for localhost, using the assumption that you are on linux or osx and will login with the current username with default ssh keys from the home dir. Otherwise, looks sensible! -Adrian
          Hide
          Tom White added a comment -

          That would be a nice default, but I don't see a way of having a default sudo_password. Also, currently Whirr cannot clean up a clusters state except by destoying the node, which obviously doesn't apply in the localhost case. WHIRR-239 dealt with this by introducing destroy scripts to stop and uninstall services. So we could do this, but it's a bit more work, and perhaps left to the other JIRA.

          Show
          Tom White added a comment - That would be a nice default, but I don't see a way of having a default sudo_password. Also, currently Whirr cannot clean up a clusters state except by destoying the node, which obviously doesn't apply in the localhost case. WHIRR-239 dealt with this by introducing destroy scripts to stop and uninstall services. So we could do this, but it's a bit more work, and perhaps left to the other JIRA.
          Hide
          Adrian Cole added a comment -

          I see what you're saying.. prompting for a sudo_password could also get clunky.

          +1 to commit and leave follow-up to other jiras

          Show
          Adrian Cole added a comment - I see what you're saying.. prompting for a sudo_password could also get clunky. +1 to commit and leave follow-up to other jiras
          Hide
          Tom White added a comment -

          I've just committed this.

          Show
          Tom White added a comment - I've just committed this.

            People

            • Assignee:
              Tom White
              Reporter:
              Tom White
            • Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development