
[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>
Undercloud-cpu
An Ansible role to check if the Undercloud fits the CPU core requirements
Requirements
This role could be used before or/and after the Undercloud installation.
Role Variables
- min_undercloud_cpu_count: <8> -- Minimal number of CPU core
Dependencies
No dependencies.
Example Playbook
- hosts: undercloud
roles:
- { role: undercloud-cpu, min_undercloud_cpu_count: 42 }
License
Apache 2.0
Author Information
Red Hat TripleO Validations Team