Beny's Blog

This blog covers the image/template migration between Openstack to Cloudstack platform. To be precise, converting the image from QCOW2 format to VHD format and upload it to Cloudstack platform.   Requirements Root access privileges to openstack and cloudstack with Xen server platform Enough free space to do the conversion python 2.7 to run a http server Image Download This part is already covered in one of my existing blogs. Please refer  https://benyraja.blogspot.in/2017/03/templateimage-migration-with-reduced.html 'Image Download' section. Image Conversion Once we have downloaded the image to local disk, we have to convert it into VHD as it is the supported version of Cloudstack Xen hypervisor. If you are using KVM hypervisor, then we can skip to next step. Use the below command to convert the image from QCOW2 to VHD. $ qemu-img convert -O vpc Now you will have the converted image in VHD format. Image Upload/Register Template To register te...

In any migration or moving the data from one platform to another, the most difficult challenge is the file size of the image. When we convert the VM instance as a template/image/snapshot it is nothing but a complete clone of the entire disk along with free sectors. Hence even the data is only 10GB the image will be around 30GB or more when the disk size is around 40GB. Moving or uploading a 30GB file over ethernet (even in fast ethernet), it is still a difficult time consuming job and it must work without interruption.   We faced a similar challenges in moving the templates from Openstack platform to VMware Esxi. In this blog, we will explain how we move the Openstack Virtual machine to VMware Esxi host with minimal effort and 100% working. I'm actually covering only QCOW2 image to VMDK image conversion in this section, however using the same methods we can do the conversion between any formats like QCOW2 to VHD, QCOW2 to OVA and vice versa.  Let us go step by step....

HA-PROXY SETUP FOR OPENSTACK SERVICES INTRODUCTION: To obtain maximum uptime in openstack services we are in need of high availability (aka HA ) in this document we are using ha-proxy for openstack HA and keepalived for H a-proxy HA. Software topology As mentioned, we’ll use the following set of software: the services themselves; HAProxy for making the services HA; and Keepalived for making HAProxy HA. Getting hands-on Suppose we have two machines, from which we want to make an HA OpenStack controller pair, installing both the API services and Keepalived + HAProxy. Suppose machine 1 has address 192.168.56.200, machine 2 has address 192.168.56.201, and we want the services to be accessible through virtual IP 192.168.56.210. And suppose all these IPs are on eth1. Installing necessary packages $ sudo apt-get install haproxy keepalived Configuration of haproxy This configuration is identical on both nodes and resides in /et...