The Open Telekom Cloud is starting the first phase towards standardization of the hypervisor. In future, we will rely on the Kernel-Based Virtual Machine Hypervisor (KVM). In this connection, in the first phase, the General Purpose Flavors (c1, c2, m1, s1) based on the Xen Hypervisor will be discontinued on December 31, 2019.
KVM instead of Xen: Start of the first phase towards standardization of the hypervisor in the Open Telekom Cloud
“Overall, KVM offers more functionality and stability in the cloud area. Most applications experience a noticeable increase in performance thanks to KVM,” said Andreas Falkner, Vice President Open Telekom Cloud. “Overall, KVM is better suited to meet the requirements of a cloud business. In addition, we are now also standardizing our cloud offering, which will ensure consistent compatibility and reduced complexity for companies.”
In the meantime, KVM has developed into a de facto standard within the user community. A significant majority uses KVM, and many have voluntarily switched from Xen to KVM in the past. During the switch, Telekom experts offer support to companies that are still using Xen-based flavors on the Open Telekom Cloud. “Switching from Xen to KVM within the Open Telekom Cloud is simple in most cases. Companies have to shut down corresponding systems and restart them with the new flavor,” said Clemens Hardewig, Vice President Open Telekom Cloud Delivery.
Telekom has put together a detailed Migration Guide outlining how exactly this works; both for systems operating on Linux and for Windows-based machines. In particular, this highlights the KVM flavors that are replacing the Xen flavors, the possible problems that might arise with drivers and device names, and how users can, if necessary, keep their IP addresses and volumes unchanged despite switching flavor.
It is still possible to book Xen-based flavors until October 31, 2019. The deadline originally set for September 30, 2019 has been extended by four weeks. After this time, it will no longer be possible to book Xen-based General Purpose Flavors (c1, c2, m1, s1). On December 31, 2019, the above-mentioned General Purpose Flavors based on the Xen hypervisor will be deactivated.
To avoid downtimes, anyone using flavors with the Xen hypervisor, must have switched over to a KVM equivalent by December 31, 2019 at the latest. Companies can direct any questions to the Telekom experts at any time by calling 0391 5976 2433 for callers from Germany or +49 391 5976 2433 for callers from different countries.
Xen flavor for SAP systems, disk-intensive, large memory, GPU and high-performance flavors will initially be excluded from the conversion
To provide customers with continuity in the provision of SAP services, the certified SAP flavors (e1, e2, h1) will initially be excluded from the conversion and can therefore still be ordered for the time being. Provision of the flavors will end in the second quarter of 2022, which is why reserved models with a term of 36 months were still available until the second quarter of 2019. Shorter terms and elastic models are available accordingly to the end of the remaining term.
At the same time, we are endeavoring to certify KVM flavors for SAP. Telekom assumes that the first certified flavors will be available in 2020. As soon as this is the case, Telekom will give notification of their availability.
In addition, the disk-intensive flavors, the large memory flavor, all GPU flavors and the high-performance flavors will initially be excluded from conversion to KVM. A schedule for further XEN-based flavors (d1, g1, g2) identified as exceptions has not yet been defined. Telekom will provide information about this.
Yes, Telekom will replace all General Purpose Xen-based flavors with KVM flavors. This will initially exclude the certified SAP flavors (e1, e2, h1), disk-intensive flavors (d1), large memory flavor, all GPU flavors and the high-performance flavors.
Initially, the rollout of new Xen machines will cease. These will no longer be offered in the shop from October 31, 2019. However, the start, stop, backup and restore functions for existing flavors will remain available until complete deactivation. The latest date for the switch is December 31, 2019. On this date, the above-mentioned General Purpose Flavors (c1, c1, m1, s1) based on the Xen hypervisor will be deactivated.
The only drawback is the switching process itself for the flavors concerned, which is unfortunately necessary.
Users must switch to a KVM-based flavor by December 31, 2019. Otherwise, systems with Xen flavors will be deactivated. Before this happens, the Open Telekom Cloud team will inform users of the tenants concerned by email.
This depends on the manner in which the companies use Xen-based flavors within the Open Telekom Cloud. The KVM Migration Guide provides detailed instructions, both for Linux and for Windows users. In addition, Telekom offers telephone support on: 0391 5976 2433 for callers from Germany or +49 391 5976 2433 for callers from other countries.
Existing reserved upfront packages for certain Xen flavors will continue to run. However, anyone who wishes to switch to KVM sooner can have the packages migrated one to one.
Yes, dedicated hosts are also involved in the switch.
Users can find a detailed list of the affected Xen flavors together with their KVM equivalent in the migration guide for Linux or Windows users and in the following table.
Xen-Flavor | KVM-Äquivalent |
s1.medium | s2.medium.4 |
s1.large | s2.large.4 |
s1.xlarge | s2.xlarge.4 |
s1.2xlarge | s2.2xlarge.4 |
s1.4xlarge | s2.4xlarge.4 |
s1.8xlarge | s2.8xlarge.4 |
Xen-Flavor | KVM-Äquivalent |
m1.medium | s2.medium.8 |
m1.large | s2.large.8 |
m1.xlarge | s2.xlarge.8 |
m1.2xlarge | s2.2xlarge.8 |
m1.4xlarge | s2.4xlarge.8 |
Xen-Flavor | KVM-Äquivalent |
c1.medium | s2.medium.1 |
c1.large | s2.large.1 |
c1.xlarge | s2.xlarge.1 |
c1.2xlarge | s2.2xlarge.1 |
c1.4xlarge | s2.4xlarge.1 |
c1.8xlarge | s2.8xlarge.1 |
c2.medium | s2.medium.2 |
c2.large | s2.large.2 |
c2.xlarge | s2.xlarge.2 |
c2.2xlarge | s2.2xlarge.2 |
c2.4xlarge | s2.4xlarge.2 |
c2.8xlarge | s2.8xlarge.2 |