> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/server-os-deployment-guide/appendix/glossary.md).

# Glossary

This chapter provides contextual definitions for the key technical terms used throughout this guide.

### **BIOS (Basic Input/Output System):**&#x20;

* The first software that runs when you power on a server. Its primary job is to initialize the hardware (like checking memory and disks) and then hand off control to the operating system. In this guide, you interact with the BIOS to change fundamental settings like the boot order and security options.

### **BMC (Baseboard Management Controller):**&#x20;

* A small, independent computer-on-a-chip on the server's motherboard. It runs its own operating system and has its own dedicated network connection. This allows you to manage the server remotely as if you were physically present, providing critical features like power control, health monitoring, Virtual Media, and the KVM console, even when the main server is powered off or has no OS installed.

### **Chassis:**&#x20;

* The physical metal frame and enclosure that houses all the server's components. In a multi-node system, a single chassis can contain several independent server nodes, sharing power and cooling.

### **GPU (Graphics Processing Unit):**&#x20;

* A specialized processor designed to handle complex mathematical calculations in parallel, making it ideal for accelerating AI and machine learning workloads. While they also render graphics, their primary role in an AI server is high-performance computing.

### **KVM (Keyboard, Video, Mouse):**&#x20;

* A feature, provided by the BMC, that allows you to see the server's video output and control its keyboard and mouse remotely through a web browser. It is your virtual "eyes and hands" for interacting with the server during OS installation and troubleshooting.

### **Node:**&#x20;

* A complete, self-contained server with its own CPU, memory, and storage, housed within a larger chassis. For the purposes of this guide, you can think of each node as an individual computer that requires its own operating system installation.

### **PSU (Power Supply Unit):**&#x20;

* The hardware component that converts AC power from an electrical outlet into the regulated DC power used by all the components inside the server chassis. Enterprise servers often have redundant (multiple) PSUs for high availability.

### **Rack:**&#x20;

* A standardized steel and aluminum frame used in data centers to house and organize servers, networking equipment, and other hardware modules. Servers are mounted into the rack to save space and streamline management.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.engenius.ai/server-os-deployment-guide/appendix/glossary.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
