Hetzner - DokuWiki

CloudServer
(Zwischen Speichern bevor ich weiterarbeite)
Zeile 1: Zeile 1:
 
{{Languages|CloudServer}}
 
{{Languages|CloudServer}}
  
Die CloudServer FAQ ist derzeit nur auf Englisch verfügbar: [[CloudServer/en|Englische CloudServer FAQ]]
+
Die Deutsche Version wird gerade geschrieben und übersetzt und ist noch in Arbeit.
 +
 
 +
= Funktionalität =
 +
 
 +
== <span id="local_and_ceph"></span>Was ist der unterschied zwischen Lokalen Speicher und Netzwerk Speicher? ==
 +
 
 +
Server mit lokalen Festplatten speichern alle Daten auf einem lokalen RAID-Spiegel auf dem Hostsystem. Sie sind für hohe E / A-Leistung und geringe Latenz optimiert und eignen sich besonders für Anwendungen, die einen schnellen Zugriff auf Festplatten mit geringer Latenz erfordern, wie z. B. Datenbanken.
 +
 
 +
Server mit ceph-Festplatten speichern ihre Daten in einem Remote-Dateisystem. Jeder Block wird auf drei verschiedenen Servern gespeichert. Sie eignen sich besonders für höhere Verfügbarkeit: Wenn die Hardware des lokalen Hosts ausfällt, starten wir den Server auf einem anderen Computer.
 +
 
 +
== <span id="dedicated_vcpu"></span>Was sind die dedizierten vCPU-Serverpläne? ==
 +
 
 +
Jede dedizierte vCPU-Instanz verfügt über eigene dedizierte CPU-Ressourcen (1 vCPU = 1 Hyper-Thread), sodass diese CCX-Server eine vorhersehbare hohe CPU-Leistung bieten. Wir empfehlen sie für Systeme mit hohen Produktionslasten und CPU-intensiven Anwendungen. Sie sind nur mit lokalem Speicher (NVMe SSD) verfügbar. Sie verwenden die gleiche Hochleistungshardware wie unsere anderen Hetzner Cloud-Server und verfügen über eine großzügige Zuordnung von E / A und Netzwerkleistung.
 +
 
 +
Natürlich sind auch alle anderen Hetzner Cloud-Funktionen, die Sie kennen und lieben, für diese dedizierten vCPU-Instanzen verfügbar.
 +
Mit der Rescale-Funktion der Administrationsoberfläche von Cloud Console können Sie die CCX-Server je nach Anzahl der benötigten Ressourcen up- und downgraden.
 +
 
 +
Bitte beachten Sie unsere Systemrichtlinien bei  https://www.hetzner.com/rechtliches/cloud-server/ gelten auch für unsere dedizierten vCPU-Instanzen.
 +
 
 +
== <span id="cloudinit"></span>Kann ich Cloud-Init beim Erstellen von Servern verwenden? ==
 +
 
 +
Beim Erstellen Ihres Servers können Sie Cloud-Init-Benutzerdaten einfügen. Dies bedeutet, dass Sie den Server beim Booten dazu veranlassen können, spezielle Befehle auszuführen, z. B. das Erstellen von Benutzern oder das Ausführen eines Shellbefehls.
 +
 
 +
Beispiel:
 +
 
 +
&#35;!/bin/bash
 +
touch /tmp/cloudinit_was_here
 +
 
 +
 
 +
Für mehr Beispiele besuchen sie https://help.ubuntu.com/community/CloudInit und http://cloudinit.readthedocs.io/en/latest/topics/examples.html
 +
 
 +
Damit Cloud-Init funktioniert, müssen Sie die von uns bereitgestellten System-Images verwenden, da diese eine spezielle Cloud-Init-Datenquelle enthalten.
 +
 
 +
== <span id="floatingips"></span>Was sind Floating Ip´s und wie funktionieren sie? ==
 +
 
 +
Floating IPs helfen Ihnen, sehr flexible Setups zu erstellen. Sie können jedem Server eine Floating-IP zuweisen. Der Server kann dann diese IP verwenden. Sie können es jederzeit einem anderen Server zuweisen, oder Sie können die Zuweisung der Floating-IP von den Servern aufheben.
 +
 
 +
Floating IPs können global verwendet werden. Das bedeutet, Sie können einem Server an einem Standort eine Floating-IP zuweisen und diese später einem Server an einem anderen Standort zuweisen. Für optimales Routing und Latenz sollten Floating-IPs an dem Ort verwendet werden, an dem sie erstellt wurden.
 +
 
 +
Damit Floating-IPs funktionieren, müssen Sie sie im Betriebssystem des verwendeten Servers konfigurieren.
 +
 
 +
Um temporär ein Floating-IPv4 "1.2.3.4" zu konfigurieren, können Sie es ausführen
 +
 
 +
ip addr add 1.2.3.4/32 dev eth0
 +
 
 +
Bitte beachten Sie, dass diese Konfiguration einen Neustart nicht übersteht.
 +
 
 +
Um die erste IPv6-Adresse des Floating-IPv6-Netzwerkblocks 2a01: 4f8: 2c17: 2c :: / 64 zu konfigurieren, sollten Sie Folgendes ausführen:
 +
 
 +
ip addr add 2a01:4f8:2c17:2c::1/128 dev eth0
 +
 
 +
==<span id="floatingips_permanent"></span>Wie konfiguriert man eine Floating-IP dauerhaft?==
 +
Informationen zum permanenten Konfigurieren einer Floating Ip lesen sie:
 +
