On 3/19/24 15:38, Pete Zaitcev wrote:
On Sun, 11 Feb 2024 21:07:42 +0100 Thomas Goirand zigo@debian.org wrote:
So I am wondering:
- is it still the case, that I shouldn't use oslo.config / oslo.log when
adding a patch in Swift?
- can we revisit this, and convert swift to oslo.config generated config
files, and PBR shell-script entry points instead of binary simply dropped into the toplevel bin folder?
I think Swift being different here is a technical baggage at this point. Switching over will please some, but upset the constituency of heavy users of Swift. We can try to stay compatible, of course.
At which point are we considered a "swift heavy user"? Is 6500+ HDD and 101 PB in production considered "heavy"? If such, then I'm part of this group of user, and I wont be upset... :)
I'm of the opinion that it'd be nice if we could relax the current policy, and make swift at least start logging like the other projects
BTW, I'll take a look at that drive checker review.
Thanks, though at this time, we want to rewrite it so that it uses the /etc/rsyncd.d folder, to do overrides rather than rewriting all the file. We're currently busy with production, so it will take a bit of time to get there, plus we need the puppetlabs-rsync to accept our patch to handle the &include in rsyncd.conf (that it currently doesn't support). So you may want to hold on reviewing that patch until we're fully done.
Cheers,
Thomas Goirand (zigo)