Differences

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

--- manuals:vps:vpsadminos [2018/05/21 08:12] – [General] /proc/cpuinfo,stat Aither
+++ manuals:vps:vpsadminos [2019/10/22 16:48] – Aither
@@ Line 47: / Line 47: @@
 ===== Changes in VPS behaviour =====
-==== Network configuration ====
-Linux kernel doesn't have anything like venet from OpenVZ, so we had to
-find a different way. Networking is done by a pair of veth interfaces:
-one on the host, the other in the VPS. IP addresses are routed through
-an interconnecting network that is assigned to every VPS.
-For example, let's say the assigned interconnecting network is
-''10.100.10.0/30''. The veth interface on the host will have address
-''10.100.10.1'' and the interface in the VPS will have ''10.100.10.2''.
-IP addresses are then routed via ''10.100.10.2'', e.g. public IPv4 ''1.2.3.4''
-would be routed as ''1.2.3.4/32 via 10.100.10.2''. The default gateway
-in the VPS would be set as ''default via 10.100.10.1 src 1.2.3.4''. The
-interface on the host is configured automatically by ''osctl'', which
-will also generate configuration files inside your VPS, depending on your
-distribution. The init system from your VPS will then read those files
-and setup the network interface. The first address on the interface will be
-the address from the interconnecting network, not the public address, as has
-been the case on OpenVZ. If you have some custom network configuration,
-you need to be aware of how the networking is supposed to work.
 ==== User namespaces ====
 VPS in vpsAdminOS are using so called //user namespaces//. User namespace
@@ Line 90: / Line 70: @@
 Changes regarding VPS, but independent on the distribution used:
-  * ''/proc/loadavg'' shows load average of the entire node, i.e. of processes from all VPS on the node you're on, it does not tell anything abour your VPS
+  * ''/proc/stat'' reports only user (including system) and idle
-  * ''/proc/cpuinfo'' and ''/proc/stat'' show all CPUs from the node, but you can't utilize more than 8 of them (800% CPU)
   * Swap is not shown in ''/proc/meminfo''
-  * ''dmesg'' is forbidden, as it's not virtualized in the kernel
 ==== Debian/Ubuntu/Alpine ====
@@ Line 119: / Line 97: @@
 resources among 4 VPS.
-It is not possible to clone or swap production VPS with VPS in the staging
+You can either create a new VPS or clone an existing production VPS.
-environment. Migration of OpenVZ VPS onto vpsAdminOS is not implemented yet.
+All mounts are removed when cloning, because NAS isn't acessible as of yet,
-Access to the NAS is also restricted, see [[#user_namespaces|user namespaces]].
+see [[#user_namespaces|user namespaces]].
 ==== Supported distributions ====
-  * Alpine 3.6, 3.7
+  * Alpine 3.8, 3.9
   * Arch
-  * CentOS 7.5
+  * CentOS 7, 8
-  * Debian 8, 9
+  * Debian 9, 10
-  * Fedora 27, 28
+  * Fedora 29, 30
   * Gentoo
   * NixOS
+  * openSUSE Leap 15.1, Tumbleweed
+  * Slackware 14.2
   * Ubuntu 16.04, 18.04
+  * Void Linux
+==== Features ====
-==== Other distributions ====
+Features can be turned on/off individually. When any change is made, the VPS restarts.
-In case your distribution isn't supported yet, you can help us make
+{{ :navody:vps:features.png?300 |}}
-it happen, or wait until someone does it for you, see
-[[https://github.com/vpsfreecz/vpsadminos/issues|open issues]].
-Distribution templates installable from vpsAdmin are built using scripts at
+  * Docker (experimental) - Enables support for Docker.
-[[https://github.com/vpsfreecz/build-vpsfree-templates/tree/vpsadminos|vpsadminos-templates]].
+  * FUSE - "Filesystem in Userspace" Enables the kernel module to allow non-privileged users create their own file systems.
-If your distribution isn't there, it has to be added.
+  * 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.
-When the built script is done, it is necessary to add support for your
+We recommend only setting the features that your really need.
-distribution into ''osctl'', so that it can configure hostname, network, DNS
-resolvers, etc., see [[https://vpsadminos.org/osctld/distributions/|doc]].
 ==== More about vpsAdminOS ====

Knowledge base

User Tools

Site Tools

Differences

Page Tools