Cloudstack test environment

admin — Tue, 25 Jan 2011 18:18:05 +0000

     I played turning the local storage from a Xen Server into an NFS volume. Use this to be shared in a Xen and using to test the live migration using only 2 boxes. Was a nice test and easy to build. But the final words was: “And now…”. It it a very good test but no other utility, until…
     Until I need to test the new beta 2.2 version of Cloudstack and I was forced to have again a small test environment. And I testing the beta version using only 2 IBMs xServer 3550 XEON dual core, one whitebox server and two Linksys switches.
     I’m using separate storage network setup in order to have the best nfs result and also I will play with virtual network for beginning.
     Let see first the preparation:

First tune-up one host to become a decent NFS server

Increasing the amount of memory associated with socket buffers

echo 262143 > /proc/sys/net/core/rmem_max

echo 262143 > /proc/sys/net/core/rmem_default

This will increase the amount of memory available for socket input queues. The “wmem_*” values do the same for output queues.
These reduce the amount of work the TCP stack has to do, so is often helpful in this situation.

echo 0 > /proc/sys/net/ipv4/tcp_sac

echo 0 > /proc/sys/net/ipv4/tcp_timestamps

Modify dedicated fixed amount of memory for dom0 from 512MB to 3GB will give us more memory for nfs
vi /boot/extlinux.conf
Change for both tage xe si xe-serial value dom0_mem from 512M to 3072M and apply the changes using this commands

. /etc/xensource-inventory

staticmax=`xe vm-param-get uuid=$CONTROL_DOMAIN_UUID param-name=memory-static-max`

echo staticmax=$staticmax

xe vm-param-set uuid=$CONTROL_DOMAIN_UUID memory-dynamic-max=$staticmax

xe vm-memory-target-set uuid=$CONTROL_DOMAIN_UUID target=$staticmax

Restart the server and check the new value for “Maximum target” to be 3GB and “High-mem balloon” to be different than 0
cat /proc/xen/balloon

Build your NFS storage

SubNetWorld

Cloudstack test environment