Differences

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

--- manuals:vps:management [2022/01/27 08:48] – [IP Addresses] /64 ipv6 Aither
+++ manuals:vps:management [2026/07/12 20:30] (current) – Annotate vpsAdmin navigation paths and update interface labels aither
@@ Line 13: / Line 13: @@
   - choosing a hostname, distro and parameters
-{{:navody:vps:create_vps.png?300|}}
+{{:en:screenshots:vpsadmin:vps-management:create-vps-form.png?300|}}
@@ Line 28: / Line 28: @@
 a good idea.
-{{:navody:vps:root_passwd.png?300|}}
+{{:en:screenshots:vpsadmin:vps-management:set-root-password.png?300|}}
+===== SSH Public Keys =====
+You can upload your public keys to vpsAdmin at <vpsadmin-nav id="member.public-keys.add">Edit profile → Public keys → Add public key</vpsadmin-nav>.
+{{:en:screenshots:vpsadmin:ssh-keys:add-public-key.png?300|}}
+The keys can be configured to be automatically deployed to new or reinstalled VPS. Alternatively,
+you can deploy individual keys to VPS on demand from VPS details page:
+{{:en:screenshots:vpsadmin:ssh-keys:deploy-public-key.png?300|}}
+===== Initial configuration =====
+It is possible to add script or cloud-init configuration that is run when the VPS
+is first started, see [[manuals:vps:userdata]].
 ===== Choosing a Distro =====
@@ Line 37: / Line 53: @@
 doesn’t correspond to reality.
-{{:navody:vps:distro_reinstall.png?300|}}
+{{:en:screenshots:vpsadmin:vps-management:reinstall-form.png?300|}}
-Reinstalling the system **deletes all VPS subdatasets**. More about datasets.
+Reinstalling the system **deletes all data in VPS root file system**.
 ===== VPS Parameters =====
 It is possible to change VPS parameters in the VPS details. The minimal configuration of a VPS is
-CPU, 1 GB of RAM and 10 GB of disk space. The maximal configuration is 8 CPUs, 16 GB
+CPU, 256 MB of RAM and 512 MB of disk space. The maximal configuration is 8 CPUs, 16 GB
 Of RAM, unlimited disk space.
-{{:navody:vps:resources.png?300|}}
+{{:en:screenshots:vpsadmin:vps-management:resource-settings.png?300|}}
-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 parameters of a different VPS or ask the support for more resources.
 ===== Hostname =====
@@ Line 59: / Line 72: @@
 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.
-{{:navody:vps:hostname.png?300|}}
+{{:en:screenshots:vpsadmin:vps-management:hostname-form.png?300|}}
 ===== Features =====
@@ Line 66: / Line 79: @@
 the VPS restarts.
-{{ :navody:vps:vps_features.png |}}
+{{:en:screenshots:vpsadmin:vps-management:feature-settings.png|}}
   * TUN/TAP - "TUN routing/TAP bridging" Allows access to virtual network interfaces, e.g. for VPN.
@@ Line 73: / Line 86: @@
   * KVM - "Kernel-based Virtual Machine"
   * LXC nesting - Needed to use LXC/LXD containers inside the VPS
-===== Migrating a VPS Between Nodes =====
-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.
-{{:navody:vps:swap_vps.png?300|}}
-Before performing the action, the table displays the state of the VPS before and after the
-migration.
 ===== Cloning VPSs =====
@@ Line 90: / Line 91: @@
 an existing VPS, the original VPS and all its subdatasets are **removed**!
-{{:navody:vps:clone_vps.png?300|}}
+{{:en:screenshots:vpsadmin:playground:clone-vps-form.png?300|}}
-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.
+In the form, choose the environment, locations or VPS to which you want to clone the VPS that is currently open.
-===== Setting the Time for Planned VPS Outages =====
+===== Setting the Time for Planned VPS Maintenances =====
-The appropriate time for planned VPS outages can be set differently for every day of
+The appropriate time for planned VPS maintenances can be set differently for every day of
 the week.
-{{:navody:vps:outage_windows.png?300|}}
+{{:en:screenshots:vpsadmin:vps-management:outage-windows.png?300|}}
 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
+necessary. This is mostly used when migrating VPSes between nodes. We always inform
-about planned outages and migrations either in the outage list or to the email that you have
+about maintenances and migrations on the email that you have
 provided in vpsAdmin.
-===== Maintenance Mode =====
-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.

Knowledge base

User Tools

Site Tools

Differences

Page Tools