Re: download.ceph.com repository changes

[Janne Johansson <icepic.dz@xxxxxxxxx>]

Den tis 24 sep. 2019 kl 23:35 skrev David Turner <drakonstein@xxxxxxxxx>:

At work I haven't had a problem with which version of Ceph is being installed because we always have local mirrors of the repo that we only update with the upstream repos when we're ready to test a new version in our QA environments long before we promote the version for production use.

Problem releases have become more problematic than needed because the packages were left the default packages after a bug was known because there was no way to remove them from the repo. People continue to see the upgrade and grabbing it not realizing it's a busted release. I've only seen that happen on the ML here, but I personally will not touch a new release for at least 2 weeks after it's been released even in my testing clusters.

So this solution (having a mirror of your own) then becomes "when should I run mirror sync" instead of "when should I make an install that pulls whatever is deemed current in the repo" which might help you but still would be prone to falling into the same trap, "bad" pgks gets listed as the latest and hence get installed, regardless of if bad means "has bugs" or just "installed before announcement is out or before announcement+2 weeks". The window gets smaller but not zero. 8-/

--

May the most significant bit of your life be positive.

_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx