Docs menu

The runtimes in your cloud

Some of what OpenX runs for your workspace runs in your own Azure subscription, inside your landing zone, so nothing you deploy relies on Fathym being up. Each of these runtimes is a container that OpenX deploys into your landing zone when you press Deploy.

RuntimeOne perWhat it does
Workspace RuntimeworkspaceRuns your workspace's own jobs in your cloud: live streams, scheduled reports, Provenance, archives and logs
Surface runtimesurfaceRuns a surface's saved warm queries and download exports, so the data they read never passes through Fathym

What works today: the Workspace Runtime starts and answers its status check; its jobs move into it one by one. The surface runtime is being built. Neither has been deployed to a customer's Azure yet. This page is written to what is being built, and says which parts are not there yet.

Configured only by your workspace

A runtime in your cloud reads one thing at start: your workspace's own configuration, written for it at Deploy and mounted into its container as a file, with the fingerprint it was deployed with. It never asks Fathym for its configuration, never reads Fathym's settings, and signs in to Azure only with its own managed identity in your subscription, never with a password or a stored key.

Running without OpenX is how the runtime is built, not a rule on what you write: a setting or configuration that names a Fathym address, such as OpenX's own sign-in as your App Identity provider, is not refused. The relay worker's outbound link to Fathym's relay, which lets OpenX's screens reach your private runtimes without opening a port into your network, comes with the relay worker, in a later release.

When a runtime refuses to start

A runtime checks its settings and configuration when it starts. If anything is wrong it does not start, and its log names every reason at once, each with the setting names or paths involved and never their values:

CodeMeansWhat to fix
REVISION_UNREADABLEThe workspace configuration file could not be read, or is not a configurationPress Deploy again so the configuration is written again
REVISION_HASH_MISMATCHThe configuration file is not the one this runtime was deployed withPress Deploy again; do not edit the mounted file by hand
REVISION_EMPTYThe configuration holds nothingPress Deploy again
REVISION_KEY_OUTSIDE_ALLOWLISTThe configuration holds a part this runtime does not runPress Deploy again; a configuration edited outside OpenX is refused
STEWARD_ENV_PRESENTA setting would make the runtime load its configuration from Fathym instead of the fileRemove the named settings from the container
CREDENTIAL_NOT_MANAGED_IDENTITYA client secret, certificate or password is set for the runtimeRemove the named settings; the runtime signs in with its own managed identity

Two more refusals come from reading the runtime's own settings and its job block: RUNTIME_ENV_INVALID names each setting that is missing or malformed, and PROCESSOR_BLOCK_INVALID names each path in the job block that is malformed. Fix the named setting or press Deploy again.

On fathym.com: OpenX →

On this page