AI in the Irish Sea
- AI in the Irish Sea: Server Configuration
This article details the server configuration supporting the “AI in the Irish Sea” project, a long-term initiative focused on marine data analysis and predictive modeling. This document is intended for new system administrators and developers joining the project. It will cover hardware specifications, software stack, networking, and security considerations. Please familiarize yourself with the MediaWiki installation guide before proceeding.
Project Overview
The “AI in the Irish Sea” project utilizes a cluster of servers to ingest, process, and analyze data from a network of underwater sensors, satellite feeds, and historical datasets. The primary goal is to develop AI models capable of predicting environmental changes, identifying pollution sources, and optimizing marine resource management. See Data Acquisition for details on data sources.
Hardware Specifications
The server cluster consists of three primary types of nodes: Ingestion Nodes, Processing Nodes, and Storage Nodes. Each node type is configured to maximize efficiency for its designated task.
| Node Type | CPU | RAM | Storage | Network Interface |
|---|---|---|---|---|
| Ingestion Nodes (x3) | 2 x Intel Xeon Silver 4310 | 64GB DDR4 ECC | 2 x 1TB NVMe SSD (RAID 1) | 10GbE |
| Processing Nodes (x8) | 2 x AMD EPYC 7763 | 256GB DDR4 ECC | 1 x 2TB NVMe SSD (OS) + 4 x 8TB SAS HDD (RAID 10) | 100GbE |
| Storage Nodes (x4) | 2 x Intel Xeon Gold 6338 | 128GB DDR4 ECC | 16 x 16TB SAS HDD (RAID 6) | 40GbE |
These servers are housed in a dedicated rack within the Data Center. Power redundancy is provided by dual power supplies and an Uninterruptible Power Supply (UPS) system. Detailed hardware inventory is available on the Asset Management System.
Software Stack
The software stack is built around a Linux foundation, utilizing containerization for application deployment and management.
| Component | Version | Purpose |
|---|---|---|
| Operating System | Ubuntu Server 22.04 LTS | Base operating system for all nodes. |
| Containerization | Docker 24.0.5 | Application packaging and deployment. |
| Orchestration | Kubernetes 1.27 | Container orchestration and scaling. |
| Database | PostgreSQL 15 | Primary database for storing metadata and processed data. See Database Schema. |
| AI Framework | TensorFlow 2.13 | Machine learning framework for model training and inference. |
| Monitoring | Prometheus 2.46 | System monitoring and alerting. |
All code is managed within a Git repository and deployed using a Continuous Integration/Continuous Deployment (CI/CD) pipeline. Refer to the Deployment Guide for specifics on the pipeline.
Networking Configuration
The server cluster utilizes a dedicated VLAN for internal communication. Each node is assigned a static IP address within the VLAN. Firewall rules are configured to restrict access to only necessary ports. The Network Diagram provides a visual representation of the network topology.
| Interface | IP Address | Subnet Mask | Gateway |
|---|---|---|---|
| Management (all nodes) | 192.168.1.10-192.168.1.35 | 255.255.255.0 | 192.168.1.1 |
| Internal (Ingestion Nodes) | 10.0.0.10-10.0.0.12 | 255.255.255.0 | 10.0.0.1 |
| Internal (Processing Nodes) | 10.0.1.10-10.0.1.17 | 255.255.255.0 | 10.0.1.1 |
| Internal (Storage Nodes) | 10.0.2.10-10.0.2.13 | 255.255.255.0 | 10.0.2.1 |
External access is provided through a reverse proxy server, configured with SSL/TLS encryption. See Security Policy for details.
Security Considerations
Security is paramount. All servers are hardened according to the Security Hardening Checklist. Regular security audits are conducted. Access control is strictly enforced, utilizing role-based access control (RBAC). Data is encrypted both in transit and at rest. The Incident Response Plan outlines procedures for handling security breaches. All software is kept up-to-date with the latest security patches. Review the Vulnerability Management Process for details.
Future Expansion
Planned future expansion includes adding GPU-accelerated processing nodes to improve model training performance. We also intend to implement a more robust backup and disaster recovery solution, documented in the Disaster Recovery Plan.
Main Page Server Administration Data Analysis Tools Monitoring Dashboard Troubleshooting Guide
Intel-Based Server Configurations
| Configuration | Specifications | Benchmark |
|---|---|---|
| Core i7-6700K/7700 Server | 64 GB DDR4, NVMe SSD 2 x 512 GB | CPU Benchmark: 8046 |
| Core i7-8700 Server | 64 GB DDR4, NVMe SSD 2x1 TB | CPU Benchmark: 13124 |
| Core i9-9900K Server | 128 GB DDR4, NVMe SSD 2 x 1 TB | CPU Benchmark: 49969 |
| Core i9-13900 Server (64GB) | 64 GB RAM, 2x2 TB NVMe SSD | |
| Core i9-13900 Server (128GB) | 128 GB RAM, 2x2 TB NVMe SSD | |
| Core i5-13500 Server (64GB) | 64 GB RAM, 2x500 GB NVMe SSD | |
| Core i5-13500 Server (128GB) | 128 GB RAM, 2x500 GB NVMe SSD | |
| Core i5-13500 Workstation | 64 GB DDR5 RAM, 2 NVMe SSD, NVIDIA RTX 4000 |
AMD-Based Server Configurations
| Configuration | Specifications | Benchmark |
|---|---|---|
| Ryzen 5 3600 Server | 64 GB RAM, 2x480 GB NVMe | CPU Benchmark: 17849 |
| Ryzen 7 7700 Server | 64 GB DDR5 RAM, 2x1 TB NVMe | CPU Benchmark: 35224 |
| Ryzen 9 5950X Server | 128 GB RAM, 2x4 TB NVMe | CPU Benchmark: 46045 |
| Ryzen 9 7950X Server | 128 GB DDR5 ECC, 2x2 TB NVMe | CPU Benchmark: 63561 |
| EPYC 7502P Server (128GB/1TB) | 128 GB RAM, 1 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (128GB/2TB) | 128 GB RAM, 2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (128GB/4TB) | 128 GB RAM, 2x2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (256GB/1TB) | 256 GB RAM, 1 TB NVMe | CPU Benchmark: 48021 |
| EPYC 7502P Server (256GB/4TB) | 256 GB RAM, 2x2 TB NVMe | CPU Benchmark: 48021 |
| EPYC 9454P Server | 256 GB RAM, 2x2 TB NVMe |
Order Your Dedicated Server
Configure and order your ideal server configuration
Need Assistance?
- Telegram: @powervps Servers at a discounted price
⚠️ *Note: All benchmark scores are approximate and may vary based on configuration. Server availability subject to stock.* ⚠️