An auth source defines a user management authority (GitLab, Google, OpenID) for a Verge.io environment. This allows a single sign-on experience for users as credentials from the defined auth source can be appointed for users to login to a Verge.io envrironment.
Breadcrumbs are links at the top of the screen that reflect the recent history of selected sections; these links provide quick access back to previous screens.
A catalog is a group of related recipes. For example one catalog may contain many varied Windows vm recipes, while another catalog in the same repository could contain all Linux based vm recipes. Administrators can group recipes into catalogs in whatever way makes sense for their particular organization.
A cluster is a group of nodes (physical or virtual) with like hardware resources, used as a pool for storage, compute or HCI functions. A single Verge.io environment can contain a variety of different clusters to provide an array of performance/costing options. The resources of a single cluster can be divided up among multiple tenants and a single tenant can be given resources to multiple clusters within the same environment.
Media images are files uploaded to the Verge.io vSAN to make available inside the Verge.io environment. Common files uploaded are those used for installing new virtual machines (e.g. *.iso) or importing Machines or drives from existing systems (e.g. *.ova, *.ovf, *.raw, *.qcow, *.vmdk, etc).
Nested Multi-Tenancy provides individual layers of secure tenancy. The host can allocate any portion of its physical resources to child tenants and those child tenants can then divide and apportion any of its resources down to its own child tenants.
A repository is a site collection of recipe catalogs. Typically, a tenant has access to a repository provided by its service provider. Each tenant can also create a local repository to store its own recipe catalogs. The Verge.io repository is also included by default on a Verge.io installation. The Verge.io repository includes the standard NAS Service VM and a "30 Day Trial POC" tenant.
Scale out is the process of adding net new additional resources to an environment. I.E, adding another storage or compute node would be considered a scale out process.
Scale up is the process of adding hardware into already existing nodes of an environment. I.E, adding more drives to a storage node or increasing RAM in a compute node would be considered a scale up process.
A snapshot captures the state of an entity at a particular point in time. Snapshots can be used to create a point-in-time capture of an entire environment, tenant, individual virtual machine, or a NAS volume. Snapshots allow "rolling back" a system, which can be helpful for recovery, development and testing purposes.
A snapshot profile defines a schedule for snapshot creation and cleanup.
A storage tier is a pool of storage with equivalent underlying physical storage devices. Storage tiering is a feature built into the Verge.io vSAN allowing splitting data between different types of physical media based on requirements for performance, accessibility, capacity and cost. Storage tiering can dramatically reduce costs by taking better advantage of more expensive disk where it's most needed while using less expensive (e.g. spinning disk) for cold storage.
Subscriptions allow for monitoring a system (or components of a system) by defining system information to send to users via email.
Subscription profiles define the aspects of a subscription (on demand/scheduled, trigger criteria/schedule). Many subscription profiles are pre-loaded by default with the Verge.io install. Custom subscription profiles can also be created with knowledge of the API.
A virtual wire is the logical process of plugging a cable into a switch. Creating a virtual wire enables the ability to pass a layer 2 network into a tenant.