[03:45:43] inflatador: what is surprising with https://ewr1.vultrobjects.com/fun/IMG_3070.jpg is the video terminal tech is from the 1970's but that VT 510 which is before personal computers, but it has an "Energy Star" logo which correspond to the eve of the public internet [03:46:42] I guess DEC was still trying to stay in the race against PC and Bill Gates ;) [07:06:18] Hi. I have a question on Cirrus search queries customisation. Is it the right place ? [07:09:00] Anyway, I shoot: [07:09:00] Mediawiki 1.38.2 and CirrusSearch generate Elastic queries using "query_string". How do I make Cirrus use "match_phrase_prefix" instead ? [07:09:01] This will allow me to find page using partial keywords: Example "Cirr" will return pages with "Cirrus" inside. [07:09:01] Any ideas ? Thanks. [08:01:59] Guest92: you might have to wait until the US is up to get an answer. But ebernhardson can probably help once he is around. [13:05:29] Greetings [13:07:46] hashar indeed I think it dates from '96 or so. Probably was a point of sale terminal for an auto shop or something in its past life ;) [14:14:34] inflatador: greetings, it definitely had a use at some point. Do you have any specific purpose for it nowadays? [14:15:15] Just for fun. I've got it hooked up with a USB to serial adapter. Still screaming at 9600 baud ;) [15:02:42] \o [15:14:03] ansible learning circle starting in a few minutes: https://meet.google.com/eki-rafx-cxi [15:59:41] ryankemper, ejoseph ^ [16:59:36] thanks everyone for joining (and thanks gehel for the great questions)!\ [17:08:51] Always a pleasure! [17:09:28] My usual question that I forgot: what are the 3 things you hate about ansible? [17:21:10] 3 things I hate about ansible? #1 is the way they changed the loop keywords along with confusing justifications and docs: https://docs.ansible.com/ansible/latest/user_guide/playbooks_loops.html#comparing-loop-and-with [17:24:15] #2 is because it's an unholy combination of jinja, python and yaml there are sometimes multiple ways to access/express the data, which can be confusing [17:28:02] #3 isn't really ansible's fault, but it's often used in places that it shouldn't be. For example, terraform does a much better job of provisioning infra [17:31:00] On the positive side, it's much easier for me as a non-developer to trust/adapt/use a playbook that has been used 1000s of times, vs a python script that 5 people have ever used (such as https://galaxy.ansible.com/geerlingguy/elasticsearch ) [17:51:17] workout/lunch, back in ~90m [18:51:31] back [19:34:40] quick break, back in ~15 [19:55:12] back [20:23:57] heads up ryankemper , ebernhardson 's PRs woke me from my Friday stupor, about to merge https://gerrit.wikimedia.org/r/c/operations/puppet/+/824568 and we should be able to attempt a beta cluster and/or relforge update shortly [20:27:34] cool! [20:33:39] sweet [20:33:49] I thought so too...but it's still blowing up ;( . time to dive back into the world of debian pkgs ;( [20:34:03] oops, may have exceeded my frowny emoji quota [20:34:11] can't say I'm too surprised haha [20:34:27] stepping out to go for a run, feel free to leave a phab comment (or w/e) with any error msgs and I can take a look later [20:35:11] sounds good. That'll teach me to get too cute on a Friday [20:51:06] OK, I guess some of my earlier PR didn't get merged, re-added it in https://gerrit.wikimedia.org/r/c/operations/puppet/+/824791 , take a look when you get back if you have time [21:00:11] inflatador: is the `component/elastic710` necessary? can't hurt to try, I'm just still a little confused on the thirdparty vs component thing [21:02:08] incidentally looks like I stuck that `thirdparty/elasticsearch-curator5` under `buster` instead of `bullseye` by mistake in https://gerrit.wikimedia.org/r/c/operations/puppet/+/824568/2/modules/aptrepo/files/distributions-wikimedia [21:02:19] iirc the idea was supposed to be that thirdparty are packages directly imported from elsewhere, and component are for packages we built internally. [21:02:33] ryankemper I'm confused too...but I got it to work last night that way, ref last comment here https://phabricator.wikimedia.org/P32542 [21:03:14] ebernhardson: ack, thanks [21:03:16] ebernhardson thanks, g-ehel was wondering if both were necessary. We ended up jamming all the packages together in the thirdparty component [21:03:37] inflatador: if it worked with ` deb http://apt.wikimedia.org/wikimedia bullseye-wikimedia component/elastic68 thirdparty/elastic710` would it also work with just `deb http://apt.wikimedia.org/wikimedia bullseye-wikimedia thirdparty/elastic710`? [21:03:57] ryankemper worth a shot, let me check [21:04:01] i could always be remembering incorrectly :P [21:05:32] ebernhardson: at a minimum that sounds plausible to me as far as what those terms are supposed to represent :P [21:07:49] ryankemper I tried your line above on relforge1004 and it did indeed work, although there are still errors with the curator repo [21:08:58] inflatador: ack, for curator I think we just need this patch https://gerrit.wikimedia.org/r/c/operations/puppet/+/824791/1/modules/aptrepo/files/distributions-wikimedia except we can presumably drop the `component/elastic710` addition [21:09:20] so it's just adding `thirdparty/elasticsearch-curator5` under bullseye and `elasticsearch-curator-5` under bullseye updates [21:10:42] inflatador: actually now that I think of it I wonder if the stuff under `update` should read `thirdparty/elastic710` and `thirdparty/elasticsearch-curator5` instead of just `elastic710` and `elasticsearch-curator5`; it feels like not including the preceding `thirdparty/` implies that it's a component [21:11:54] actually ignore that last line because I see for example a `thirdparty/routinator` whose update line just says `routinator` so we can prob just not worry about that for now [21:12:59] ahh, routinator. i guess we aren't the only ones with rediculous names :) [21:23:32] school run, back in a bit [22:14:15] have a good weekend, all!