Redhat stopped CentOS 7 updates, Do we need to upgrade to CentOS 8 Stream version? - centos

We are using 'CentOS Linux release 7.9.2009 (Core)' for production servers. But it seems that Redhat stopped Centos 7 full updates from November 2020 onwards. We are in confusion do we need to upgrade to CentOS 8 or Centos Stream?, As per Centos / wiki official docs. They were providing full/maintenance support for Centos 8 Stream still 2024. Is this Centos 8 Steam version is stable or can we continue with Centos 7 maintenance version?
Reference URLS :
https://wiki.centos.org/About/Product,
https://en.wikipedia.org/wiki/CentOS#CentOS_version_7

In my career i have seen prod servers even running on Solaris 11 which was released 10 years ago and has no support now.
This usually depends, whether the underlying dependencies required by your application change/requires to be updated frequently or not,
If yes - Go with supported version.( which will also run out of support :D )
If No - Stay where you are. ( Best choice Mostly )

Related

Openstack Kolla-ansible migration route from CentOS Linux 8 to CentOS Stream8

I am currently using Kolla-ansible for deploying my OpenStack environment and I am running the Openstack Victoria version on CentOS Linux 8. Due to EOL of CentOS Linux 8 is no longer supported. I wanted to migrate now on CentOS stream8.
On the official website they have mentioned the following Note:
CentOS Linux 8 (as opposed to CentOS Stream 8) is no longer supported as a host OS. The Victoria release will in the future support both CentOS Linux 8 and CentOS Stream 8, and provide a route for migration.
My question is:
Has anyone done this migration (any worrisome issues)?
Any idea, are they going to provide a migration route soon because the above-mentioned note is there for around 3-4 months and they stopped supporting CentOS Linux 8?

Does kubespray support CentOS 8?

I have a quick question related to "Kubespray".
Does "Kubespray" support CentOS 8?
I wanted to deploy "Kubespray" on "CentOS" and I came to know that the CentOS 8 has Kernel version 4.18 and If I can use "CentOS 8" for "Kubernetes" deployment, maybe I can get rid of the "c-group" issue which we are currently facing for all the CentOS distribution which has Kernal Version less than 4.18.
Thanks in Advance.
According to the official documentation Kubesprawy provides support for CentOS/RHEL 7 only. The problem is that:
Installing Kubespray on a RHEL8 systems does not work since the
default Python version is 3.6 and thus python3-libselinux should be
installed instead of libselinux-python. Even that python2 is still
available, the libselinux-python package is not.
I hope it helps.

Windows 7 update not installing two updates for many hours

My windows 7 Update says 2 important updates are available but when i click
install updates it doesn't install the updates for many hours ! So how to fix this problem ? Should i install those two updates or just leave it as it is ?
(Note:Microsoft .NET Framework 4.5.2 for Windows 7 x64-based Systems (KB2901983) is already installed successfully and many other security updates)
2 important updates that doesn't install:
Microsoft .NET Framework 4.6.1 for Windows 7 for x64 (KB3102433)
Security Update for Windows 7 for x64-based Systems (KB3110329)
Try downloading the updates, disconnecting the PC from the internet and then running the update. See here: https://superuser.com/questions/951960/windows-7-sp1-windows-update-stuck-checking-for-updates for a more detailed guide on the problems with Windows Update

What packages need to upgrade for RHEL 6.x from RHEL 5.11

i would like to know, based on what rpm packages upgrade i can upgrade my RHEL version 5.11 to 6.x
We can't use re-installation of RHEL 6.x, so wanted an option(s) to upgrade to RHEL 6.x from 5.x by upgrading all needful packages.
By upgrading kernal or core rhel release rpm, can we upgrade to latest?
Please let me know details. Thank you.
In place upgrades between 4, 5, and 6 are not supported by RedHat and you risk impacting the support that you pay for by doing so. The only supported upgrade path is from 6 to 7. The expectation is that an upgrade path will continue in future releases.
You state that you cannot re-install but don't state why. Is it because the criticality of the system or is it because of the configuration of the application? I'm guessing the latter and that the system is not all that critical (because otherwise you wouldn't want to impact your support agreement). With that said, there is a way to upgrade and the procedure is provided by RedHat but, again, it is not supported by them.
The link is: In place upgrade

Can File Maker Server 5 Run under windows server 2008 or 2012

I am working with a client that is running Filemaker Server 5 in a workgroup environment and is now upgrading to a true client server network running either MS windows server 2008 or 2012. Will Filemaker Server 5 run in the new network environment. They do not want to upgrade Filemaker. Any help would be greatly appreciated
Have a look at this:
FileMaker Server operating system requirements - all versions
Windows 2008 does not appear on the list until FileMaker 10. Windows 2012 only supported only with FileMaker 13.
This is an official supported version chart, so you still can try and install it. I am sure, there is a compatibility mode which will let you run it. If you have any problem, you will not be able to get any support from FileMaker.
If updating FileMaker is such an issue, you might be better of running a VM on the same server with an older OS and serve it from there.
You will probably have a similar problem with clients' installs when their workstations are upgraded. FileMaker 15 is around 15 years old.
You should also consider that the filemaker 5 / 6 clients will not install on a new OSX OS Version - I'm not sure about Windows, that should be tested before moving forward if that is a requirement.
All new versions of Filemaker will convert Filemaker 5 files to a new format, however it's a big change and the scripting and layouts need to be checked after conversion. Filemaker 5 is 14+ years old and support stopped around 10 years ago which explains the compatibility issues.