Beta: CloudLinux introduces gradual rollout for all its production releases

Mar 11, 2020 8:22:49 PM / by Ivan Zhmud

 

rollout

Introduction

Here at CloudLinux, we are on a mission to make Linux servers stable, secure, and profitable. While releasing packages, we use a bunch of synthetic tests covered diverse cases and various configurations. And today, we introduce a beta version of a gradual rollout system to reduce all possible risks. We are planning to release it to production within the next two weeks.

What It Means To You

We will spread each update to only a limited subset of servers (1%) initially and then increase that number smoothly in two weeks. You will be able to get a safe gradual rollout update using a regular update command or get an update immediately using a special bypass repository by executing a command provided with each update.

How To Enable Gradual Rollout

To enable the gradual rollout system, you should update the following packages (you can see the packages release announcement here):

  • cloudlinux-release
  • rhn-client-tools

CloudLinux OS 6 / 6 Hybrid / 7 / 7 Hybrid upgrade command:

yum upgrade --enablerepo=cloudlinux-updates-testing -y cloudlinux-release rhn-client-tools

CloudLinux OS 8 upgrade command:

dnf upgrade --enablerepo=cloudlinux-updates-testing -y cloudlinux-release rhn-client-tools

How To Opt-Out From Gradual Rollout

To opt-out from the CloudLinux gradual rollout, run the following command:

yum-config-manager --disable cloudlinux-rollout*

What To Expect From Gradual Rollout And How To Get Updates Immediately?

All updates will be available for customers automatically with increasing the number of servers within two weeks. But if you want to get the latest update right after it is available in our production repository (bypassing the gradual rollout by temporarily enable a special repository), you can use the following command:

yum install --enablerepo=cloudlinux-rollout-N-bypass packageName

Where N is a repository number. There are six slots of three repositories defined in the same manner.
We will provide a required bypass command with a specific repository number for each release.

We strongly recommend you not to enable those bypass repositories by default. Use them with caution and only if you really need to install the latest packages right now.

Repositories Description

  • The cloudlinux-rollout-N is a binary packages repository managed by the gradual rollout system. The system automatically decides which server will receive updates and which server will see an empty repository instead. This repository is enabled by default so a server will receive gradual updates transparently when his turn comes.
  • The cloudlinux-rollout-N-source is a source packages repository managed by the gradual rollout system as well.
  • The cloudlinux-rollout-N-bypass is a bypass repository which contains binary packages and makes them available for any registered CloudLinux OS powered server.

Registration And SSL Certificates

Access to the gradual rollout repositories is controlled by an SSL certificate. A machine without a valid certificate will always see an empty dummy repository just to make yum/dnf work properly. A certificate is generated automatically on the CLN side and saved on a server with the help of the rhn-client-tools package during registration or check-in process.

Stay in Touch

Don’t hesitate to give us feedback or share your ideas and feature requests via feedback@cloudlinux.com.

If you encounter any problems, please send a request to our support team via https://cloudlinux.zendesk.com/.

Topics: beta, News, rhn-client-tools, Technical Blog, Gradual rollout

Ivan Zhmud

Written by Ivan Zhmud

Ivan is a Project Manager at CloudLinux and is leading the CloudLinux OS product team.

    Subscribe to Email Updates

    Recent Posts