User Tools

Site Tools


manuals:vps:vpsadminos

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
manuals:vps:vpsadminos [2018/09/30 13:11] – Removed network configuration Aithermanuals:vps:vpsadminos [2020/01/13 19:57] – [Staging environment] keep platform Aither
Line 31: Line 31:
   - Developing vpsAdminOS into something usable   - Developing vpsAdminOS into something usable
   - Integration with vpsAdmin   - Integration with vpsAdmin
-  - Opening of a staging environment with vpsAdminOS (:!: we're here :!:)+  - Opening of a staging environment with vpsAdminOS
     - Testing, fixing bugs, implementing missing features, preparing for production     - Testing, fixing bugs, implementing missing features, preparing for production
-  - New production nodes are using vpsAdminOS, new VPS can be created only there+  - New production nodes are using vpsAdminOS (:!: we're here :!:) 
 +    - vpsAdminOS is available in Prague
   - Gradual migration of all VPS from OpenVZ nodes to vpsAdminOS, one node after another   - Gradual migration of all VPS from OpenVZ nodes to vpsAdminOS, one node after another
   - End of story   - End of story
Line 61: Line 62:
 UID/GID maps for VPS and NAS datasets, which will let each member to isolate UID/GID maps for VPS and NAS datasets, which will let each member to isolate
 his own VPS and yet share some chosen range of user/group IDs. his own VPS and yet share some chosen range of user/group IDs.
- 
-The user namespace significantly changes how you can share data between VPS 
-and NAS. At the moment, it is **not possible** to mount NAS to a VPS running 
-on a vpsAdminOS node so that you'd have access to the data. This will become 
-possible when custom UID/GID maps are properly implemented. 
  
 ==== General ==== ==== General ====
 Changes regarding VPS, but independent on the distribution used: 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 systemand 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''   * Swap is not shown in ''/proc/meminfo''
-  * ''dmesg'' is forbidden, as it's not virtualized in the kernel 
  
 ==== Debian/Ubuntu/Alpine ==== ==== Debian/Ubuntu/Alpine ====
Line 83: Line 77:
 ===== Behaviour changes in vpsAdmin ===== ===== 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.   * 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.   * VPS features: bridge, iptables and NFS aren't configurable, they're always on.
Line 90: Line 86:
 In order for all members to test VPS on vpsAdminOS, we've created so called 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 staging environment. It's similar to playground, where everyone can create a
-VPS. When creating a VPS, just select location **Staging** and the VPS will be +VPS. When creating a VPS, just select location **Staging** and deselect **Keep platform**. 
-created on a vpsAdminOS node.+The VPS will be created on a vpsAdminOS node.
  
 It's terms of use are similar to [[manuals:vps:playgroundvps|playground VPS]], It's terms of use are similar to [[manuals:vps:playgroundvps|playground VPS]],
Line 99: Line 95:
 resources among 4 VPS. 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 ==== ==== Supported distributions ====
  
-  * Alpine 3.6, 3.7+  * Alpine 3.8, 3.9
   * Arch   * Arch
-  * CentOS 7.5 +  * CentOS 7, 8 
-  * Debian 8, +  * Debian 9, 10 
-  * Fedora 2728+  * Fedora 2930
   * Gentoo   * Gentoo
   * NixOS   * NixOS
 +  * openSUSE Leap 15.1, Tumbleweed
 +  * Slackware 14.2
   * Ubuntu 16.04, 18.04   * Ubuntu 16.04, 18.04
- +  * Void Linux
-==== Other distributions ==== +
- +
-In case your distribution isn't supported yet, you can help us make +
-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  +
-[[https://github.com/vpsfreecz/build-vpsfree-templates/tree/vpsadminos|vpsadminos-templates]]. +
-If your distribution isn't there, it has to be added. +
- +
-When the built script is done, it is necessary to add support for your +
-distribution into ''osctl'', so that it can configure hostname, network, DNS +
-resolvers, etc., see [[https://vpsadminos.org/osctld/distributions/|doc]].+
  
 ==== Features ==== ==== Features ====
Line 134: Line 119:
 {{ :navody:vps:features.png?300 |}} {{ :navody:vps:features.png?300 |}}
  
-  * Docker (experimental) - Enables trial support for Docker.+  * Docker (experimental) - Enables support for Docker.
   * FUSE - "Filesystem in Userspace" Enables the kernel module to allow non-privileged users create their own file systems.   * 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.   * KVM - "Kernel-based Virtual Machine" Enables KVM for hardware support of virtualization.
manuals/vps/vpsadminos.txt · Last modified: 2024/01/02 20:39 by aither