[09:24:33] In the context of https://de.wikipedia.org/wiki/Wikipedia:Projekt_Pressearchiv, it would be great if we could set up a SPARQL endpoint with the project's data (uncompressed ca. 270 MB .nq file), and open it to federated queries from WDQS. Thoughts about this? Hints who have experiences? [09:35:16] !log toolsbeta carry out nfs tests on toolsbeta-test-k8s-worker-nfs-8 - T411248 [09:35:22] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [09:35:23] T411248: Plan to make clouddumps more resilient and easier to operate - https://phabricator.wikimedia.org/T411248 [10:18:20] !log tools deploy latest striker with T430120 T409341 fixes [10:18:27] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [10:18:28] T430120: [striker] Failing to create new phabricator projects - https://phabricator.wikimedia.org/T430120 [10:18:28] T409341: Striker: Always set all IO to none and hidden for internal URIs when creating Diffusion repositories - https://phabricator.wikimedia.org/T409341 [13:09:44] jneubert I am an SRE that supports WDQS. I'm far from a sparql expert but if you want to set up a simple qlever service in WMCS with Puppet and/or Docker I'm happy to help. We are currently refactoring WDQS to use qlever instead of blazegraph, ref T422522 [13:09:45] T422522: WE2.5.8 WDQS v2 technical build - https://phabricator.wikimedia.org/T422522 [13:56:07] inflatador That would be wonderful! My own experience with qlever is very limited - just set up a test instance with the debian package and our data set. Though I worked with Fuseki in the last 15 years, Qlever fits well in the wikimedia environment, so I'm happy to learn. Also very limited experience with Docker, and none with puppet. So where to [13:56:08] start best? [14:06:04] jneubert I'm not 100% sure myself. ;) Do you have an existing Wikimedia Cloud Services project? [14:09:16] If anyone has advice on where this qlever endpoint for the `Projekt_Pressearchiv` project should live let us know. Toolforge ( https://admin.toolforge.org/ )? or a WMCS project? [14:26:57] I think a Toolforge project pm20-sparql would be nice (in parallel to https://pm20-search.toolforge.org/ et al.). That could be just a reverse proxy to a service situated where it fits best into the infrastructure. [14:29:35] We have an Postgres DB at https://openstack-browser.toolforge.org/project/pm20database# for data input (so the SPARQL endpoint would be read only). [14:45:13] jneubert ACK, so I think we can build the endpoint in your existing `pm20database` openstack project. [14:52:17] I'll get a phab task started, it will be useful for me as well to learn a bit more about qlever since we're migrating to it soon [15:03:14] jneubert I created T430976 , feel free to look it over and edit/respond [15:03:15] T430976: Deploy a SPARQL instance for Projekt_Pressearchiv - https://phabricator.wikimedia.org/T430976 [15:28:24] !log gergesshamon@tools-bastion-15 tools.wikimonitor [DEPLOY] Starting deployment | ref=v1.5.7 (for fix v1.5.6) [15:28:28] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wikimonitor/SAL [15:29:39] !log gergesshamon@tools-bastion-15 tools.wikimonitor [DEPLOY] Build triggered successfully | ref=v1.5.7 (for fix v1.5.6) [15:29:39] !log gergesshamon@tools-bastion-15 tools.wikimonitor [DEPLOY] Restarting buildservice | ref=v1.5.7 (for fix v1.5.6) [15:29:40] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wikimonitor/SAL [15:29:41] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wikimonitor/SAL [15:29:51] !log gergesshamon@tools-bastion-15 tools.wikimonitor [DEPLOY] Deployment completed successfully | ref=v1.5.7 (for fix v1.5.6) [15:29:52] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wikimonitor/SAL [16:37:46] andrewbogott: If I want to be sure a particular hiera key is being used in cloud-vps, is it sufficient for me to look only in https://gerrit.wikimedia.org/r/cloud/instance-puppet? [16:39:12] 'be sure' because you want to eliminate the key or because you're trying to debug something that isn't picking it up? [16:39:55] instance-puppet will cover /most/ cases but it's always possible that something is mentioned in prod puppet as well [16:40:18] In this specific case, I'm hoping to drop some puppet code if there are no users of a particular key [16:40:37] ok [16:40:46] instance-puppet is where I would start certainly [16:41:11] Thanks. It looks clean there. [19:33:57] !log lucaswerkmeister@tools-bastion-15 tools.wd-image-positions deployed bb43718fe8 (l10n updates: kw) [19:33:59] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wd-image-positions/SAL