Eugo for org owners
Oversee plans, billing, and organization-wide settings
Courses for this role
Ordered as they appear in the catalog; any of them can be taken on its own.
What you will actually cover
Every lesson in those courses, so you can see the ground before committing to it.
Vocabulary you will meet
The terms these courses use, defined.
- High-performance computing (HPC): Running work across many machines at once so it finishes far sooner. The technique behind weather models, genomics, and large-scale simulation.
- HPC as a service (HPCaaS): High-performance computing consumed on demand rather than owned: request compute for one run, stop paying when it ends. No hardware, no scheduler to run.
- Distributed computing: Splitting one job across several machines that work on it simultaneously. The core technique of HPC, and what the distribute decorator gives you in Python.
- Job scheduler: The queueing system on a traditional HPC cluster that decides when a submitted job runs. Eugo has no queue: you launch a cluster and dispatch work to it.
- Activity log: The record of actions taken inside an organization: who created a workspace, changed a role, or launched a cluster.
- Billing period: The interval over which an organization’s compute usage is accumulated and charged.
- Cluster: A set of machines, one head node and one or more compute nodes, launched together to run distributed work.
- Compute node: A machine in a cluster that executes tasks. Compute nodes do the work; the head node coordinates it.
- EugoHPC Manager: The panel inside EugoIDE used to launch, monitor, and shut down clusters.
- EugoIDE: The browser-based notebook environment where you write and run Python on Eugo. Built on JupyterLab, connected to compute in your workspace.
- Head node: The machine in a cluster that coordinates work: it schedules tasks onto compute nodes and tracks their results.
- Interactive session: A running EugoIDE instance attached to your workspace. It is where you write code; a cluster is what runs it at scale.
- Member: A user who belongs to an organization. What a member can do is governed by their assigned role.
- Object storage: Storage reachable by every node in a cluster. Inputs must live here, or in workspace storage, rather than on one machine’s local disk.
- Organization: The top-level account that owns one or more workspaces and is the unit of billing. Members belong to an organization and hold roles within it.
- Persistent storage: Workspace storage that survives between interactive sessions. Files saved elsewhere in a session are lost when it ends.
- Pricing plan: The tier assigned to a workspace, which governs its resource limits and concurrency: how much can run, and how much can run at once.
- Role: The permission level a member holds in an organization, determining what they can change rather than only what they can see.
- Administration: The operational side of Eugo: managing members and roles, monitoring usage, and reviewing activity logs.
- Usage: Accumulated compute consumed by an organization in a billing period, shown against plan limits on the dashboard.
- Workspace: An isolated compute environment with its own persistent storage, preinstalled libraries, and resource allocation. Where your sessions and clusters run.
- Notebook: A document interleaving code, output, and prose. The primary interface for writing Python in EugoIDE.
- Dashboard: The first page you see when opening an organization. Aggregates workspace status, plan usage, and recent activity.
- Idle cluster: A cluster still running after its work finished. It bills at the full rate, and is the largest avoidable cost for most organizations.
- Independent work: Units of work that can each produce their result without needing another unit’s output. A precondition for distributing anything.