OpenVZ Forum


Home » General » Support » OpenVZ 7 - should I upgrade?
Re: OpenVZ 7 - should I upgrade? [message #52766 is a reply to message #52595] Fri, 10 March 2017 15:40 Go to previous messageGo to previous message
tomp is currently offline  tomp
Messages: 64
Registered: August 2007
Member
I am facing the same decision. Have been using OpenVZ since CentOS 5, and am now running CentOS 6 for many years.

Very happy with OpenVZ 6.

But with only 2 years left on security support from CentOS, I need to start planning the replacement.

I have experimented with CentOS 7 and OpenVZ 7 using the unofficial upgrade script vzdeploy

https://marc.ttias.be/openvz-users/2016-08/msg00027.php
http://repo.virtuozzo.com/vzlinux/vzdeploy/vzdeploy

This does work, however I am left uneasy as it is an non-official approach.

I can't understand why OpenVZ team would not allow CentOS upgrades, given its worked fine for years, and that it makes installing it on remote hosts so much easier than using an ISO.

The other major problem for me is the lack of container level disk quotas when using simfs.

Simfs with quotas in OpenVZ 6 was great, along with vzmigrate and our own backup/restore system, things worked great.

However with simfs in OpenVZ 7 there is no quota, so I am now looking at options such as:

* LVM/LVM thin per container
* Ploop

Both approaches work, but present their own new set of challenges, LVM requires additional outside scripts for container creation and migration, and I have seen some pretty worrying comments about ploop's stability and efficiency. This worries me. https://github.com/pavel-odintsov/OpenVZ_ZFS/blob/master/plo op_issues.md

With all of these new requirements I began to look at LXC. LXC 2 is supported until June 2021.

I've managed to create an OpenVZ-like setup in LXC using LVM thin (and LXC's hook scripts), and proxy arp to give a venet like network config without bridging.

I am aware that in CentOS 7 there is not user namespace, so we cannot run unprivileged LXC containers, but as my usage is for internal systems (where root user is trusted) this is acceptable to me.

Also, root is also privileged in OpenVZ containers anyway.

[Updated on: Fri, 10 March 2017 15:44]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Kernel of Openvz7 support DRBD
Next Topic: openvz-diff-backups: a file-based incremental backup tool (Beta Testers Welcome!)
Goto Forum:
  


Current Time: Tue Aug 06 09:13:12 GMT 2024

Total time taken to generate the page: 0.03291 seconds