| 26 Apr 2024 |
|  @federicodschonborn:matrix.org changed their profile picture. | 14:48:22 |
|  @patka_123:matrix.org left the room. | 19:33:03 |
| 28 Apr 2024 |
| @federicodschonborn:matrix.org changed their profile picture. | 22:47:07 |
| @federicodschonborn:matrix.org left the room. | 23:13:56 |
| 29 Apr 2024 |
|  SomeoneSerge (back on matrix) changed their display name from SomeoneSerge (UTC+1) to SomeoneSerge (is taking time off and doesn't want to hear about it). | 11:43:00 |
|  NixOS Moderation Botchanged room power levels. | 15:28:34 |
| 30 Apr 2024 |
|  ondt joined the room. | 22:23:18 |
| 1 May 2024 |
| NixOS Moderation Botchanged room power levels. | 15:06:08 |
| 4 May 2024 |
| SomeoneSerge (back on matrix) changed their display name from SomeoneSerge (is taking time off and doesn't want to hear about it) to SomeoneSerge (Way down Hadestown). | 21:03:31 |
| 9 May 2024 |
| SomeoneSerge (back on matrix) changed their display name from SomeoneSerge (Way down Hadestown) to SomeoneSerge (UTC+3). | 17:11:18 |
| 20 May 2024 |
|  mei 🌒& changed their display name from ckie (they/them) to mei 🌒&. | 00:07:53 |
| 22 May 2024 |
| NixOS Moderation Botchanged room power levels. | 15:25:51 |
| NixOS Moderation Botchanged room power levels. | 15:28:05 |
| 29 May 2024 |
|  raitobezarius changed their display name from raitobezarius to raitobezarius (DECT: 7248). | 17:10:59 |
| 2 Jun 2024 |
|  @aloisw:kde.org set a profile picture. | 18:01:43 |
| @aloisw:kde.org changed their profile picture. | 18:23:53 |
| 4 Jun 2024 |
| raitobezarius changed their display name from raitobezarius (DECT: 7248) to raitobezarius. | 11:16:22 |
| 6 Jun 2024 |
|  tomberek joined the room. | 20:20:13 |
| tomberek | What was the latest analysis/decision on moving old+infrequent access to Glacier? | 20:31:02 |
 edef | everyone is fairly aligned on that, but i have to ship some pieces to handle aggregating small objects | 20:36:37 |
|  lassulus joined the room. | 21:07:17 |
| 8 Jun 2024 |
 Jonas Chevalier | In reply to @edef1c:matrix.org
everyone is fairly aligned on that, but i have to ship some pieces to handle aggregating small objects it might be easier to leave those where they are, and only Glacierize(?) large-enough files. it should get us 80% there and be pretty safe since we're not adding additional logic. | 06:13:49 |
| Jonas Chevalier | I guess we're going to need a separate service for the narinfos to answer queries properly. | 06:14:37 |
| edef | yeah, but that part is easy enough | 16:02:09 |
| 12 Jun 2024 |
| tomberek | edef: do you need anything to start "Glacierize"? | 21:25:01 |
 flokli | A big snow cannon | 22:39:36 |
| 14 Jun 2024 |
 tpw_rules | what does that mean for users? | 20:36:05 |
| tomberek | Proposal: start by copying NARs created prior to 2024. Keep a record of the copy. Meanwhile, we can generate some proposed sets to delete:
1. Unreachable NARs.
2. Infrequently accessed
3. Oldest
This would mean that if you would want to build something in one of those sets, you'd have to rebuild. We can try to make this a rarer occurrence, but I will happen. In that case we would need a procedure to either allow you to access old data at your own cost, or to restore it to the mainline cache.
| 23:29:24 |
| 16 Jun 2024 |
| tpw_rules | so NARs will not be automatically un-glacierized? by delete here do you mean from the main cache or from glacier? doesn't glacierization increase egress costs? | 17:08:58 |
| tomberek | No, for simplicity, and at least for now, the idea is to start copying things over. That will be desirable almost no matter what. An automatic retrieval could be nice; perhaps make that "requestor pays". And we can restore some set of objects if we find the popular and useful enough to do so. For deletion, I meant deletion from S3. | 17:38:06 |
