openstack/openstack-ansible-ops
Code Issues Proposed changes

Ensure upper and lower memory limits are whole numbers

Browse Source 
This change will ensure that the upper and lower memory limits are set
to whole numbers when dynamically setting the memory limits. Before this
change a memory limit could be a float, and in certain versions of
ansible + python the option could evaluate to 0, which would break
everything.

Change-Id: Ibfb8af60db6566937cbf77243b0e6848d542665d
Signed-off-by: cloudnull <kevin@cloudnull.com>
This commit is contained in:
cloudnull 2019-02-19 13:09:42 -06:00
parent e52e99166c
commit 22f997f7fa
No known key found for this signature in database
GPG Key ID: 9443251A787B9FB3
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
elk_metrics_6x/vars/variables.yml
View File

@ -1,6 +1,6 @@
---
elastic_memory_lower_limit: "{{ (ansible_memtotal_mb | int) * 0.15 // 1 }}"
elastic_memory_upper_limit: "{{ (ansible_memtotal_mb | int) * 0.35 // 1 }}"
elastic_memory_lower_limit: "{{ (((ansible_memtotal_mb | int) * 0.15) // 1) | int }}"
elastic_memory_upper_limit: "{{ (((ansible_memtotal_mb | int) * 0.35) // 1) | int }}"
# Option to set persistent queue storage in gigabytes
q_storage: "{{ (ansible_processor_count | int) * (ansible_processor_threads_per_core | int) * 2 }}"