Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Live migration #66

Open
sdpeters opened this issue Jan 24, 2023 · 0 comments
Open

Live migration #66

sdpeters opened this issue Jan 24, 2023 · 0 comments

Comments

@sdpeters
Copy link
Contributor

sdpeters commented Jan 24, 2023

Reflect Ceph's support for live migration of RBD images between clusters in the NVMe-oF gateway.

Since a gateway or gateway group in any Ceph cluster presents an NVMe-oF subsystem to hosts, migration between Ceph clusters implies migration between subsystems. Migration of NVMe namespaces between subsystems is theoretically possible, using an NVMe feature called "dispersed namespaces". Without that feature the NVMe spec forbids the appearance of any namespace in more than one subsystem (as you might do while the namespace was moving from one Ceph cluster to another, and temporarily accessible by gateways in both Ceph clusters).

One obstacle there is that the Linux NVMe-oF maintainers have some issues with the dispersed namespace feature which seem to make it unlikely that Linux will support dispersed namespaces. If there's another NVMe-oF host the gateway will be used with that does support dispersed namespaces, we look closer at dispersed namespace support in the gateway.

One alternative is to allow gateway groups to span clusters, but that might be awkward operationally.

Perhaps we could enable subsystems to be passed from one gateway group to another, enabling all the namespaces they contain to migrate. This isn't as flexible as we'd like, but can comply with the standard.

[This should probably be marked as a release 2 feature]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant