Previous page

Next page

Locate page in Contents

Print this page

Terminology

This section describes some of the Agent terminology. Please take a moment to familiarize yourself with it so that you can use the documentation efficiently. The table below describes the commonly used terms:

Term

Description

Server

We use the term server to identify any computer, physical or virtual, in the Agent infrastructure. When we talk about a physical machine hosting Virtuozzo Containers, we may call it a Hardware Node or a host. When we talk about a Virtuozzo Container specifically, we call it a Container. Sometimes, however, we will be talking about servers in general. So, when you see the term "server", it could mean any server, physical or virtual.

Server ID

This is a globally unique ID that is assigned to any server in the Agent infrastructure. As soon as Agent is installed on a physical machine, it is assigned a Server ID. Every Virtuozzo Container that you create on it is also assigned a globally unique Server ID. The ID is guaranteed to be unique across computers and networks. Server IDs are kept internally by Agent and are used as references in all other API calls that perform operations on the servers.

Environment

Same as Server above. This is an obsolete term but it still can be seen in some of the Agent source code and data.

EID

Environment ID. Same as Server ID above. The term is obsolete but it is still being used in the Agent API code -- eid is the name of the parameter in calls that perform operations on physical and virtual servers.

Virtuozzo Container ID

Virtuozzo Container ID is a Virtuozzo-level ID, which is assigned to every Container when it is created. If you are familiar with the previous versions of Virtuozzo, this is the old-style "VPS ID". This ID is unique only within the context of a given Hardware Node. The ID is not to be confused with the Server ID described above, which is a universally unique Agent-level ID.

Virtuozzo group

Master Node

Slave Node

The term Virtuozzo group refers to a network of servers each running its own Agent software and interconnected with each other by means of internal Agent mechanisms. The servers in such a group are organized in a hierarchical structure where there's one Master Node and many Slave Nodes.

Master Node administers the entire group by allocating, monitoring, and controlling the group resources. Master is also capable of accessing any Slave Node in a group, meaning that once a client program is connected to the Master Node, it can send requests to any Slave Node in the group.

Realm

A Realm is a collection of parameters that define an authentication database containing the Agent user and group data. Agent supports a number of different databases, including operating system user registries and LDAP-compliant directories. Realm definitions are stored in the Agent configuration. Every Realm is assigned a universally unique ID by Agent when it is created.

Please send us your feedback on this help page