Create Block devices during configuration instead of boot-time #1736
Conversation
This file contains 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
acatangiu
added
the
Status: Awaiting review
acatangiu
force-pushed
the
build_block
branch
2 times, most recently
from
18a9d45 to
4d4e2be
Compare
|
Will this help in being able to attach block devices to a running Firecracker? |
|
It is a step in that direction yes, but we're far from it since the biggest missing piece there is PCI + Hotplug |
sandreim
reviewed
Apr 3, 2020
ioanachirca
reviewed
Apr 4, 2020
ioanachirca
reviewed
Apr 4, 2020
|
This PR is a prerequisite for #1713 |
andreeaflorescu
previously requested changes
Apr 8, 2020
alxiord
previously approved these changes
Apr 8, 2020
7 tasks
Signed-off-by: Adrian Catangiu <acatan@amazon.com>
Following the more decoupled design we can now create block devices on their configuration path, rather than saving a config and delaying creation to boot-time. This model allows user-errors (like invalid resources or permissions) to be reported as part of the configuration step rather than later at attempted boot. It also removes the time window between configuration and boot where changes to the host system (deleting files, changing permissions, etc) could cause microVM boot failures. This commit decreases code complexity and should provide better efficiency to the process of configuring and starting a microVM. Signed-off-by: Adrian Catangiu <acatan@amazon.com>
Validating the Display value of errors against the static strings used in the Display implementation is redundant. This is typically a bad engineering practice referred to as WET. You can read more about it here: https://en.wikipedia.org/wiki/Don%27t_repeat_yourself Signed-off-by: Adrian Catangiu <acatan@amazon.com>
|
@ioanachirca @aghecenco I've rebased, please take a look. |
ioanachirca
approved these changes
Apr 9, 2020
alxiord
approved these changes
Apr 9, 2020
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reason for This PR
Fixes #1702
Prerequisite for #1713
Description of Changes
Following the more decoupled design we can now create
blockdevices on their configuration path, rather than saving a config and delaying creation to boot-time.Such a model allows user-errors (like invalid resources or permissions) to be reported as part of the configuration step rather than later at attempted boot.
It would also remove the time window between configuration and boot where changes to the host system (deleting backing files, changing permissions, etc) would cause microVM boot failures (race condition between validation and commitment of resources).
Such a model should also decrease code complexity and should provide better efficiency to the process of configuring and starting a microVM (no more moving configurations around in memory and validating resources both at config time and boot-time).
License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.
PR Checklist
[Author TODO: Meet these criteria.][Reviewer TODO: Verify that these criteria are met. Request changes if not]git commit -s).unsafecode is properly documented.firecracker/swagger.yaml.CHANGELOG.md.