Servers
Bare metal servers and virtual machines on Fugoku
Servers
Fugoku offers bare metal servers and virtual machines through the Latitude-style server model. Servers provide dedicated hardware with full IPMI access.
What Are Servers?
Servers in Fugoku are Latitude-aligned bare metal or virtual machine instances. They provide dedicated hardware resources with:
- IPMI-based remote management
- Rescue mode for recovery
- Multiple OS options
- Flexible billing (hourly, monthly, yearly)
Server Plans
Server plans are defined in the server catalog. Each plan specifies CPU, RAM, disk, and network resources.
Plan Categories
| Category | Description |
|---|---|
| Standard | Balanced CPU/RAM for general workloads |
| Core-Optimized | High CPU count for compute-intensive tasks |
| Memory-Optimized | High memory for databases and caching |
| GPU | NVIDIA A100 for AI/ML workloads |
Example Plans
| Plan | CPU | RAM | Disk | GPU | Price/hr |
|---|---|---|---|---|---|
rs4.metal.large | AMD 9354P (32 cores) | 768 GB | 2x480GB NVME + 2x8TB NVME | — | $3.22 |
m4.metal.large | AMD 9254 (24 cores) | 384 GB | 2x480GB NVME + 2x3.8TB NVME | — | $2.03 |
f4.metal.medium | AMD 4564P (16 cores) | 128 GB | 2x480GB NVME + 2x1.9TB NVME | — | $0.76 |
f4.metal.small | AMD 4484PX (12 cores) | 96 GB | 2x960GB NVME | — | $0.55 |
m4.metal.small | AMD 4244P (6 cores) | 64 GB | 2x960GB NVME | — | $0.41 |
rs4.metal.xlarge | AMD 9554P (64 cores) | 1536 GB | 2x480GB NVME + 4x8TB NVME | — | $6.44 |
m4.metal.xlarge | AMD 9455P (48 cores) | 768 GB | 2x480GB NVME + 2x3.8TB NVME | — | $4.12 |
f4.metal.large-gpu | AMD 9275F (24 cores) | 768 GB | 2x480GB NVME + 2x3.8TB NVME | 8x A100 | $8.99 |
vm-standard | AMD 9354P (4 cores) | 16 GB | 80GB NVME | — | $0.35 |
Operating Systems
| OS | Default User | Deploy Time |
|---|---|---|
| Ubuntu 24.04 | ubuntu | 5s |
| Ubuntu 22.04 | ubuntu | 5s |
| Debian 12 | debian | 8s |
| Rocky 9 | rocky | 10s |
| AlmaLinux 9 | almalinux | 10s |
| Proxmox 8.3 | proxmox | 15s |
Regions
| Region | Code | Locations |
|---|---|---|
| North America | north-america | Ashburn, Chicago, Dallas, Los Angeles, Miami, New York, Silicon Valley, Toronto |
| South America | south-america | São Paulo |
| Europe | europe | London, Frankfurt, Amsterdam |
| APAC | apac | Singapore, Tokyo, Sydney |
Server Lifecycle
1. Creating
Server is being provisioned on the hardware. OS is being installed.
2. Active
Server is running and accessible. You can SSH in and use it.
3. Stopping
Server is being shut down gracefully.
4. Stopped
Server is powered off. You can restart it.
5. Maintenance
Server is undergoing maintenance (firmware updates, hardware repairs).
6. Terminating
Server is being decommissioned. Data will be erased.
7. Terminated
Server has been fully terminated.
IPMI Rescue Mode
IPMI provides out-of-band management for servers. Use rescue mode when SSH is unavailable.
Accessing IPMI
- Navigate to Servers → Select Server → Overview
- Find the IPMI connection details
- Use the IPMI IP address and credentials to connect
Rescue Mode
- Power off the server via IPMI or Console
- Boot into rescue mode
- Access the server's filesystem
- Fix the issue (e.g., restore from snapshot, fix network config)
- Reboot into normal mode
SSH Key Management
Servers use SSH keys for access. Keys are associated with providers and can be used across multiple servers.
Key Formats
- RSA (2048-bit or 4096-bit)
- Ed25519
- ECDSA (256-bit or 521-bit)
Default Users
| OS | Default User |
|---|---|
| Ubuntu | ubuntu |
| Debian | debian |
| CentOS/Rocky | centos |
| Fedora | fedora |
| Proxmox | root |
Servers vs. Virtual Machines
| Feature | Bare Metal Server | Virtual Machine |
|---|---|---|
| Hardware | Dedicated | Shared |
| IPMI | Yes | No |
| Rescue Mode | Yes | No |
| GPU Options | A100 (8x) | Available |
| Billing | Hourly/monthly/yearly | Hourly |
| Performance | Maximum | Shared |
| Backups | Supported | Supported |
| Upgrade | Plan migration | Plan migration |
Creating a Server
Via Console
- Navigate to Servers
- Click Create Server
- Choose category (Bare Metal, Bare Metal GPU, Virtual Machine)
- Select region, image, and plan
- Configure SSH keys, tags, and billing
- Click Create
Via API
curl -X POST https://api.fugoku.com/v1/servers \
-H "Authorization: Bearer $FUGOKU_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"data": {
"type": "servers",
"attributes": {
"name": "my-server",
"hostname": "my-server.example.com",
"project": "proj-abc",
"site": "NYC",
"plan": "rs4.metal.large",
"operating_system": "ubuntu-24.04",
"billing": "hourly",
"ssh_keys": ["key-abc123"]
}
}
}'Backups
Both bare metal servers and virtual machines support backups.
Creating Backups
Console: Server detail → Backups tab → Create backup
API:
# For bare metal servers
curl -X POST https://api.fugoku.com/v1/servers/srv-abc123/backups \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"data": {
"type": "backups",
"attributes": {
"name": "backup-before-upgrade"
}
}
}'
# For virtual machines
curl -X POST https://api.fugoku.com/v1/servers/srv-abc123/backups \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"data": {
"type": "backups",
"attributes": {
"name": "backup-before-upgrade"
}
}
}'Restoring Backups
Restoring a backup creates a new server or instance from the backup data. The original backup is archived.
curl -X POST https://api.fugoku.com/v1/backups/backup-abc123/restore \
-H "Authorization: Bearer $TOKEN"Deleting Backups
curl -X DELETE https://api.fugoku.com/v1/backups/backup-abc123 \
-H "Authorization: Bearer $TOKEN"Next Steps
- API Reference — Server API endpoints
- SSH Keys — Key management
- Jobs — Async provisioning and job tracking