I hope that you are using a tool like foreman or spacewalk to deploy your dev & production environments as they allow you to "freeze" your repo content. Then you deploy all your servers with the content of these repositories (you may even use lifecycles to ease dev -> test -> prod) therefore they are all the same regardless when you deploy them. This works for CentOS stream as well. Without using such tools, even with the "old" CentOS, a server deployed at the beginning of the month would be different from one deployed a few weeks later as s-stream fixes were "regularly" shipped. On Mon, Mar 8, 2021 at 11:31 AM Marc <Marc@xxxxxxxxxxxxxxxxx> wrote: > > > This is fundamentally not true. Centos stream uses the "rolling > > release" > > > model, which means that it is not versioned (there will be no CentOS > > stream > > > 8,9,10,etc). > > > > Please read this instead of spreading such non sense: > > > > https://www.linkedin.com/pulse/why-you-should-have-already-been-centos- > > stream-back-2019-smith/?trackingId=dPaTlPfqLABwcKbgGYV%2FuA%3D%3D > > > > The reason why I am using centos7 is that I know that there is a el7 and > they are identical. So if I have some sort of issue, I have the option to > decide to get a license and paid support. > > If centos stream != el8 this means this option is gone, it is that simple > to me. > > And as Matthew wrote "Starting of Ceph 4, RH does only support RHEL 7.x & > 8.1.", and since Mark is only using "CentOS 8 stream for our upstream > performance testing clusters", and not production there does not seem to be > a valid argument for using stream. I do not really get even why you would > like to have different os in your testing and production environment. If > you look at this 'bug of the year' case, you would never discover this in > your testing environment, and would be hit with it on your production. > And if such minor lz patch can take your whole cluster down, I cannot > imagine what can all happen if you are getting more frequent > uncontrolled(?), not verified(?) updates. > > > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |