Version 2 (modified by ibaldin, 8 years ago)

--

Testing NEuca/EC2 handler

Prerequisites

Testing NEuca from tools/cmdline

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'.
  • 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>.

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.