README
¶
Hanzo Visor
Cloud operating-system management platform (Go + React).
Architecture
Hanzo Visor has two parts:
| Name | Description | Language | Source code |
|---|---|---|---|
| Frontend | Web UI | JavaScript + React | https://github.com/hanzoai/visor/tree/main/web |
| Backend | RESTful API + Beego | Go + Beego + Postgres | https://github.com/hanzoai/visor |
Installation
Hanzo Visor uses Hanzo IAM as the authentication system. Create an organization and an application for Visor in your IAM instance, then wire it via app.conf.
Necessary configuration
Get the code
git clone https://github.com/hanzoai/iam
git clone https://github.com/hanzoai/visor
Setup database
Visor stores users, nodes, and resource information in a Postgres database named visor (auto-created). The DB connection string is configured in conf/app.conf:
dataSourceName = postgres://user:pass@localhost:5432/visor
Configure IAM
After creating an organization and an application in Hanzo IAM, update clientID, clientSecret, iamOrganization, and iamApplication in app.conf.
Run
go run main.go
Open browser: http://localhost:16001/
Optional
RDP
Run guacd for RDP connections:
docker run --name guacd -d -p 4822:4822 guacamole/guacd
License
Documentation
¶
Overview ¶
Command visor is the Hanzo Visor cloud compute/VM/GPU management service: zip-native on the hanzoai/orm store. It serves two addresses — the HTTP edge the ingress reaches, and the canonical ZAP socket the rest of the fleet dials it by name on.
Run it with no arguments to serve (the container contract); `visor version` prints the build version.
Source Files
Directories
¶
| Path | Synopsis |
|---|---|
|
fleet.go is the fleet-billing orchestrator — the ONE place the three connected- compute tiers are metered, all through the canonical commerce/metering path (service.NewMeteringClient), per org+project, so a customer sees ONE invoice however their compute is connected:
|
fleet.go is the fleet-billing orchestrator — the ONE place the three connected- compute tiers are metered, all through the canonical commerce/metering path (service.NewMeteringClient), per org+project, so a customer sees ONE invoice however their compute is connected: |
|
validator.go reads the hanzo.network (the Hanzo EVM) mainnet validator set — the source of truth for the FREE fleet-billing tier.
|
validator.go reads the hanzo.network (the Hanzo EVM) mainnet validator set — the source of truth for the FREE fleet-billing tier. |
|
Package conf is visor's ONE configuration reader.
|
Package conf is visor's ONE configuration reader. |
|
compute.go is the canonical /v1 resell compute surface: the cached DigitalOcean catalog (regions/sizes/GPUs, resale-priced) and per-org machine operations backed by Hanzo's house DO account.
|
compute.go is the canonical /v1 resell compute surface: the cached DigitalOcean catalog (regions/sizes/GPUs, resale-priced) and per-org machine operations backed by Hanzo's house DO account. |
|
Package logs writes visor's leveled log lines.
|
Package logs writes visor's leveled log lines. |
|
tenant_context.go is the ONE source of truth for the tenant-hierarchy request scope (org > app > project, plus tenant/actor/env).
|
tenant_context.go is the ONE source of truth for the tenant-hierarchy request scope (org > app > project, plus tenant/actor/env). |
|
pkg
|
|
|
visor
Package visor exposes visor's in-process bootstrap so a parent binary (github.com/hanzoai/cloud) can mount visor's /v1 surface in the same address space — the same routers, controllers and filters the standalone server runs, minus the listener.
|
Package visor exposes visor's in-process bootstrap so a parent binary (github.com/hanzoai/cloud) can mount visor's /v1 surface in the same address space — the same routers, controllers and filters the standalone server runs, minus the listener. |
|
analytics.go is the ONE path by which visor rolls compute fleet/spend events into hanzoai/datastore (hanzo.compute_usage, ClickHouse) — the ANALYTICAL plane that mirrors, but is orthogonal to, the OPERATIONAL commerce ledger (tenant-data-hierarchy HIP).
|
analytics.go is the ONE path by which visor rolls compute fleet/spend events into hanzoai/datastore (hanzo.compute_usage, ClickHouse) — the ANALYTICAL plane that mirrors, but is orthogonal to, the OPERATIONAL commerce ledger (tenant-data-hierarchy HIP). |
|
instrument.go is the small, typed instrumentation API the rest of visor calls.
|
instrument.go is the small, typed instrumentation API the rest of visor calls. |