Open dpap-qs opened 3 years ago
Thanks for the PR. I need to dive a bit into the libvirt documentation to understand well how this is supposed to work.
Any progress?
@dpap-qs I have tested this. Its awesome! :sunglasses:
we will review this PR after the 13
release see #813 PR which . Stay tuned :)
@dpap-qs A suggestion: At the moment the name of the storage pool in libvirt is the name of the volume group.
We could reuse the path
setting to select a volume group (my-volumegroup) and create a volume pool (example-pool):
resource "libvirt_pool" "example" {
name = "example-pool"
type = "logical"
path = "my-volumegroup"
}
any update on this guys??
I'm interested in seeing this implemented. Are there any plans to continue with this?
If not, perhaps I can try to do a new PR against current master
instead?
Thanks!
Logical storage pool implementation.
Our team needed the lvm storage pool, so I implemented it. We tested, it seems fine. What do you think @dmacvicar ? If you say it's ok, then I write acceptance tests, and add the documentation.
If everything is fine, I think we should discuss about this: The volumes created in logical storage pool, don't preserve de volume
format
. See: pool and volume. It's a problem when you try to determine the disk driver based on volume format during the domain creation here:https://github.com/dmacvicar/terraform-provider-libvirt/blob/30595333cabd9d1651449c18acfaa2f99aaef928/libvirt/domain.go#L513 So right now we can only use the default disk driver, which is raw, so e.g. cqow2 cannot be used. I see two options:disk
resource with adriver
attribute. If it's provided, we use it, otherwise we should use the current logic..raw
or.qcow2
, use them.