Changes between Version 40 and Version 41 of Eucalyptus-1.6.2-Setup

Show
Ignore:
Timestamp:
06/15/10 15:55:30 (9 years ago)
Author:
shuang (IP: 152.54.8.247)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Eucalyptus-1.6.2-Setup

    v40 v41  
    225225}}} 
    226226 
    227  
     227== Testing Eucalyptus == 
     228 
     229 1. {HN] Create a key pair that will be injected into the VM to be created so user can ssh to it: 
     230{{{ 
     231euca-add-keypair mykey >mykey.private 
     232('mykey' is the name for the key in Eucalyptus, 'mykey.private' is the file to be used by ssh) 
     233 
     234chmod 0600 mykey.private 
     235 
     236euca-run-instances --addressing private -k mykey -n <number of instances to start> <emi-id>  
     237 
     238euca-describe-instances 
     239(should now show the instance) 
     240 
     241ssh -i mykey.private root@<accessible-instance-ip> 
     242}}} 
     243 1. [HN as root] If client machines aren't showing up, try restarting cloud controller and portal 
     244{{{ 
     245# /etc/init.d/eucalyptus-cc restart 
     246# /etc/init.d/eucalyptus-cloud restart 
     247}}} 
     248  
    228249== Troubleshooting == 
    229250 
     
    247268$ sudo vonfig rem eth0.10 
    248269}}} 
    249 If the bridges are correctly configured, you should see they've successfully obtained private IP addresses from front-end's dhcp server. 
     270If the bridges are correctly configured, you should see they've successfully obtained private IP addresses from front-end's dhcp server (Managed mode). 
     271 1. run 
     272{{{ 
     273euca-describe-availability-zones verbose 
     274}}} 
     275to make sure there is enough resources for creating the VM. If not you could add more compute nodes to the cluster. 
    250276 1. Check the VMs are created in machines (may have to hunt for them since you don't know which specific compute node a VM will be created on): 
    251277{{{