[08:21:47] Lofhi: that'd be one way yes. You can also use the buildservice to build your application (https://wikitech.wikimedia.org/wiki/Help:Toolforge/Build_Service), that uses upstream https://github.com/heroku/heroku-buildpack-nodejs [10:28:10] dcaro: do you think it's worth linking/mentioning the build service in that node.js help page? [10:29:38] most of what's there is heroku specific though (any `heroku ...` command, etc.) so maybe not that useful [10:29:57] would be nicer to create a small sample app maybe [10:30:37] like this one that I added this morning: sample-static-buildpack-app.toolforge.org/ [10:38:27] what I was thinking was adding a link from https://wikitech.wikimedia.org/wiki/Help:Toolforge/Node.js to https://wikitech.wikimedia.org/wiki/Help:Toolforge/Build_Service, not to the heroku page [10:38:43] but maybe we should first add a node.js buildpack tutorial [10:39:36] I can create the tutorial, should be fun :D do we have a task already? [10:40:59] I think that for nodejs there might not be [10:43:48] there's T188397 that I guess we might consider resolved since we have https://wikitech.wikimedia.org/wiki/Help:Toolforge/Node.js [10:43:49] T188397: Document node.js in toolforge - https://phabricator.wikimedia.org/T188397 [10:44:35] yep, that's not buildservice related xd [10:45:18] I'll create a new task for a sample buildpack app [10:48:32] T353313 [10:48:33] T353313: [tbs] Create a tutorial on how to deploy a Node.js app using Build Service - https://phabricator.wikimedia.org/T353313 [10:50:07] 👍 [11:43:57] !log tools.bub disabled tool T319610 [11:44:01] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.bub/SAL [11:44:01] T319610: Migrate bub from Toolforge GridEngine to Toolforge Kubernetes - https://phabricator.wikimedia.org/T319610 [13:54:24] !log tools deploy toolforge-builds-cli version 0.0.9 (with envvars support) [13:54:29] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [17:11:53] something seems up with the grid: T353352 [17:11:54] T353352: read error closing "tools-sgegrid-master.tools.eqiad1.wikimedia.cloud/qmaster/1" - https://phabricator.wikimedia.org/T353352 [17:13:04] anyone familiar with celery running with redis broker willing to lend a hand to video2commons debugging? [17:14:59] JJMC89: yeah it seems to have been upset by me moving some capacity from the grid to k8s. i'm looking. [17:56:59] taavi: i think you might have answered this already at the devex offsite, but can one create WMCS DNS record sets via opentofu at the moment? [17:59:26] dduvall: you can. the main thing to be aware is that designate wants you to use the fully qualified domain name as the name and not just the subdomain [18:07:04] oh nice, ok. ty! [18:38:39] !log tools rebooting tools-nfs-2 server to resolve weird file locking issues [21:01:22] Hi, anyone around for quick tips about migrating to Kubernetes? [21:03:43] !help Hi, anyone around for quick tips about migrating to Kubernetes? [21:03:44] don't ask to ask [21:03:44] If you don't get a response in 15-30 minutes, please create a phabricator task -- https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=wmcs-kanban [21:04:01] !ask | jem [21:04:01] jem: Hi, how can we help you? Just ask your question. [21:04:02] Ok, sorry, taavi [21:04:21] It's just that I don't know how to begin :) [21:04:40] Ok, currently webservice status tells me that the webservice is not running, but it is [21:05:23] I just stopped gridengine and changed to: webservice --backend=kubernetes php7.4 start [21:05:40] btw, the tool is jembot [21:06:14] So thinks are working but I don't know if I really changed or not [21:06:48] https://grid-deprecation.toolforge.org/ says currently running but I don't know if it's immediate [21:07:05] it is not immediate, no [21:07:43] Ok [21:08:04] although `webservice` is,s os it saying it's not running but https://jembot.toolforge.org/ loading is a problem [21:08:47] I can see no grid jobs and I can see a pod. I'm not sure what's up with `webservice status` [21:08:55] ah, you have a `service.template` that defaults to --backend=gridengine. you might want to update that [21:09:07] First it said that "Backend 'kubernetes' from /data/project/jembot/service.manifest does not match 'gridengine'" [21:09:13] Ah [21:09:55] With type: php7.4 ? [21:10:13] go spot taavi. jem: put the kubernetes & php7.4 values you used in the cli into that template to make your future easier. :) [21:10:34] jem: yes. "type: php7.4" [21:10:49] Ok [21:11:14] So now status is Your webservice of type php7.4 is running on backend kubernetes [21:11:20] checking service.template is probably something worth mentioning on the News page if it's not there already [21:12:34] I think I didn't read about it, but maybe I didn't pay much attention [21:14:11] I don't see anything in https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation#Solutions_to_common_problems which is where I would expect it. [21:14:37] Ok, I think /home is no longer accesible, am I right? [21:15:01] That stopped me in my last try some months ago [21:15:10] jem: accessible from where? what are you hoping to do? [21:16:03] Read a file from a php file which is symbolic-linked to /home/jem [21:16:23] It's copied from outside [21:17:01] Probably just to make things easier some years ago [21:17:10] So /home/jem is your user's $HOME and not the tool's $HOME. I do not think that we mount user $HOME directories into the Kubernetes pods. But we do mount tool's $HOME directories. [21:17:21] Of course [21:18:08] Ok, I can fix that later [21:18:27] Let's hope that's the only problem [21:18:30] If you have things symlinked for convenience, you should be able to reverse that setup so that the canonical file is in /data/project/jembot and /home/jem has a symlink [21:19:06] Yes, it's just that I need to become jembot for the remote copy command [21:19:33] But I've done it in more recent cases [21:19:36] yes. it does make data upload a bit more complicated [21:19:52] Ok, I can live with it [21:21:38] Thanks, bd808 and taavi [21:22:19] One point that I also missed is that the Phabricator task about Jembot migration didn't mention or ping me [21:23:23] Of course I was aware because of the mail list, Tech News, etc. [21:24:18] If things go well tomorrow, should I close the task myself? [21:24:51] jem: I think T319828 doesn't ping you because your https://phabricator.wikimedia.org/p/-jem-/ account is not linked to your Developer account [21:24:51] T319828: Migrate jembot from Toolforge GridEngine to Toolforge Kubernetes - https://phabricator.wikimedia.org/T319828 [21:25:13] Ugh [21:25:39] jem: you should claim T319828 right now and add a note that you are working on it. They yes, if things look good to your tomorrow go ahead and close it. [21:25:47] Ok [21:26:01] And how I do the link to the developer account? [21:27:09] jem: It would be in https://phabricator.wikimedia.org/settings/user/-jem-/page/external/ [21:27:43] The "LDAP" account is your Developer account (same credentials as you would use to login to wikitech) [21:29:16] You can also use https://idm.wikimedia.org/ldapbackend/properties/ to record your SUL account as a property of your Developer account [21:29:53] Task updated [21:30:56] LDAP linked, I think [21:31:35] yes, I can see "LDAP User -jem- " on your Phab profile now [21:32:33] And SUL recorded as a property, I think [21:32:58] (and I have to check those things more carefully...) [21:33:28] I can see "wikimediaGlobalAccountName: -jem-" in your LDAP Developer account record now. Thanks! [21:34:17] No problem, thank you again :) [21:35:44] komla: ^ these ideas about linking Developer accounts to Phabricator and SUL accounts to Developer accounts are maybe things worth adding to some of your follow up communications. [22:42:26] !log tools.bridgebot Restarting. Looks like the bot got confused when some Kubernetes nodes restarted. [22:42:29] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.bridgebot/SAL [23:49:24] !log devtools starting manual gitlab upgrade process on gitlab-prod-1002 [23:49:26] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Devtools/SAL