Single-binary dashboard for OpenStack (and VMware vCenter / ESXi / Cloud Foundation), written in Rust with an embedded React UI. Rassvet (рассвет) means "dawn".
-
Backend: Rust (axum + tokio + reqwest). Keystone tokens stay on the server; the browser gets an opaque HttpOnly session cookie.
-
Frontend: React + TypeScript + Tailwind, built into
ui/distand embedded into the binary. -
OpenStack: targets 2026.2 (Hibiscus) APIs, oldest supported release 2026.1 (Gazpacho). Microversions are negotiated per cloud.
-
Core services: Keystone, Glance, Nova, Placement, Neutron, Cinder, Barbican.
-
Extensions: other services (Octavia load balancers, Magnum Kubernetes clusters, Designate DNS, and Monitors: instance and physical server dashboards from Prometheus, defined in YAML) are compile-time extension crates under
extensions/. -
Cloud platforms: each
[[cloud]]has aplatform:openstack(default),vcenter,esxiorvcf. Signing in is two steps: pick the platform, then fill in that platform's form (Keystone password / TOTP / application credential for OpenStack; user name and password for VMware). Each platform has its own client crate undercrates/clients/. VMware clouds show an overview (product, VMs, hosts, clusters, datastores…) for now; their resource pages come next.
The user guide is in docs/: a feature overview, step-by-step guides for
project users (docs/project) and for cloud administrators (docs/admin).
crates/clients/openstack OpenStack client (rassvet-os-client): Keystone, Glance, generic REST, catalog, microversions, API errors
crates/clients/vsphere VMware vSphere client: vCenter Automation REST API, ESXi vim25 SOAP sign-in
crates/clients/vcf VMware Cloud Foundation client: SDDC Manager tokens and inventory
crates/ext-api Extension contract (Extension trait, NavItem, RequestContext, ApiError)
crates/server rassvet binary: config, sessions, core API, embedded UI
crates/server/src/platform Sign-in, sign-out and overview of non-OpenStack clouds (vsphere.rs, vcf.rs)
extensions/octavia Reference extension: Rust crate + ui/ (React pages)
extensions/magnum Kubernetes clusters (Magnum): gateway, kubeconfig signing + ui/
extensions/designate DNS zones (Designate): gateway, zone file import / export + ui/
extensions/monitors Monitors: dashboards from Prometheus; panels/default.yaml = built-in panels + ui/
ui/ Host UI (Vite + React); `@rassvet/sdk` is the API exposed to extension UIs
ui/src/platforms/ Platform picker and one folder per platform (openstack/, vsphere/, vcf/): sign-in forms, overview
Requirements: Rust 1.88+ (edition 2024), Node 22+, pnpm 10+.
cd ui && pnpm install && pnpm build && cd ..
cargo build --release
./target/release/rassvet --config rassvet.tomlCopy rassvet.example.toml to rassvet.toml and set your Keystone auth_url.
Build without an extension: cargo build --release --no-default-features.
By default login sessions live in the server's memory (a restart signs everyone out). Add a
[memcached] section to keep them in memcached instead, so they survive restarts and can be
shared by several Rassvet instances behind a load balancer:
[memcached]
servers = ["10.0.0.11:11211", "10.0.0.12:11211"]
key_prefix = "rassvet"
timeout_ms = 500
secret_key_file = "/etc/rassvet/session.key" # or secret_key = "…" (≥ 16 chars, same on every instance)- Sessions are encrypted with ChaCha20-Poly1305 when a secret key is set (they contain Keystone
tokens); keys are a hash of the cookie, so neither appears in memcached. A key is required:
without one Rassvet refuses to start, unless
allow_unencrypted = true(plain JSON, not recommended). - Memory stays the fallback: if memcached isn't configured, can't be reached at startup, or fails later (per-request timeout, then the server is skipped for 15 s), logins and requests keep working from memory. Sessions created meanwhile, or lost by a memcached restart, are written back once it answers again. Logging out leaves a short tombstone so other instances drop their copy.
- Sessions are deleted, from memory and from memcached, at the first of: no request for
session_idle_minutes(default 60),session_max_minutesafter login however active (default 720; 0 = no limit), or the expiry of the Keystone token. The memcached TTL is set to exactly that deadline (the idle part is refreshed at most once a minute), and memory is swept everysession_cleanup_seconds(default 60). An expired session found on a request is deleted at once.
A session can be signed in to several [[cloud]]s at once: the UI's cloud menu signs in to another one
(POST /api/session/clouds) and switches between them without signing in again. Each request names its
cloud in the X-Rassvet-Cloud header (downloads: ?rassvet_cloud=), so every browser tab can work on its
own cloud; requests without it use the cloud chosen last. Each cloud keeps its own Keystone tokens: when one
expires only that cloud is signed out, and the session lasts until its last token expires (or the idle and
maximum limits above). Cloud ids must be letters, digits, -, _ or .. Sessions stored in memcached by
older versions are still read after an upgrade.
- Run behind HTTPS and set
[server] secure_cookies = true: the session cookie becomesSecureand responses carryStrict-Transport-Security. Rassvet warns at startup when it is off on a non-loopback address. - The browser holds only an opaque, HttpOnly, SameSite=Strict session cookie; Keystone tokens
stay on the server. Changes need the
X-Rassvet-CSRFheader and are refused when the browser reports a cross-site origin (Sec-Fetch-Site). API responses areno-store. - Sign-in is throttled per account: after 10 failed attempts in 15 minutes the account's
sign-ins are refused (429,
Retry-After) until the window ends; a success resets it. Each instance counts on its own; Keystone's own lockout ([security_compliance]) still applies. - OpenStack calls follow redirects only within the same origin and pagination links only on the same endpoint, so the token is never sent to another host.
- Object downloads are attachments with
Content-Security-Policy: sandbox; Swift object names with./..segments are refused (they would address another path). - Image import from a URL (
web-download) is fetched by Glance, not Rassvet: restrict it in glance-api.conf ([import_filtering_opts]allowed schemes, hosts and ports) so users can't reach internal addresses.
Some menu entries are only shown when the cloud's policy lets the user use them: Rassvet asks the
service once (e.g. GET groups/detail?limit=1 for Volume groups / Group snapshots) and hides the
entry on 401, 403 or 404. Results are kept for 10 minutes per user, project and region.
[log] sets the level (info, debug… or a full filter; RUST_LOG overrides it), the format
(text or json), standard output and an optional file that rotates hourly, daily or by
size (rotation = "size", max_size_mb), keeping max_files rotated files
(rassvet.log.2026-10-22T05-00-00). With rotation = "never" an external logrotate can move
the file and send SIGHUP; Rassvet reopens it.
Every browser request gets an id like req-6df3735c-…: it is in every log line written while
the request runs, returned as the X-Request-Id header, and sent to OpenStack as
X-OpenStack-Request-ID, which oslo.middleware records as the global_request_id in Nova,
Neutron, Cinder… logs. Each OpenStack call is logged (rassvet::openstack) with the service,
method, path, status, time and the service's own request id (upstream_request_id, the
x-openstack-request-id / x-compute-request-id header), which is also returned in API errors:
INFO request{request_id=req-6df3…}: rassvet::openstack: OpenStack call service="compute" method=GET path="/compute/v2.1/servers/…" status=404 ms=3 upstream_request_id="req-6b79…"
INFO request{request_id=req-6df3…}: rassvet::http: request method=GET path="/api/os/compute/servers/…" status=404 ms=12
cargo run -p rassvet -- -c rassvet.toml # API on :8080
cd ui && pnpm dev # UI on :5173, proxies /api to :8080
cargo test && cargo clippy --all-targetsextensions/<id>/Cargo.toml+src/lib.rsimplementingrassvet_ext_api::Extension(manifest with requiredservice_types, nav items, axum routes mounted at/api/ext/<id>). Handlers takeRequestContextto get the endpoint and an authenticated request builder.extensions/<id>/ui/index.tsxdefault-exporting anExtensionUi(routes mounted at/ext/<id>/...). Import shared components and the API client only from@rassvet/sdk.- Add the crate to the workspace, add an
ext-<id>feature incrates/server/Cargo.toml, and register it incrates/server/src/extensions.rs.
An extension is shown only when all its service types have endpoints in the user's current region.
Besides routes, an ExtensionUi can contribute to features the host owns. Each contribution lives in its
own file of the extension, so the host has no extension-specific code (see extensions/magnum/ui/ for all
three):
extensions/<id>/ui/
index.tsx routes + the contributions below
palette.ts palette: PaletteContribution (command palette)
terraform.ts terraform: TerraformContribution (Operations › Export to Terraform)
cleanup.tsx cleanup: CleanupContribution (Operations › Cleanup)
- Command palette —
keywords(extra words that find the extension's pages),actions("Create …" entries;pathis relative to/ext/<id>) andresources: oneResourceKindper kind of resource, withaliases(for<alias>:<name>searches, e.g.vol:db),get(id)to find it by a pasted UUID,search(q)(the API filters names) orlist()(cached, matched here), andpath(row, ctx)to open it (ctx.baseis/ext/<id>or/admin/ext/<id>). The host's own kinds are inui/src/lib/palette.ts; a list page without a detail page can be opened on one row withfindPath(list, id)(?find=<id>). - Export to Terraform —
useSource({ projectId })is a hook that loads the extension's resources and returns aTfSource:sections(the pickable lists; kinds named<id>.<kind>),dependencies(what a picked resource needs, core kinds included),namesandgenerate, which write blocks with theTfGenhelpers (block,attrs,str,network,subnet,image,keypair,variable…) so references to exported resources, lookups and import blocks work like the core ones. - Cleanup —
useFindings(ctx)is a hook returningFinders (a card and the table it opens). The context carries the view (admin,projectId), the chosen age (idle(...timestamps)) and the helpers that make the tables look like the host's (table,projectCol,ageCol).
Contributions are optional; the host only calls those an available extension provides.