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

Storage backend should be able to recommend a 'backend' kind #38

Open
djs55 opened this issue Oct 12, 2014 · 1 comment
Open

Storage backend should be able to recommend a 'backend' kind #38

djs55 opened this issue Oct 12, 2014 · 1 comment

Comments

@djs55
Copy link
Collaborator

djs55 commented Oct 12, 2014

It should be the job of the storage system to recommend a particular backend implementation, whether this is

  • vbd: blkback
  • vbd3: tapdisk3
  • qdisk: qemu qdisk

For example, a Ceph implementation could recommend 'qdisk'; a regular .vhd backend could recommend 'vbd3' and an LVM implementation with type=raw could recommend 'vbd'.

It's fine to keep a per-VBD override for people who really know what they're doing.

@djs55
Copy link
Collaborator Author

djs55 commented Oct 13, 2014

A simple implementation would allow the storage layer to provide xenstore_data:backend-kind= -- this is how the current per-VBD override works.

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

No branches or pull requests

1 participant