Changes between Version 11 and Version 12 of NEuca-in-orca

Show
Ignore:
Timestamp:
10/19/10 14:33:53 (9 years ago)
Author:
anirban (IP: 152.54.9.209)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NEuca-in-orca

    v11 v12  
    196196}}} 
    197197 
     198== Eucalyptus Keys == 
     199 
     200The path to ec2.keys in the config file is important. It must point to the location which has the eucalyptus keys and eucarc. In the example config file, the ec2 keys are stored in /opt/orca/ec2. To get the keys for your eucalyptus account, you have to log in to your Eucalyptus portal with the euca username, say,  'orca'. Go to Credentials tab and then click on 'Download Credentials' under 'Credentials ZIP-file'. Unzip the contents of this zip file (which will have a name like euca2-<euca username>-x509.zip) in the ec2.keys directory.  
     201 
     202Associate a private key to your euca account, which can be used to log in to any instances brought up. This key can be generated by issuing the following command after sourcing eucarc.  
     203 
     204$ 
     205euca-add-keypair keyName 
     206$ 
     207 
     208Store the output of this command in a file with the name name as keyName and put it in the ec2.keys directory. 
     209 
     210Edit eucarc in that directory as follows. Comment out the first line by inserting '#' at the beginning of the line. Add the following lines to eucarc. The AMI_NAME must correspond to the emi-id of a neuca-enabled image. Replace XXXXXX with the correct id . The EC2_SSH_KEY property must point to the keyName file. 
     211 
     212{{{ 
     213export AMI_NAME=emi-XXXXXX 
     214export EC2_SSH_KEY=keyName 
     215}}}  
    198216 
    199217== NEuca Handler ==