Converting Virtualizor Master -> SolusVM Slave [OpenVZ]

Portal Home > Knowledgebase > Articles Database > Converting Virtualizor Master -> SolusVM Slave [OpenVZ]

Posted by Johnny Cache, 04-09-2014, 05:26 PM
Hiya: For a variety of reasons I'm taking the two nodes that are running Virtualizor and converting them back to SolusVM. Migrating the containers off the Virtualizor slave was easy as I moved them to an existing SolusVM slave, deployed them and brought them into SolusVM using import mode. No issue there. The Virtualizor "master" is where I need clarification. The initial install configures it as a master with OpenVZ virtualization and there is no way of running a master from a local or offsite VPS, so it does run some containers. It has it's own I.P. pool/resources which aren't shared with any of the slaves, so I wouldn't be able to do this without renumbering the containers or having the DC share the I.P. resources with the other nodes. Here's what I was thinking- Having appropriate container + DB backups at the ready, I should be able to stop the Virtualizor service, and install SolusVM as either a slave with no virtualization (since the kernel and utils are there already) or a slave with OpenVZ support. I'm on the fence as to which one I can safely choose here. I'm not sure if installing SVM as a slave without is going to prevent me from creating containers on it entirely, but I'm also not sure what could be overwritten/changed if I ran the install with OpenVZ. It may recreate /vz/ and erase the existing container private areas. Either way the goal is to get the right SolusVM slave install in place, and pull Virtualizor out by hand. Is there any reason to think I might encounter a problem with either of the two SolusVM slave install types? If it's too risky I'd rather schedule some downtime, replace the drives, do a ground-up SolusVM slave install and restore the containers. I just want to make sure I do it right. Comments always appreciated. Thanks!
Posted by Srv24x7, 04-12-2014, 03:23 AM
So, you are planning to have SolusVM installed on a server which already has a working virtualizor, right? If you choose SolusVM with no virtualization, then there will not underlying virtualization platform installed. If you choose SolusVM with OpenVZ virtualization, then there are chances that it may wipe out the current files/folder in the /vz directory. The best option for you will be to dump the existing OpenVZ VPS, copy it over if you are formatting the current OS otherwise no need, install SolusVM with OpenVZ virtualization, and then restore the container back. OR you may rename the current /vz directory, install SolusVM, and the revert back to renamed vz directory. But in either case, I will advise you to backup the container.
Posted by Johnny Cache, 04-12-2014, 03:37 AM
Great timing on your response, and thanks. Decided the safest bet to remove all traces of Virtualizor and protect the containers' integrity, I had another server deployed last week at the DC. Testing has been great, and I'm actually performing the migrations now. That node really needed better HDDs anyhow. Like you I was concerned that a Slave + VZ install would erase the existing container private areas. I have appropriate backups, of course. It's probably safer anyhow as far as ensuring that Virtualizor gets pulled completely. Thanks again for the confirmation!