Differences

This shows you the differences between two versions of the page.

--- manuals:vps:vpsadminos [2022/04/06 08:45] – [vpsAdminOS] update info Aither
+++ manuals:vps:vpsadminos [2024/01/02 20:39] (current) – aither
@@ Line 1: / Line 1: @@
 <page>manuals:vps:vpsadminos</page>
 ====== vpsAdminOS ======
-Since [[information:openvz|OpenVZ Legacy]] is no longer supported and new distributions
+vpsAdminOS is a host system for containers developed by vpsFree.cz. We use it
-don't work there, we had to find a way to upgrade our kernel, which
+to run our VPS.
-meant choosing a different virtualization technology. Linux kernel now
-has some support for containers, so we've decided to use it.
-We needed some distribution that we could use on nodes to serve as
-a hypervisor, as a replacement of Scientific Linux 6 with OpenVZ kernel.
-We've chosen [[https://nixos.org|NixOS]], because it allows us to declaratively
-configure the system and its services. And since our requirements are quite specific,
-we're maintaining our own spin of NixOS called vpsAdminOS.
-[[https://github.com/vpsfreecz/vpsadminos|vpsAdminOS]] is based on
+===== About vpsAdminOS =====
-[[https://nixos.org|NixOS]] and [[https://github.com/cleverca22/not-os/|not-os]].
+vpsAdminOS is a spin of NixOS. The host system is rather small and includes only management
-It's a //live// distribution serving as a hypervisor for container
+services, as it focuses on running everything else in Linux system containers. vpsAdminOS
-virtualisation. It's as capable as OpenVZ Legacy was in its time.
+is interconnected with vpsAdmin, our control panel. It is however also usable outside
-vpsAdminOS naturally integrates with vpsAdmin, our administration interface
+of vpsFree.cz's infrastructure, e.g. on your home server.
-with web interface. However, vpsAdminOS is meant to be fully usable even on its own,
-outside vpsFree.cz's infrastructure.
-===== Migration from OpenVZ to vpsAdminOS ======
-The upgrade of our infrastructure with all VPSes to vpsAdminOS is divided into
-several phases:
-  - Developing vpsAdminOS into something usable
+If you're interested in our stack and how vpsAdminOS works, see https://vpsadminos.org.
-  - Integration with vpsAdmin
-  - Opening of a staging environment with vpsAdminOS
-    - Testing, fixing bugs, implementing missing features, preparing for production
-  - New production nodes are using vpsAdminOS (:!: we're here :!:)
-  - Gradual migration of all VPS from OpenVZ nodes to vpsAdminOS, one node after another
-  - End of story
-===== What does it mean for members ======
-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| staging environment]], so that we can find
-and solve problems before we start migration production VPS.
-===== Changes in VPS behaviour =====
-==== General ====
-Changes regarding VPS, but independent on the distribution used:
-  * ''/proc/stat'' reports only user (including system) and idle
-  * Swap is not shown in ''/proc/meminfo''
-==== Debian/Ubuntu/Alpine ====
-  * Network is configured using ''ip'' from ''iproute2'', you no longer need ''ifconfig'' from ''net-tools''
-  * If there is a directory called ''/etc/network/interfaces.d'', it is sourced before ''/etc/network/interfaces.tail''.
-===== Behaviour changes in vpsAdmin =====
-  * NAS and snapshots are not accessed using vpsAdmin [[manuals:vps:vpsadminos:storage|mounts, but NFS exports]]
-  * IP address management is split into routed and interface addresses
-  * Reinstalling VPS on vpsAdminOS no longer deletes subdatasets and does not reset its configuration to the initial state, e.g. VPS features remain as they were.
-  * VPS features: bridge, iptables and NFS aren't configurable, they're always on.
-  * It is possible to change the network interface name within the VPS in VPS details page.
 ===== Staging environment ======
@@ Line 73: / Line 25: @@
 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|user namespaces]].
-==== Features ====
-Features can be turned on/off individually. When any change is made, the VPS restarts.
-{{ :navody:vps:vps_features.png |}}
-  * FUSE - "Filesystem in Userspace" Enables the kernel module to allow non-privileged users create their own file systems.
-  * KVM - "Kernel-based Virtual Machine" Enables KVM for hardware support of virtualization.
-  * LXC nesting - "Linux Containers" Enables nested LXC containers.
-  * PPP - "Point-to-Point Protocol" Enables communications protocol used to establish a direct connection between point-to-point links.
-  * TUN/TAP - "TUN routing/TAP bridging" Enables the creation of virtual interfaces that are then bridged.
 ==== More about vpsAdminOS ====
@@ Line 92: / Line 30: @@
   * https://vpsadminos.org
   * https://github.com/vpsfreecz/vpsadminos
-  * IRC chat.freenode.net #vpsadminos
 ==== Reporting bugs and ideas ====
 Choose at your own discretion:
-  * [[information:chat|IRC]]: #vpsfree and #vpsadminos on chat.freenode.net
+  * [[information:chat]]
   * podpora@vpsfree.cz
   * vpsAdminOS issues: https://github.com/vpsfreecz/vpsadminos/issues
   * vpsAdmin issues: https://github.com/vpsfreecz/vpsadmin/issues

Knowledge base

User Tools

Site Tools

Differences

Page Tools