Members are allowed to create VPSs in the playground and the production environment provided that they have enough resources and their environment settings allow it. You can gain resources by lowering the parameters of existing VPSs or paying extra for more resources.
Creating a new VPS consists of three steps:
So far, creating several production VPSs is only allowed for those users who request it and want to test this function.
Each member gets 1 public IPv4 address and 32 IPv6 addresses in each environment. These addresses can be distributed between various VPSs as you please. Additional IPv4 addresses are available for a fee, IPv6 addresses are given upon request.
You can find more information about the management and various types of IP addresses here.
When setting the root password, you can choose between two types of generated passwords. A simple password is easier to write down, but keeping it active for an extended period of time is not a good idea.
The distro reinstall form now makes it possible to just update the information about the distro which is used in a VPS. An example case of when you can use this is when you update your system to a newer version and the distro displayed in vpsAdmin doesn’t correspond to reality.
Reinstalling the system deletes all VPS subdatasets. More about datasets.
It is possible to change VPS parameters in the VPS details. The minimal configuration of a VPS is 1 CPU, 1 GB of RAM and 10 GB of disk space. The maximal configuration is 8 CPUs, 16 GB Of RAM, unlimited disk space.
Although “swap” is displayed among the parameters, we typically don’t assign it since swap behaves like a memory extension in OpenVZ.
If you want to create a new VPS, you need to make space for it – decrease the parameters of a different VPS.
The VPS hostname can be changed directly in vpsAdmin and each time the VPS starts, the chosen option in
/etc/hosts will be automatically rewritten. The hostname can also be managed manually, outside of vpsAdmin. You can choose which solution you prefer in the VPS details.
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. Some functions tend to run into conflicts with each other, for example turning on NFS blocks online migration.
Most frequently, VPSs are migrated between the playground and the production environment. It is only possible to swap VPSs that are located in different locations (Prague, Playground, Brno). Within one location, all you need to do is swap IP addresses.
Before performing the action, the table displays the state of the VPS before and after the migration.
You can either clone to a new or to an existing VPS. If you’re cloning to an existing VPS, the original VPS and all its subdatasets are removed!
In the form, choose the environment, locations or VPS to which you want to clone the VPS that is currently open. Based on this choice, either a new VPS will be created or an existing one will be overwritten. So make sure to be careful with what you are doing.
The appropriate time for planned VPS outages can be set differently for every day of the week.
During this time period, short VPS outages can occur if it’s absolutely necessary. This is mostly used when migrating VPSs between nodes. We always inform about planned outages and migrations either in the outage list or to the email that you have provided in vpsAdmin.
If we want to turn on maintenance mode, we can do so for the whole cluster, individual environments, locations, nodes or VPS. The reason is stated in the title of the maintenance mode icon.