Skip to content

Latest commit

 

History

History
99 lines (62 loc) · 7.19 KB

higher-ed-container-stories.md

File metadata and controls

99 lines (62 loc) · 7.19 KB

Higher-Ed Container & Orchestration Stories

A reading and viewing list of how universities and research organizations actually run containers — plus the talks, papers, and primers this workshop draws on. Use it to see the patterns from 02 — Containers in Higher Ed and 04 — Cloud & Orchestration in the wild.

Some links are recordings and decks from community sessions and may require sign-in.

Case studies from higher ed

Cornell — Dev to production with Amazon ECS

Containerized deployments on Amazon ECS, with SSM Parameter Store holding secrets and configuration. A namespace convention (custom apps → app name → environment) keeps IAM policies for container access simple, and each container declares the variables it needs — so the same image redeploys across environments with only its configuration changing.

University of Chicago (Gen3) — Workspace orchestration for biomedical research

A custom workspace orchestrator written in Go that spins up containers and their underlying infrastructure on demand and brokers networking/proxy traffic between cloud providers. Kubernetes-native by design (originally built for KubeCon).

Cornell — College of Veterinary Medicine — Kubernetes for a busy campus team

YAML defines the orchestration — storage, memory, and CPU limits — and containers ship through CI/CD (Bitbucket Pipelines). The story emphasizes iterating on resource limits with rolling deployments rather than getting them right the first time.

Lafayette College — Azure researcher & IAM in the cloud

Treats containers as the deployment model for "cookie-cutter" infrastructure-as-code, pursuing a SaaS-like operational experience instead of managing workload dependencies by hand — and highlights how cost-effective micro-workloads become in that model.

New York University — HPC and big data with containers

Makes the case for Singularity/Apptainer on on-prem HPC clusters: reproducibility, environment consistency across platforms, and applications that stay independent of the host OS — the reasons the Docker daemon was never the right fit on shared HPC.

University of Virginia (APTrust) — Modernizing legacy architectures

One container framework serves every service through environment-variable injection, with Parameter Store pushing configuration in and Route 53 handling DNS. Result: deployment time dropped from days to minutes, since a change is often just a variable update.

Carnegie Mellon University — Shibboleth IdP in AWS containers

A proof of concept running the Shibboleth Identity Provider on AWS ECS + Fargate: the motivation for moving identity to the cloud, a minimum-viable architecture, and where it could go next.

Research computing, HPC & Apptainer/Singularity

Kubernetes on campus

Learning Kubernetes & Helm

CI/CD & local development

Containers & OS fundamentals

Orchestration at scale — and when it breaks

Misc