Bring Your Own Licence at no additional charge

Bring Your Own Licence at no additional charge

The latest Open Telekom Cloud Release features a new service called "Bring your own license" for public and private images.

Bring your own license (BYOL) allows you to use your existing OS license so there is no need to apply for additional OS licenses on the Open Telekom Cloud. What’s more, you can continue using your existing licenses at no additional charge. However, you should adhere to the licensing conditions of the OS vendors and you need to configure, update and secure channels yourself.

Bring your own license (BYOL) allows you to use your existing OS license

There is a BYOL check-box for the relevant public or private images in the Open Telekom Cloud dashboard. This option can also be activated via an API by using "--meta BYOL=true".

The default is set to use the license from Open Telekom Cloud (T-Systems).

If BYOL is chosen, no update/repository servers will be configured in your virtual machine (VM) but publicly available repositories could be used. But if you choose "Use license from T-Systems", the update/repository servers provided by Open Telekom Cloud will be configured in the repo files via the cloud-init vendordata feature.

Vendordata follows the same rules as user-data, with the following caveats:

Users have ultimate control over vendordata. They can disable its execution or disable handling of specific parts of a multipart input.

By default, it only runs on first boot.

User-supplied cloud-config is merged via the vendordata cloud-config.

Your current virtual machines running on Open Telekom Cloud will remain unaffected. For newly created VMs, the vendordata script will be executed and update/repository servers config will be written.

Controlling vendordata

Vendordata can be disabled via the cloud-init userdata Interface. Please note: no Open Telekom Cloud update/repository servers will be configured.

#cloud-config
vendor_data:
enabled: False

Userdata is merged via vendordata

The vendordata script is executed via the cloud-init bootcmd command. If the bootcmd command is also used in the cloud-init userdata interface, then the userdata bootcmd command will overwrite the vendordata bootcmd command, and the vendordata script will not be executed. As a result, no Open Telekom Cloud update/repository servers will be configured. To avoid this situation, use the runcmd module in the userdata interface.

Daniela Ebert spent many years as an AIX Engineer in the Solution Delivery department at T-Systems. Leading up to the launch of Open Telekom Could at CeBIT 2016, she developed the technical implementation of the platform. At the moment her work is concentrated on technical development, the evaluation of technical features, and architecture issues.

* Voucher can be redeemed until June 30, 2020. Please contact us when using the voucher for booking. The discount is only valid for customers with a billing address in Germany and expires two months after conclusion of the contract. The credit is deducted according to the valid list prices as per the service description. Payment of the credit in cash is excluded.

Note: Your browser does not support modern web technologies to a sufficient extent. Please use a modern standard browser (Internet Explorer version 9 or higher, Mozilla Firefox, Google Chrome). Many Thanks.