-
Notifications
You must be signed in to change notification settings - Fork 200
Support RateLimiters and ReadOnly for DriveMounts #296
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
Labels
kind/enhancement
New feature or request
Comments
sipsma
added a commit
to sipsma/firecracker-containerd
that referenced
this issue
Oct 17, 2019
This implements the proposal found in docs/drive-mounts-proposal.md, with the exception for supporting RateLimiters and IsReadOnly in the DriveMount objects, due to the need for further refactoring of the internal stub drive code (will be followed up in firecracker-microvm#296). Signed-off-by: Erik Sipsma <[email protected]>
sipsma
added a commit
to sipsma/firecracker-containerd
that referenced
this issue
Oct 21, 2019
This implements the proposal found in docs/drive-mounts-proposal.md, with the exception for supporting RateLimiters and IsReadOnly in the DriveMount objects, due to the need for further refactoring of the internal stub drive code (will be followed up in firecracker-microvm#296). Signed-off-by: Erik Sipsma <[email protected]>
sipsma
added a commit
to sipsma/firecracker-containerd
that referenced
this issue
Oct 21, 2019
This implements the proposal found in docs/drive-mounts-proposal.md, with the exception for supporting RateLimiters and IsReadOnly in the DriveMount objects, due to the need for further refactoring of the internal stub drive code (will be followed up in firecracker-microvm#296). Signed-off-by: Erik Sipsma <[email protected]>
sipsma
added a commit
to sipsma/firecracker-containerd
that referenced
this issue
Oct 24, 2019
This implements the proposal found in docs/drive-mounts-proposal.md, with the exception for supporting RateLimiters and IsReadOnly in the DriveMount objects, due to the need for further refactoring of the internal stub drive code (will be followed up in firecracker-microvm#296). Signed-off-by: Erik Sipsma <[email protected]>
sipsma
added a commit
to sipsma/firecracker-containerd
that referenced
this issue
Oct 24, 2019
This implements the proposal found in docs/drive-mounts-proposal.md, with the exception for supporting RateLimiters and IsReadOnly in the DriveMount objects, due to the need for further refactoring of the internal stub drive code (will be followed up in firecracker-microvm#296). Signed-off-by: Erik Sipsma <[email protected]>
sipsma
added a commit
to sipsma/firecracker-containerd
that referenced
this issue
Oct 25, 2019
This implements the proposal found in docs/drive-mounts-proposal.md, with the exception for supporting RateLimiters and IsReadOnly in the DriveMount objects, due to the need for further refactoring of the internal stub drive code (will be followed up in firecracker-microvm#296). Signed-off-by: Erik Sipsma <[email protected]>
sipsma
added a commit
to sipsma/firecracker-containerd
that referenced
this issue
Nov 6, 2019
This implements the proposal found in docs/drive-mounts-proposal.md, with the exception for supporting RateLimiters and IsReadOnly in the DriveMount objects, due to the need for further refactoring of the internal stub drive code (will be followed up in firecracker-microvm#296). Signed-off-by: Erik Sipsma <[email protected]>
sipsma
added a commit
to sipsma/firecracker-containerd
that referenced
this issue
Nov 7, 2019
This implements the proposal found in docs/drive-mounts-proposal.md, with the exception for supporting RateLimiters and IsReadOnly in the DriveMount objects, due to the need for further refactoring of the internal stub drive code (will be followed up in firecracker-microvm#296). Signed-off-by: Erik Sipsma <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The first iteration of support for DriveMounts leaves out RateLimiter and IsReadOnly settings for the drives due to the fact that doing so requires significant refactoring of the stubdrive code (as RateLimiter and IsReadOnly settings cannot be updated via a Patch call).
Right now, users can still specify that a filesystem be bind-mounted as read-only into their container, but they don't have any options for the rate-limiter currently.
The text was updated successfully, but these errors were encountered: