Page MenuHomePhabricator

Slst2020 (Slavina S)
Software Engineer

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Sunday

  • Clear sailing ahead.

User Details

User Since
Oct 7 2020, 6:01 PM (181 w, 1 d)
Availability
Available
IRC Nick
blancadesal
LDAP User
Slavina Stefanova
MediaWiki User
SStefanova (WMF) [ Global Accounts ]

Recent Activity

Wed, Mar 20

Slst2020 added a comment to T360509: [harbor,infra] Find a way to manage toolforge project policies with code.

Note also that maintain-harbor already manages the policies for all the other projects in harbor.

Wed, Mar 20, 10:43 AM · Toolforge
Slst2020 created T360509: [harbor,infra] Find a way to manage toolforge project policies with code.
Wed, Mar 20, 10:02 AM · Toolforge

Tue, Mar 19

Slst2020 renamed T354270: [harbor] Investigate new robot account permissions in Harbor 2.10.0 from [harbor] Investigate new robot account permissions in Harbor 2.10 to [harbor] Investigate new robot account permissions in Harbor 2.10.0.
Tue, Mar 19, 12:49 PM · Toolforge Build Service, Toolforge (Toolforge iteration 02)
Slst2020 renamed T354507: [harbor] upgrade to 2.10.1 from [harbor] upgrade to 2.10.x to [harbor] upgrade to 2.10.1.
Tue, Mar 19, 7:26 AM · Toolforge (Toolforge iteration 07)
Slst2020 changed the status of T354507: [harbor] upgrade to 2.10.1, a subtask of T352417: [maintain-harbor] Manage project quotas via maintain-harbor, from Stalled to Open.
Tue, Mar 19, 7:22 AM · Toolforge (Toolforge iteration 07), Upstream, Patch-For-Review
Slst2020 changed the status of T354507: [harbor] upgrade to 2.10.1, a subtask of T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds, from Stalled to Open.
Tue, Mar 19, 7:22 AM · Toolforge (Toolforge iteration 07)
Slst2020 changed the status of T354507: [harbor] upgrade to 2.10.1 from Stalled to Open.
Tue, Mar 19, 7:22 AM · Toolforge (Toolforge iteration 07)
Slst2020 moved T354507: [harbor] upgrade to 2.10.1 from Blocked/Paused to Next Up on the Toolforge (Toolforge iteration 07) board.
Tue, Mar 19, 7:22 AM · Toolforge (Toolforge iteration 07)

Mon, Mar 18

Slst2020 added a comment to T245683: Find and fix inaccuracies in Toolforge Django tutorial.

Using the new Build Service is now the recommended method for deploying Django applications on Toolforge. I think a better idea would be to:

Mon, Mar 18, 9:14 AM · Wikimedia-Hackathon-2024, good first task, Toolforge, Documentation

Fri, Mar 15

Slst2020 closed T358100: [toolforge API] expose all backend APIs OpenAPI specs as Resolved.
Fri, Mar 15, 11:46 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 closed T358100: [toolforge API] expose all backend APIs OpenAPI specs, a subtask of T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client, as Resolved.
Fri, Mar 15, 11:46 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 moved T356523: [jobs-api] introduce OpenAPI to jobs framework from In Progress to Done on the Toolforge (Toolforge iteration 07) board.
Fri, Mar 15, 11:45 AM · Toolforge (Toolforge iteration 07), User-aborrero
Slst2020 updated the task description for T358100: [toolforge API] expose all backend APIs OpenAPI specs.
Fri, Mar 15, 11:45 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T360147: [envvars-api, envvars-cli] Create envvar name error message is not user friendly.

The current error message probably comes from the envvars API that envvars-cli talks to. The repo is here: https://gitlab.wikimedia.org/repos/cloud/toolforge/envvars-api

Fri, Mar 15, 7:12 AM · Toolforge
Slst2020 renamed T360147: [envvars-api, envvars-cli] Create envvar name error message is not user friendly from [envvars-cli] Create envvar name error message is not user friendly to [envvars-api, envvars-cli] Create envvar name error message is not user friendly.
Fri, Mar 15, 6:53 AM · Toolforge

Thu, Mar 14

Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

