Page MenuHomePhabricator

nskaggs ( Nicholas Skaggs)
User

Projects (8)

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Thursday

  • Clear sailing ahead.

User Details

User Since
Jun 16 2020, 4:12 PM (154 w, 6 d)
Availability
Available
IRC Nick
balloons
LDAP User
Nskaggs
MediaWiki User
NSkaggs (WMF) [ Global Accounts ]

Recent Activity

Yesterday

nskaggs claimed T337718: Request increased quota for add-text Toolforge tool.

I can't find a tool with the specific name of wmr-bot. @wmr do you know the name of your tool within toolforge?

Mon, Jun 5, 11:31 PM · Toolforge (Quota-requests)

Thu, Jun 1

nskaggs created T337990: Draft dashboards are hidden from users.
Thu, Jun 1, 7:34 PM · superset.wmcloud.org
nskaggs added a comment to T337965: Export results as other things.

Note that chart data can be exported as json, excel, image or csv. SQL Lab export seems limited to csv.

Thu, Jun 1, 6:49 PM · superset.wmcloud.org
nskaggs renamed T337979: Make terms and licensing clear for superset.wmcloud.org from Make terms and licensing clear for superset to Make terms and licensing clear for superset.wmcloud.org.
Thu, Jun 1, 6:39 PM · superset.wmcloud.org
nskaggs created T337979: Make terms and licensing clear for superset.wmcloud.org.
Thu, Jun 1, 6:38 PM · superset.wmcloud.org
nskaggs added a comment to T337342: Improve Superset documentation.

The documentation page for PAWS might serve as an inspiration: https://wikitech.wikimedia.org/wiki/PAWS

Thu, Jun 1, 6:30 PM · superset.wmcloud.org, User-EpicPupper, Documentation
nskaggs created T337936: Toolhunt seems down.
Thu, Jun 1, 1:16 PM · Toolhunt
nskaggs created T337935: Data submissions to toolhunt time out.
Thu, Jun 1, 1:15 PM · Toolhunt

Wed, May 31

nskaggs added a comment to T337571: Requesting access to ops group for nskaggs.

I'm wondering if this was the right long term approach. In general we're trying to reduce the need for global root, not expand it.
I see that we already have a wmcs-roots group in modules/admin/data/data.yaml that has full sudo permissions on the hosts where it's applied adding it to the hiera profile::admin::groups setting.
I wonder if that would be a more suitable solution for the cloudb hosts and similar other clusters related to WMCS.

Wed, May 31, 8:57 PM · SRE, SRE-Access-Requests
nskaggs added a comment to T337829: Requesting access to ops (or wmcs-roots) for TheresNoTime.

I presume resolving T337848: WMCS-roots access would unblock the situation you described, yes? And if I'm reading correctly, your desire would be to help in WMCS spaces longer term yes? That would point to wmcs-roots as the correct level of access. Additionally, it would be helpful on an ongoing basis in understanding other situations where wmcs-roots access isn't enough to help ensure a WMCS root can manage all WMCS hosts.

Wed, May 31, 8:40 PM · SRE, SRE-Access-Requests
nskaggs added a comment to T319593: Migrate bldrwnsch from Toolforge GridEngine to Toolforge Kubernetes.

For apt support, T336669: Decision request - How to provide a way to install system dependencies for buildpack-based images decided on using https://github.com/heroku/heroku-buildpack-apt. Would this unlock the migration?

Wed, May 31, 8:32 PM · User-aborrero, Wikimedia-Hackathon-2023, Grid-Engine-to-K8s-Migration

Fri, May 26

