Glossary

The installed Virtual Appliance deployment, including its nodes, cluster services and ERS workload.

The stable customer-facing name of an installed appliance. It distinguishes the appliance in monitoring and remains the same across appliance updates.

A virtual machine that runs Talos and the installed appliance services. It is separate from the Management host.

A sensitive archive of configuration and administrative access material for one appliance. Use it to reconnect Management. It is not an appliance backup.

An archive containing appliance state and a record of the configuration and software captured in one coordinated backup run.

The six-hour period during which Management retains an artifact bundle and may use its cluster credentials. It is separate from a browser sign-in session.

Uploading a valid artifact bundle again to start a new access period. It does not rotate credentials.

Ending the current access lease and removing Management’s retained bundle. It attempts remote firewall closure but does not undo appliance changes or revoke downloaded credentials.

A downloadable archive of evidence and findings from one diagnostics run. Use it for investigation and support.

Enterprise Resource Security, the MTG application suite deployed on the appliance.

The first initialization of ERS and its PKI on an already installed appliance.

The destructive removal of active ERS application data and configuration so the installed appliance can accept new ERS initialization. This does not erase the appliance, external HSM objects, Git history or existing backups.

Installation of a new appliance without carrying forward a previous appliance’s Management configuration or installation and update history.

Keeping the desired appliance configuration in a repository, publishing it and applying it to the appliance.

Hardware security module. An HSM library supplies the vendor interface used by CARA. Uploading that library, activating it and configuring the HSM connection are separate tasks.

An operator-requested stop of installation. Cancellation is complete after execution stops and temporary workspaces are cleaned up. Changes already made to target machines remain.

The application used to install and administer one appliance. It runs on the Management host.

A signed-in user identified as a Gitea administrator by the current Management session.

The live boot medium for the Management VM. It contains the host operating system and embedded Management software and must remain attached for subsequent boots.

Reconstructing Management after losing the previous instance or access to it, while the installed appliance survives.

A captured appliance configuration delivered to its configured registries and selected for reconciliation. Publication alone does not confirm that the configuration was applied or that workloads are healthy.

The backup, matching artifact and release bundles, and their version records needed to restore an appliance.

A backup bundle stored in Management’s bundle list for selection during appliance recovery.

An executable image that installs one appliance release. Release content contains its prebuilt dependencies.

The dedicated persistent disk used by the Management VM for host settings, application data, credentials and runtime caches.

The versioned noCloud ISO or VMware OVA used to boot appliance targets before Management installs them. Use the artifact selected by the installation wizard.

An executable image that applies one exact source-to-target appliance update. It is separate from a Management ISO update.