Document and validate Proxmox-to-Odorobo Ceph adoption

[halfcyan]

Summary

Define a safe, incremental operational path for moving workloads from Proxmox to Odorobo while continuing to use the existing Ceph cluster.

Scope

• Document required pools, permissions, image naming, and RBD features.
• Define discovery/reference/clone behavior for existing Proxmox images.
• Define the cutover procedure for each migrated VM, including shutdown, import or clone, Odorobo registration, and validation.
• Document temporary Proxmox/Odorobo coexistence and rollback expectations during the migration window.
• Add a non-destructive validation command or diagnostic procedure.

Tasks

• Inventory the existing Proxmox Ceph pools, images, permissions, and required RBD features.
• Document the Odorobo Ceph client permissions and configuration.
• Define how existing Proxmox images are discovered and referenced.
• Identify which Proxmox VM metadata must be translated into the new Odorobo manifest.
• Define clone, import, handoff, rollback, and coexistence workflows.
• Add a non-destructive Ceph connectivity and capability validation command or procedure.
• Add operator documentation for gradual Proxmox-to-Odorobo workload migration.
• Review all workflows for accidental image or pool deletion.

What this should do

• An operator can validate that an existing Ceph cluster is usable by Odorobo.
• Existing Proxmox images can be identified without destructive operations.
• A VM can be moved from Proxmox into Odorobo using a documented, repeatable procedure.
• The migration procedure supports gradual workload movement.
• No image or pool is deleted implicitly.

Dependencies

• Depends on draft issue 05.

Issue links

• Depends on #102.
• This is the only migration issue in this backlog: Proxmox to Odorobo.
• Related to existing #16.