Moving from CityCloud Gen1 to OpenStack – Part 2

Luc Van Steen City Cloud, Cloud, Cloud Computing, OpenStack Leave a Comment

With OpenStack now available in CityCloud, providing a new flexible and scalable cloud platform, it’s time to migrate your servers from the current Gen1 platform to the OpenStack platform.

To get you up to speed in this migration, I’ve compiled some steps to support this move. In my previous post, I described the process in how to get started. This post will elaborate on how to interconnect and move your data to OpenStack.

Let’s step back for a minute and take a look again on the process.
The following diagram captures the basic steps I follow for moving my generation 1 cloud servers to the OpenStack Platform.


With Analysis and Deploy phase completed, we can start connecting both environments.

tipThere are different approaches. I will describe the approach I take to move my servers and data. Feel free to post your preferred way in interconnecting and migrating data in the comment section.

1. Interconnect

To establish connectivity, I add a virtual machine in each CityCloud Datacenter where I host servers.
On these machines, OpenVPN will be installed. One machine will act as OpenVPN server, the rest are configured as clients.
Also it is not mandatory to have access to between all servers across datacenters. Connectivity between the appliances is enough.



warning-2-256If you need a guide on installing and configuring OpenVPN,
just drop me a email on info AT inovatech DOT be.

2. Move your data

To move data from CityCloud Gen1 to OpenStack, I will be using the same virtual machine(s) as I use for establishing connectivity between the platforms.
The trick is to create the necessary volumes on each of the appliances. Number and size of volumes depends on the analysis you’ve made before.
Once you added the volumes to the IC/DM (InterConnect/Data Mover), we can continue with following steps:

  • 2.1 Copy your master data to the IC/DM appliance
  • 2.2 Sync your data during migration
    • 2.2.1 Sync within Gen1
    • 2.2.2 Sync from Gen1 to OpenStack
  • 2.3 Move volumes to new servers

2.1 Copy your master data to the IC/DM Appliance

In this step, I’m moving the data of my Gen1 servers to the IC/DM appliance volumes within the same environment (so Gen1).

A tool I often use is “Fast Data Transfer” (FDT).
FDT is an application for efficient data transfers which is capable of reading and writing at disk speed over wide area networks (with standard TCP). It is written in Java, runs an all major platforms and it is easy to use. The software is free and can be downloaded from
Other free tools are rsync, unison, robocopy, …



Note: Moving databases is aways tricky. My preference is to establish a temporary replication.

2.2 Sync your data during migration

Once you have your master copy ready, you still need to keep that data in sync.
This step is the same for 2.2.1 Sync within Gen1 and 2.2.2 Sync from Gen1 to OpenStack.

Again, I use the same data mover appliance. Only difference is I don’t use FDT but the well-know rsync which runs as a cronjob for each volume I want to sync. Be aware that rsync only supports a one-way sync. For two-way syncronization, I use unison.

2.3 Move volumes to new servers

Final step in the data move process.
The nice thing about volumes is that you can attach them to another server. Once you decide to cut over, you just detach the volumes from the IC/DM appliance and attach them to destination server.

I hope this post will allow you support your migration.
Share your experiences, tips,… by posting your comments. And don’t forget to have fun!


Luc Van Steen

Luc Van Steen

Luc is an IT Specialist/consultant for one of the largest IT companies in the world with a main focus on infrastructure and integration. Networking, security, storage, virtualization, Linux, Windows and scripting are some of Luc’s main skills.

Luc is a major article contributor in the City Cloud blog where he covers all sorts of topics, from the latest industry news to tips&tricks for City Cloud users.