-
Notifications
You must be signed in to change notification settings - Fork 492
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
Add volatile disks support for LXD #3297
Comments
dann1
added a commit
that referenced
this issue
May 16, 2019
dann1
added a commit
to dann1/docs
that referenced
this issue
May 16, 2019
dann1
added a commit
that referenced
this issue
May 22, 2019
dann1
added a commit
that referenced
this issue
Jun 20, 2019
rsmontero
added
Category: LXD/LXC
Status: Accepted
and removed
Type: Backlog
Category: KVM
labels
Sep 27, 2019
dann1
added a commit
to OpenNebula/docs
that referenced
this issue
Dec 11, 2019
Closed
rsmontero
added a commit
that referenced
this issue
Mar 17, 2020
rsmontero
added a commit
to OpenNebula/docs
that referenced
this issue
Mar 17, 2020
rsmontero
added a commit
that referenced
this issue
Mar 17, 2020
(cherry picked from commit ab0dbc7)
dann1
added a commit
to dann1/docs
that referenced
this issue
Mar 17, 2020
atodorov-storpool
pushed a commit
to storpool/one
that referenced
this issue
Mar 18, 2020
rsmontero
pushed a commit
to OpenNebula/docs
that referenced
this issue
Mar 23, 2020
rsmontero
pushed a commit
that referenced
this issue
Nov 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Images used by the LXD driver, must have at least, a pre-formatted partition. Volatile disks are created by opennebula, but are unusable to the LXD drivers, the mount will fail. In order to support this, the driver could perform an
mkfs
on the image if it is validated the image is volatile, and then proceed as usual.The default format will be ext4, but this could be possibly extended later on to allow the user to set the desired format.
Interface Changes
Maybe modify the core in order to allow the format field to be valid for the user to fill. It would be required to check first the hypervisor.
Progress Status
The text was updated successfully, but these errors were encountered: