Changes between Version 33 and Version 34 of NEuca-in-orca

Show
Ignore:
Timestamp:
01/13/11 15:35:28 (9 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NEuca-in-orca

    v33 v34  
    229229== Testing NEuca from tools/cmdline == 
    230230 
    231 You can use a test config file - tools/cmdline/tests/euca.xml  to test the NEuca handler without deploying webapp. The steps are the following. Make a new directory tools/cmdline/ec2 . Copy the contents of your ec2.keys dir (See section on Eucalyptus keys) into  tools/cmdlime/ec2 . Edit tools/cmdline/tests/euca.xml by uncommenting the line with 'ec2.keys' and providing the ABSOLUTE path to tools/cmdline/ec2. For example, that line might look like : <property name="ec2.keys" value="/home/orca/orca-trunk/trunk/tools/cmdline/ec2" /> . Set "emulation=false" in tools/cmdline/config/container.properties. Edit ant/tests.xml . Go to the section that starts with '<target name="test.euca">' and change the following property "<property name="leaseLength" value="30" />" to "<property name="leaseLength" value="300" />". In tools/cmdline, run 'ant get.packages'. Then run 'ant test.euca' . This should fire up one instance on your euca-installation. If things go fine, you should be able to login to the instance at the ip specified in unit.manage.ip in the output using your key - <keyName>. Do ssh -i <keyName> root@<unit.manage.ip>. 
    232  
    233 '''NOTE:''' handler scripts (start.sh/stop.sh that invoke ec2 scripts) produce log file /tmp/ec2.handler.log on failure that can contain useful information). 
     231You can use a test config file - tools/cmdline/tests/euca.xml  to test the NEuca handler without deploying webapp. The steps are the following.  
     232 * Make a new directory tools/cmdline/ec2 . Copy the contents of your ec2.keys dir (See section on Eucalyptus keys) into  tools/cmdlime/ec2 .  
     233 * Edit tools/cmdline/tests/euca.xml by uncommenting the line with 'ec2.keys' and providing the ABSOLUTE path to tools/cmdline/ec2. For example, that line might look like : <property name="ec2.keys" value="/home/orca/orca-trunk/trunk/tools/cmdline/ec2" /> .  
     234 * Set "emulation=false" in tools/cmdline/config/container.properties.  
     235 * Edit ant/tests.xml . Go to the section that starts with '<target name="test.euca">' and change the following property "<property name="leaseLength" value="30" />" to "<property name="leaseLength" value="300" />".  
     236 * In tools/cmdline, run 'ant get.packages'.  
     237 * Run 'ant test.euca' . This should fire up one instance on your euca-installation. If things go fine, you should be able to login to the instance at the ip specified in unit.manage.ip in the output using your key - <keyName>. Do ssh -i <keyName> root@<unit.manage.ip>. 
     238 
     239'''NOTE:''' In Bella 2.2 handler scripts (start.sh/stop.sh that invoke ec2 scripts) produce log file /tmp/ec2.handler.log on failure that can contain useful information). Obsoleted in Camano-3.x.  
    234240 
    235241== NEuca Handler ==