> ## Documentation Index
> Fetch the complete documentation index at: https://dpos.xdr.ooo/llms.txt
> Use this file to discover all available pages before exploring further.

# Requirements

> Current validated Mirror Server baseline, network paths, credentials, and DP safety requirements.

# Requirements

## Mirror Server baseline

Use a clean **Ubuntu 24.04 LTS amd64** system.

| Requirement            | Current baseline                                                        |
| ---------------------- | ----------------------------------------------------------------------- |
| CPU                    | 2 vCPU minimum; 4 vCPU recommended                                      |
| Memory                 | 4 GB minimum; 8 GB recommended                                          |
| Disk                   | **100 GB total** for the current artifact set                           |
| IP address             | Stable IPv4 reachable by all DP hosts                                   |
| DP → Mirror Server     | TCP **80**                                                              |
| Mirror Server outbound | HTTPS to GitHub, Ubuntu bootstrap repositories, Cloudflare R2, and ACPS |

Current artifact sizes are approximately:

* OS Core / selective mirror: **3.4 GiB**
* DP 6.6.0 Phase 2 bundle: **28.2 GiB**
* fresh Download and Prepare peak: approximately **70 GiB** including build overhead and reserve

The application performs a free-space preflight. The 100 GB value is the validated baseline for the current artifact set, not a guarantee for future releases.

## Credentials

The Mirror Manager requires:

* ACPS username and password
* one common `aella` worker SSH password when worker nodes are configured

ACPS credentials are stored root-owned with mode `600` in:

```text theme={null}
/etc/ubuntu-mirror/dp-upgrade-mirror.conf
```

Application logs redact credentials.

## Network requirements

Mirror Server outbound access is required for:

* GitHub for initial clone and source updates
* `https://xdrsolutions.uk` for the R2 OS Core package in Full mode
* the configured/fixed ACPS endpoint for Phase 2 artifacts
* Ubuntu repositories required to bootstrap the Mirror Server itself

DP hosts only need access to:

```text theme={null}
http://<MIRROR_SERVER_IP>:80
```

DP hosts do not require direct R2 or ACPS connectivity.

## DP safety prerequisites

Before running destructive DP commands:

* create a full hypervisor snapshot of every DP VM
* verify the Mirror Server readiness result is `PASS`
* use the current Menu 7 commands generated for the active Mirror Server IP
* confirm the maintenance window is large enough to complete the required LTS hops and Phase 2
* preserve `/opt/aelladata` and do not treat intermediate Ubuntu releases as rollback points

The supported recovery method for destructive failure is the hypervisor snapshot.