From 69d2d458119c058211af411c0165ab258708482a Mon Sep 17 00:00:00 2001 From: Stephen Finucane Date: Thu, 11 Jun 2020 10:18:40 +0100 Subject: [PATCH] Improve documentations for NovaLibvirtFileBackedMemory There is some interplay between this option and other memory-related options. Document this. Change-Id: I408feb3ac8e30b67be8b01388926c6ab3d43bfac Signed-off-by: Stephen Finucane Related-Bug: #1882821 (cherry picked from commit 620112173076f13a937bf71c526897aa25dc4574) (cherry picked from commit 4ac41b46dd6775e7af06b6b27cd4df94dac41873) --- deployment/nova/nova-compute-container-puppet.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/deployment/nova/nova-compute-container-puppet.yaml b/deployment/nova/nova-compute-container-puppet.yaml index 70d150c4b4..597f995274 100644 --- a/deployment/nova/nova-compute-container-puppet.yaml +++ b/deployment/nova/nova-compute-container-puppet.yaml @@ -272,7 +272,9 @@ parameters: - role_specific NovaLibvirtFileBackedMemory: description: > - Available capacity in MiB for file-backed memory. + Available capacity in MiB for file-backed memory. When configured, the + ``NovaRAMAllocationRatio`` and ``NovaReservedHostMemory`` parameters must + be set to 0. default: 0 type: number tags: