From fd34e0cda4a5ef0841e04dee27d0d857167a1076 Mon Sep 17 00:00:00 2001 From: Sylvain Bauza Date: Wed, 2 Mar 2016 17:09:58 +0100 Subject: [PATCH] Reno for libvirt libosinfo with OS Change I1ab0c33f7ac4690b72a14e7748356a6ec22c9308 was missing the relnote Change-Id: I582832f4fcb5d2aa52a3c5165e2ac5fffb43ed62 --- ..._hardware_policy_from_libosinfo-19e261851d1ad93a.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 releasenotes/notes/libvirt_hardware_policy_from_libosinfo-19e261851d1ad93a.yaml diff --git a/releasenotes/notes/libvirt_hardware_policy_from_libosinfo-19e261851d1ad93a.yaml b/releasenotes/notes/libvirt_hardware_policy_from_libosinfo-19e261851d1ad93a.yaml new file mode 100644 index 000000000000..725d1744cd40 --- /dev/null +++ b/releasenotes/notes/libvirt_hardware_policy_from_libosinfo-19e261851d1ad93a.yaml @@ -0,0 +1,9 @@ +--- +features: + - For the libvirt driver, by default hardware properties will be retrieved + from the Glance image and if such haven't been provided, it will use + a libosinfo database to get those values. If users want to force a specific + guest OS ID for the image, they can now use a new glance image property + ``os_distro`` (eg. ``--property os_distro=fedora21``). In order to use + the libosinfo database, you need to separately install the related native + package provided for your operating system distribution.