Infrastructure
Distributed File System - User Guide | Infrastructure Section
1. What Is Infrastructure?
The Infrastructure section is where you manage the physical and daemon-level foundation of your Karios DFS cluster. Everything in Storage, Block Storage, and Object Storage depends on what is configured here first.
The five Infrastructure pages and what they do:
Page |
What It Manages |
|---|---|
Hosts |
Physical nodes registered in the cluster - hardware profiles, labels, daemons, and devices per host |
Monitors |
Ceph Monitor daemons - the quorum system that maintains cluster state |
OSDs |
Object Storage Daemons - one per disk, responsible for storing all data |
Services |
All Ceph daemon types managed by the orchestrator - deploy, monitor, and manage services |
Physical Disks |
Every block device visible across all hosts - availability status and disk health |
Why Infrastructure must be healthy before anything else:
All storage features (Pools, File Systems, NFS, Block Images, Object Storage) depend on healthy Infrastructure. A new user should always verify Infrastructure before creating any storage resources.
Correct check order for a new user:
Hosts - Confirm all cluster nodes show
Status = Online.Monitors - Confirm all monitors are In Quorum.
OSDs - Confirm all OSDs show status up/in.
Services - Confirm all services show Running.
Physical Disks - Verify available disks for future OSD deployment.
2. Quick Reference - Infrastructure Health Check Sequence
Use this as your complete checklist for verifying Infrastructure health before creating storage resources.
# |
What To Do |
Where To Go |
What To Check |
Healthy Result |
|---|---|---|---|---|
1 |
Verify all hosts are online |
Infrastructure > Hosts |
Status column for every host row |
All hosts show Online |
2 |
Verify no host is in maintenance |
Infrastructure > Hosts |
Status column |
No host shows Maintenance unless intentionally set |
3 |
Check all monitors in quorum |
Infrastructure > Monitors |
In Quorum panel and Not In Quorum panel |
All monitors appear in In Quorum, and Not In Quorum shows the healthy empty-state message |
4 |
Verify monitor quorum count |
Infrastructure > Monitors |
quorum field in Status panel |
Count matches expected (for example 3/3) |
5 |
Check all OSDs are up/in |
Infrastructure > OSDs |
Status column for every OSD row |
All OSDs show up/in |
6 |
Check OSD usage levels |
Infrastructure > OSDs |
Usage column progress bars |
No OSD above 80% usage |
7 |
Check no unexpected cluster flags set |
Infrastructure > OSDs |
FLAGS row at top of page |
Flags are default (unset) unless intentionally set |
8 |
Verify all services running |
Infrastructure > Services |
Running and Status columns |
All services show matching counts (for example 4/4) and Status = Running |
9 |
Check available disks |
Infrastructure > Physical Disks |
Available count in page header |
Available count matches expected free disks for future OSD deployment |
10 |
Verify disk health |
Infrastructure > Hosts > Device Health tab |
SMART health for each disk |
All disks show Health = PASSED |
Note
If any issue persists, raise a support ticket via Monitoring > Alerts or
Karios Support.