Node Documentation: pterodactyl

This document describes the hardware, operating system, Pterodactyl configuration, and hosted services for the node named pterodactyl.

This document should be updated when the node hardware, operating system, status, location, resource allocation, network configuration, or hosted services significantly change.

Node Identity

Node Name:

pterodactyl

Role:

Pterodactyl panel host
Wings node host

Current purpose:

• Hosts the Pterodactyl panel.
• Runs a Pterodactyl Wings instance.
• Hosts Minecraft servers.

The node name reflects its original deployment purpose as the host for the Pterodactyl panel. The name is retained for consistency with the existing deployment.

Status:

Active

Location:

us.pa.gallitzin.loc1

The location name follows the internal Pterodactyl infrastructure naming convention.

Physical Host

Hardware

CPU:

2x Intel Xeon E5-2667 v4

CPU Architecture:

x86_64

RAM:

384 GB ECC RAM

Memory Configuration:

48x 8 GB ECC DIMMs

Manufacturer:

Dell

Model:

PowerEdge R730xd

Firmware and Management Controllers

BIOS Version:

2.19.0

Management Controller:

Dell iDRAC8 Enterprise

Management Controller Firmware:

2.86.86.86

Storage Controller:

Dell PERC H730 Mini (Embedded)

Controller Cache:

1 GB battery-backed cache

Storage Controller Firmware:

25.5.9.0001

CPU Topology

The server contains:

2 CPU sockets

Each CPU:

8 physical cores
16 logical threads

Total:

16 physical cores
32 logical threads

CPU pinning may be configured on individual server allocations when latency-sensitive workloads require predictable CPU placement.

The following is an example CPU pinning allocation and does not represent a node-wide CPU reservation:

0,2,4,6,8,16,18,20,22,24

This allocation represents:

• Five physical cores from one CPU socket.
• The corresponding Hyper-Threading sibling logical CPUs.

This does not reserve these cores exclusively at the operating system level; it restricts the assigned container workload to these logical CPUs.

This allows a server workload to be constrained to a known CPU topology while still utilizing both logical threads of the assigned physical cores.

CPU topology should be considered when changing allocations to avoid unnecessary contention between latency-sensitive game servers.

Memory

Total host memory:

384 GB ECC RAM

Memory is shared between:

• Pterodactyl services.
• Wings-managed containers.
• Operating system usage.
• File caching.
• Other system services.

Individual game servers should not be allocated enough memory to exhaust available host resources.

Operating System

Operating System:

Debian 13

Swap Configuration:

Approximately 120 GB swap partition

The swap partition is configured as part of the Debian host installation and is managed by Debian.

Future operating system changes should be documented if this node is upgraded or replaced.

Storage

Primary Storage Volume:

/dev/sda2

Filesystem usage:

Root filesystem

Array Configuration:

RAID-10 logical volume

Raw Array Capacity:

Approximately 4.8 TB

Usable Logical Capacity:

Approximately 2.1 TB

Drive configuration:

24x 200 GB SSDs

Drive Hardware:

Dell-branded Toshiba SSDs

Drive Model:

THNSF8200CCSE

Purpose:

• Container storage.
• Game server data.
• Pterodactyl application data.
• System storage.

Pterodactyl Configuration

Panel:

Self-hosted Pterodactyl Panel

Panel Version:

1.14.1

Wings Version:

1.13.1

The node hosts the self-hosted Pterodactyl Panel and runs a registered Wings node within the deployment.

Resource Allocation

Resource management for this node is handled through Pterodactyl server allocations.

CPU Limit:

Unlimited

CPU Pinning:

Managed per server allocation.

Memory:

Shared host resource

Disk:

Managed through Pterodactyl allocations.

Hosted Services

Current services:

Additional workloads may be assigned if resource availability and compatibility requirements permit.

Network Configuration

Public services hosted on this node are exposed through externally managed hostnames.

Current network features:

• DNS records.
• SRV records (where applicable).
• DDNS hostname updates (where applicable).

Reverse proxy:

Not currently used

Service-Specific Network Requirements

No additional service-specific network requirements are currently configured.

Additional service ports should be documented in the corresponding server environment documentation if deployed.

Backup Storage

Backup storage is separated from container storage through a dedicated backup directory.

Pterodactyl backup storage path:

/mnt/backups/wings/

Purpose:

• Stores Pterodactyl-generated server backups.
• Keeps backup data separate from container storage.
• Allows backup storage to be managed independently from server allocations.

Backup configuration such as retention limits, schedules, and enabled backups is managed at the individual server level and is documented in the corresponding server environment documentation.

External Mounts

The node allows mounts from:

/mnt/backups/

This allows servers to use dedicated external storage directories while maintaining a single approved mount path in the Wings configuration.

Example:

Host:

/mnt/backups/minecraft-world-backups/<server-name>

Container:

/home/container/simplebackups/

Purpose:

• Keeps application-specific backups outside the container.
• Prevents Pterodactyl backups from recursively including generated backup archives.
• Allows multiple applications to share a structured backup storage location.

Migration Considerations

Servers may be migrated between Wings nodes.

Before migrating servers from this node, verify:

• Required storage exists on the destination node.
• External mounts are available.
• Backup paths are accessible.
• CPU and memory allocations are supported.
• Network requirements are available.
• Pterodactyl Panel availability is considered during migration planning.

Maintenance Notes

When making changes to this node:

• Update this documentation after significant changes.
• Record operating system changes.
• Record hardware changes.
• Record firmware changes.
• Record Pterodactyl Panel version changes.
• Record Wings version changes.
• Verify backups before migrations or upgrades.
• Review server documentation for consistency after infrastructure changes.

Related Documentation

The following documents provide additional information about this node and the services hosted on it.

Change History

2026-08-03

Updated node documentation structure and clarified hardware, operating system, storage, and resource allocation details.

Documented CPU topology, swap configuration, RAID storage layout, Pterodactyl/Wings versions, external mounts, and current hosted services. Improved consistency with the centralized infrastructure documentation structure.

2026-07-26

Initial node documentation created.

Documents the pterodactyl Wings node hardware, operating system, storage layout, current role within the self-hosted Pterodactyl deployment, node status, location, related documentation references, and repository documentation structure.