mirror of https://github.com/NVIDIA/OpenShell.git synced 2026-10-16 05:20:22 +08:00

Files

T

History

Eric Curtin 29e2539abb refactor: deduplicate shared utilities across driver crates (#1660 )

Move three duplicated definitions into openshell-core so every
consumer has a single canonical source:

- format_bytes: identical 14-line function existed in docker,
  kubernetes, and vm drivers. Moved to openshell-core::progress
  where all three already imported from.

- DEFAULT_SANDBOX_PIDS_LIMIT: i64 constant (2048) duplicated in
  docker driver and podman config. Moved to openshell-core::config
  alongside other shared defaults. Podman re-exports it for
  internal call-site compatibility.

- current_time_ms: secrets.rs in openshell-sandbox reimplemented
  the same logic as openshell-core::time::now_ms(). Remove the
  local copy and call now_ms() directly via the existing dep.

2026-06-01 15:38:15 -07:00

src

refactor: deduplicate shared utilities across driver crates (#1660 )

2026-06-01 15:38:15 -07:00

build.rs

feat(server): declare gRPC auth (mode + scope + role) at the handler, enforce at the router (#1596 )

2026-05-27 14:14:54 -07:00

Cargo.toml

feat(telemetry): add anonymous opt-out OpenShell usage telemetry (#1433 )

2026-06-01 14:35:51 -07:00

README.md

docs(architecture): reset subsystem docs (#1184 )

2026-05-07 08:59:02 -07:00

README.md

openshell-core

Shared types, constants, configuration, and helpers used across OpenShell crates.

Object Metadata

Top-level user-facing objects use a Kubernetes-style metadata convention. The metadata shape provides:

Stable server-generated ID.
Human-readable name.
Creation timestamp.
Optional labels for filtering and automation.

Code that works with object metadata should use the traits in openshell_core::metadata instead of reaching into protobuf fields directly:

use openshell_core::{ObjectId, ObjectLabels, ObjectName};

let id = sandbox.object_id();
let name = sandbox.object_name();
let labels = sandbox.object_labels();

Trait methods must tolerate missing metadata and return safe empty values rather than panicking.

Label Rules

Labels follow Kubernetes-style key and value conventions:

Keys may include an optional DNS-prefix followed by /.
Names are limited to alphanumeric characters plus -, _, and ..
Values use the same character set and may be empty.
Selectors use comma-separated key=value pairs with AND semantics.

Validate labels at API ingress before persisting objects.

Inference Profiles

Provider inference profiles live in this crate so the gateway, sandbox, and router agree on provider defaults. Profiles define:

Auth header style.
Default upstream headers.
Client-supplied passthrough headers.
Supported inference protocol shapes.

Do not duplicate provider-specific inference behavior in callers. Add shared behavior here, then consume it from the gateway, sandbox, and router.