Storage

Where This Fits in Karios

Karios is the unified infrastructure platform described in Getting Started. This section covers the Control Center storage workflows used for runtime disks, image stores, object endpoints, templates, boot images, and snapshots.

If you landed here directly, use Glossary for shared terms and keep Getting Started as the platform-level reference.

What Storage Is

This section covers storage resources used by virtual machines and images: instance storage pools, image stores, object endpoints, block volumes, templates, boot images, and snapshots.

Purpose

Storage covers how to configure runtime disk pools, image/object endpoints, block disks, VM templates, boot images, and snapshots.

Quick Start (Minimum Path)

Use this path if you need the fastest valid onboarding flow:

  1. Validate one healthy pool in Instance Storage.

  2. Validate one reachable store in Image Storage.

  3. Add one artifact in VM Templates or Boot Images.

  4. Create one disk in Block Storage.

  5. Confirm snapshot visibility in Snapshots.

Use Object Storage only when bucket/object workflows are required.

Before You Start Checklist

Validate these prerequisites before you begin module steps:

Prerequisite

Operational relevance

Access to storage actions in your role

Without add/edit/delete permission, workflow steps fail even when values are correct.

At least one healthy zone

Storage resources are zone-scoped in the create forms.

At least one volume profile

Required for block disk creation in Block Storage. Configure or verify here: Volume Profiles.

Required OS types available

Required by template registration and Boot Image registration/upload forms. Validate with: VM Templates and Boot Images.

Object endpoint credentials (if using Object Storage)

Required to authenticate endpoint registration and bucket operations.

A safe change window for destructive actions

Delete/disable/maintenance actions can impact workloads.

Access to Observability

Needed for fast escalation when create/import operations fail.

Execution Guidance

Follow each module in order and do not skip validation:

  1. Perform the step-by-step actions in the module page.

  2. Check the expected outcome after each create/update/delete action.

  3. Mark the module complete only when its done criteria are met.

Modules marked Conditional in the execution matrix can be skipped if that workflow is not part of your deployment.

If a step fails, use that module’s troubleshooting section before moving on.

Execution Matrix

Use this matrix for sequence, applicability, and validation.

Step

Module

Applicability

Validate before proceeding

1

Instance Storage

Required

At least one pool is Up and add-pool workflow is understood

2

Image Storage

Required

Image store endpoint is reachable and browse view works

3

Object Storage

Conditional

Use when object endpoint or bucket workflows are required

4

Block Storage

Required

Disk create/attach and delete/detach actions are validated

5

VM Templates

Conditional

Required when provisioning from templates

6

Boot Images

Conditional

Required when provisioning from Boot Image media

7

Snapshots

Required

Snapshot state visibility is confirmed and errors are triaged

End-to-End Validation Scenario

Run this once after finishing all module walkthroughs:

  1. In Instance Storage, confirm one pool is Up.

  2. In Image Storage, confirm one image store opens in Details and Browse.

  3. In VM Templates or Boot Images, add one test artifact and wait until it is usable.

  4. In Block Storage, create one test disk and verify it appears in list with expected state.

  5. In Object Storage (if used), create one test bucket.

  6. In Snapshots, verify snapshot visibility for target volumes and triage any Error rows.

Section completion criteria:

  • All required and selected conditional create actions complete with expected outcomes.

  • No unresolved critical storage errors remain in active workflows.

  • You can explain which storage module to use for each ongoing storage task.

Quick Troubleshooting Entry Points

Symptom

First page to check

VM deploy fails due to storage

Instance Storage and Block Storage

VM template/boot image import or readiness issue

Image Storage, VM Templates, Boot Images

Bucket/object operations fail

Object Storage

Snapshot failures or missing backup rows

Snapshots

→ Next: Compute – Virtual Machines