Ceph Ceph Month 2021, 1 Jun 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Ceph Month 2021: Call for Participation: Ceph Stable Releases Team

Description

By Loïc Dachary

Slides: https://www.slideshare.net/Inktank_Ceph/call-for-participation-ceph-stable-release-team
Ceph Month 2021 schedule: https://pad.ceph.com/p/ceph-month-june-2021

A

um So my name is louis desjardins and I participate in the self release, theft, staple release team, and I hope that this five minutes will inspire other people to do the same.

A

um Oops though pacific is currently latest staff stable release and when people upgrade to a pacific point release, they expect to get bug, fixes and security fixes that were backported while the development continues.

A

This is called backporting because, as code changes, applying a fix on an older version may fail, because the code changed and then, if, when that happens, you have to port the fix allowing it to go back in time in a minor of speaking.

A

uh In truth, this is no different from what happens with most software. You run on your machine, except you trust, ceph, with your data, and this is really what sets apart the ceph release process, because for every bug fix that gets backported to pacific.

A

The following must be done. First, in addition to the unit tests that only take one hour, a test lab, including hundreds of machine, is used to run actual theft clusters and verify. There is no regression because of the bug fix. That is supposed to fix it back, but may also inadvertently do something that is not desirable.

A

Second, at any given point in time, there are two stable releases, so currently it's octopus and pacific and tests must also be run to ensure that an octopus cluster can be upgraded to a pacific cluster, so that again, this backboard does not prevent that from happening, which would be a catastrophe.

A

um This may seem like a lot, but if you're willing to help there is an onboarding process that is much easier.

A

That is a very lively project and there always are dozens of bug fixes uh lined up for backporting.

A

So you can try to apply the patch that interests you more and to for insta, for example uh to octopus, and from that you create a pro request. You wait for the unit tests to pass and they are triggered automatically you.

A

You don't have anything to do and then, if that works, if it's green, you can move on to the next back port and that's actually what corey did he joined the team a few weeks ago and, as you can see on the slide, uh he was able to uh to get a few quite a few backboards right.

A

But what you can also see is that one of them has a red cross, which means the tests are failed, and this is where the real work begins. You have to figure out why it failed and fix it.

A

But when that happens, the first time you you're, not alone, you can come and there is an irc channel dedicated to that which is called staff backports and uh you can discuss with other people uh but how to go about that.

A

To be clear, this process is only about what you can find on download.set.com.

A

So if you get your stable release from somewhere else, you will have to figure out how the testing is done, how the backboarding is done and how to participate if it's possible at all, I'm employed by easter eggs. So it's the logo on the left of the slide. It's a small free software uh service provider located in france, and uh it has been running clusters for for itself and its customers for over five years now, and it gets the releases from download whatsapp.com.

A

It did not join the seth foundation. They are the big names at to the right of the slide, but they decided this year that it uh it could contribute to seph by allowing me to spend just two days a month helping with the safe table release team.

A

Now you may wonder: does that make a difference? I think it does, even though it's really small compared to what other people do, but it's not a competition and for easter eggs. It's uh it's about giving back uh with the hope that others will also do the same and that it will maintain a healthy community of contributors and.

B

C

Thanks so week uh we have uh one question here: how are particular backboards prioritized as non-dev users? Sometimes bugs look very scary, but they are not backported for several months as an example of recent issues affecting devlab cluster that allows pg to activate below min size.

A

This is a very complex question. The short answer is uh there is to my knowledge uh there is not a written down strategy to prioritize uh back ports, uh so it really depends on the urgency of course, and as um so it's difficult to figure out the as a small company who depends on let's say this particular backport, and they really need it.

A

I think participating in the stable release. Team is really the best way to push forward back ports that matter to you, but now maybe uh someone else involved in the core.

B

Yeah I can yeah, I can. I can chime in a little bit uh so sometimes, as is uh pointed out, uh that's that's generally the protocol and then sometimes there are things that are not safe to backport.

B

uh Those are the times when we know that a particular fix might be fixing the problem, the current release, but back porting. It might cause more problems because of a lot of refactoring changes, a lot of invariants that change across releases in general. Those are the ones where we are more careful about and we do not rush into back porting things. There are certain things that we say. This is a term we use.

B

We allow it to bake, so we let it bake for a particular release and once we think it is safe, that is when we um backport it and certain things we say: okay, there's a this is a no-brainer, so we just backboard it immediately and there's this always this uh gray area, where we we don't want to cause more issues by backboarding, certain things. So I think the the I'm not sure like if I can look at the tracker or anything for the pg below in size activation thing um yeah.

B

If I'm understanding this correctly this, this is more more a feature that we added versus a fix uh in general. So if I can get a tracker ticket or something I can take a look at it and comment uh better.

C

C

Thank you. Thank you for the answer there and okie. Thank you for the um for the presentation.