I'm working on getting our foreman up and running but we're currently
looking at using a multipath pool and pre-defining LUNs in our san for
foreman to use. Currently, when presented with a multipath pool, foreman
continues to treat it like it can have libvirt create a volume on it,
but it can't (libvirt doesn't support volume creation / management at
all on multipath pools, currently)
What I think would be best for foreman to do right now is simply present
a list of available volumes on the multipath pool and I can choose one
to use. This seems like it should be fairly straightforward to add, and
I can almost certainly get a dev on my side to help me get this added
soon, I just want to make sure we do it in a way that will allow it to
be a candidate for inclusion in a later foreman release.
Any thoughts on implementation, here?
The alternative, of course, is to simply define one large lun for each
VM host and layer LVM on top of that, but we're hoping to be able to
have the ability to migrate VMs across hosts at some point, so we would
like to avoid that if at all possible.