Do we want to expose the /healthz and /metrics endpoints in the unified spec?

Thu, Mar 14, 3:01 PM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero

Wed, Mar 13

Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

operationIds need to be unique. At what level do we want to deal with this? Enforce a naming convention across the individual APis such as {serviceName}_{resourceName}_{operation}? Prefixing when merging the specs?

Not really, that can be dropped if needed, it's only used for code generation I think.

Hmm, we do want to generate the client libraries that we will use in the consolidated CLI, though. Also, I think tools that generate documentation rely on the uniqueness of operationId to correctly link operations to descriptions, parameters, and responses.

Wed, Mar 13, 11:05 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

operationIds need to be unique. At what level do we want to deal with this? Enforce a naming convention across the individual APis such as {serviceName}_{resourceName}_{operation}? Prefixing when merging the specs?

Wed, Mar 13, 10:50 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

@dcaro How should we deal with the security top-level element. We are currently ignoring it. Maybe add it to the base.yaml?

Wed, Mar 13, 9:55 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero

Tue, Mar 12

Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

@dcaro thanks! Another question: each openapi spec has it's own /openapi.json endpoint. We will want the gateway to expose the unified spec created by merging the files. Should we remove the individual /openapi.json endpoints from the merged spec?

Tue, Mar 12, 4:06 PM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

@dcaro what is the base.yaml in your script?

Tue, Mar 12, 1:35 PM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero

Mon, Mar 11

Slst2020 added a comment to T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation.

@dcaro What is our plan for creating the Toolforge CLI from the autogenerated SDK? Manually? Automatically with a post-generation script?

Will depend on the quality of the code generated, though I expect that there will always be some manual things we want to check, we could easily just create a new MR with the changes when any of the APIs is changed, for someone to review and merge right away if possible, or manually adapt if not.

Mon, Mar 11, 2:57 PM · Toolforge (Toolforge iteration 07)
Slst2020 updated subscribers of T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation.

@dcaro What is our plan for creating the Toolforge CLI from the autogenerated SDK? Manually? Automatically with a post-generation script?

Mon, Mar 11, 2:34 PM · Toolforge (Toolforge iteration 07)

Fri, Mar 8

Slst2020 added a comment to T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation.

OpenAPI Ggenerator and Swagger Codegen look very similar on the surface. A little digging reveals that OpenAPI Generator was forked from Swagger Codegen in 2018 by a group of the Swagger Codegen community and contributors who wanted to proceed in a slightly different direction. Their stated goals were to speed up development and acceptance of new features, improve the quality and maintainability of the code base, and make it easier for new contributors to get involved.

Fri, Mar 8, 2:58 PM · Toolforge (Toolforge iteration 07)
Slst2020 updated the task description for T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation.
Fri, Mar 8, 2:12 PM · Toolforge (Toolforge iteration 07)
Slst2020 changed the status of T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation from Open to In Progress.
Fri, Mar 8, 1:16 PM · Toolforge (Toolforge iteration 07)
Slst2020 changed the status of T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation, a subtask of T356262: [jobs-cli,builds-cli,toolforge-cli,webservice] Consolidate the Toolforge CLIs, from Open to In Progress.
Fri, Mar 8, 1:15 PM · Toolforge (Toolforge iteration 07), Epic

Thu, Mar 7

Slst2020 created T359558: [envvars-cli] Either hide or show envvars values, but not both.
Thu, Mar 7, 3:17 PM · Toolforge

Feb 23 2024

Slst2020 added a comment to T356729: Research API repository.

Do reach out if you need help with anything Toolforge or Cloud VPS related. Especially the build service is still somewhat new, so we are eager to hear what worked/didn't work for you.

Feb 23 2024, 4:53 PM · Research

Feb 22 2024

Slst2020 renamed T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation from [Toolforge CLI consolidation] Explore OpenAPI tooling to [Toolforge CLI consolidation] Explore OpenAPI SDK tooling .
Feb 22 2024, 3:55 PM · Toolforge (Toolforge iteration 07)
Slst2020 updated the task description for T358100: [toolforge API] expose all backend APIs OpenAPI specs.
Feb 22 2024, 2:54 PM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T357227: Elasticsearch credential request for capacity-exchange.

