AI in the Sea of Japan
AI in the Sea of Japan: Server Configuration
This document details the server configuration for the "AI in the Sea of Japan" project, a research initiative focused on real-time analysis of marine data gathered from sensor networks deployed in the Sea of Japan. This guide is intended for new team members and system administrators responsible for maintaining the server infrastructure. It covers hardware specifications, software stack, network topology, and security considerations. Please familiarize yourself with Special:MyPreferences to customize your MediaWiki experience. Refer to Help:Contents for general MediaWiki help.
Overview
The project relies on a distributed server architecture to handle the high volume and velocity of data generated by the sensor network. The system comprises three primary tiers: data ingestion, processing, and storage. Each tier is designed for scalability and redundancy. The system utilizes Semantic MediaWiki extensions for data organization and querying. Understanding Help:Linking is crucial for navigating this documentation. The core principle guiding the design is maximizing uptime and data integrity. We also leverage Help:Tables for clear data presentation.
Hardware Specifications
The server infrastructure consists of a cluster of machines, each with dedicated roles. Details are provided in the following tables:
| Server Role | CPU | RAM | Storage | Network Interface |
|---|---|---|---|---|
| Ingestion Nodes (x3) | Intel Xeon Silver 4310 (12 cores) | 64 GB DDR4 ECC | 4TB NVMe SSD (RAID 0) | 10 Gbps Ethernet |
| Processing Nodes (x5) | AMD EPYC 7763 (64 cores) | 256 GB DDR4 ECC | 8TB NVMe SSD (RAID 1) | 25 Gbps Ethernet |
| Storage Nodes (x2) | Intel Xeon Gold 6338 (32 cores) | 128 GB DDR4 ECC | 64TB SAS HDD (RAID 6) | 10 Gbps Ethernet |
The servers are housed in a dedicated, climate-controlled data center with redundant power supplies and network connectivity. Consider reviewing the Manual:Configuration settings for further details on system configuration.
Software Stack
The software stack is built around a Linux distribution (Ubuntu Server 22.04 LTS) and leverages containerization technologies for ease of deployment and management. The following table outlines the key software components:
| Component | Version | Purpose | Notes |
|---|---|---|---|
| Operating System | Ubuntu Server 22.04 LTS | Base OS for all servers | Kernel version 5.15 |
| Docker | 24.0.5 | Containerization platform | Used for deploying applications |
| Docker Compose | v2.20.3 | Orchestration of Docker containers | Simplifies multi-container application management |
| PostgreSQL | 15.3 | Database for metadata and processed data | Configured with replication for high availability |
| Python | 3.10 | Primary programming language for data processing | Utilizes libraries such as NumPy, Pandas, and TensorFlow |
| Nginx | 1.25 | Reverse proxy and load balancer | Distributes traffic across ingestion nodes |
All software is managed using a combination of Ansible for configuration management and Prometheus for monitoring. See Help:Editing pages for how to contribute to the documentation.
Network Topology
The server infrastructure is connected via a dedicated VLAN. The network topology is a star configuration, with a central core switch providing connectivity to all servers. Network security is enforced using firewalls and intrusion detection systems.
| Network Segment | IP Range | Subnet Mask | Gateway |
|---|---|---|---|
| Ingestion Network | 192.168.1.0/24 | 255.255.255.0 | 192.168.1.1 |
| Processing Network | 192.168.2.0/24 | 255.255.255.0 | 192.168.2.1 |
| Storage Network | 192.168.3.0/24 | 255.255.255.0 | 192.168.3.1 |
Internal communication between servers utilizes secure protocols (HTTPS, SSH). External access is restricted to authorized personnel only. Refer to Help:Search to locate other relevant documentation.
Security Considerations
Security is paramount. The following measures are in place:
- **Firewall:** A stateful firewall is configured to allow only necessary traffic.
- **Intrusion Detection System (IDS):** An IDS monitors network traffic for malicious activity.
- **Regular Security Audits:** Periodic security audits are conducted to identify and address vulnerabilities.
- **Access Control:** Access to servers is restricted to authorized personnel only, using strong authentication methods (SSH keys, multi-factor authentication).
- **Data Encryption:** Sensitive data is encrypted both in transit and at rest.
- **Regular Backups:** Data is backed up regularly to an offsite location. Consult Help:Page history to track modifications. Familiarize yourself with Special:AllMessages for system messages.
Future Enhancements
Planned enhancements include the implementation of a Kubernetes cluster for improved container orchestration and scalability. We also aim to integrate a machine learning pipeline for automated anomaly detection. Consider exploring Manual:Shortcuts for quick access to helpful tools.
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.* ⚠️