P.S.  I have opened and attached patches for a couple things that can also help:

  * WHIRR-417 -> allows you to pass a property to change jclouds
modules.  Ex. if for some reason you have doubts about sshj, you can
switch to jsch.
  * WHIRR-418 -> logs ssh connection details to jclouds-ssh.log

I hope these help!
-Adrian

On Sat, Oct 29, 2011 at 9:10 AM, Adrian Cole <[email protected]> wrote:
> Hi, Paul.
>
> There's also this post, which automates this process:
>
> http://www.google.com/url?sa=t&rct=j&q=whirr%20%20jclouds%20compute-basics&source=web&cd=1&ved=0CBkQFjAA&url=http%3A%2F%2Fmail-archives.apache.org%2Fmod_mbox%2Fwhirr-dev%2F201108.mbox%2F%253CCAARMrHXi1ad5fkGvSYJRYJB7OsDmsOtzLgbR%3D0G9KNP-FdjBeA%40mail.gmail.com%253E&ei=laarTrrECebi4QTUxOiJDw&usg=AFQjCNF4Ix6I6m0o0pOws1v1Oi_sb05awg&sig2=caDzIifCj-RxEQ_bSqDI7Q
>
> This could be brushed up and/or made as formalized tool.
>
> -A
>
> On Sat, Oct 29, 2011 at 4:10 AM, Paul Baclace <[email protected]> wrote:
>> What is the right way to build whirr using mvn on my laptop and then
>> how/what to deploy on my ec2 launcher machine (a tiny instance)?
>>
>> What I have tried so far:
>>
>> On laptop::
>>  cd trunk
>>  #  is this correct goal?
>>  mvn install
>>  #  copy the whole thing?  really?  or some clever subset of files?
>>  scp -r . my_ec2_machine:/tmp/whirr7
>>
>> On my_ec2_machine::
>>  export WHIRR_HOME=/tmp/whirr7
>>  WHIRR_BIN=$WHIRR_HOME/bin/whirr
>>  ... run my script that runs $WHIRR_BIN
>>
>> if $WHIRR_HOME/services/*/src/main/resources/functions/*.sh files are
>> changed in place where deployed, I think that works for quick testing of
>> experimental changes.
>>
>> One more vital question:  how do I build trunk jclouds and correctly update
>> the multitude of cli/target/lib/jclouds-*.jar files in whirr so that whirr
>> actually uses them?  If the jar filename changes what xml files need to be
>> changed in jclouds and whirr?
>>
>> Thanks!
>>
>> Paul
>>
>>
>

Reply via email to