[https://wiki.hetzner.de/index.php/Cloud_floating_IP_persistent/de '''our tutorial.''']
 +
 
 +
== <span id="snapshots_and_backups"></span>Was sind Momentaufnahmen und Backups? ==
 +
 
 +
Snapshots sind Kopien der Festplatten Ihres Servers.
 +
 
 +
Sie können Snapshots erstellen, wenn Sie sie benötigen, und sie für immer behalten, bis Sie sie löschen. Wir von Hetzner Online speichern die Snapshots auch dann, wenn Sie den Server löschen, von dem der Snapshot aufgenommen wurde. Wir stellen Snapshots pro Gigabyte pro Monat in Rechnung. Sehen sie  [[#How_do_you_bill_for_snapshots_and_backups.3F|here in the billing FAQ]]
 +
 
 +
Backups sind nächtliche Kopien Ihres Servers. Unser System erstellt sie automatisch für jeden Server, auf dem Sie sie aktiviert haben. Sie werden mit einer Pauschale pro Server in Rechnung gestellt. Siehe [[# How_do_you_bill_for_snapshots_and_backups.3F | hier in den häufig gestellten Fragen zur Abrechnung]]. Sicherungen sind an einen einzelnen Server gebunden und werden automatisch gelöscht, wenn Sie den Server löschen. Für jeden Server gibt es sieben Slots für Backups. Wenn alle Slots voll sind und Sie einen weiteren erstellen, wird das älteste Backup gelöscht.
 +
 
 +
Um auf einen Schnappschuss oder eine Sicherung zuzugreifen, müssen Sie entweder
 +
 
 +
* Erstellen Sie mit der Cloud-Konsole einen neuen Server und wählen Sie den Snapshot oder das Backup als Quellabbild aus. Oder
 +
* Erstellen Sie einen vorhandenen Server mit dem Snapshot oder der Sicherung als Quellabbild neu. Beachten Sie, dass dadurch der Inhalt der Serverfestplatte überschrieben wird.
 +
 
 +
 
 +
Es empfiehlt sich, beim Erstellen von Momentaufnahmen oder Sicherungen den Server herunterzufahren, um die Datenkonsistenz auf den Festplatten sicherzustellen. Sie können sie jedoch auch aus einem laufenden System erstellen. In diesem Fall werden wir versuchen, die Festplatten-Caches Ihres Betriebssystems mit [https://wiki.libvirt.org/page/Qemu_guest_agent Qemu Guest Agent] zu leeren, bevor Sie Snapshots erstellen. In diesem Fall können wir die Datenkonsistenz jedoch nicht garantieren.
 +
 
 +
== <span id="backup_window"></span>Kann ich mein Backup-Fenster auswählen? ==
 +
 
 +
Früher gab es eine Option, ein Fenster selbst auszuwählen, wir mussten diese Funktion jedoch deaktivieren. Dadurch können wir die zusätzliche Last, die durch das Ausführen von Backups entsteht, besser über den Tag verteilen. Dies war notwendig, da viele Benutzer dasselbe Fenster auswählten. Dies hatte Auswirkungen auf die Leistung und beeinträchtigte die Serverleistung zu bestimmten Tageszeiten.
 +
 
 +
Verwenden Sie unsere Snapshot-Funktion, wenn Sie genau steuern möchten, wann Ihre Festplatte gespeichert wird.
 +
 
 +
== <span id="projects"></span>What are projects, and how can I use them? ==
 +
 
 +
You can group your servers and other resources into projects. For each project you can invite other users to join and therefore work with you on the project via Cloud Console. To invite a user select "Access; Members; Add Member".
 +
 
 +
[[Datei:add_member.png|none|600px]]
 +
 
 +
 
 +
You can then enter the email address of the person you want to invite and choose their role, which determines their access level in this project.
 +
 
 +
[[Datei:add_member_2.png|center|500x339px]]
 +
 
 +
 
 +
The invitee will get an email containing a special link. After clicking it he can log in with his existing Hetzner Account details or create a new account. On completion he can accept the invitation and work together with you in your project.
 +
 
 +
You can always revoke access to the project or change the role of another member by going to  "Access; Members in your Cloud Console".
 +
 
 +
Each member's role in a project determines what they are allowed to do:
 +
 
 +
 
 +
{| class="wikitable"
 +
|-
 +
! Role
 +
! Permissions
 +
|-
 +
| Owner
 +
| Highest access level. Can do everything an admin can do. Will be invoiced for all resources in the project, regardless of who created them. Each project can only have one owner.
 +
|-
 +
| Admin
 +
| Can do everything a member can do. Additionally can manage project members (add/remove/change role) and API tokens.
 +
|-
 +
| Member
 +
| Can create, modify and delete all resources in the project, such as servers, floating IPs, images, etc.
 +
|-
 +
| Restricted
 +
| Can create, modify and delete all resources in the project except for:
 +
* creating or deleting servers
 +
* creating snapshots
 +
* deleting snapshots or backups
 +
* converting backups into snapshots
 +
* switching on or off backups for a server
 +
* creating floating IPs
 +
* changing server types
 +
|}
 +
 
 +
== <span id="limits"></span>Are there limits to the number of resources I can get? ==
 +
 
 +
Our cloud services are designed in a way so that you can tap into additional resources easily. In order to prevent abuse, we put some limits on the number of resources a single account can create.
 +
 
 +
These limits can be found on the "Limits" tab in your overview page. If you would like us to increase the resource limits use the "Request limit change" button on the "Limits" tab.
 +
 
 +
== <span id="rebuild"></span>How can I reinstall a server? ==
 +
 
 +
Our recommended way to do this is to delete your old server and create a new one instead. This way you can ensure that all settings -- e.g. regarding ssh access keys and other things -- are fresh and up-to-date. There is also a high chance that your new server will get the same ip address your old, deleted server had.
 +
 
 +
== <span id="rebuild_access"></span>How can I access the server I rebuilt? ==
 +
 
 +
Assume you rebuilt your Server ''server1'' from a snapshot called ''snap1''.
 +
 
 +
'''Case 1: ''server1'' was originally created without selecting a SSH-Key:'''
 +
 
 +
After rebuild, a new root-password for ''server1'' will be generated and mailed to you. It will be set on first boot using the cloud-init mechanism.
 +
 
 +
If ''snap1'' contained injected SSH keys, these will also continue to work.
 +
 
 +
'''Case 2: ''server1'' was created with selecting your SSH-Key ''key1'': '''
 +
 
 +
After rebuild, the key ''key1'' will be injected into ''server1'' on first boot using the cloud-init mechanism. You can use ''key1'' to access your server.
 +
 
 +
If ''snap1'' contained any more keys in its authorized_keys file, you can also still use these to access ''server1''.
 +
 
 +
In all cases, ''server1'' cannot be accessed using a root-password directly after the rebuild, even if one was set in ''snap1''.
 +
 
 +
 
 +
Case 1 and Case 2 only apply if you restore a snapshot that was taken from our officially provided images. If you used the rescue system or other means to install the server ''snap1'' was taken from, it will not be fit for reconfiguration via cloud-init, and its behavior might be different.
 +
 
 +
== <span id="create_access"></span>While creating a new server, I have selected a snapshot as source image. How can I access this server? ==
 +
 
 +
Assume you created your server ''server1'' from a snapshot called ''snap1''.
 +
 
 +
'''Case 1: You did not select a ssh key while creating ''server1:''
 +
 
 +
After server creation, a root password for access will be generated and mailed to you. It will be set using the cloud-init mechanism.
 +
 
 +
If ''snap1'' contained injected SSH keys, these will also continue to work.
 +
 
 +
'''Case 2: You selected ssh key ''key1'' while creating ''server1'':
 +
 
 +
After server creation, the key ''key1'' will be injected into ''server1'' using the cloud-init mechanism. You can use ''key1'' to access your server.
 +
 
 +
If ''snap1'' contained any more keys in its authorized_keys file, you can also still use these to access ''server1''.
 +
 
 +
In all cases ''server1'' cannot be accessed using a root-password directly after it creation, even if one was set in ''snap1''.
 +
 
 +
 
 +
Case 1 and Case 2 only apply if you use a snapshot that was taken from our officially provided images. If you used the rescue system or other means to install the server ''snap1'' was taken from, it will not be fit for reconfiguration via cloud-init, and its behavior might be different.
 +
 
 +
== <span id="console_keyboard_mapping"></span>The keyboard mapping in the console window seems to be wrong. How can I fix this? ==
 +
 
 +
All of our images come with keyboard mapping set for a US keyboard. If you have something different, you need to configure it yourself within your server.
 +
 
 +
For example, on Ubuntu you can do so by running
 +
 
 +
sudo dpkg-reconfigure keyboard-configuration
 +
 
 +
and selecting the keyboard layout you are using on your local PC. After a reboot, the keyboard mapping in the console will be correct.
 +
 
 +
== <span id="server_protection"></span>How do I protect my server from being deleted by accident?  ==
 +
 
 +
Servers, Snapshots and Floating IPs can be protected in the Cloud Console and API.
 +
 
 +
Before you can delete a protected resource, you have to first deactivate the deletion protection.
 +
This provides an additional safeguard for accidental deletion.
 +
 
 +
Protected resources are indicated by a lock icon on the Server, Snapshot and Floating IP overview page.
 +
You can't use the "Rebuild" feature to reinstall a protected server.
 +
 
 +
= Volumes =
 +
 
 +
== <span id="what_are_volumes"></span> What are the Hetzner Cloud Volumes? ==
 +
 
 +
It is a feature for fast, flexible, and cost-effective (SSD based) block storage which you can attach to your Hetzner Cloud Server.
 +
 
 +
== <span id="volume_locations"></span> Are volumes available in all locations? ==
 +
 
 +
Volumes are available at the Nuremberg and Helsinki locations. We expect to bring them online in Falkenstein before the end of 2018.
 +
 
 +
== <span id="volume_resize"></span> Can I resize Volumes? ==
 +
 
 +
You can resize a Volume to up to 10 TB. The feature uses a sliding bar to allow you to choose the size you need in 1 GB increments. Please note, however, that you can only increase the size of your Volume, not descrease it.
 +
 
 +
== <span id="volume_mounting"></span> How can I mount a volume on the server? ==
 +
 
 +
When you attach the volume to your server using the Cloud Console, you will see the commands you can use to mount the Volume.
 +
 
 +
== <span id="volume_attaching_failed"></span> Attaching a volume fails. Why does this happen? ==
 +
 
 +
Servers which have run for quite some time may need a power off and power on cycle.
 +
This is a one time only requirement and will trigger our cloud management system to enable Volume support for this server.
 +
Please note, a soft reboot is not enough.
 +
 
 +
== <span id="volume_backup"></span> How does Hetzner Online store the data in volumes? ==
 +
 
 +
Every block of data is stored on three different physical servers (triple replication).
 +
 
 +
== <span id="volume_server_limit"></span> Is there a limit on the number of attached volumes? ==
 +
 
 +
You can mount up to five volumes on each of your Hetzner Cloud Servers.
 +
 
 +
== <span id="volume_size_limit"></span> Are there size limits for volumes? ==
 +
 
 +
Volumes can be between 10 GB and 10 TB.
 +
 
 +
== <span id="volume_dedicated_server"></span> Can I also mount Hetzner Cloud Volumes on a Hetzner dedicated root server? ==
 +
 
 +
Unfortunately not: Volumes only work with cloud servers.
 +
 
 +
== <span id="volume_beta_cost"></span> What do the volumes cost? ==
 +
 
 +
During the beta test, volumes are free. After the beta test, the price will be € 0.04 / GB per month (excl. VAT).
 +
 
 +
== <span id="volume_beta_deletion"></span> Will Hetzner Online delete my volumes at the end of the beta test? ==
 +
 
 +
No. All the volumes that you create during the beta test will remain. But after the beta test is over, we at Hetzner Online will begin to invoice you for all remaining Volumes. We will send you an email to remind you about this before the beta test is over.
 +
 
 +
== <span id="volume_beta_limits"></span> Which limits apply during the beta test? ==
 +
 
 +
During the beta test, you can have up to 10 Hetzner Cloud Volumes. The minimum size per Volume is 10 GB. Each customer can have a maximum of 100 GB storage on all their Volumes total.
 +
 
 +
= Billing =
 +
 
 +
== <span id="bill_servers"></span>How do you bill your servers? ==
 +
 
 +
Servers have both a monthly price cap and a price per hour. Your server's bill will never exceed its monthly price cap. If you choose to use the server for less than a month, you will be billed at the hourly rate.
 +
 
 +
Mathematically speaking, you will be billed the minimum amount, whether that is the monthly price cap OR the hourly price multiplied by the number of hours you used the server.
 +
 
 +
Hourly usage of a server is always rounded up: If you create a server just for a few minutes you will still be billed for one whole hour. This reflects the additional load on your systems that is caused by the server's creation.
 +
 
 +
== <span id="bill_off_servers"></span>Do you bill servers that are off? ==
 +
 
 +
Yes. All servers that have finished their creation process will be billed until they are deleted, regardless of their state.
 +
 
 +
This is because, internally, we allocate full resources to servers regardless of their power state. And it enables rapid startup and boot times for you, the customer.
 +
 
 +
== <span id="bill_floating_ips"></span>How do you bill for floating IPs? ==
 +
 
 +
Floating IPs are billed monthly. If you use your floating IP for less than a month, you will be billed for the appropriate fraction of it.
 +
 
 +
== <span id="bill_traffic"></span>How do you bill for traffic? ==
 +
 
 +
We only bill for outgoing traffic. Incoming and internal traffic is free. Internal traffic includes other Hetzner Cloud servers, other Hetzner Online dedicated root servers, and other Hetzner Online servers, services, or web hosting packages.
 +
 
 +
If you exceed the traffic included in your package, we will bill you for every TB of over usage. If you only consume a fraction of a TB, it will be rounded up to the next full TB.
 +
 
 +
Example: Your server has 20TB included traffic. Within a month you use 20.8TB. You will be billed for 1 TB of over usage.
 +
 
 +
== <span id="bill_snapshots_and_backups"></span>How do you bill for snapshots and backups? ==
 +
 
 +
Snapshots are billed per gigabyte per month. If a snapshot only exists for a fraction of a month, then it will only be billed for this fraction. We will only bill you for the space the compressed snapshot uses in our storage system. So if you create a snapshot of a disk of 40GB, you will be billed for 40GB or less - depending on how the data on your disk compresses.
 +
 
 +
Backups are billed as a monthly flat price which is 20% of the price of the server you activate them for. So if you activate backups for a server that costs €2.49 per month, you will be billed an additional €2.49 * 0.2 = €0.498/month. For this price you will get a total of 7 backup slots.
 +
 
 +
== <span id="bill_when_invoice"></span>When will I get my invoice? ==
 +
 
 +
When you sign up for our offer, we will create the first invoice earlier than usual. We will only do this for the very first invoice. We find that it helps prevent abuse.
 +
 
 +
You can manage your open invoices at any time, regardless of when we create your invoice, via your account on Cloud Console by going to "Account; Billing".
 +
 
 +
After the first invoice, we will create invoices based on full calendar months. To space out invoices, we may create them up to 28 days after the last month was completed.
 +
 
 +
== <span id="bill_control_costs"></span>How do I keep my costs under control? ==
 +
 
 +
You can set alerts that will send you an email if you exceed a certain cost limit. To set an alert, go to "Account; Billing" in your Cloud Console.
 +
 
 +
[[Datei:billing_alert.png|none]]
 +
 
 +
 
 +
You can set values per project by clicking on the numbers.
 +
 
 +
 
 +
== <span id="bill_small_amounts"></span>How are small amounts handled in invoices? ==
 +
 
 +
All amounts within an invoice are added to the total sum.
 +
 
 +
Example: You use multiple servers with a price of 0.004€ for just one hour. When we create an invoice, all of these amounts will be added to the total sum of the invoice only after that the total sum will be rounded to two digits using commercial rounding rules. This gives us a higher level of precision than if we used the commercial rounding rules on the sub-totals.
 +
 
 +
= Technical details =
 +
 
 +
== <span id="tech_hardware"></span>What hardware do my servers run on? ==
 +
 
 +
Hetzner Cloud servers run on the latest generation of Intel Xeon CPUs (Skylake) with ECC RAM. For local storage we use NVMe SSDs.
 +
 
 +
== <span id="tech_hypervisor"></span>What hypervisor and NIC/disk drivers do you use? ==
 +
 
 +
We are running KVM as a hypervisor. We use virtio for both virtual NICs and disks.
 +
 
 +
== <span id="tech_customconfig"></span>Is there any way to get a custom configuration? ==
 +
 
 +
Customized virtual servers are not currently available. However, you can mount additional disks, called Volumes, which are flexible block storage drives with up to 10 TB storage. And you can add RAM and CPU resources with the Rescale feature.
 +
 
 +
== <span id="tech_images"></span>How are your images set up? ==
 +
 
 +
The images we provide use cloud-init to set up networking and other options.
 +
 
 +
They come with qemu-guest agent preinstalled. It is used for:
 +
 
 +
* force flushing of disk caches before snapshots and backups are created
 +
* resetting the root password on your request
 +
 
 +
If you do not want to have qemu guest agent running, feel free to uninstall it. However you will lose the functionality mentioned above.
 +
 
 +
== <span id="tech_windows"></span>Can I install Windows? ==
 +
 
 +
Right now we are focusing on support for Linux as an operating system. You can install Windows manually on your own using an ISO image. For more information, please see [[Windows_on_Cloud/en|here.]]
 +
 
 +
Please note that we will not provide any support for Windows.
 +
 
 +
== <span id="tech_meltdown"></span>Are you patched against Meltdown and Spectre? ==
 +
 
 +
All currently released stable patches are applied. We expect to apply more patches as they get released by our vendors over the new few days and weeks.
 +
 
 +
== <span id="tech_api_tokens"></span>How are API tokens stored? ==
 +
 
 +
In order to access our API you will need to generate an API token, which is a 64 byte string. The last 32 bytes of this key are secret. The first 32 bytes are a prefix which is used for identification, similar to a username. On Token creation we will display the full version only once.
 +
 
 +
After that your token cannot be retrieved in full again since the secret portion is stored in a hashed format only. The prefix can be retrieved again to identify the token, for example in the list of account activities.
 +
 
 +
The prefix part itself does not enable access to the API since the secret part is needed as well.
 +
 
 +
== <span id="tech_distributions"></span>For your Debian and Centos Images: What is the minor version? ==
 +
 
 +
We automatically update our images to be the latest minor version within two weeks after the release. That means that our existing Debian 9 image will always contain the latest Debian 9.X version within two weeks after its release.
 +
 
 +
'''More detail:'''
 +
 
 +
For Debian and Centos the versioning scheme is MAJOR.MINOR, e.g. Debian 9.1 is Debian with major version 9 and minor version 1.
 +
 
 +
For both Debian and Centos updating a minor Version (e.g. Debian 9.3 -> 9.4) is done implicitly when updating your software packages. Therefore the minor version will change during the lifetime of your server. To avoid confusion our Image descriptions do not contain the minor version but only the major (e.g. "Debian 9" instead of "Debian 9.1")
 +
 
 +
= Future plans =
 +
 
 +
== <span id="future_feature_x"></span>Do you plan to add x feature?/Will you add more features? ==
 +
 
 +
We started Hetzner Cloud with the minimal feature set we think is necessary to enter the market.
 +
However we intend to continually add new features and services. We have designed our internal development methods and systems to allow us to add more features.
 +
 
 +
Unfortunately we cannot provide you with a precise roadmap of the things we are working on. However you can stay up to date by following us on Twitter at https://twitter.com/hetzner_online
 +
 
 +
== <span id="future_add_locations"></span>Will you add additional locations in different geographic regions? ==
 +
 
 +
We are actively looking into this option right now.
 +
 
 +
= API =
 +
 
 +
== <span id="api_general"></span>Can I access your Service through an API? ==
 +
 
 +
Of course! You can find current the api docs under https://docs.hetzner.cloud.
 +
 
 +
If you develop something against our API we appreciate feedback through the support form of your Cloud Console.
 +
 
 +
== <span id="api_sponsor"></span>Do you sponsor efforts to integrate Hetzner Cloud into Open Source libs? ==
 +
 
 +
Yes we do: If you are developing integrations based on our API and your product is Open Source you may be eligible for a free one time €50 (excl. VAT) credit on your account. Please contact us via the support page on your Cloud Console and let us know the following:
 +
 
 +
* The type of integration you would like to develop
 +
* Link to the GitHub repo you will use for the project
 +
* Link to some other Open Source work you have already done (if you have done so)
 +
 
 +
A list of integrations that are already done or being worked on can be found here:
 +
 
 +
https://github.com/hetznercloud/awesome-hcloud
 +
 
 +
We'd love to hear from you! :)
 +
 
 +
== <span id="api_cli"></span>Is there a command line (CLI) tool to access Hetzner Cloud? ==
 +
 
 +
Yes. It is provided as an Open Source Project here: https://github.com/hetznercloud/cli
 +
 
 +
If you would like to contribute or extend it, please do so by opening pull requests.
 +
 
 +
== <span id="api_lib"></span>Is there a library to access Hetzner Cloud from my programming language? ==
 +
 
 +
We currently provide a library for Go as Open Source under https://github.com/hetznercloud/hcloud-go.
 +
 
 +
You can find inofficial libraries for many languages at our integrations list: https://github.com/hetznercloud/awesome-hcloud
 +
 
 +
Since our API is very easy to use you may not even need a full lib and a quick HTTPS request may be enough; check out our API documentation at https://docs.hetzner.cloud
 +
 
 +
== <span id="work_for_us"></span>Work for us ==
 +
 
 +
We are looking for new developers. So if you like our product and would like to work for Hetzner Online, please take a look at https://career.hetzner.com
 +
 
 +
[[Kategorie:Cloud Server]]

Version vom 6. November 2018, 16:52 Uhr

Die Deutsche Version wird gerade geschrieben und übersetzt und ist noch in Arbeit.

Inhaltsverzeichnis

Funktionalität

Was ist der unterschied zwischen Lokalen Speicher und Netzwerk Speicher?

Server mit lokalen Festplatten speichern alle Daten auf einem lokalen RAID-Spiegel auf dem Hostsystem. Sie sind für hohe E / A-Leistung und geringe Latenz optimiert und eignen sich besonders für Anwendungen, die einen schnellen Zugriff auf Festplatten mit geringer Latenz erfordern, wie z. B. Datenbanken.

Server mit ceph-Festplatten speichern ihre Daten in einem Remote-Dateisystem. Jeder Block wird auf drei verschiedenen Servern gespeichert. Sie eignen sich besonders für höhere Verfügbarkeit: Wenn die Hardware des lokalen Hosts ausfällt, starten wir den Server auf einem anderen Computer.

Was sind die dedizierten vCPU-Serverpläne?

Jede dedizierte vCPU-Instanz verfügt über eigene dedizierte CPU-Ressourcen (1 vCPU = 1 Hyper-Thread), sodass diese CCX-Server eine vorhersehbare hohe CPU-Leistung bieten. Wir empfehlen sie für Systeme mit hohen Produktionslasten und CPU-intensiven Anwendungen. Sie sind nur mit lokalem Speicher (NVMe SSD) verfügbar. Sie verwenden die gleiche Hochleistungshardware wie unsere anderen Hetzner Cloud-Server und verfügen über eine großzügige Zuordnung von E / A und Netzwerkleistung.

Natürlich sind auch alle anderen Hetzner Cloud-Funktionen, die Sie kennen und lieben, für diese dedizierten vCPU-Instanzen verfügbar. Mit der Rescale-Funktion der Administrationsoberfläche von Cloud Console können Sie die CCX-Server je nach Anzahl der benötigten Ressourcen up- und downgraden.

Bitte beachten Sie unsere Systemrichtlinien bei https://www.hetzner.com/rechtliches/cloud-server/ gelten auch für unsere dedizierten vCPU-Instanzen.

Kann ich Cloud-Init beim Erstellen von Servern verwenden?

Beim Erstellen Ihres Servers können Sie Cloud-Init-Benutzerdaten einfügen. Dies bedeutet, dass Sie den Server beim Booten dazu veranlassen können, spezielle Befehle auszuführen, z. B. das Erstellen von Benutzern oder das Ausführen eines Shellbefehls.

Beispiel:

#!/bin/bash
touch /tmp/cloudinit_was_here


Für mehr Beispiele besuchen sie https://help.ubuntu.com/community/CloudInit und http://cloudinit.readthedocs.io/en/latest/topics/examples.html

Damit Cloud-Init funktioniert, müssen Sie die von uns bereitgestellten System-Images verwenden, da diese eine spezielle Cloud-Init-Datenquelle enthalten.

Was sind Floating Ip´s und wie funktionieren sie?

Floating IPs helfen Ihnen, sehr flexible Setups zu erstellen. Sie können jedem Server eine Floating-IP zuweisen. Der Server kann dann diese IP verwenden. Sie können es jederzeit einem anderen Server zuweisen, oder Sie können die Zuweisung der Floating-IP von den Servern aufheben.

Floating IPs können global verwendet werden. Das bedeutet, Sie können einem Server an einem Standort eine Floating-IP zuweisen und diese später einem Server an einem anderen Standort zuweisen. Für optimales Routing und Latenz sollten Floating-IPs an dem Ort verwendet werden, an dem sie erstellt wurden.

Damit Floating-IPs funktionieren, müssen Sie sie im Betriebssystem des verwendeten Servers konfigurieren.

Um temporär ein Floating-IPv4 "1.2.3.4" zu konfigurieren, können Sie es ausführen

ip addr add 1.2.3.4/32 dev eth0

Bitte beachten Sie, dass diese Konfiguration einen Neustart nicht übersteht.

Um die erste IPv6-Adresse des Floating-IPv6-Netzwerkblocks 2a01: 4f8: 2c17: 2c :: / 64 zu konfigurieren, sollten Sie Folgendes ausführen:

ip addr add 2a01:4f8:2c17:2c::1/128 dev eth0

Wie konfiguriert man eine Floating-IP dauerhaft?

Informationen zum permanenten Konfigurieren einer Floating Ip lesen sie: our tutorial.

Was sind Momentaufnahmen und Backups?

Snapshots sind Kopien der Festplatten Ihres Servers.

Sie können Snapshots erstellen, wenn Sie sie benötigen, und sie für immer behalten, bis Sie sie löschen. Wir von Hetzner Online speichern die Snapshots auch dann, wenn Sie den Server löschen, von dem der Snapshot aufgenommen wurde. Wir stellen Snapshots pro Gigabyte pro Monat in Rechnung. Sehen sie here in the billing FAQ

Backups sind nächtliche Kopien Ihres Servers. Unser System erstellt sie automatisch für jeden Server, auf dem Sie sie aktiviert haben. Sie werden mit einer Pauschale pro Server in Rechnung gestellt. Siehe hier in den häufig gestellten Fragen zur Abrechnung. Sicherungen sind an einen einzelnen Server gebunden und werden automatisch gelöscht, wenn Sie den Server löschen. Für jeden Server gibt es sieben Slots für Backups. Wenn alle Slots voll sind und Sie einen weiteren erstellen, wird das älteste Backup gelöscht.

Um auf einen Schnappschuss oder eine Sicherung zuzugreifen, müssen Sie entweder

  • Erstellen Sie mit der Cloud-Konsole einen neuen Server und wählen Sie den Snapshot oder das Backup als Quellabbild aus. Oder
  • Erstellen Sie einen vorhandenen Server mit dem Snapshot oder der Sicherung als Quellabbild neu. Beachten Sie, dass dadurch der Inhalt der Serverfestplatte überschrieben wird.


Es empfiehlt sich, beim Erstellen von Momentaufnahmen oder Sicherungen den Server herunterzufahren, um die Datenkonsistenz auf den Festplatten sicherzustellen. Sie können sie jedoch auch aus einem laufenden System erstellen. In diesem Fall werden wir versuchen, die Festplatten-Caches Ihres Betriebssystems mit Qemu Guest Agent zu leeren, bevor Sie Snapshots erstellen. In diesem Fall können wir die Datenkonsistenz jedoch nicht garantieren.

Kann ich mein Backup-Fenster auswählen?

Früher gab es eine Option, ein Fenster selbst auszuwählen, wir mussten diese Funktion jedoch deaktivieren. Dadurch können wir die zusätzliche Last, die durch das Ausführen von Backups entsteht, besser über den Tag verteilen. Dies war notwendig, da viele Benutzer dasselbe Fenster auswählten. Dies hatte Auswirkungen auf die Leistung und beeinträchtigte die Serverleistung zu bestimmten Tageszeiten.

Verwenden Sie unsere Snapshot-Funktion, wenn Sie genau steuern möchten, wann Ihre Festplatte gespeichert wird.

What are projects, and how can I use them?

You can group your servers and other resources into projects. For each project you can invite other users to join and therefore work with you on the project via Cloud Console. To invite a user select "Access; Members; Add Member".

Add member.png


You can then enter the email address of the person you want to invite and choose their role, which determines their access level in this project.

Add member 2.png


The invitee will get an email containing a special link. After clicking it he can log in with his existing Hetzner Account details or create a new account. On completion he can accept the invitation and work together with you in your project.

You can always revoke access to the project or change the role of another member by going to "Access; Members in your Cloud Console".

Each member's role in a project determines what they are allowed to do:


Role Permissions
Owner Highest access level. Can do everything an admin can do. Will be invoiced for all resources in the project, regardless of who created them. Each project can only have one owner.
Admin Can do everything a member can do. Additionally can manage project members (add/remove/change role) and API tokens.
Member Can create, modify and delete all resources in the project, such as servers, floating IPs, images, etc.
Restricted Can create, modify and delete all resources in the project except for:
  • creating or deleting servers
  • creating snapshots
  • deleting snapshots or backups
  • converting backups into snapshots
  • switching on or off backups for a server
  • creating floating IPs
  • changing server types

Are there limits to the number of resources I can get?

Our cloud services are designed in a way so that you can tap into additional resources easily. In order to prevent abuse, we put some limits on the number of resources a single account can create.

These limits can be found on the "Limits" tab in your overview page. If you would like us to increase the resource limits use the "Request limit change" button on the "Limits" tab.

How can I reinstall a server?

Our recommended way to do this is to delete your old server and create a new one instead. This way you can ensure that all settings -- e.g. regarding ssh access keys and other things -- are fresh and up-to-date. There is also a high chance that your new server will get the same ip address your old, deleted server had.

How can I access the server I rebuilt?

Assume you rebuilt your Server server1 from a snapshot called snap1.

Case 1: server1 was originally created without selecting a SSH-Key:

After rebuild, a new root-password for server1 will be generated and mailed to you. It will be set on first boot using the cloud-init mechanism.

If snap1 contained injected SSH keys, these will also continue to work.

Case 2: server1 was created with selecting your SSH-Key key1:

After rebuild, the key key1 will be injected into server1 on first boot using the cloud-init mechanism. You can use key1 to access your server.

If snap1 contained any more keys in its authorized_keys file, you can also still use these to access server1.

In all cases, server1 cannot be accessed using a root-password directly after the rebuild, even if one was set in snap1.


Case 1 and Case 2 only apply if you restore a snapshot that was taken from our officially provided images. If you used the rescue system or other means to install the server snap1 was taken from, it will not be fit for reconfiguration via cloud-init, and its behavior might be different.

While creating a new server, I have selected a snapshot as source image. How can I access this server?

Assume you created your server server1 from a snapshot called snap1.

Case 1: You did not select a ssh key while creating server1:

After server creation, a root password for access will be generated and mailed to you. It will be set using the cloud-init mechanism.

If snap1 contained injected SSH keys, these will also continue to work.

Case 2: You selected ssh key key1 while creating server1:

After server creation, the key key1 will be injected into server1 using the cloud-init mechanism. You can use key1 to access your server.

If snap1 contained any more keys in its authorized_keys file, you can also still use these to access server1.

In all cases server1 cannot be accessed using a root-password directly after it creation, even if one was set in snap1.


Case 1 and Case 2 only apply if you use a snapshot that was taken from our officially provided images. If you used the rescue system or other means to install the server snap1 was taken from, it will not be fit for reconfiguration via cloud-init, and its behavior might be different.

The keyboard mapping in the console window seems to be wrong. How can I fix this?

All of our images come with keyboard mapping set for a US keyboard. If you have something different, you need to configure it yourself within your server.

For example, on Ubuntu you can do so by running

sudo dpkg-reconfigure keyboard-configuration

and selecting the keyboard layout you are using on your local PC. After a reboot, the keyboard mapping in the console will be correct.

How do I protect my server from being deleted by accident?

Servers, Snapshots and Floating IPs can be protected in the Cloud Console and API.

Before you can delete a protected resource, you have to first deactivate the deletion protection. This provides an additional safeguard for accidental deletion.

Protected resources are indicated by a lock icon on the Server, Snapshot and Floating IP overview page. You can't use the "Rebuild" feature to reinstall a protected server.

Volumes

What are the Hetzner Cloud Volumes?

It is a feature for fast, flexible, and cost-effective (SSD based) block storage which you can attach to your Hetzner Cloud Server.

Are volumes available in all locations?

Volumes are available at the Nuremberg and Helsinki locations. We expect to bring them online in Falkenstein before the end of 2018.

Can I resize Volumes?

You can resize a Volume to up to 10 TB. The feature uses a sliding bar to allow you to choose the size you need in 1 GB increments. Please note, however, that you can only increase the size of your Volume, not descrease it.

How can I mount a volume on the server?

When you attach the volume to your server using the Cloud Console, you will see the commands you can use to mount the Volume.

Attaching a volume fails. Why does this happen?

Servers which have run for quite some time may need a power off and power on cycle. This is a one time only requirement and will trigger our cloud management system to enable Volume support for this server. Please note, a soft reboot is not enough.

How does Hetzner Online store the data in volumes?

Every block of data is stored on three different physical servers (triple replication).

Is there a limit on the number of attached volumes?

You can mount up to five volumes on each of your Hetzner Cloud Servers.

Are there size limits for volumes?

Volumes can be between 10 GB and 10 TB.

Can I also mount Hetzner Cloud Volumes on a Hetzner dedicated root server?

Unfortunately not: Volumes only work with cloud servers.

What do the volumes cost?

During the beta test, volumes are free. After the beta test, the price will be € 0.04 / GB per month (excl. VAT).

Will Hetzner Online delete my volumes at the end of the beta test?

No. All the volumes that you create during the beta test will remain. But after the beta test is over, we at Hetzner Online will begin to invoice you for all remaining Volumes. We will send you an email to remind you about this before the beta test is over.

Which limits apply during the beta test?

During the beta test, you can have up to 10 Hetzner Cloud Volumes. The minimum size per Volume is 10 GB. Each customer can have a maximum of 100 GB storage on all their Volumes total.

Billing

How do you bill your servers?

Servers have both a monthly price cap and a price per hour. Your server's bill will never exceed its monthly price cap. If you choose to use the server for less than a month, you will be billed at the hourly rate.

Mathematically speaking, you will be billed the minimum amount, whether that is the monthly price cap OR the hourly price multiplied by the number of hours you used the server.

Hourly usage of a server is always rounded up: If you create a server just for a few minutes you will still be billed for one whole hour. This reflects the additional load on your systems that is caused by the server's creation.

Do you bill servers that are off?

Yes. All servers that have finished their creation process will be billed until they are deleted, regardless of their state.

This is because, internally, we allocate full resources to servers regardless of their power state. And it enables rapid startup and boot times for you, the customer.

How do you bill for floating IPs?

Floating IPs are billed monthly. If you use your floating IP for less than a month, you will be billed for the appropriate fraction of it.

How do you bill for traffic?

We only bill for outgoing traffic. Incoming and internal traffic is free. Internal traffic includes other Hetzner Cloud servers, other Hetzner Online dedicated root servers, and other Hetzner Online servers, services, or web hosting packages.

If you exceed the traffic included in your package, we will bill you for every TB of over usage. If you only consume a fraction of a TB, it will be rounded up to the next full TB.

Example: Your server has 20TB included traffic. Within a month you use 20.8TB. You will be billed for 1 TB of over usage.

How do you bill for snapshots and backups?

Snapshots are billed per gigabyte per month. If a snapshot only exists for a fraction of a month, then it will only be billed for this fraction. We will only bill you for the space the compressed snapshot uses in our storage system. So if you create a snapshot of a disk of 40GB, you will be billed for 40GB or less - depending on how the data on your disk compresses.

Backups are billed as a monthly flat price which is 20% of the price of the server you activate them for. So if you activate backups for a server that costs €2.49 per month, you will be billed an additional €2.49 * 0.2 = €0.498/month. For this price you will get a total of 7 backup slots.

When will I get my invoice?

When you sign up for our offer, we will create the first invoice earlier than usual. We will only do this for the very first invoice. We find that it helps prevent abuse.

You can manage your open invoices at any time, regardless of when we create your invoice, via your account on Cloud Console by going to "Account; Billing".

After the first invoice, we will create invoices based on full calendar months. To space out invoices, we may create them up to 28 days after the last month was completed.

How do I keep my costs under control?

You can set alerts that will send you an email if you exceed a certain cost limit. To set an alert, go to "Account; Billing" in your Cloud Console.

Billing alert.png


You can set values per project by clicking on the numbers.


How are small amounts handled in invoices?

All amounts within an invoice are added to the total sum.

Example: You use multiple servers with a price of 0.004€ for just one hour. When we create an invoice, all of these amounts will be added to the total sum of the invoice only after that the total sum will be rounded to two digits using commercial rounding rules. This gives us a higher level of precision than if we used the commercial rounding rules on the sub-totals.

Technical details

What hardware do my servers run on?

Hetzner Cloud servers run on the latest generation of Intel Xeon CPUs (Skylake) with ECC RAM. For local storage we use NVMe SSDs.

What hypervisor and NIC/disk drivers do you use?

We are running KVM as a hypervisor. We use virtio for both virtual NICs and disks.

Is there any way to get a custom configuration?

Customized virtual servers are not currently available. However, you can mount additional disks, called Volumes, which are flexible block storage drives with up to 10 TB storage. And you can add RAM and CPU resources with the Rescale feature.

How are your images set up?

The images we provide use cloud-init to set up networking and other options.

They come with qemu-guest agent preinstalled. It is used for:

  • force flushing of disk caches before snapshots and backups are created
  • resetting the root password on your request

If you do not want to have qemu guest agent running, feel free to uninstall it. However you will lose the functionality mentioned above.

Can I install Windows?

Right now we are focusing on support for Linux as an operating system. You can install Windows manually on your own using an ISO image. For more information, please see here.

Please note that we will not provide any support for Windows.

Are you patched against Meltdown and Spectre?

All currently released stable patches are applied. We expect to apply more patches as they get released by our vendors over the new few days and weeks.

How are API tokens stored?

In order to access our API you will need to generate an API token, which is a 64 byte string. The last 32 bytes of this key are secret. The first 32 bytes are a prefix which is used for identification, similar to a username. On Token creation we will display the full version only once.

After that your token cannot be retrieved in full again since the secret portion is stored in a hashed format only. The prefix can be retrieved again to identify the token, for example in the list of account activities.

The prefix part itself does not enable access to the API since the secret part is needed as well.

For your Debian and Centos Images: What is the minor version?

We automatically update our images to be the latest minor version within two weeks after the release. That means that our existing Debian 9 image will always contain the latest Debian 9.X version within two weeks after its release.

More detail:

For Debian and Centos the versioning scheme is MAJOR.MINOR, e.g. Debian 9.1 is Debian with major version 9 and minor version 1.

For both Debian and Centos updating a minor Version (e.g. Debian 9.3 -> 9.4) is done implicitly when updating your software packages. Therefore the minor version will change during the lifetime of your server. To avoid confusion our Image descriptions do not contain the minor version but only the major (e.g. "Debian 9" instead of "Debian 9.1")

Future plans

Do you plan to add x feature?/Will you add more features?

We started Hetzner Cloud with the minimal feature set we think is necessary to enter the market. However we intend to continually add new features and services. We have designed our internal development methods and systems to allow us to add more features.

Unfortunately we cannot provide you with a precise roadmap of the things we are working on. However you can stay up to date by following us on Twitter at https://twitter.com/hetzner_online

Will you add additional locations in different geographic regions?

We are actively looking into this option right now.

API

Can I access your Service through an API?

Of course! You can find current the api docs under https://docs.hetzner.cloud.

If you develop something against our API we appreciate feedback through the support form of your Cloud Console.

Do you sponsor efforts to integrate Hetzner Cloud into Open Source libs?

Yes we do: If you are developing integrations based on our API and your product is Open Source you may be eligible for a free one time €50 (excl. VAT) credit on your account. Please contact us via the support page on your Cloud Console and let us know the following:

  • The type of integration you would like to develop
  • Link to the GitHub repo you will use for the project
  • Link to some other Open Source work you have already done (if you have done so)

A list of integrations that are already done or being worked on can be found here:

https://github.com/hetznercloud/awesome-hcloud

We'd love to hear from you! :)

Is there a command line (CLI) tool to access Hetzner Cloud?

Yes. It is provided as an Open Source Project here: https://github.com/hetznercloud/cli

If you would like to contribute or extend it, please do so by opening pull requests.

Is there a library to access Hetzner Cloud from my programming language?

We currently provide a library for Go as Open Source under https://github.com/hetznercloud/hcloud-go.

You can find inofficial libraries for many languages at our integrations list: https://github.com/hetznercloud/awesome-hcloud

Since our API is very easy to use you may not even need a full lib and a quick HTTPS request may be enough; check out our API documentation at https://docs.hetzner.cloud

Work for us

We are looking for new developers. So if you like our product and would like to work for Hetzner Online, please take a look at https://career.hetzner.com



© 2020. Hetzner Online GmbH. Alle Rechte vorbehalten.