Virtual Server Request Form

Virtual server variant Server variant ^*

Items marked with an asterisk *) are mandatory.

Custom variant Number of CPUs ^* RAM size [GB] ^* Disk size [GB] ^*

Technical contact (server administrator) Name ^* Phone Number E-Mail admin ^*

Your address will be added to the virtualization platform user mailing list. This information channel is used to report scheduled maintenance, outages or security threats.

Virtual server configuration Operating system ^* Hostname ^*

The virtual server is assigned 1x IPv4 and 1x IPv6 address from the reserved range. The second and additional IPv4 address is charged. If you need to connect the server to a different or custom subnet, select the "request custom addresses" option and justify the request.

IP address ^* I prefer datacenter to run virtual server ^*

Public SSH key (server administrator)

Insert the public part of your SSH key. This key is used to log in to the virtual server as root. Name and password logins are prohibited on virtual servers.

SSH key

Service provided Brief description of the service hosted on the server ^* Hosted service classification ^*

The information does not affect the server's functionality, it just allows administrators to properly route priorities when dealing with emergencies.

Criticality of the virtual machine and its services Availability Classification ^*

Virtual servers are automatically protected against the failure of a single component within a single datacenter (HA0). If it is a major failure affecting the entire single datacenter, we are waiting for the issue to be resolved before starting. By selecting a higher category, you can skip/reduce this time.

*HA1* (The server can be started from a semi-synchronous replica (or backup) in another location even with the risk of incomplete data. In the event that the affected site is restored to full operation after the servers are started in the other site, the servers will remain running from the restored data; reverting to the original data is no longer possible! This option is not suitable for servers with frequently changing data, e.g. DB)

*HA2* (maximum possible availability, there must be multiple instances in multiple sites that use a floating address and the service will be served by another system in case of failure)

Disaster recovery ^*

This information will help us to better allocate our forces and get the most important systems up and running as soon as possible in the event of an emergency.

Network Security IDS/IPS protection ^*

By default, the virtual server will be protected at the network level and will be placed behind the IDS/IPS Fortigate element. It is not suitable for data-intensive services. Please write any questions in the comments.

Organization requesting the virtual server Virtual server owner ^*

Detail of organization requesting virtual server Oddělení provozující virtuální server ^*

Additional comments/requests or additional services Do I agree to the Terms of Service of the virtualization platform?

Finish