Finally done with our project presentation...!!!! :)
Thursday, 20 December 2012
Wednesday, 19 December 2012
Tuesday, 18 December 2012
Monday, 17 December 2012
Sunday, 16 December 2012
Saturday, 15 December 2012
This is the final answer i got from the Eucalyptus Support team for the question
Q: We have successfully installed Eucalyptus on VM, everything is working fine, But our instance in Eucalyptus is not getting to running state. we have tried with managed novlan mode and static mode, Can we get help to solve this problem?
Ans:Hello,
Q: We have successfully installed Eucalyptus on VM, everything is working fine, But our instance in Eucalyptus is not getting to running state. we have tried with managed novlan mode and static mode, Can we get help to solve this problem?
Ans:Hello,
we don't advice to run eucalyptus in a vm and we don't support it directly. You have to work on bare machine to install and successfully run instances of your Eucalyptus cloud. Better Luck.
regards
graziano Wednesday, 12 December 2012
After our long trial on eucalyptus 3.1 to migrate instances to AWS public cloud, left with no results. Had a conversation with Eucalyptus support team on IRC free node, eucalyptus 3.1 has no features supporting all the hybrid functionalities. The new release Eucalyptus 3.2 has updated with all thiese features and we are waiting for its release to have a trial.
Saturday, 8 December 2012
Monday, 3 December 2012
Friday, 30 November 2012
Thursday, 29 November 2012
How to get rid of this?
[root@eucanode kvm-kernel]# euca-run-instances emi-21C335F8 -k suresh.priv
RunInstancesType: Failed to lookup kernel image information eki-8A553D65--ramdisk because of: Failed to lookup image: eki-8A553D65--ramdisk because of example: [KernelImageInfo manifestLocation=null signature=null checksum=null checksumType=null bundleSizeBytes=null imageName=null description=null architecture=null imagePublic=null platform=null imageType=kernel permissions=[] productCodes=[] deviceMappings=[] imageSizeBytes=null fullName=null ownerUserId=null ownerUserName=null ownerAccountNumber=null ownerAccountName=null uniqueName=null ownerFullNameCached=null state=null lastState=null stateChangeStack=null displayName=eki-8A553D65--RAMDISK id=null version=null creationTimestamp=null lastUpdateTimestamp=null naturalId=null]
Yippeee.... Trouble shooted source from https://engage.eucalyptus.com/customer/portal/questions/342904-euca-describe-availability-zones-verbose-availabilityzone
Solution
If Free/Max value is 0000/0000 for all then
a) CC not able to communicate to NC, Just test with ping <ip of node>
b) Time-value difference between CC and NC – correct with ntp
c) Password less login to NC is lost – redo ssh-copy-id
d) Already registered Ips or Keys of either CC or NC have changed
e) If none works, then regenerate the credentials using
sudo euca_conf --get-credentials <newname>.zip
unzip it and source eucarc
Transfer the zip file to NC and source eucarc there too.
Solution
If Free/Max value is 0000/0000 for all then
a) CC not able to communicate to NC, Just test with ping <ip of node>
b) Time-value difference between CC and NC – correct with ntp
c) Password less login to NC is lost – redo ssh-copy-id
d) Already registered Ips or Keys of either CC or NC have changed
e) If none works, then regenerate the credentials using
sudo euca_conf --get-credentials <newname>.zip
unzip it and source eucarc
Transfer the zip file to NC and source eucarc there too.
[root@eucahost .euca]# euca-describe-availability-zones verbose
AVAILABILITYZONE cluster01 192.168.47.131
arn:euca:eucalyptus:cluster01:cluster:cc-192.168.47.131/
AVAILABILITYZONE |- vm types free / max cpu ram disk
AVAILABILITYZONE |- m1.small 0000 / 0000 1 128 2
AVAILABILITYZONE |- c1.medium 0000 / 0000 1 256 5
AVAILABILITYZONE |- m1.large 0000 / 0000 2 512 10
AVAILABILITYZONE |- m1.xlarge 0000 / 0000 2 1024 20
AVAILABILITYZONE |- c1.xlarge 0000 / 0000 4 2048 20
All the values of FREE/MAX are 0000/0000.....Trying to troubleshoot.... :(
Wednesday, 28 November 2012
Subscribe to:
Posts (Atom)