That's a password hash, not a password...

I regenerated the credentials and copied the correct password to the envvar.

Feb 22 2024, 2:16 PM · Capacity Exchange, cloud-services-team, Toolforge

Feb 21 2024

Slst2020 added a subtask for T358100: [toolforge API] expose all backend APIs OpenAPI specs: T356523: [jobs-api] introduce OpenAPI to jobs framework.
Feb 21 2024, 1:17 PM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a parent task for T356523: [jobs-api] introduce OpenAPI to jobs framework: T358100: [toolforge API] expose all backend APIs OpenAPI specs.
Feb 21 2024, 1:17 PM · Toolforge (Toolforge iteration 07), User-aborrero
Slst2020 created T358100: [toolforge API] expose all backend APIs OpenAPI specs.
Feb 21 2024, 1:16 PM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

We can do it literally on the fly, every request that comes for the schema pulls it from the APIs and generates them (I don't think we will have much traffic there, so validity trumps performance in my mind).

Feb 21 2024, 12:57 PM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

The big advantage of doing it on the fly, is that (as long as the generated schema is syntactically valid) the exposed schema would be the current exposed APIs, otherwise, every time we modify any of the backend APIs, there will be a period where the schema does not represent the current exposed APIs until we regenerate and deploy the gateway.

Feb 21 2024, 12:27 PM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

Being js also means that if we serve it as an API, we would have to use a nodejs server.

I think that going with python/golang might be safer (python might be enough).

Feb 21 2024, 11:54 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

The ability to configure it using json is nice though

Feb 21 2024, 11:38 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

sounds like a more featureful version of the above script xd, we might want to avoid the extra complications though, our merging operation should be dead simple.

Though if it's stable enough might be ok to use.

Feb 21 2024, 11:36 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

Nice! I was just experimenting with https://www.npmjs.com/package/openapi-merge-cli, merging just envvars and build to begin with. It generates a valid spec out-of-the-box but I'm also visually checking it.

Feb 21 2024, 11:26 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 claimed T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.
Feb 21 2024, 10:54 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.

Doing it "on the fly", so we don't have to generate a new definition any of the sub-apis changes

Feb 21 2024, 10:46 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added a comment to T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.
Feb 21 2024, 10:29 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero

Feb 19 2024

Slst2020 closed T357227: Elasticsearch credential request for capacity-exchange as Resolved.
Feb 19 2024, 11:44 AM · Capacity Exchange, cloud-services-team, Toolforge
Slst2020 added a comment to T357227: Elasticsearch credential request for capacity-exchange.

@Albertoleoncio Your tool has been granted write access to Elasticsearch now. The credentials are available to your tool as envvars. When logged into Toolforge as your tool, you can see them by running toolforge envvars list:

Feb 19 2024, 11:43 AM · Capacity Exchange, cloud-services-team, Toolforge
Slst2020 changed the status of T357227: Elasticsearch credential request for capacity-exchange from Open to In Progress.
Feb 19 2024, 10:52 AM · Capacity Exchange, cloud-services-team, Toolforge
Slst2020 claimed T357227: Elasticsearch credential request for capacity-exchange.
Feb 19 2024, 10:22 AM · Capacity Exchange, cloud-services-team, Toolforge

Feb 16 2024

Slst2020 closed T357694: request temporary quota increase for project iiab as Resolved.
sstefanova@cloudcontrol1005:~$ sudo wmcs-openstack quota show iiab | grep ram
| ram                   | 32768 |
sstefanova@cloudcontrol1005:~$ sudo wmcs-openstack quota show iiab | grep cores
| cores                 |    16 |
Feb 16 2024, 12:48 PM · Cloud-VPS (Quota-requests)
Slst2020 claimed T357694: request temporary quota increase for project iiab.
Feb 16 2024, 9:12 AM · Cloud-VPS (Quota-requests)

Feb 12 2024

Slst2020 added a parent task for T354507: [harbor] upgrade to 2.10.1: T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds.
Feb 12 2024, 11:22 AM · Toolforge (Toolforge iteration 07)
Slst2020 added a subtask for T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds: T354507: [harbor] upgrade to 2.10.1.
Feb 12 2024, 11:22 AM · Toolforge (Toolforge iteration 07)
Slst2020 reopened T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds as "Stalled".
Feb 12 2024, 11:21 AM · Toolforge (Toolforge iteration 07)
Slst2020 added a comment to T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds.

@Slst2020 this does not seem resolved to me? I can still reproduce the issue and there are no patches attached to this task.

Feb 12 2024, 11:18 AM · Toolforge (Toolforge iteration 07)
Slst2020 claimed T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation.
Feb 12 2024, 10:56 AM · Toolforge (Toolforge iteration 07)
Slst2020 closed T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds as Resolved.
Feb 12 2024, 10:55 AM · Toolforge (Toolforge iteration 07)

Feb 6 2024

Slst2020 updated subscribers of T356094: EXPLORE removing Openstack API calls from the user critical path.

during development, the Openstack API would at time timeout or return 500 errors

Why is there no task or other discussion I have heard about about fixing those 5xx errors? That seems like a more stable solution than trying to invent a hack to work around them.

Feb 6 2024, 7:50 PM · Catalyst (Prototype API)
Slst2020 added a comment to T356094: EXPLORE removing Openstack API calls from the user critical path.

I'm a bit confused by the scope of this task and the current proposal.

I thought there was no work remaining in the backend/infra for the PoC.

Feb 6 2024, 10:25 AM · Catalyst (Prototype API)

Feb 1 2024

Slst2020 added a comment to T356094: EXPLORE removing Openstack API calls from the user critical path.

would a pool of warm VMs instantiated outside the user critical path lessen this issue? Or only move it around?

Feb 1 2024, 4:55 PM · Catalyst (Prototype API)
Slst2020 added a comment to T351752: Implement access control via Puppet.

We now have support for unmanaged (unpuppetized) instances, so this should no longer be necessary.

Feb 1 2024, 3:56 PM · Catalyst (Prototype leftovers 🍱)

Jan 31 2024

Slst2020 added a parent task for T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client: T356262: [jobs-cli,builds-cli,toolforge-cli,webservice] Consolidate the Toolforge CLIs.
Jan 31 2024, 10:49 AM · Toolforge (Toolforge iteration 07), Patch-For-Review, User-aborrero
Slst2020 added subtasks for T356262: [jobs-cli,builds-cli,toolforge-cli,webservice] Consolidate the Toolforge CLIs: T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation, T354745: [jobs-api,buildservice-api,envvars-api] Investigate ways to present our multiple Openapi definitions to a future consolidated CLI client.
Jan 31 2024, 10:49 AM · Toolforge (Toolforge iteration 07), Epic
Slst2020 added a parent task for T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation: T356262: [jobs-cli,builds-cli,toolforge-cli,webservice] Consolidate the Toolforge CLIs.
Jan 31 2024, 10:49 AM · Toolforge (Toolforge iteration 07)
Slst2020 created T356262: [jobs-cli,builds-cli,toolforge-cli,webservice] Consolidate the Toolforge CLIs.
Jan 31 2024, 10:48 AM · Toolforge (Toolforge iteration 07), Epic
Slst2020 created T356261: [toolforge-cli,jobs-cli,builds-cli,envvars-cli] Explore OpenAPI SDK tooling for client consolidation.
Jan 31 2024, 10:46 AM · Toolforge (Toolforge iteration 07)
Slst2020 moved T348749: Decision request – Toolforge CLI consolidation from In Progress to Done on the Toolforge (Toolforge iteration 04) board.
Jan 31 2024, 10:43 AM · Toolforge (Toolforge iteration 04), Cloud Services Proposals
Slst2020 closed T348749: Decision request – Toolforge CLI consolidation as Resolved.

As there is no clear consensus, a decision meeting will be scheduled as described here: https://www.mediawiki.org/wiki/Wikimedia_Cloud_Services_team/Decision_Making

Jan 31 2024, 10:43 AM · Toolforge (Toolforge iteration 04), Cloud Services Proposals
Slst2020 updated the task description for T348749: Decision request – Toolforge CLI consolidation.
Jan 31 2024, 10:19 AM · Toolforge (Toolforge iteration 04), Cloud Services Proposals

Jan 30 2024

Slst2020 updated the task description for T348749: Decision request – Toolforge CLI consolidation.
Jan 30 2024, 3:01 PM · Toolforge (Toolforge iteration 04), Cloud Services Proposals

Jan 29 2024

Slst2020 closed T355997: Requesting additional Harbor / Toolforge Build Service disk quota for wd-shex-infer tool as Resolved.
Jan 29 2024, 10:56 AM · Toolforge (Quota-requests)
Slst2020 closed T355997: Requesting additional Harbor / Toolforge Build Service disk quota for wd-shex-infer tool, a subtask of T320140: Migrate wd-shex-infer from Toolforge GridEngine to Toolforge Kubernetes, as Resolved.
Jan 29 2024, 10:56 AM · Grid-Engine-to-K8s-Migration
Slst2020 changed the status of T355997: Requesting additional Harbor / Toolforge Build Service disk quota for wd-shex-infer tool from Open to In Progress.

Done – Both projects now have 2Gi harbor storage quota each.

Jan 29 2024, 10:56 AM · Toolforge (Quota-requests)
Slst2020 changed the status of T355997: Requesting additional Harbor / Toolforge Build Service disk quota for wd-shex-infer tool, a subtask of T320140: Migrate wd-shex-infer from Toolforge GridEngine to Toolforge Kubernetes, from Open to In Progress.
Jan 29 2024, 10:56 AM · Grid-Engine-to-K8s-Migration
Slst2020 added a comment to T351092: [harbor,docs] Improve Harbor quota handling and docs.

For the docs on the current quota setup this might be T329176: [maintain-harbor,docs] Document current setup and admin procedures

Jan 29 2024, 10:19 AM · Toolforge (Toolforge iteration 07), Documentation
Slst2020 added a comment to T329176: [maintain-harbor,docs] Document current setup and admin procedures.

@Raymond_Ndibe do you still plan to work on this during this iteration? If not, I wouldn't mind doing it.

Jan 29 2024, 10:08 AM · Toolforge (Toolforge iteration 07), Cloud-Services-Worktype-Project, Cloud-Services-Origin-Team, User-dcaro
Slst2020 added a comment to T355997: Requesting additional Harbor / Toolforge Build Service disk quota for wd-shex-infer tool.

It’s perhaps worth noting that for some reason, 317.19Mi or 317.20Mi of storage are still reported by toolforge build quota even after a successful toolforge build clean (twice now, with almost the same number). I don’t know where that’s coming from.

Jan 29 2024, 9:57 AM · Toolforge (Quota-requests)

Jan 25 2024

Slst2020 changed the status of T353052: [ci] Add shellcheck to pre-commit where missing from Open to In Progress.
Jan 25 2024, 1:42 PM · Toolforge (Toolforge iteration 04)
Slst2020 changed the status of T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds from Open to In Progress.
Jan 25 2024, 1:41 PM · Toolforge (Toolforge iteration 07)

Jan 24 2024

Slst2020 added a comment to T348960: [dev] find an alternative to Vagrant.

With there being support for lima in addition to vagrant now (T354406: [dev] Investigate lima-vm as an alternative to Vagrant for lima-kilo) I think this task can be closed. If anyone feels like exploring other alternatives, feel free to open it again.

Jan 24 2024, 2:18 PM · Toolforge
Slst2020 closed T348960: [dev] find an alternative to Vagrant as Resolved.
Jan 24 2024, 2:18 PM · Toolforge
Slst2020 added a comment to T348749: Decision request – Toolforge CLI consolidation.

As there is no clear consensus, a decision meeting will be scheduled as described here: https://www.mediawiki.org/wiki/Wikimedia_Cloud_Services_team/Decision_Making

Jan 24 2024, 2:13 PM · Toolforge (Toolforge iteration 04), Cloud Services Proposals
Slst2020 changed the status of T348749: Decision request – Toolforge CLI consolidation from Stalled to In Progress.
Jan 24 2024, 2:10 PM · Toolforge (Toolforge iteration 04), Cloud Services Proposals
Slst2020 closed T354406: [dev] Investigate lima-vm as an alternative to Vagrant for lima-kilo as Resolved.
Jan 24 2024, 2:10 PM · Toolforge (Toolforge iteration 04)
Slst2020 closed T354406: [dev] Investigate lima-vm as an alternative to Vagrant for lima-kilo, a subtask of T348960: [dev] find an alternative to Vagrant, as Resolved.
Jan 24 2024, 2:09 PM · Toolforge
Slst2020 added a comment to T354406: [dev] Investigate lima-vm as an alternative to Vagrant for lima-kilo.

There is now support for lima in addition to vagrant. Some things may still need improvement, e.g. for me builds run considerably slower on lima vs. vagrant, but I think this task can be closed as the basic support is there.

Jan 24 2024, 2:09 PM · Toolforge (Toolforge iteration 04)

Jan 22 2024

Slst2020 added a comment to T351410: [toolsdb] Can't authenticate with Toolsdb.

Thank you @taavi

Jan 22 2024, 5:58 AM · Data-Services

Jan 12 2024

Slst2020 renamed T353044: [ci][builds-cli][envvars-cli] Investigate discrepancy between different CI envs from [ci] Investigate discrepancy between different CI envs to [ci][builds-cli][envvars-cli] Investigate discrepancy between different CI envs.
Jan 12 2024, 11:19 AM · Toolforge
Slst2020 edited projects for T353044: [ci][builds-cli][envvars-cli] Investigate discrepancy between different CI envs, added: Toolforge Build Service; removed Toolforge.
Jan 12 2024, 11:19 AM · Toolforge
Slst2020 created T354942: [dev][harbor] reconcile harbor install methods.
Jan 12 2024, 11:16 AM · Toolforge (Toolforge iteration 04), Toolforge Build Service
Slst2020 updated subscribers of T347723: [tbs][dev] decide on which kubernetes bootstrapper to focus on between minikube and kind.
Jan 12 2024, 10:59 AM · Toolforge Build Service
Slst2020 added a comment to T347723: [tbs][dev] decide on which kubernetes bootstrapper to focus on between minikube and kind.

I think we're increasingly using lima-kilo, where kind has been working fine. If I'm wrong or you feel a strong preference for minikube, please chime in. Otherwise I will close this task as resolved a week from now.

Jan 12 2024, 10:58 AM · Toolforge Build Service
Slst2020 reopened T351476: [envvars-cli] move pytest from tox to pre-commit as "In Progress".
Jan 12 2024, 10:55 AM · Toolforge (Toolforge iteration 03)
Slst2020 closed T351476: [envvars-cli] move pytest from tox to pre-commit as Declined.
Jan 12 2024, 10:55 AM · Toolforge (Toolforge iteration 03)
Slst2020 changed the status of T351476: [envvars-cli] move pytest from tox to pre-commit from Declined to Resolved.
Jan 12 2024, 10:55 AM · Toolforge (Toolforge iteration 03)

Jan 10 2024

Slst2020 updated the task description for T354755: [builds-api] Improve error message when logs time out.
Jan 10 2024, 12:53 PM · Toolforge
Slst2020 created T354755: [builds-api] Improve error message when logs time out.
Jan 10 2024, 12:49 PM · Toolforge
Slst2020 added a comment to T354748: [jobs-cli] AttributeError: module 'requests.exceptions' has no attribute 'InvalidJSONError' when getting 5xx from the server.

I ran into the same error yesterday with builds-cli when trying to start a build. Upon retry a few moments later, it worked fine.

Jan 10 2024, 11:34 AM · Toolforge (Toolforge iteration 03)

Jan 9 2024

Slst2020 changed the status of T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds from In Progress to Open.
Jan 9 2024, 2:47 PM · Toolforge (Toolforge iteration 07)
Slst2020 moved T353701: [builds-cli,builds-api] `build quota` fails if tool has no builds from In Progress to Next Up on the Toolforge (Toolforge iteration 02) board.
Jan 9 2024, 2:47 PM · Toolforge (Toolforge iteration 07)
Slst2020 moved T354406: [dev] Investigate lima-vm as an alternative to Vagrant for lima-kilo from Next Up to In Progress on the Toolforge (Toolforge iteration 02) board.
Jan 9 2024, 2:46 PM · Toolforge (Toolforge iteration 04)