1. Overview
2. Getting Started
   • Installation
     • With Ansible >= 2.10
     • With Ansible < 2.9
3. Documentation
   • Roles
   • Modules
     • node_settings
       • Module parameters
       • Example Playbook
     • server_settings
       • Module parameters
       • Example Playbook
     • Inventory
       • Example usage
4. Going further
   • Uninstall the collection
5. Development
   • Run checks locally with Docker
   • Improve code quality
   • Run unit tests locally
   • Push this collection on Ansible Galaxy

This Ansible collection allows to manage and interact with one or more Rudder instances. It was created in order to gather all the necessary tools for a good integration of Ansible with Rudder.

This collection allows you to:

• Provides a plugin that extracts the inventory from Rudder and transforms it into Ansible format so that it can be retrieved (in CLI, in Ansible Tower/AWX).
• Module for provisioning the configuration of Rudder nodes.
• Module to configure the different parameters of a Root Rudder server.
• An armada of roles that allow each to deploy a particular element:
  • rudder_agent as the name suggests, allows you to deploy and configure a Rudder agent.
  • rudder_server allows you to deploy, provision and configure the nodes properties of a root server.
  • rudder_relay allows you to deploy a relay server and configure it.
  • rudder_repository allows the management of private Rudder repos.

To install the collection directly from this git repository, you must create a requirements.yml file and add the following content:

collections:
  - name: https://github.com/Normation/rudder-ansible.git
    type: git
    version: master

Then execute the following command:

ansible-galaxy install -r requirements.yml

You must first clone the current git repo, move to the directory of the cloned repo and then use the following command:

ansible-galaxy collection install .

A set of Ansible roles for installing and managing Rudder servers and agents. The roles works with Debian, RedHat and SUSE based systems.

• rudder_agent: Configures repository and installs a Rudder agent
• rudder_relay: Configures repository and installs a Rudder relay
• rudder_server: Configures repository and installs a Rudder server
• rudder_repository: Configures Rudder repositories

You can find the documentation for each role in its folder, in the README.md file.

The collection provides 2 major roles allowing to configure a Rudder root server but also to set up nodes dynamically (adding node properties for example).

Configure Rudder nodes parameters via APIs.

• rudder_url (str): Providing Rudder server IP address. Defaults to localhost.
• rudder_token (str): Providing Rudder server token. Defaults to the content of /var/rudder/run/api-token if not set.
• validate_certs (bool): Choosing either to ignore or not Rudder certificate validation. Defaults to true.
• node_id (str): Define the identifier of the node to be configured.
• policy_mode (str): Set the policy mode
  • Choices: audit, enforce, default, keep
• pending (str): Set the status of the (pending) node
  • Choices: accepted or refused
• state (str): Set the node life cycle state
  • Choices: enabled, ignored, empty-policies, initializing, preparing-eol
• properties (list): Define a list of properties
  • Subparameters:
    • name (str): Property name
    • value (str): Property value
• agent_key (dict): Define information about agent key or certificate
  • Subparameters:
    • status (str): TODO
      • Choices: certified, undefined
    • value (str): Agent key, PEM format
• include (str): Level of information to include from the node inventory.
• query (dict): The criterion you want to find for your nodes.
  • Subparameters:
    • composition (str): Boolean operator to use between each where criteria.
      • Choices: or, and
    • select (str): What kind of data we want to include. Here we can get policy servers/relay by setting nodeAndPolicyServer. Only used if where is defined.
    • where (list): The criterion you want to find for your nodes. List of selectors.
      • Subparameters:
        • object_type (str): Object type from which the attribute will be taken.
        • attribute (str): Attribute to compare to value.
        • comparator (str): Comparator type to use.
          • Choices: or, and
        • value (str): Value to compare to.

# Example 1
- name: Simple Modify Rudder Node Settings
  hosts: server
  become: yes
  collections:
    - rudder.rudder
  node_settings:
      rudder_url: "https://my.rudder.server/rudder"
      node_id: my_node_id
      policy_mode: enforce

