Since OpenVZ is dead and new distributions aren't supporting it, we had to find a way to upgrade our kernel, which meant choosing a different virtualization technology. Linux kernel now has some support for containers, so we've decided to stick with that. Next, we needed some distribution that we could use on nodes to serve as hypervisors, as a replacement of Scientific Linux 6 with OpenVZ kernel. We've chosen NixOS, which allows you to declare the system and its configuration and then reproducibly build it. And since we have a bit specific requirements, we've created our own distribution on top of NixOS.
vpsAdminOS is based on
NixOS and not-os.
It's a live distribution serving as a hypervisor for container
virtualisation. Its as capable as OpenVZ Legacy was in its time. We have
our own userspace tools to manage containers called
internally uses LXC. vpsAdminOS naturally integrates with vpsAdmin, our
administration interface with web interface, which you're all using to manage
your VPS. However, vpsAdminOS is meant to be fully usable even on its own, as
a replacement to OpenVZ Legacy deployments. If you have some OpenVZ servers
and would like a newer system, you can consider vpsAdminOS. We also have
scripts to help
with migration of OpenVZ containers onto vpsAdminOS.
The upgrade of our infrastructure with all VPSes to vpsAdminOS is divided into several phases:
We're trying to make the migration to vpsAdminOS as seamless as possible, so that one day your VPS will stop on the OpenVZ node and will start on vpsAdminOS node a while later, without you having to do anything. However, it depends on what programs you're running and what configuration changes you have made. That's why we recommend for everyone to try VPS on vpsAdminOS in the staging environment, so that we can find and solve problems before we start migration production VPS.
Changes regarding VPS, but independent on the distribution used:
/proc/statreports only user (including system) and idle
iproute2, you no longer need
/etc/network/interfaces.d, it is sourced before
In order for all members to test VPS on vpsAdminOS, we've created so called staging environment. It's similar to playground, where everyone can create a VPS. When creating a VPS, just select location Staging and deselect Keep platform. The VPS will be created on a vpsAdminOS node.
You can either create a new VPS or clone an existing production VPS. All mounts are removed when cloning, because NAS isn't acessible as of yet, see user namespaces.
Features can be turned on/off individually. When any change is made, the VPS restarts.
We recommend only setting the features that your really need.