Differences

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

--- manuals:vps:management [2016/12/10 13:49] – created toms
+++ manuals:vps:management [2025/03/14 20:35] (current) – user data aither
@@ Line 3: / Line 3: @@
 ===== Creating a VPS =====
-Members are allowed to create VPSs in the [[navody:vps:playgroundvps|playground]] and the production environment provided
+Members are allowed to create VPSs in the [[manuals:vps:playgroundvps|playground]] and the production environment provided
 that they have **enough resources** and their
-[[navody:vps:prostredi|environment settings]] allow it. You can gain resources by lowering the parameters of existing VPSs or paying extra for more resources.
+[[manuals:vps:environment|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:
@@ Line 15: / Line 15: @@
 {{:navody:vps:create_vps.png?300|}}
-So far, creating several production VPSs is only allowed for those users who
-request it and want to test this function.
 ===== IP Addresses =====
-Each member gets 1 public IPv4 address and 32 IPv6 addresses in each environment. These
+Each member gets 1 public IPv4 address and 32 /64 IPv6 addresses in each environment. These
-addresses can be distributed between various VPSs as you please. Additional IPv4 addresses are available for a [[informace:platby|fee]], IPv6 addresses are given upon request.
+addresses can be distributed between various VPSs as you please. Additional IPv4 addresses are available for a [[information:membership_fees|fee]], IPv6 addresses are given upon request.
-You can find more information about the management and various types of IP addresses [[navody:vps:ip_adresy|here]].
+You can find more information about the management and various types of IP addresses [[manuals:vps: ip_addresses|here]].
 ===== Root Password =====
@@ Line 31: / Line 29: @@
 {{:navody:vps:root_passwd.png?300|}}
+===== SSH Public Keys =====
+You can upload your public keys to vpsAdmin at Edit profile → Public keys → Add public key.
+{{ :navody:server:add_ssh_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:
+{{ :navody:server:deploy_ssh_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 46: / Line 60: @@
 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|}}
-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 68: / Line 79: @@
 the VPS restarts.
-{{:navody:vps:features.png?300|}}
+{{ :navody:vps:vps_features.png |}}
-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.
-===== 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.
+  * TUN/TAP - "TUN routing/TAP bridging" Allows access to virtual network interfaces, e.g. for VPN.
+  * FUSE - "Filesystem in Userspace" Allows access to mounting FUSE-based filesystems.
+  * PPP - "Point-to-Point Protocol"
+  * KVM - "Kernel-based Virtual Machine"
+  * LXC nesting - Needed to use LXC/LXD containers inside the VPS
+  * AppArmor control directories - Allows access to AppArmor interfaces in the kernel. Disabling this feature will prevent applications from using AppArmor.
 ===== Cloning VPSs =====
@@ Line 91: / Line 94: @@
 {{:navody:vps:clone_vps.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.
@@ Line 100: / Line 103: @@
 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