controller_ulimits

Role Documentation

Welcome to the “controller_ulimits” role documentation.

Role Defaults

This section highlights all of the defaults and variables set within the “controller_ulimits” role.

nofiles_min: 1024
nproc_min: 2048

Role Variables: main.yml

metadata:
  name: Check controller ulimits
  description: >
    This will check the ulimits of each controller.
  groups:
  - post-deployment

Molecule Scenarios

Molecule is being used to test the “controller_ulimits” role. The following section highlights the drivers in service and provides an example playbook showing how the role is leveraged.

Scenario: default

Driver: podman

Molecule Platform(s)

- name: centos
  hostname: centos
  image: centos/centos:stream8
  registry:
    url: quay.io
  dockerfile: ../../../../.config/molecule/Dockerfile
  pkg_extras: python*-setuptools python*-pyyaml
  volumes:
  - /etc/ci/mirror_info.sh:/etc/ci/mirror_info.sh:ro
  privileged: true
  environment:
    http_proxy: "{{ lookup('env', 'http_proxy') }}"
    https_proxy: "{{ lookup('env', 'https_proxy') }}"
  ulimits:
  - host

Molecule Inventory

hosts:
  all:
    hosts:
      centos:
        ansible_python_interpreter: /usr/bin/python3

Example default playbook

- name: Converge
  hosts: all
  gather_facts: false

  tasks:
  - block:
    - include_role:
        name: controller_ulimits
      vars:
        nofiles_min: 102400
        nproc_min: 512
    rescue:
    - name: Clear host errors
      meta: clear_host_errors

    - debug:
        msg: The validation works for detecting nofiles_min!

  - block:
    - include_role:
        name: controller_ulimits
      vars:
        nofiles_min: 512
        nproc_min: 204800
    rescue:
    - name: Clear host errors
      meta: clear_host_errors

    - debug:
        msg: >-
          The validation works for detecting noproc_min!
          End of playbook run.

    - name: End play
      meta: end_play

  - name: Fail the test
    fail:
      msg: |
        The controller-ulimits failed detecting bad limits