This developer documentation is outdated , but provides historical context.

It is not user documentation and should not be treated as such.

Documentation is available here.

Storage Domain Version 0

Storage Domain Version 2

Storage Domain Version 3

The storage domain version 3 has been introduced in VDSM on the 30th of January 2012 with the commit 8665716c: Use SANLock for the SPM resource [1]. The new format has been introduced to overcome some of the limitations present in the previous formats (with regard to live snapshots, live merges and internationalization) and mainly to introduce the use of SANLock [2].

  • Supported Domain Types: Block (iSCSI, FCP) and File (NFS, local) domains
  • Supported Domain Classes: Data, Export

Changes

VDSM and Format

  • Uses SANLock to acquire the SPM resource [3]
  • Uses SANLock to acquire the volume resources (virtualization subsystem, libvirt) [4]
  • In block domains the permissions of the LVs in the metadata are always RW (to allow live snapshots and live merges)
  • Unicode[5] support in the name and description of:
    • Storage Pools
    • Storage Domains
    • Disks and NICs
    • Virtual Machines
  • New mailbox format (in progress)

Engine and GUI

  • Display the Storage Domain Version (already present in the "Storage" tab)
  • Support the creation of Storage Domain V3
  • Accept unicode strings for the descriptions (only V3)
  • Block the import of VM containing unicode to V2 domains
  • Prevent moving Storage Domain Version V3 to 3.0 Data Centers

Required Actions On Upgrade

VDSM

  • Initialize the resources for all the volumes in the domain
  • Set all the LVs to RW
  • Check that the volume SIZE in the metadata is consistent with the block size (RAW) or with the qcow2 virtual size (COW) BZ811880, BZ611183, BZ706014

Engine and GUI

REST API

The operation is driven by pool compatibility change. So there is no need for a new REST API.

Requirements

  • All nodes in the cluster must have 5a0b2c9 "Do not lock the image when preparing the VM path" (vdsm >= 4.9.4) to avoid the LVM mda corruption

Export Domains

Export domains cannot be upgraded; they must be created in the version 3 format (and previous versions of VDSM won't be able to attach it to a V1/V2 pool).

Upgrade

At the moment it is planned to support an automatic upgrade to version 3 from the previous versions.

References

` `[6]

[1]

[2] https://fedorahosted.org/sanlock

[3]

[4] http://gerrit.ovirt.org/1253

[5] http://gerrit.ovirt.org/637

[6] http://gerrit.ovirt.org/726