nskaggs updated subscribers of T336940: Create a #wmcs-superset tag.
Fri, May 26, 6:07 PM · Project-Admins
nskaggs closed T336941: Create a #openstack-magnum, a subtask of T328711: Magnum in Horizon in codfw1dev, as Resolved.
Fri, May 26, 6:05 PM · Openstack-Magnum
nskaggs closed T336941: Create a #openstack-magnum, a subtask of T326436: Multiple control nodes for magnum, as Resolved.
Fri, May 26, 6:05 PM · Openstack-Magnum
nskaggs closed T336941: Create a #openstack-magnum, a subtask of T328712: Create a community offering of magnum, as Resolved.
Fri, May 26, 6:05 PM · Openstack-Magnum
nskaggs closed T336941: Create a #openstack-magnum, a subtask of T328713: Create default magnum template, as Resolved.
Fri, May 26, 6:05 PM · Openstack-Magnum
nskaggs closed T336941: Create a #openstack-magnum, a subtask of T333703: Failing to create magnum template with terraform in eqiad1, as Resolved.
Fri, May 26, 6:04 PM · Openstack-Magnum, PAWS
nskaggs closed T336941: Create a #openstack-magnum, a subtask of T333874: Permission error while trying to create magnum cluster, as Resolved.
Fri, May 26, 6:04 PM · Openstack-Magnum, PAWS
nskaggs closed T336941: Create a #openstack-magnum, a subtask of T328715: document magnum in horizon, as Resolved.
Fri, May 26, 6:04 PM · Openstack-Magnum
nskaggs closed T336941: Create a #openstack-magnum, a subtask of T336586: magnum: kubectl fails to connect after time, as Resolved.
Fri, May 26, 6:04 PM · Openstack-Magnum
nskaggs closed T336941: Create a #openstack-magnum, a subtask of T337507: Magnum nodes alert as down, as Resolved.
Fri, May 26, 6:04 PM · Openstack-Magnum
nskaggs closed T336941: Create a #openstack-magnum as Resolved.

I added a description and created this sub-project here: https://phabricator.wikimedia.org/project/view/6568/

Fri, May 26, 6:04 PM · Project-Admins
nskaggs created Openstack-Magnum.
Fri, May 26, 6:04 PM
nskaggs updated the task description for T337571: Requesting access to ops group for nskaggs.
Fri, May 26, 4:40 PM · SRE, SRE-Access-Requests
nskaggs renamed T337571: Requesting access to ops group for nskaggs from Requesting access to global root for nskaggs to Requesting access to ops group for nskaggs.
Fri, May 26, 4:37 PM · SRE, SRE-Access-Requests
nskaggs created T337571: Requesting access to ops group for nskaggs.
Fri, May 26, 4:12 PM · SRE, SRE-Access-Requests
nskaggs updated subscribers of T336940: Create a #wmcs-superset tag.
Fri, May 26, 2:48 PM · Project-Admins
nskaggs added a comment to T336940: Create a #wmcs-superset tag.

It's possible you may wish to force both tags to have prefixes or suffices on them. And updating the tags to have public and NDA/restricted prefixes/suffices might make more sense in the longterm rather than attaching to a specific team name or prefix.

Fri, May 26, 2:38 PM · Project-Admins
nskaggs added a comment to T336940: Create a #wmcs-superset tag.

@Aklapper https://wikitech.wikimedia.org/wiki/Superset has a disambiguation on it, if that helps. Simply put Data Engineering runs a restricted superset instance; superset.wikimedia.org, while WMCS has launched a public instance at superset.wmcloud.org. The existing tags and documentation only spoke about Data Engineering's restricted instance. With the addition of the public instance, we need to keep them separate and clear. I might update the existing project to say something like

Design, implementation and maintenance of the NDA restricted Wikimedia Superset instance(s), administrated by Data Engineering....
Fri, May 26, 2:36 PM · Project-Admins

Thu, May 25

nskaggs added a comment to T336669: Decision request - How to provide a way to install system dependencies for buildpack-based images.

Of the options listed, I agree with going with option 2. I would be curious to hear about any other concerns with enabling it unrestricted for anyone using buildpacks. I don't feel the mentioned issue of potential TOU violations warrants the extra work required for option 1. Any other concerns beyond image size?

Thu, May 25, 5:30 PM · Toolforge Build Service (Iteration 15), Cloud Services Proposals
nskaggs added a comment to T337506: Additional storage for Quarry.

+1

Thu, May 25, 5:23 PM · Cloud-VPS (Quota-requests)

Wed, May 24

nskaggs added a comment to T337196: Request trove db for Lutz Toolforge tool.

+1 to the request.

Wed, May 24, 3:17 PM · Toolforge (Quota-requests)
nskaggs added a comment to T337183: Request increased quota for urbanecmbot Toolforge tool.

+1 to the request.

Wed, May 24, 3:17 PM · urbanecmbot, Toolforge (Quota-requests)

Mon, May 22

nskaggs renamed T337192: Toolforge: consider introducing some semantics for persistent storage from Toolforge: consider introducing some semantics for presistent storage to Toolforge: consider introducing some semantics for persistent storage.
Mon, May 22, 4:49 PM · cloud-services-team, Toolforge

Wed, May 17

nskaggs added a comment to T169452: Move Quarry to be an installation of Superset.

I've created https://wikitech.wikimedia.org/w/index.php?title=Superset to provide some more details and potentially hold some basic user documentation for superset. Edits welcome!

Wed, May 17, 10:06 PM · superset.wmcloud.org, cloud-services-team (FY2022/2023-Q4), Quarry
nskaggs moved T336905: Supporting AI, LLM, and data models on WMCS from Inbox to Needs discussion on the cloud-services-team board.
Wed, May 17, 9:10 PM · cloud-services-team, Cloud-Services
nskaggs added a project to T336905: Supporting AI, LLM, and data models on WMCS: cloud-services-team.
Wed, May 17, 9:09 PM · cloud-services-team, Cloud-Services
nskaggs created T336905: Supporting AI, LLM, and data models on WMCS.
Wed, May 17, 9:08 PM · cloud-services-team, Cloud-Services
nskaggs added a comment to T333856: Cloud VPS open exception request.

Thanks for response and additional engagement. I don't expect the conclusion to change but some additional context / thoughts:

There are a few reasons for why we're declining this but the main one is wanting to ensure that everyone (both in the WMF and outside) has the same experience on our platform.

I'll admit that I'm a bit confused about this reasoning. The purpose of an exception is to carve out a clear instance where it's okay for the experience to vary, such as testing compatibility with proprietary software as mentioned in the current Terms of use. I thought I had crafted this request to match that suggested exception pretty closely (time-bound; for the purposes of experimentation/testing). What I'm hearing though is that exceptions to the current open-source definition are not being considered without a broader discussion?

WMCS treat every request distinctly. So future exceptions are possible and will be evaluated within their own merit. Sorry if that seems like a boilerplate answer, but for example, if you wish to personally test a non-OSS model in the future, please do ask, with context. Don't assume this specific answer invalidates all future requests as well.

+1 to having a broader discussion. It would be helpful for me to understand more about what the "code" versus "model" looks like.

Much longer debate than should happen on this ticket but, for instance, a model has at least three separate pieces that are often treated independently: the final model artifact (a bunch of numbers essentially), the code used to train the model, and the data that was fed into the model. Right now, the question of AI licenses seems to focus heavily on the final model artifact. The question of whether the training code is open-source is pretty trivial (the code itself is often very basic) but obviously an easy thing to expect. Where we'd get most of the traditional benefits of open (many eyes, ability for anyone to contribute/fork, etc.) is around the underlying data. That's best way to understand how the model was built, where it might fail etc., and make contributions to improving it. For example, for the stableLM example you gave:

  • They release the base model artifact as CC-BY-SA 4.0, which would meet our expectations around content licenses.
  • They say the underlying dataset is based on The Pile (which is open in the sense that it is freely downloadable though the data within it is variably licensed -- some explicitly open-source, other being incorporated under fair use such as Common Crawl). They don't share what their particular dataset is yet though so I wouldn't consider it open.
  • I didn't see their training code shared -- they just say An upcoming technical report will document the model specifications and the training settings. The code in that repo which is Apache 2.0 is just examples of how to use the model.

So from my standpoint, it may seem like stableLM is a better fit because its model artifact (what I would download and use on Cloud VPS) is openly-licensed, but in reality I know far far less about that model than BLOOM or some of the Responsible AI Licensed models that have much more transparency about their process.

Some additional reading about other aspects here and here.

So by the pile, it seems you are referring to https://pile.eleuther.ai/. They don't give any licensing information at all. However, https://github.com/EleutherAI/the-pile has some details you are talking about. The code to process the datasets is MIT, but clearly the source data is a myriad of things. Looking further into the paper published about the dataset, answers more technical questions. See https://arxiv.org/pdf/2201.07311.pdf. Quoting from there "All data contained in the Pile has been heavily processed to aid in language modeling research and no copyrighted text is contained in the Pile in its original form. As far as we are aware, under U.S. copyright law use of copyrighted texts in the Pile falls under the “fair use” doctrine, which allows for the unlicensed use of copyright-protected works in some circumstances." I understand you could remix the pile to include / exclude datasets. For example, basing the dataset only on wikipedia and other CC-by-SA licensed content. Based on the description however, I'm not sure what "heavily processed" and "no copyrighted text" really means.

As a random aside, I saw the announce today about stablelm, which is using cc-by-sa for base models: https://github.com/stability-AI/stableLM/#licenses. Specific to the hackathon, can you use an OSI compatible model?

Thanks for mentioning this. Building on above, the reason I requested the exception is not because there aren't open-source models available for some of these tasks but because there's been community interest in models like BLOOM given their collaborative approach to training the model and care around data governance, carbon costs, etc. (i.e. ethics beyond just the question of licensing model artifacts).

Ethical licensing isn't compatible with CC-by-SA which is the issue in question here. Given what you've shared though, I'm curious how anyone can take a mix of data sources and license under any terms really. They aren't the creators of the source content used to create the dataset.

Would GPU access help?

I'd definitely be curious if Cloud VPS is considering incorporating GPUs. For many modern ML models, they are essentially required for reasonable performance.

Let's discuss more about how many GPU's would be needed in order to be meaningful and useful.

Wed, May 17, 8:30 PM · cloud-services-team, Cloud-VPS

Mon, May 15

nskaggs added a comment to T169452: Move Quarry to be an installation of Superset.

For docs, upstream has a few. Dashboards are new idea, and can be collaborative, which I think is a useful feature that goes beyond what quarry can offer. I believe people will be reason about a shared set of queries and data, and collaborative edit and view said data via dashboards.

Mon, May 15, 4:01 PM · superset.wmcloud.org, cloud-services-team (FY2022/2023-Q4), Quarry

Fri, May 12

nskaggs added a comment to T311466: Create a kubernetes container with mono and dotnet.

Seeing as heroku doesn't seem to have a dotnet buildpack, I'm guessing it would be https://github.com/paketo-buildpacks/dotnet-core.

Fri, May 12, 8:04 PM · Toolforge (Software install/update)

Thu, May 11

nskaggs updated the task description for T322500: 2022 Cloud Services Survey.
Thu, May 11, 1:45 PM · Developer-Advocacy (Apr-Jun 2023), Goal, Surveys
nskaggs updated the task description for T322500: 2022 Cloud Services Survey.
Thu, May 11, 1:45 PM · Developer-Advocacy (Apr-Jun 2023), Goal, Surveys
nskaggs updated the task description for T322500: 2022 Cloud Services Survey.
Thu, May 11, 1:45 PM · Developer-Advocacy (Apr-Jun 2023), Goal, Surveys

Wed, May 10

nskaggs changed the status of T334748: Split cloud-announce into two lists: toolforge-announce and cloudvps-announce from Open to Stalled.

For now marking as stalled / blocked on T279023 as noted. I'm doing so because I don't believe any advocates would move forward without the ability to automatically subscribe folks to the correct mailing list.

Wed, May 10, 8:38 PM · Cloud Services Proposals, cloud-services-team
nskaggs placed T316391: Create cookbook to manage K8s quotas on Toolforge up for grabs.
Wed, May 10, 8:07 PM · cloud-services-team, Toolforge

May 2 2023

nskaggs updated subscribers of T324998: Q3:rack/setup/install cloudcephosd10(3[5-9]|40).

@Jclark-ctr These should be setup with software RAID just like last time. See @Andrew comment: https://phabricator.wikimedia.org/T294972#8029219. @Andrew feel free to correct or jump in if needed.

