Hi all, notes from this week's CLT meeting. David is trying to get CentOS Stream container builds going for our future use and hitting issues. We discussed options (Dan says CERN has been building on them, so it should be feasible) and possible fallback plans if Stream doesn't work out as a stable base for us. Also went over some test results for trying to speed up lab build times. There's a proprietary tool that spreads out builds across systems, but it makes dwz (used to extract debug symbols and shrink packages) SIGNIFICANTLY slower, and that dominates our current builds. Asked to test out distcc since that's free. Also suggested we might be okay not stripping out debug symbols for lab builds, since we install the debug packages anyway, but didn't go further down that thought. We're going to get some test time on a very large system. Currently focused on the orchestration layer, which should let the cephadm upstream see scaling issues in person and identity things to work on. A discussion on why some users were asking for extreme LTS releases, and what we can do about that. Suggested that the biggest issues stem from upgrade orchestration bugs rather than inherent stable releases, and we have plans to improve the testing around that significantly. It also came up that many of our largest users run test clusters and are happy to run stable branch release candidates on them, which would let us identify issues missed in our testing before the wider user community sees things. We may start doing release candidates and a delay to make that possible. There's absolutely no appetite for the upstream doing more LTS-style releases than we currently do, though — stable branches already take a lot of work, and longer-term support would require an infeasible amount of upgrade compatibility and testing. Will discuss RCs in next week's Dev/User meeting: https://pad.ceph.com/p/ceph-user-dev-monthly-minutes Briefly asked about the recent BlueStore omap upgrade bug. There've been informal post-mortems and we expect to hear more about this. _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
