Lxlabs

One of the most common requests that we have received were by customers who were already running openvz/xen without any control panels, and wanting to import them into hyperVM. Considering the widespread nature of this particular requirement, we have decided to make 'import' an integral part of hyperVM, something that is accessible from the control panel itself. Also the current import system is intelligent enough to fail gracefully when it encounters situations where import may not be directly possible.

Importing actually consists of two steps:

Install hyperVM as either master or slave. Choose the virtualization-type as NONE.

sh ./hypervm-install-master --virtualization-type=NONE

This will install just the hyperVM web-interface and the backend, and will not install any of the kernels or the associated programs.

In the case of openvz, you can directly import the vpses using the webinterface. For Xen, you will need to write a small driver, which should read your configuration files and return the requisite data structures. Please contact us with your configuration, and we will supply the driver specific to your configuration.

Click on 'server list' -> 'server home' -> 'import vps' . This will automatically import all the existing openvz vpses cleanly into the hyperVM. Some of the vps parameters will be automatically assigned by hyperVM, and you can manually change them later.

The name of the vps will be automatically assigned as openvz<vpsid>.vm. You can change this by going to vps home -> advanced -> change name. In the case of xen, the name will the <virtual machine name>.vm.

All the vpses will be imported under admin. You can move the vpses trivially by going to vps home -> advanced -> change owner, and switch the vps to the customer that you would want it under.

The password for the vps and the console will be <vpsid> in the case of openvz, and the virtual machine name in the case of xen. The root password is left unchanged, and if you want to you can reset it from the Control Panel.

If the vpsid or name already exists under hyperVM, then the vps will be silently ignored, and the rest will be imported. However, if the same vpsid exists on a different server, hyperVM will fail immediately and return an error, and no vps on the server will be imported unless this is fixed.

The problem here comes from the hyperVM requirement that vpsid is unique across a cluster, and that if a vpsid exists on one server, then the same cannot exist on another server. This is necessary to make migrations easier, and even otherwise, will prevent unncessary confusion while moving vpses across servers. But this means that while importing, you have to make sure that all the vpsids are unique. The problem can be solved pretty much easily by changing the vpsid of the affected vps. You can shut the vps down, and then just move the vps to another directory, and also move the /etc/vz/conf/<vpsid>.conf file to another name, and then go through the import procedure again.

If you have any issues, please contact lxhelp . at . lxlabs.com or describe your situation in our forum

© 2002-2008 lxlabs	lxinfo . at . lxlabs.com
Terms of Use \| Privacy Statement \| Contact Us \| Live \| Home