[Cloud] Re: [Cloud-announce] [IMPORTANT] Grid Engine Shutdown Timeline

I assume you are talking about the amorybot tool. That tool is running several scripts directly on the cron node using jlocal in a way that is against the rules for its use . That does have the unfortunate but unavoidab

[Cloud] Re: [Cloud-announce] [IMPORTANT] Grid Engine Shutdown Timeline

On Dec 7, 2023 at 07:00:08, cloud-requ...@lists.wikimedia.org wrote: > Hello Amory, > > We reached out directly on several occasions to maintainers via email, > phabricator and announcements were made on the mailing list. > What's the username you use and is this the same email address you use? L

[Cloud] Re: [Cloud-announce] [IMPORTANT] Grid Engine Shutdown Timeline

On Thu, Dec 7, 2023 at 7:26 AM Kunal Mehta wrote: > > Just FYI if you weren't aware, the default quotas were recently raised > to 8CPU + 8GB total, with a max of 3CPU + 6GB per pod. (This is also > something I ran into.) > Thanks, that will help! I was unaware. > > > - Even the current Wikitec

[Cloud] Re: [Cloud-announce] [IMPORTANT] Grid Engine Shutdown Timeline

Hi, On 12/6/23 03:59, Magnus Manske via Cloud wrote: Hi all, I do appreciate the efforts to keep toolforge running, and that sometimes massive changes are necessary to do this, which has implications for tool maintainers. +1, I am not sure people fully appreciate how massive of a change thi

[Cloud] Re: [Cloud-announce] [IMPORTANT] Grid Engine Shutdown Timeline

Hello Amory, We reached out directly on several occasions to maintainers via email, phabricator and announcements were made on the mailing list. What's the username you use and is this the same email address you use? Let me crosscheck this again. On jlocal, you can schedule a cron job with Jobs F

[Cloud] Re: [Cloud-announce] [IMPORTANT] Grid Engine Shutdown Timeline

On Tue, 5 Dec 2023 at 19:13, wrote: > * When "grid infrastructure is deleted" on March 14, will there be backups > of the tools for people who want to migrate them in the future? > The "grid infrastructure" is different than the "tools". I expect the tools would still be there, they would just n

[Cloud] Re: [Cloud-announce] [IMPORTANT] Grid Engine Shutdown Timeline

Is there also the chance that those numbers are an undercount? I've got a bunch of simple cron tasks but they're using jlocal, not jsub, and I don't appear to have been contacted. The documentation vaguely alludes to this, but I wonder if there are a number of other tools/maintainers who have als

[Cloud] Re: [Cloud-announce] [IMPORTANT] Grid Engine Shutdown Timeline

Hi all, I do appreciate the efforts to keep toolforge running, and that sometimes massive changes are necessary to do this, which has implications for tool maintainers. I also understand that there have to be deadlines at some point, otherwise things will never get finished. But as I have said on

[Cloud] Re: [Cloud-announce] [IMPORTANT] Grid Engine Shutdown Timeline

Hello, this is a provocative approach to migration! * Clarification Q: The timeline was finalized on November 28, and any tools and cronjobs w/ no response from maintainers will stop working on the same day on December 14th, regardless of how actively they are used? Is there anything that u

[Cloud] Re: [Cloud-announce] [IMPORTANT] Grid Engine Shutdown Timeline

On Mon, Dec 4, 2023 at 2:11 PM John wrote: > I will also note the last time that I attempted to move to the k grid it > was about as smooth as sandpaper. Giving us a shutdown date less than 30 > days, and during a major holiday timeframe is really not helpful. Planning > for this should have been

[Cloud] Re: [Cloud-announce] [IMPORTANT] Grid Engine Shutdown Timeline

I will also note the last time that I attempted to move to the k grid it was about as smooth as sandpaper. Giving us a shutdown date less than 30 days, and during a major holiday timeframe is really not helpful. Planning for this should have been scheduled for a window with higher user availability

[Cloud] Re: [Cloud-announce] [IMPORTANT] Grid Engine Shutdown Timeline

Hi, The email I received was probably well intended, but felt like a threat to sabotage my tools. The whole project already got me unhappy from the start with tasks, contrary to Phabricator etiquette [1], being assigned to me because I happened to be at the top of the list. I called out the p