[EXTERNAL] Re: New Openstack Deployment questions

Tobias Urdin tobias.urdin at binero.com
Fri Dec 11 14:58:13 UTC 2020


We are running solid on CentOS and will continue to do so.

But this just reaffirms my ideas that OpenStack should be packaged and distributed as an application by upstream

and not by downstream.

One of the best ideas so far is on Mohammed Naser's line, which is a shame that there isn't more colaboration on already, is ready-to-use container images for running OpenStack services which would make the layer beneath more "not important".

Seeing as a lot of projects already try to work on deploying OpenStack in containers but is working on their own fronts (except some Kolla <-> TripleO relationship, that I think is getting scaled down as well). StarlingX, TripleO, Kolla, OpenStack-Helm, all these container-related deployment tools but no common goal.

/end of random post, sorry.

Best regards


From: Braden, Albert <C-Albert.Braden at charter.com>
Sent: Friday, December 11, 2020 3:09:34 PM
To: openstack-discuss at lists.openstack.org
Subject: RE: [EXTERNAL] Re: New Openstack Deployment questions

Centos Stream is fine for those who were using Centos for testing or development. It's not at all suitable for production, because rolling release doesn't provide the stability that production clusters need. Switching to Centos Stream would require significant resources to be expended to setup local mirrors and then perform exhaustive testing before each upgrade. The old Centos did this work for us; Centos was built on RHEL source that had already been tested by paying customers, and bugs fixed with the urgency that paying customers require.

Adding an upstream build (Stream) to the existing downstream (Centos 8.x) was fine, but I'm disappointed by the decision to kill Centos 8. I don't want to wax eloquent about how we were betrayed; suffice it to say that even for a free operating system, suddenly changing the EOL from 2029 to 2021 is unprecedented, and places significant burdens on companies that are using Centos in production. I can understand why IBM/RH made this decision, but there's no denying that it puts production Centos users in a difficult position.

I hope that Rocky Linux [1], under Gregory Kurtzer (founder of the Centos project) will turn out to be a useful alternative.

{1} https://github.com/rocky-linux/rocky

-----Original Message-----
From: Luigi Toscano <ltoscano at redhat.com>
Sent: Thursday, December 10, 2020 3:51 PM
To: Thomas Wakefield <dwakefi2 at gmu.edu>; openstack-discuss at lists.openstack.org
Cc: Satish Patel <satish.txt at gmail.com>
Subject: [EXTERNAL] Re: New Openstack Deployment questions

CAUTION: The e-mail below is from an external source. Please exercise caution before opening attachments, clicking links, or following guidance.

On Thursday, 10 December 2020 15:27:40 CET Satish Patel wrote:
> I just built a new openstack using openstack-ansible on CentOS 8.2
> last month before news broke out. I have no choice so i am going to
> stick with CentOS.
> What is the future of RDO and EPEL repo if centOS going away. ?

Continue as before on CentOS Stream.


The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20201211/1c97a499/attachment.html>

More information about the openstack-discuss mailing list