Quick Reference
Use this page as a fast action map for common Karios DFS operations.
Quick Ops Cheat Sheet
Action |
Where To Go |
Why |
Outcome |
|---|---|---|---|
Create a storage pool |
Storage > Pools > |
Establishes a storage domain for file, block, or object workloads. |
Pool is listed and converges to |
Verify file system readiness |
Storage > File System > Expand row > Details, MDS Ranks |
Confirms metadata service health before client onboarding. |
Active and standby MDS visibility is confirmed. |
Create an NFS export |
Storage > NFS Shares > |
Exposes DFS data to standard NFS clients. |
Export is listed and mount-ready. |
Create an RBD image |
Block Storage > Block Images > Images > |
Provides block disk capacity for VM or volume workloads. |
New image appears with provisioned usage tracking. |
Create and protect snapshot for clone workflow |
Block Storage > Images > Expand row > Snapshots |
Creates rollback/checkpoint and enables clone creation. |
Snapshot is available and can be cloned when protected. |
Flatten a clone |
Block Storage > Images > |
Removes parent dependency before parent cleanup or migration. |
Clone becomes standalone. |
Restore image from trash |
Block Storage > Trash > Restore |
Recovers a soft-deleted image within retention window. |
Image returns to active Images list. |
Create object user and retrieve keys |
Object Storage > Users > |
Generates credentials for S3/Swift clients. |
Access key and secret key are available for client setup. |
Create a bucket |
Object Storage > Buckets > |
Provides object container for uploads. |
Bucket appears with owner and empty object count. |
Put host in maintenance mode |
Infrastructure > Hosts > |
Safely prepares host for hardware work. |
OSD drain/rebalance starts and host enters maintenance state. |
Reweight an OSD |
Infrastructure > OSDs > |
Shifts data distribution when one OSD is overloaded. |
PG/data distribution adjusts over time. |
Create service |
Infrastructure > Services > |
Deploys required cluster daemons to eligible hosts. |
Service appears and running count rises to target. |
Silence an alert |
Monitoring > Alerts > Silences > |
Suppresses expected maintenance noise without disabling alert evaluation. |
Matching alert notifications are suppressed for configured window. |
Expire a silence |
Monitoring > Alerts > Silences > Expire |
Restores normal alert notification behavior after maintenance. |
Silence status becomes |
Download logs for analysis |
Monitoring > Logs > Cluster Logs or Audit Logs > Download |
Captures filtered evidence for troubleshooting and escalation. |
Exported log file is available for sharing. |
Run benchmark |
Monitoring > Benchmark > select tab > Select target node > Run |
Validates performance after infrastructure change. |
Benchmark history includes IOPS, throughput, and latency results. |
Safe Operations Checklist
Before Action |
Validate |
Why It Matters |
|---|---|---|
Any storage create/edit/delete |
Dashboard health and capacity |
Prevents changes during degraded cluster state. |
OSD maintenance and mark-out operations |
Replication health and available headroom |
Reduces data-risk during rebalance. |
Snapshot rollback or destructive delete |
Backup/restore plan and workload dependency check |
Prevents irreversible data loss. |
Alert silencing |
Clear maintenance window and comment |
Preserves auditability and avoids hidden long-running faults. |
Benchmark execution |
Low-traffic window and non-production target |
Avoids noisy-neighbor impact on active workloads. |
Warning
Destructive actions such as delete, purge, rollback, and rule/profile removal are irreversible in normal workflows. Confirm dependency and data-impact checks before execution.