You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
libvirt: use consistent pool path variables and use optional yaml output
Turns out we define CONFIG_KDEVOPS_STORAGE_POOL_PATH only to make it be the
same as generic CONFIG_LIBVIRT_STORAGE_POOL_PATH only later to then
use the old GUESTFS_ARGS or VAGRANT_ARGS to define the yaml version with
a postfix "kdevops".
Fix all this mess by using yaml output and cleaing its use up.
This does not fix any bugs, it just make things consistent.
And so where you saw CONFIG_KDEVOPS_STORAGE_POOL_PATH we now just use
the generic version CONFIG_LIBVIRT_STORAGE_POOL_PATH.
The kconfig symbol CONFIG_KDEVOPS_STORAGE_POOL_PATH gets promoted to be
what we expect it, that is:
"{{ libvirt_storage_pool_path }}/kdevops"
This also ensure we will barf as we want to promote using ansible for
this anyway and do away with all of the CONFIG_KDEVOPS_STORAGE_POOL_PATH
uses in shell scripts.
This kills all use of CONFIG_KDEVOPS_STORAGE_POOL_PATH from shell
scripts too then.
The motivation for all this is to slowly trim away the large
error-prone script scripts/bringup_guestfs.sh into ansible. This
is just a small step towards making that easier.
Signed-off-by: Luis Chamberlain <[email protected]>
0 commit comments