May 2 2023, 7:28 PM · SRE, cloud-services-team (Hardware), ops-eqiad, DC-Ops
nskaggs updated the task description for T289882: Q1:(Need By: TBD) rack/setup/install cloudswift100[12].
May 2 2023, 7:23 PM · SRE, Infrastructure-Foundations, ops-eqiad, netops, cloud-services-team (Hardware), DC-Ops
nskaggs updated the task description for T289882: Q1:(Need By: TBD) rack/setup/install cloudswift100[12].
May 2 2023, 7:22 PM · SRE, Infrastructure-Foundations, ops-eqiad, netops, cloud-services-team (Hardware), DC-Ops

Apr 28 2023

nskaggs removed a project from T178834: Provide any rough metrics for tool and project usage: cloud-services-team (FY2022/2023-Q3).
Apr 28 2023, 8:01 PM · Tool Maintainers, Cloud-VPS, Toolforge
nskaggs removed a project from T270694: CloudVPS: introduce tenant networks: cloud-services-team (FY2022/2023-Q3).
Apr 28 2023, 8:01 PM · Cloud-VPS, Epic
nskaggs removed a project from T289883: cloud-vps: actively deprecate/phase out use of Debian Stretch: cloud-services-team (FY2022/2023-Q3).
Apr 28 2023, 8:01 PM · Cloud-VPS (Debian Stretch Deprecation)
nskaggs removed a project from T327254: WMCS FY22/23 Q3: next steps in grid engine deprecation: cloud-services-team (FY2022/2023-Q3).
Apr 28 2023, 8:00 PM · Toolforge
nskaggs edited projects for T169452: Move Quarry to be an installation of Superset, added: cloud-services-team (FY2022/2023-Q4); removed cloud-services-team (FY2022/2023-Q3).
Apr 28 2023, 8:00 PM · superset.wmcloud.org, cloud-services-team (FY2022/2023-Q4), Quarry
nskaggs removed a project from T328649: [tbs.buildpack-admission-service] throw error if unable to load ssl cert: cloud-services-team (FY2022/2023-Q3).
Apr 28 2023, 1:54 PM · Toolforge Build Service, Cloud-Services-Worktype-Project, Cloud-Services-Origin-Team, User-dcaro
nskaggs removed a project from T329176: [tbs.maintain-harbor] Document current setup and admin procedures: cloud-services-team (FY2022/2023-Q3).
Apr 28 2023, 1:54 PM · Toolforge Build Service (Iteration 15), Cloud-Services-Worktype-Project, Cloud-Services-Origin-Team, User-dcaro
nskaggs removed a project from T325189: tbs: user-story 13: Add ci to the buildservice repo: cloud-services-team (FY2022/2023-Q3).
Apr 28 2023, 1:53 PM · Toolforge Build Service (Iteration 14), Patch-For-Review, User-Raymond_Ndibe, Cloud-Services-Worktype-Project, Cloud-Services-Origin-Team, User-dcaro
nskaggs removed a project from T325192: tbs: user-story 13: Add ci to the buildpack-admission-controller repo: cloud-services-team (FY2022/2023-Q3).
Apr 28 2023, 1:53 PM · Toolforge Build Service (Iteration 14), User-Raymond_Ndibe, Cloud-Services-Worktype-Project, Cloud-Services-Origin-Team, User-dcaro
nskaggs removed a project from T330075: [cloudvirt] Move to jumbo frames: cloud-services-team (FY2022/2023-Q3).
Apr 28 2023, 1:53 PM · Infrastructure-Foundations, netops, Cloud-Services-Worktype-Unplanned, Cloud-Services-Origin-Team, User-dcaro
nskaggs edited projects for T332153: cloudlb: prepare backends, added: cloud-services-team (FY2022/2023-Q4); removed cloud-services-team (FY2022/2023-Q3).
Apr 28 2023, 1:53 PM · cloud-services-team (FY2022/2023-Q4)
nskaggs removed a project from T333982: [toolforge] Allow easily turning on new NFS setups: cloud-services-team (FY2022/2023-Q3).
Apr 28 2023, 1:52 PM · Toolforge, Cloud-Services-Worktype-Project, Cloud-Services-Origin-Team, User-dcaro
nskaggs archived cloud-services-team (FY2022/2023-Q3).
Apr 28 2023, 1:52 PM

Apr 26 2023

nskaggs closed T334913: k8s quota increase request for sdzerobot tool as Resolved.

Done. Updated CPU and deployment limits to 5 each. If you need more resources, don't hesitate to ask. My apologies for the delay in processing. Thanks for helping the migration from grid engine!

Apr 26 2023, 3:28 PM · Toolforge (Quota-requests)

Apr 24 2023

Qgil awarded T335190: Request creation of civicrm-prototype VPS project a Party Time token.
Apr 24 2023, 8:29 PM · cloud-services-team, Cloud-VPS (Project-requests)
nskaggs closed T335190: Request creation of civicrm-prototype VPS project as Resolved.

This should now be created, with qgil as the sole admin. Feel free to add more as needed.

Apr 24 2023, 6:37 PM · cloud-services-team, Cloud-VPS (Project-requests)
nskaggs changed the status of T335190: Request creation of civicrm-prototype VPS project from Open to In Progress.
Apr 24 2023, 2:02 PM · cloud-services-team, Cloud-VPS (Project-requests)

Apr 20 2023

nskaggs added a comment to T333856: Cloud VPS open exception request.

As a random aside, I saw the announce today about stablelm, which is using cc-by-sa for base models: https://github.com/stability-AI/stableLM/#licenses. Specific to the hackathon, can you use an OSI compatible model? Would GPU access help?

Apr 20 2023, 12:22 PM · cloud-services-team, Cloud-VPS

Apr 19 2023

nskaggs added a comment to T333856: Cloud VPS open exception request.

+1 to having a broader discussion. It would be helpful for me to understand more about what the "code" versus "model" looks like.

Apr 19 2023, 4:48 PM · cloud-services-team, Cloud-VPS
nskaggs moved T334565: [toolforge-cli.build] Differenciate between verbose and debug from Backlog to Done on the cloud-services-team (FY2022/2023-Q4) board.
Apr 19 2023, 2:25 PM · User-Raymond_Ndibe, cloud-services-team (FY2022/2023-Q4), Toolforge Build Service (Iteration 13), Cloud-Services-Worktype-Project, Cloud-Services-Origin-Team, User-dcaro
nskaggs moved T334566: [toolforge-cli.build] show only the status line instead of the whole tasks unless --verbose is passed from Backlog to Done on the cloud-services-team (FY2022/2023-Q4) board.
Apr 19 2023, 2:25 PM · User-Raymond_Ndibe, cloud-services-team (FY2022/2023-Q4), Toolforge Build Service (Iteration 13), Cloud-Services-Worktype-Project, Cloud-Services-Origin-Team, User-dcaro
nskaggs moved T334586: [toolforge-cli.webservice] Set a default value for the buildservice-image parameter of the buildservice type from Backlog to Done on the cloud-services-team (FY2022/2023-Q4) board.
Apr 19 2023, 2:25 PM · User-Raymond_Ndibe, cloud-services-team (FY2022/2023-Q4), Toolforge Build Service (Iteration 13), Cloud-Services-Worktype-Project, Cloud-Services-Origin-Team, User-dcaro
nskaggs moved T334828: [wmcs.alert] The service unit maintain-dbusers.service is in failed status on host cloudcontrol1005. from Backlog to Done on the cloud-services-team (FY2022/2023-Q4) board.
Apr 19 2023, 2:25 PM · Patch-For-Review, Cloud-Services-Worktype-Unplanned, Cloud-Services-Origin-Alert, cloud-services-team (FY2022/2023-Q4), User-dcaro
nskaggs moved T331336: [tbs] Francesco has deployed the webservice cli in toolsbeta from Backlog to In progress on the cloud-services-team (FY2022/2023-Q4) board.
Apr 19 2023, 2:25 PM · Toolforge Build Service (Iteration 14), cloud-services-team (FY2022/2023-Q4), Cloud-Services-Worktype-Project, Cloud-Services-Origin-Team, User-dcaro
nskaggs closed T326756: Archive Grid Engine Documentation on Wikitech, a subtask of T321582: WMCS doc improvements for FY22/23: Improve the navigability, freshness, and topic coverage of Cloud Services docs, as Resolved.
Apr 19 2023, 2:22 PM · Cloud-Services, Documentation, Developer-Advocacy (Apr-Jun 2023), Epic
nskaggs closed T326756: Archive Grid Engine Documentation on Wikitech as Resolved.
Apr 19 2023, 2:22 PM · cloud-services-team (FY2022/2023-Q3), Documentation, Toolforge

Apr 14 2023

nskaggs added a comment to T333856: Cloud VPS open exception request.

Thanks for opening this ticket! I've added this to the agenda for next week's team meeting for consideration. In the meantime, comments welcome!

Apr 14 2023, 1:40 PM · cloud-services-team, Cloud-VPS

Apr 11 2023

nskaggs edited projects for T306820: ceph: upgrade to v16 now that v17 is stable, added: cloud-services-team (FY2022/2023-Q4); removed cloud-services-team (FY2022/2023-Q3).
Apr 11 2023, 9:18 PM · Goal, cloud-services-team (FY2022/2023-Q4), Cloud-Services-Worktype-Maintenance, Cloud-Services-Origin-Team, User-dcaro
nskaggs edited projects for T309789: ceph: upgrade hosts to bullseye, added: cloud-services-team (FY2022/2023-Q4); removed cloud-services-team (FY2022/2023-Q3).
Apr 11 2023, 9:18 PM · Goal, cloud-services-team (FY2022/2023-Q4), Patch-For-Review, Cloud-Services-Worktype-Maintenance, Cloud-Services-Origin-Team, User-dcaro
nskaggs edited projects for T324992: cloudlb: create PoC on codfw, added: cloud-services-team (FY2022/2023-Q4); removed cloud-services-team (FY2022/2023-Q3).
Apr 11 2023, 9:18 PM · User-aborrero, Goal, cloud-services-team (FY2022/2023-Q4), Patch-For-Review
nskaggs edited projects for T327725: Realign and agree on the team social norms., added: cloud-services-team (FY2022/2023-Q4); removed cloud-services-team (FY2022/2023-Q3).
Apr 11 2023, 9:18 PM · cloud-services-team (FY2022/2023-Q4), wmcs-retrospective
nskaggs reopened T324992: cloudlb: create PoC on codfw as "In Progress".
Apr 11 2023, 9:16 PM · User-aborrero, Goal, cloud-services-team (FY2022/2023-Q4), Patch-For-Review
nskaggs reopened T324992: cloudlb: create PoC on codfw, a subtask of T297596: have cloud hardware servers in the cloud realm using a dedicated LB layer, as In Progress.
Apr 11 2023, 9:15 PM · Goal, cloud-services-team (FY2022/2023-Q4)
nskaggs closed T324992: cloudlb: create PoC on codfw as Resolved.
Apr 11 2023, 9:15 PM · User-aborrero, Goal, cloud-services-team (FY2022/2023-Q4), Patch-For-Review
nskaggs closed T324992: cloudlb: create PoC on codfw, a subtask of T297596: have cloud hardware servers in the cloud realm using a dedicated LB layer, as Resolved.
Apr 11 2023, 9:15 PM · Goal, cloud-services-team (FY2022/2023-Q4)

Apr 7 2023

nskaggs closed T319639: Migrate commons-app-stats from Toolforge GridEngine to Toolforge Kubernetes as Resolved.

@whym Thanks for migrating! I will resolve this task for you given the tool is now running on k8s.

Apr 7 2023, 7:05 PM · Grid-Engine-to-K8s-Migration
nskaggs added a comment to T333059: Spread Toolforge tools to multiple Kubernetes clusters.

Thanks for sharing this idea Taavi. If we allow a tool to be restarted as part of a transition to a different cluster does that change the requirements mentioned? In general, are there other things we can do to simplify the list of requirements? For example, if some downtime was ok, does that change anything? If users weren't blocked on using kubectl, but also had no support if a k8s upgrade broke them, does that lessen requirements in a useful way? What if we deployed a clone of toolforge today, but did so with a current version of k8s? Could tools be migrated?

Apr 7 2023, 6:56 PM · Toolforge
nskaggs moved T320163: Migrate wikipedia-library from Toolforge GridEngine to Toolforge Kubernetes from Backlog to No identified maintainer on the Grid-Engine-to-K8s-Migration board.
Apr 7 2023, 6:39 PM · User-bd808, The-Wikipedia-Library, Grid-Engine-to-K8s-Migration
nskaggs moved T319788: Migrate hewiki-tools from Toolforge GridEngine to Toolforge Kubernetes from Backlog to No identified maintainer on the Grid-Engine-to-K8s-Migration board.
Apr 7 2023, 6:34 PM · Grid-Engine-to-K8s-Migration
nskaggs moved T319610: Migrate bub from Toolforge GridEngine to Toolforge Kubernetes from Backlog to No identified maintainer on the Grid-Engine-to-K8s-Migration board.
Apr 7 2023, 6:33 PM · Grid-Engine-to-K8s-Migration
nskaggs changed the status of T313405: Migrate remaining tools off Gridengine from Open to In Progress.
Apr 7 2023, 4:52 PM · cloud-services-team, Toolforge
nskaggs changed the status of T313405: Migrate remaining tools off Gridengine, a subtask of T314664: Toolforge: Decomission the Grid Engine infrastructure, from Open to In Progress.
Apr 7 2023, 4:52 PM · Patch-For-Review, cloud-services-team, Toolforge
nskaggs updated the task description for T313405: Migrate remaining tools off Gridengine.
Apr 7 2023, 4:52 PM · cloud-services-team, Toolforge
nskaggs closed T319884: Migrate mdaniels-refill-ng from Toolforge GridEngine to Toolforge Kubernetes as Resolved.

I think marking for deletion is enough. Thanks for your help!

Apr 7 2023, 4:50 PM · Grid-Engine-to-K8s-Migration

Apr 5 2023

nskaggs added a comment to T332400: Migrate cloudweb, cloudbackup, cloudmetrics physical servers off buster .

Note, WMCS would like to migrate directly to bookworm if possible.

Apr 5 2023, 2:42 PM · cloud-services-team
nskaggs added a subtask for T297596: have cloud hardware servers in the cloud realm using a dedicated LB layer: T289882: Q1:(Need By: TBD) rack/setup/install cloudswift100[12].
Apr 5 2023, 2:04 PM · Goal, cloud-services-team (FY2022/2023-Q4)
nskaggs added a parent task for T289882: Q1:(Need By: TBD) rack/setup/install cloudswift100[12]: T297596: have cloud hardware servers in the cloud realm using a dedicated LB layer.
Apr 5 2023, 2:04 PM · SRE, Infrastructure-Foundations, ops-eqiad, netops, cloud-services-team (Hardware), DC-Ops
nskaggs added a comment to T289882: Q1:(Need By: TBD) rack/setup/install cloudswift100[12].

As an update, this is now blocked on T297596: have cloud hardware servers in the cloud realm using a dedicated LB layer. The previous implementation discussion led to a finalization of guidelines, which are now published in https://wikitech.wikimedia.org/wiki/Cross-Realm_traffic_guidelines#Case_4:_cloud-dedicated_hardware. This implementation will be conformant with those guidelines, which requires T297596, cloud based load balancers to exist. The network requirements are likely to shift to a new cloud-private + cloud-hosts VLAN setup, but otherwise I don't anticipate any changes required related to network or racking.

Apr 5 2023, 2:04 PM · SRE, Infrastructure-Foundations, ops-eqiad, netops, cloud-services-team (Hardware), DC-Ops

Apr 4 2023

nskaggs added a comment to T333986: Superset project.

+1

Apr 4 2023, 4:57 PM · Quarry, Cloud-VPS (Project-requests)
nskaggs added a parent task for T333986: Superset project: T169452: Move Quarry to be an installation of Superset.
Apr 4 2023, 4:56 PM · Quarry, Cloud-VPS (Project-requests)
nskaggs added a subtask for T169452: Move Quarry to be an installation of Superset: T333986: Superset project.
Apr 4 2023, 4:56 PM · superset.wmcloud.org, cloud-services-team (FY2022/2023-Q4), Quarry