(unless that's github being weird, I did not check locally, but)
2022-05-13 13330, 2022
zas
grrrr, it seems the other nvme drive on trille exhibits same issue the one we just replaced, I guess we'll have to replace it too. That's weird, but those were likely from the same series.
2022-05-13 13356, 2022
reosarevok
Well, this time we know in advance that we need to move stuff, at least
2022-05-13 13306, 2022
zas
yup ;)
2022-05-13 13318, 2022
reosarevok
mayhem: ^ :/
2022-05-13 13333, 2022
alastairp
also, at least we have a good drive in the raid array
2022-05-13 13313, 2022
zas
I'll ask for a replacement on Tuesday 24th, at 16:00 CEST
2022-05-13 13300, 2022
yvanzo
reosarevok: Ok, the 3rd file was changed and reverted in the same PR, thus GH displaying only 2 files in the tab :D
2022-05-13 13318, 2022
bitmap
reosarevok: the script found all of them except for the missing auto-generated files
2022-05-13 13321, 2022
yvanzo
reosarevok: What time for the schema change on Monday?
2022-05-13 13334, 2022
reosarevok
yvanzo: I see :) Well, if that passes, then that looks good to me, but let bitmap take a quick look since he's here :D
2022-05-13 13348, 2022
bitmap
(I just noticed the latter after running GenerateSQLScripts.pl and having a lot of untracked files)
2022-05-13 13352, 2022
reosarevok
bitmap: neat :) Really need to document this somewhere in "how to prepare a schema change"
2022-05-13 13323, 2022
bitmap
this was a new script I added in the last schema change so my bad for not documenting it yet
afaict the prod database has all of these fks from previous upgrade scripts. (however, I think the prod db may be missing FKs for the sitemaps schema somehow...)
2022-05-13 13327, 2022
yvanzo
#2523 can be rebased so tests should pass again :)
akshaaatt: I haven't created a PR yet, it's probably best to have a separate project for the script to pull the docker info and the web page that consumes the JSON
2022-05-13 13357, 2022
akshaaatt
Interesting.
2022-05-13 13310, 2022
atj
did you create a GitHub actions workflow to publish your design guidelines site?
2022-05-13 13344, 2022
atj
just wondering if we could do something similar with this and use some test JSON data
2022-05-13 13356, 2022
akshaaatt
Yusss atj
2022-05-13 13303, 2022
akshaaatt
I can handle that
2022-05-13 13337, 2022
atj
the remaining tasks I had in my mind for the UI were: 1) convert to bootstrap 5 2) remove the sub-menu with the "last updated at" 3) add a reload button to trigger datatables to reload the JSON
2022-05-13 13350, 2022
akshaaatt
Sounds good to me atj!
2022-05-13 13354, 2022
atj
4) add some JS to check if the JSON contains an "errors" key (which would contain a list of hosts the script failed to retrieve data for) and add an info box at the top
I guess we'll have to redesign it partly, because it currently relies on a repo deployed in /opt. We only need keys & configs for the target node, and borg installed
2022-05-13 13315, 2022
atj
yes, I think a redesign will be needed to some extent, but it shouldn't be too difficult to integrate if just worry about the clients
2022-05-13 13354, 2022
atj
we're probably going to need to start using Ansible vault at some point
2022-05-13 13343, 2022
zas
yes, we'll have to manage more keys soon, for example we need them to deploy node exporter too
2022-05-13 13335, 2022
zas
btw, we'll move aretha to ansible during schema upgrade
2022-05-13 13336, 2022
atj
akshaaatt: ok, I'm thinking we create a repo for the HTML/JS that consumes the JSON, then create a test domain for it to be deployed to
yvanzo: next is what, new mb-docker image with this change?
2022-05-13 13339, 2022
bitmap
before running a full migration test, I'll do a pg_dump of the prod schema (without data) and try a local upgrade using that. sometimes it finds issues
2022-05-13 13309, 2022
reosarevok
oh, to see if it's different than a brand new standalone schema? Sure, why not
2022-05-13 13317, 2022
reosarevok
bitmap: wanna document all this as you do it? :p
2022-05-13 13349, 2022
bitmap
I'll try :)
2022-05-13 13319, 2022
yvanzo
bitmap: Can we merge schema-change-2022-q2 into master now?
2022-05-13 13332, 2022
bitmap
yes, let's
2022-05-13 13312, 2022
bitmap
(feel free if you're already on it)
2022-05-13 13355, 2022
yvanzo
ok, will do
2022-05-13 13325, 2022
akshaaatt
atj I think something including `services` or `status` or `live`
2022-05-13 13328, 2022
yvanzo
bitmap, reosarevok: done, #2524 is ready for review
2022-05-13 13315, 2022
reosarevok
yvanzo: so, to check if the strings look legit etc? :) Can do
2022-05-13 13351, 2022
akshaaatt
atj: `docker-containers` in itself sounds like a good repo name
2022-05-13 13354, 2022
yvanzo
reosarevok: To answer about musicbrainz-docker, I have to update it for mbdb schema 27 but also for sir 3.0.0, with full upgrade steps.
