Toytoy Googie's Geeky blog

To resize the disk image in Linux, do # sudo fsck.ext4 -f DISK_IMAGE_FILE # sudo resize2fs DISK_IMAGE_FILE This is very helpful specially if you are having an instance in the cloud and wanted to resize an image.

First, do # fdisk -l to list the device available. You can identify what's the current device the Eucalyptus have avail for the current block storage given. Now, to mount this, do # mkfs.ext4 /dev/sda where my current filing system is ext4 and the availed virtual device is /dev/sda. Then afterwards, you can do # mount -t ext4 /dev/sda /path/to/mounted/directory Hope this helps.

The current setup for this is that, I have this current instance in Eucalyptus and was already customized while its being in the cloud. This means like, installing packages and added extra configurations to some packages. While its time wasting if to go back and install those packages, doing a dd (disk dump) tool is very helpful. Below is the command I issued, #> dd if=/dev/vda1 of=jenkins.img conv=noerror,sync  I use the conv=noerror,sync which the sync to sync every input block and also its meta data. I've tried w/o that option and it didn't work.  After I run this into the cloud, I can ssh and I see the state before dd finished, it was there. It's really great! Hope this helps!

Previously, we just have bought a cool machines supposedly to be setup as Node Controllers for our cloud master machine (running Walrus Controller, Cloud Controller, Storage Controller, and Cluster Controller). The current setup we have is, SERVER1 - Cloud master running i3 with 12GB of memory SERVER2 and SERVER3 - running i7 3.0 with 16GB of memory With our setup, our ideal result must have 62 available instances to be run inside the cloud, however, due to the inconsistency we found (check this http://open.eucalyptus.com/wiki/EucalyptusKnownBugs_v1.5.2 ) with the problem with cloud master against NC's, issuing the command #> euca-describe-availability-zones verbose AVAILABILITYZONE kinten-cloud 122.2.1.4 AVAILABILITYZONE |- vm types free / max   cpu   ram  disk AVAILABILITYZONE |- m1.small 0031 / 0031   1    512    10 AVAILABILITYZONE |- c1.medium 0015 / 0015   1   1024    15 AVAILABILITYZONE |- m1...