openstack
/
validations-common
Code Issues Proposed changes
validations-common/validations_common/roles/check_ram
History
Gael Chamoulaud (Strider) 1f3c0d2e7b
Remove workaround for tox-ansible and global molecule config 
[1] has been merged and released[2] in upstream tox-ansible and it is now
able to manage global molecule configuration. The workaround, which
consisted in adding the molecule driver name in each scenarios
molecule.yml files, is not necessary anymore.

This patch also removes all the relative symlink to the Dockerfile and
adds directly in the global molecule configuration file.

[1] https://github.com/ansible-community/tox-ansible/pull/89
[2] https://github.com/ansible-community/tox-ansible/releases/tag/v1.5.0

Change-Id: I8ac3f731c9d6af983dd902fc94e06a07c2ab9954
Signed-off-by: Gael Chamoulaud (Strider) <gchamoul@redhat.com>
 		2021-05-17 09:34:32 +02:00
..
defaults Make some roles more generic 2020-03-05 16:59:43 +01:00
molecule/default Remove workaround for tox-ansible and global molecule config 2021-05-17 09:34:32 +02:00
tasks Validations now gather only the subset of facts they need 2021-02-23 10:42:51 +01:00
README.md Make some roles more generic 2020-03-05 16:59:43 +01:00

README.md

Undercloud-ram

An Ansible role to check if the Undercloud fits the RAM requirements

Requirements

This role could be used before or/and after the Undercloud installation

Role Variables

  • min_undercloud_ram_gb: <24> -- Minimal amount of RAM in GB

Dependencies

No dependencies.

Example Playbook

- hosts: undercloud
  roles:
     - { role: undercloud-ram, min_undercloud_ram_gb: 24 }

License

Apache

Author Information

Red Hat TripleO Validations Team