8d849e5fea
Ceph 16 (Pacific) is going to support mounting RBD images on
Windows[1].
This change provides a simplified RBD connector for Windows.
The Windows RBD connector is very similar to the Linux one.
There are a few main differences though:
* the Ceph python bindings are not available on Windows yet, so
we'll always do a local mount. Besides, Hyper-V cannot use
librbd directly, so we'll need a local mount anyway.
* The device names aren't handled in the same way. On Windows,
disk names such as "\\.\PhysicalDrive1" are provided by
the OS and cannot be explicitly requsted.
* under high load, the disk might not become available immediately,
we're adding a few checks when mapping the image.
* rbd-wnbd provides a "show" command, which we're going to use
in order to retrieve mounted disk paths
* rbd-wnbd provides a "hard-disconnect" option, used when forcefully
disconnecting volume. By default, WNBD waits for the Windows
storage PnP stack before removing the attachment (e.g. waiting for
open handles, unflushed data, pending IO, etc).
We're adding a mixin class meant to avoid duplicating code between
the Linux and Windows RBD connectors.
Integration testing will be covered by the existing Windows CI.
[1] https://github.com/ceph/ceph/pull/33750
Implements: blueprint os-brick-windows-rbd
Change-Id: I56bf09cbd40679eefa5e378c9b36383de89e980c
6 lines
166 B
YAML
6 lines
166 B
YAML
---
|
|
features:
|
|
- |
|
|
RBD volumes can now be attached to Windows hosts and Hyper-V VMs.
|
|
The minimum requirements are Ceph 16 (Pacific) and Windows Server 2016.
|