-
Notifications
You must be signed in to change notification settings - Fork 27
server: populate disk backend names correctly #751
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it seems like instead of having
ParsedStorageDevice.backend_nameand requiring it always matches what happens to also be in the device spec, that we'd be better off with aStorageDeviceV0::backend_name()helper that we use in places likeadd_storage_device(). something like.insert(device_spec.backend_name(), backend_spec)?do we expect to have storage devices that don't know their backend name? (that seems unlikely, but it's an obvious reason my thought wouldn't stick!)
(i also understand this change and why it fixes things, so +1 for landing to make things fixed and adjusting after if you're so inclined)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ultimately my plan is to do away with
ParsedStorageDeviceentirely and replace it with aDisktype that contains both the device and backend halves of each of a VM's storage components. In this bug I got caught looking the wrong way halfway through the series of refactoring PRs that's supposed to make that happen ;)I have the result of this wave of refactoring in a branch in my fork; here's what the routine this PR fixes will look like when that's done. This will (hopefully) foreclose on the sort of bug we hit here, since machine init won't be looking up named backends in a map anymore. (I think the code can be improved even more beyond what I have in the fork at this point, but am trying to stick to one renovation project at a time--insert the beaver-big-plans meme here...)
There's even more context in #735 if you're looking for some light bedtime reading.