[13:58:20] !log tools rebooting tools-k8s-worker-nfs-2 [13:58:22] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [14:01:18] andrewbogott: oh, that one was getting better by itself I think [14:01:41] hmm, it's kinda flapping [14:01:41] oh? I didn't know they ever got better :) [14:02:44] https://usercontent.irccloud-cdn.com/file/4mJPl9EV/image.png [14:03:14] that looks like just load, not really stuck (not stable/monotonous increase) [14:03:24] ok to restart though, should be no problem [14:04:06] ok! [16:28:42] Can I retrieve data from Toolforge using modules in wikitext? [16:28:54] nope [16:29:39] Arbitrary URL access from Lua in Scribunto would be fun and also horrible. [16:30:41] ok, shall I create a request for that? I have a script (on Toolforge) from where we can use the data to customize the content of a page on trwiki [16:32:06] IMHO the chances of the request being fulfilled are basically zero [16:32:33] what you can do instead is make the Toolforge tool regularly update an on-wiki page with the needed information [16:32:42] and load it from there in the module [16:33:34] It's functionally the same idea as https://www.mediawiki.org/wiki/Manual:$wgEnableScaryTranscluding [16:41:24] Hi y'all, I was reading through the wikitech openstack api docs and found the recommendation to create what amounts to service accounts for credentials that need to live on server. Are there any conventions I should be following in the creation of such an account? [16:44:27] The particulars for this case are that we're moving some data from a cinder volume to a swift object store [16:44:27] https://wikitech.wikimedia.org/wiki/Help:Object_storage_user_guide#Swift_API [16:44:27] in the wikilink project [16:44:27] https://openstack-browser.toolforge.org/project/wikilink [17:06:24] JSherman: https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/Service_accounts is maybe the only docs we have written on the topic? The basic idea is just to separate the credentials you personally use to do things as a Developer account from the things that your service account will do so that if the service account's credentials are compromised somehow that can be dealt with without worrying about your personal Developer account. [17:12:53] bd808: thanks! I'll update the api doc pages to link to that. [17:14:12] oh, yeah, I see that's more backend. I assume that for my use, I'd just be creating a accounts through IDM. [17:15:38] the existing api docs definitely gave me the right understanding, I just wanted to make sure there weren't any undocumented expectations around this. Thanks for the response! [17:16:10] JSherman: yeah, the checklist is in the Setup section: make a new Developer account, decide if it needs to be a project admin or just a member, add it to the project. The bit about keystone.conf is for password auth from inside the cluster and that takes a Cloud VPS admin's help. [17:20:22] the keystone.conf bit predates application credentials I think [17:21:36] yeah