7 posts tagged with "os"

After the acquisition of CoreOS by RedHat and the discontinuation of CoreOS support.

CoreOS Container Linux will reach its end of life on May 26, 2020 and will no longer receive updates.
(source: https://coreos.com/releases/)

We have decided together with our customer to provide an alternative to CoreOS before the 26.05.2020.

The current project name is Gardenlinux, although the name may not change until the public release.

Gardenlinux builds a full replacement for CoreOS based on Debian, without being biased by a target architecture.

Currently, the project supports the following platforms: BareMetal, AWS, GCP, Azure, VMWare, Openstack, and KVM and Docker.

Ports for AlibabaCloud are still under development.

In Produkton, Gardenlinux has already proven itself on BareMetal, KVM and AWS.

CentOS Linux 8 will reach End Of Life (EOL) on December 31st, 2021. Here’s what that means.

CentOS Linux EOL

End dates are coming for CentOS Stream 8 and CentOS Linux 7 We’ve got an important message for Developers, Administrators, and Users.

end dates

interesting insights into how dependency on external operating system libraries can affect the operation of Ceph.

https://www.youtube.com/watch?v=_4HUR00oCGo

https://codimd.web.cern.ch/p/rkNZH4JR8?print-pdf#/

For some time now there are no more official packages for Debian on the ceph.io site. The reason for this is the switch to a C++ version, which was only supported by Debian with Buster. All the more pleasing is the fact that Bernd Zeimetz has been working on the Ceph package for Debian since 28.11.2019 and is currently maintaining it for the current Nautilus versions from 14.2.4-1 for Bullseye and Buster backports.

See changelog of the project:

https://packages.debian.org/de/bullseye/ceph

https://packages.debian.org/de/buster-backports/ceph

During maintenance work, we noticed that a "ceph clock skew detected" always occurred when restarting the Ceph monitors.

What makes this interesting for the Ceph Monitor Leader is the fact that it assumes that its time is correct and that everyone else's time is wrong.

This means that the cluster remains in the "ceph clock skew detected" state with all its consequences until the time is synchronized.

All ceph monitors and osd nodes are synchronized via ntp and so the state lasts for about 20 seconds.

Possible solutions:

Synchronize the hardware clock before rebooting

hwclock --systohc

When starting the system, do not start the Ceph Monitor until the time has been synchronized.

However, you should always bear in mind the risks and side effects on rainy days.

First you need access to the boot screen.

Than reboot your server, you will see the boot loader screen, select the recovery mode.

Type e for edit and add the following option to the kernel boot options:

init=/bin/bash

Press Enter to exit the edit mode and boot into the single-user mode.

This will boot the kernel with /bin/bash instead of the standard init.