OpenSDL Hub

OpenSDL Hub is a public catalog of virtual-laboratory assets. Search for an asset, inspect its model preview and versions, then copy the detail page's lab pull command to retrieve the original package. The current Test catalog is available at hub.test.sciol.ac.cn, and UAT is available at hub.uat.sciol.ac.cn. Browsing and public asset pulls require no login.

For your first asset, install lab CLI and follow the Quick Start to pull, validate, and reuse it offline.

How the components work together

ComponentResponsibility
OpenSDLDefines asset.yaml, OCI asset packages, validation rules, and device runtime interfaces
lab CLIValidates, builds, splits, inspects, pushes, pulls, caches, and materializes assets locally; its daemon owns the local store
OpenSDL HubIndependently hosts the public catalog, versions, previews, and publication admission; an OCI registry distributes package bytes
LiyanLabsQueries remote Hub models for its simulation interface and operates devices through the selected Desktop / Runner

The Hub website and registry are separate entry points. The website/API uses hub.test.sciol.ac.cn or hub.uat.sciol.ac.cn; the detail page's pull_reference uses the hub.sciol.ac.cn OCI Registry. Preserve the complete OCI reference, including its registry host and digest, and do not rewrite the web host by hand.

Delivery channels

The current Test service is hub.test.sciol.ac.cn. A successful main check builds immutable API/Web images, runs the migration, deploys Test, and publishes a verified image receipt. UAT is hub.uat.sciol.ac.cn and is promoted manually from that exact receipt; it uses an independent database and the same API/Web digests. Production has no automatic target.

Versions and publication

Published versions cannot be overwritten. An @sha256:... reference identifies exact package content, so different machines can pull the same bytes. The browser GLB preview and the package's glTF / OpenUSD source serve different purposes.

Publication includes preparing and validating the asset, running lab build (or lab pack) and lab push, uploading previews, and completing Hub admission. lab push uploads to the registry; listing the package in the public catalog also requires the remaining publication steps and separate write credentials. Public browsing and pulling grant no publication authority.

Current usage boundaries

lab pull --output restores a package into a local directory for downstream tools. It does not create a simulation or device instance automatically. LiyanLabs set_asset stores a visual model reference and the interface loads its preview; physics assembly and simulation execution require a separate runtime integration.

The public CLI provides asset packaging, distribution, caching, and validation. Local asset management adds inventory, tags, removal, and safe garbage collection. Runtime instances provide create, start, stop, restart, and remove for runnable kinematic packages. The v0.3.1 release ships the daemon and Docker-style shortcuts. Public pulls require no account; publication still requires separate write credentials.