Notes from yesterday's meeting (#9)
# Snapshot meeting #9
Date: 2024-10-21T17:00:00Z
Present: h01ger, ln5, weasel
## Summary
To make sure that we won't fail any imports if the new primary (-mlm-01)
falls over and stays down, we will set up another machine as a snapshot
mirror. This machine will have the same specs as -mlm-01.
Backlogged: Test suite (ln5); Import of historical -ports packages (axhn).
Next meeting at 2024-11-18 17:00 UTC
https://volatile.noreply.org/2024-10-21-TigSgWK9Zpg/995E471E-927A-4408-8231-B71963EF8F04.ics
## Full log
<ln5> #startmeeting snapshot #9 [19:01]
<ln5> hmm
<ln5> who can summon the bot?
<h01ger> i tried. but thats not a real realtime request [19:02]
<ln5> hmm, i should've checked yesterday
<ln5> i'm learning
<h01ger> [11:35] <-- | MeetBot [~meetbot@meetbot.bot.oftc.net] has
quit (Ping timeout: 480 seconds) [19:03]
<h01ger> on the 17th
<ln5> ok
<h01ger> so we are just unlucky :)
<ln5> let's wait a minute or two and then go ahead
<ln5> perhaps one can retrofeed the log to meetbot. or not. [19:04]
<ln5> ooook, who's here for a meeting? [19:05]
* h01ger [19:06]
<ln5> great! here's a proposed agenda: status, old action items, service
contingency, aob, next meeting
<ln5> weasel: we're getting started
<ln5> #topic status updates [19:07]
<ln5> 1. snapshot is currently using 173TiB for storing 844k srcpkgs and 5.74M
binpkgs
<ln5> 2. test/dev environment is pretty functional, with db and web running in
separate containers with systemd and snapshot commands in short-lived
containers
<ln5> see https://salsa.debian.org/linus/snapshot/-/commits/devdeploy if you
want to discuss it before it becoming an MR
* h01ger has another topic for the agenda: snapshot news item
followups. though this could also be discussed async after the meeting with
joostvb [19:08]
<ln5> do we want to use containers for -mlm-01 and lw07 (the web part) too?
<ln5> h01ger: ack
* h01ger is very happy the news is on snapshot.d.o now
<ln5> 3. for a snapshot testsuite, i think that minitest could be the right
thing for unit testing
<ln5> and i wonder if we should use tox and build on existing tests in
web/app/tests for functional testing of snapshot the program (importing,
indexing and mirroring) [19:09]
<ln5> my plan for snapshot-the-program is to follow weasels advice and rewrite
it in python so tox might be a good fit for that reason too
<ln5> 4. front page has been updated with a news entry and a new sponsor
[19:10]
<ln5> h01ger: will you be moving micronews and -devel posting forward?
<h01ger> ln5: yes [19:11]
<ln5> thank you
<ln5> #action h01ger move micronews and -devel posting forward
<h01ger> ln5: my pleasure!
<ln5> anything else about updates before we move on to the next topic?
<h01ger> also, thanks to the publicity team!
<h01ger> not from me\ [19:12]
<ln5> #topic action items carry over
<ln5> 1. -ports import? (axhn)
<ln5> anything else on the backlog that we haven't mentioned in updates?
[19:13]
<ln5> ok, moving on [19:14]
<ln5> #topic service contingency
<ln5> if -mlm-01 burns to the ground at this moment, we have copies of the
farm and the db but nowhere to run imports
<weasel> (re)
<ln5> great! i'll let you do catch-up before moving on
<weasel> caught up (ish) [19:15]
<ln5> ack
<ln5> i suggest we do a copy-paste on -mlm-01 and call it a day, rather than
inventing another layer (of importers)
<ln5> at least for now
<ln5> comments, suggestions, other?
<weasel> what do you mean with "do a copy-paste on -mlm-01"? [19:16]
<ln5> buy another server, same spec. let it do what -mlm-01 does but alone.
<weasel> right
<weasel> sounds sane [19:17]
<ln5> it's a bit wasteful but at least it shouldn't be wasteful on our hours
<ln5> good, i'll wait a week and then get that going [19:18]
<weasel> where would we put it?
<ln5> same hoster, other DC
<weasel> and how would you run it? just as an independent instance, or as a
mirror off the primary? [19:19]
<ln5> was thinking independent
<weasel> hm
<weasel> means they will have different databases (and import timestamps and
stuff)
<ln5> but if it can take load off lw07 by being a mirror, we can do that
<weasel> as a mirror off the primary, we could just add it to the rotation
<ln5> hmm, true
<ln5> and it'd be easy to promote the db to be primary if -01 burnds [19:20]
<weasel> yes
<ln5> ok makes sense. same spec is nice bc less job with procurement and daily
maintenance. [19:21]
<weasel> yup
<ln5> ok, anything else on this topic?
<weasel> not from me
<ln5> #topic any other business
<ln5> h01ger: do you want to talk about news?
<weasel> thanks a lot for doing all that work!
<ln5> a pleasure!
<h01ger> ln5: i've not much to add than what we said before [19:22]
<ln5> ack
<ln5> any other business?
<weasel> reverse dns is fixed, as noted
<ln5> nice, thank you
<ln5> (i learned something about DNS today. again.) [19:23]
<weasel> next meeting?
<ln5> #topic closing
<ln5> next meeting 2024-11-18?
<weasel> ok
<ln5> 1700Z? [19:24]
<ln5> (ie back to 1800 european time)
<ln5> or did you enjoy 1900 local time today?
<weasel> 1800 works
<weasel>
https://volatile.noreply.org/2024-10-21-TigSgWK9Zpg/995E471E-927A-4408-8231-B71963EF8F04.ics
<ln5> 1800 CET you mean? [19:25]
<weasel> yes
<weasel> so 17x
<weasel> 17z
<ln5> #agreed meeting 2024-11-18 17:00 UTC
<ln5> #endmeeting
Reply to: