Skip to content
PurdueAFPublic

About

Purdue Analysis Facility

Resources

Stars

8 stars

Watchers

1 watching

Forks

Repository files navigation

Purdue Analysis Facility

CI codecov Docs deploy Registry GC Component status platform

GitOps source of truth for the Purdue Analysis Facility — a Kubernetes-based interactive analysis platform for high energy physics research at CMS experiment.

Everything the cluster runs is declared here and reconciled by Flux.

User documentation: analysis-facility.physics.purdue.edu Admin documentation: https://purdue-cms-tier2.gitlab.io/documentation

Platform at a glance

Orchestration Kubernetes on the Geddes cluster; Flux CD (roots)
Sessions JupyterHub — JupyterLab and code-server interfaces, CILogon auth
Scale-out Dask Gateway
Training Ray on KubeRay — GPU training sent from notebooks, one cluster per user and per job (gateway)
User environment the purdue-af image, pixi environments
Data CVMFS, XRootD, XCache, EOS, Depot NFS; ServiceX for columnar delivery
Inference SuperSONIC
Observability Prometheus, Grafana, Loki, Pyroscope, Alloy + purpose-built exporters
Agents MCP server exposing AF-specific tools to any MCP client

Component status

Whether the ref behind each component holds what is on main (which ref each root deploys; unreleased).

Core — platform

af-users-graph af-x509-secrets database-backup jupyterhub jupyterhub-ssh userlist-sync grafana prometheus storage pixi-global-sync

Experimental

agentic-interface dask-gateway flyte interlink-hammer interlink-nrp interlink-traefik agentic-analysis af-monitoring alloy loki pyroscope servicex-anvil servicex-eos supersonic supersonic-af supersonic-interlink supersonic-interlink-nrp model-manager kuberay-operator ray-train krab mattermost-agent

Images — which tag each one ships on: RELEASING.md.

purdue-af agentic-interface af-pod-monitor af-node-monitor agentic-analysis supersonic-model-manager interlink-slurm-plugin interlink-kubernetes-plugin ray-nrp

Environments — released with the purdue-af image the hub runs.

pixi-base pixi-global

Reading the badges:

  • released — the Flux source holds this commit, which is a fact about git, not the cluster: a delivery that fails appears under the delivery component of the Alerts dashboard
  • awaiting release — validated, and only a release stands between it and the Flux source
  • validating — CI has not finished on those commits yet
  • failed CI — do not release; the drift is broken
  • the trailing number is how many commits it has moved since it was released
  • a leading X.Y.Z is the released version, for images on a version stream and the environments they ship

Recomputed after every CI run on main, after every release, and hourly by component-status.yml; the badge data lives on the status branch, so keeping it current never touches main.

How a change reaches the cluster, version rules and rollback: RELEASING.md.

About

Purdue Analysis Facility

Resources

Stars

8 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages