This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
manuals:vps:vpsadminos [2022/04/06 08:45] – [vpsAdminOS] update info Aither | manuals:vps:vpsadminos [2024/10/09 18:11] (current) – Remove staging environment aither | ||
---|---|---|---|
Line 1: | Line 1: | ||
< | < | ||
====== vpsAdminOS ====== | ====== vpsAdminOS ====== | ||
- | Since [[information: | + | vpsAdminOS |
- | 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 | + | |
- | 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:// | + | |
- | configure the system and its services. And since our requirements are quite specific, | + | |
- | we're maintaining our own spin of NixOS called vpsAdminOS. | + | |
- | [[https:// | + | ===== About vpsAdminOS ===== |
- | [[https:// | + | vpsAdminOS is a spin of NixOS. The host system is rather small and includes only management |
- | It's a //live// distribution serving | + | services, |
- | virtualisation. It's as capable as OpenVZ Legacy was in its time. | + | is interconnected |
- | vpsAdminOS | + | of vpsFree.cz' |
- | with web interface. However, vpsAdminOS | + | |
- | outside | + | |
- | ===== 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' |
- | - 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 | + | |
- | have made. That's why we recommend for everyone to try VPS on vpsAdminOS | + | |
- | in the [[# | + | |
- | and solve problems before we start migration production VPS. | + | |
- | + | ||
- | ===== Changes in VPS behaviour ===== | + | |
- | + | ||
- | ==== General ==== | + | |
- | Changes regarding VPS, but independent on the distribution used: | + | |
- | + | ||
- | * '' | + | |
- | * Swap is not shown in ''/ | + | |
- | + | ||
- | ==== Debian/ | + | |
- | + | ||
- | * Network is configured using '' | + | |
- | * If there is a directory called ''/ | + | |
- | + | ||
- | ===== Behaviour changes in vpsAdmin ===== | + | |
- | + | ||
- | * NAS and snapshots are not accessed using vpsAdmin [[manuals: | + | |
- | * 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, | + | |
- | * It is possible to change the network interface name within the VPS in VPS details page. | + | |
- | + | ||
- | ===== Staging environment ====== | + | |
- | 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. | + | |
- | + | ||
- | It's terms of use are similar to [[manuals: | + | |
- | only it can be a bit rougher, like unplanned outages and reboots when we need | + | |
- | to fix something. Everyone can use up to 8 CPUs, 4 GB RAM, 120 GB disk space, | + | |
- | 4 public IPv4 addresses and 32 IPv6 /64 addresses. You can split these | + | |
- | resources among 4 VPS. | + | |
- | + | ||
- | 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 [[# | + | |
- | + | ||
- | ==== Features ==== | + | |
- | + | ||
- | Features can be turned on/off individually. When any change is made, the VPS restarts. | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | * FUSE - " | + | |
- | * KVM - " | + | |
- | * LXC nesting - "Linux Containers" | + | |
- | * PPP - " | + | |
- | * TUN/TAP - "TUN routing/TAP bridging" | + | |
==== More about vpsAdminOS ==== | ==== More about vpsAdminOS ==== | ||
Line 92: | Line 16: | ||
* https:// | * https:// | ||
* https:// | * https:// | ||
- | * IRC chat.freenode.net #vpsadminos | ||
==== Reporting bugs and ideas ==== | ==== Reporting bugs and ideas ==== | ||
Choose at your own discretion: | Choose at your own discretion: | ||
- | * [[information: | + | * [[information: |
* podpora@vpsfree.cz | * podpora@vpsfree.cz | ||
* vpsAdminOS issues: https:// | * vpsAdminOS issues: https:// | ||
* vpsAdmin issues: https:// | * vpsAdmin issues: https:// | ||