# Example 2
- name: Complex Modify Rudder Node Settings
  hosts: server
  become: yes
  collections:
    - rudder.rudder
  node_settings:
      rudder_url: "https://my.rudder.server/rudder"
      rudder_token: "<rudder_server_token>"
      node_id: root
      pending: accepted
      policy_mode: audit
      state: enabled
      properties:
        name: "env_type"
        value: "production"
      validate_certs: False

# Example 3
- name: Complex Modify Rudder Node Settings with query
  hosts: server
  become: yes
  collections:
    - rudder.rudder
  node_settings:
      rudder_url: "https://my.rudder.server/rudder"
      rudder_token: "<rudder_server_token>"
      pending: accepted
      policy_mode: audit
      state: enabled
      properties:
        name: "env_type"
        value: "production"
      query:
        select: "nodeAndPolicyServer"
        composition: "and"
        where:
          - object_type: "node"
            attribute: "nodeHostname"
            comparator: "regex"
            value: "rudder-ansible-node.*"

Configure Rudder Server parameters via APIs.

• rudder_url (str): Providing Rudder server IP address. Defaults to localhost.
• rudder_token (str): Providing Rudder server token. Defaults to the content of /var/rudder/run/api-token if not set.
• name (str): The name of the parameter to set.
• value (str): The value defined to modify a given parameter name.
• validate_certs (bool): Choosing either to ignore or not Rudder certificate validation. Defaults to true.

# Example 1
- name: Simple Modify Rudder Settings
  hosts: server
  become: yes
  collections:
    - rudder.rudder
  server_settings:
      name: "modified_file_ttl"
      value: "23"

# Example 2
- name: Complex Modify Rudder Settings
  hosts: server
  become: yes
  collections:
    - rudder.rudder
  server_settings:
      rudder_url: "https://my.rudder.server/rudder"
      rudder_token: "<rudder_server_token>"
      name: "modified_file_ttl"
      value: "22"
      validate_certs: False

Plugin to get the Rudder inventory in Ansible.

Add follow lines in your inventory file:

plugin: rudder.rudder.inventory

To delete the collection, if you have not changed the default settings, is stored in ~/.ansible/collections/ansible_collections/. So you will have to delete the directory named "rudder".

You can use the following command to see if the collection is correctly installed and to see where it is installed.

ansible-galaxy collection list

You have the possibility to run status checks on the code before publishing it locally. To do this, you need to create a Dockerfile (with ansible-test.Dockerfile for example) with the content below in the root of the project.

FROM debian:bullseye
ARG USER_ID=1000
COPY ci/user.sh .
RUN ./user.sh $USER_ID

RUN apt-get -y update && \
    apt-get install -y ansible git python3-pip
RUN pip install pycodestyle voluptuous yamllint

RUN mkdir -p /tmp/ansible_collections/rudder/rudder

COPY . /tmp/ansible_collections/rudder/rudder/
WORKDIR "/tmp/ansible_collections/rudder/rudder/"

ENTRYPOINT ["/bin/bash", "-c"]

To build the container :

docker build . -f ansible-test.Dockerfile

To start the verification, simply use the command :

docker run <container-hash> "ansible-test sanity" 

If you make new changes in the code, you will have to restart a build of the container and make a new run of the Docker command that goes well with the new container hash obtained.

To be able to run unit tests locally, you must have the following dependencies:

pip3 install -r ci/requirements.txt

You will have to go to the root of the project and temporarily change the content of the environment variable PYTHONPATH.

export PYTHONPATH="."

You can then run the tests:

python -m unittest tests/unit/plugins/modules/

# or 
pytest tests/unit/plugins/modules/

To improve the quality of your Python code you can use the blue tool.

To install it, you must have installed the basic requirements (via the command pip install -r utils/python/requirements/base-requirements.txt).

Then, you just have to execute it as in the following example on your Python file. This is so that the sanity tests can be conclusive.

blue tests/unit/plugins/modules/test_node_settings_parameter_overloard.py

To push the collection, you must have a GitHub account.

• Log in to Galaxy with the account that will perform the buid and publication.
• Generate Galaxy API key, more informations here.
• Modify the content of the galaxy.yml file before publishing.
• Build the collection locally with ansible-galaxy collection build.
• Then publish the collection with the following command ansible-galaxy collection publish ./rudder-ansible-1.0.0.tar.gz --api-key you_galaxy_api_key