Ansible Role: serdigital64.devops.dops_molecule

Purpose

Manage provisioning of Molecule

Supported features in the current version:

  • Deploy application. Packages are defined in the variable dops_molecule_profiles.

The dops_molecule Ansible-Role is part of the A:Platform64 project and is available in the devops Ansible-Collection.

Usage

The following example is an Ansible Playbook that includes all the supported features:

use this link if viewing the doc on github

---
- name: "DevOps / Molecule / Usage example"
  hosts: "localhost"
  gather_facts: true

  tasks:
    - name: "Example: install"
      vars:
        dops_molecule:
          resolve_prereq: true
          deploy: true
      ansible.builtin.include_role:
        name: "serdigital64.devops.dops_molecule"
...

The playbook can be run by executing:

# Set ANSIBLE_COLLECTIONS_PATHS to the default location. Change as needed.
ANSIBLE_COLLECTIONS_PATHS="${HOME}/.ansible/collections"
ansible-playbook "${ANSIBLE_COLLECTIONS_PATHS}/ansible_collections/serdigital64/devops/playbooks/dops_molecule.yml"

Role Parameters

Actions

  • Use action-parameters to control what tasks are enabled for the role to execute.
  • Parameters should be declared as task level vars as they are intented to be dynamic.
dops_molecule:
  resolve_prereq:
  deploy:
Parameter Required? Type Default Purpose / Value
dops_molecule.resolve_prereq no boolean false Enable automatic resolution of prequisites
dops_molecule.deploy no boolean false Enable installation of application packages

End State

  • Use end-state parameters to define the target state after role execution.
  • Parameters should be declared in host_vars or group_vars as they are intended to be permanent.
dops_molecule_application:
  name:
  type:
  version:
  installed:
dops_molecule_paths:
  root:
dops_molecule_owners:
  app:
    name:
    group:
    home:
Parameter Required? Type Default Purpose / Value
dops_molecule_application yes(deploy) dictionary Set application package end state
dops_molecule_application.name yes string "molecule" Select application package name
dops_molecule_application.type yes string "pip" Select application package type
dops_molecule_application.version yes string "latest" Select application package version
dops_molecule_application.installed yes boolean true Set application package end state
dops_molecule_paths yes(prepare) dictionary Set paths
dops_molecule_paths.root yes string "/opt/molecule"
dops_molecule_owners yes(prepare) dictionary Define users
dops_molecule_owners.app yes dictionary Define directory structure owner
dops_molecule_owners.app.name yes string "molecule" Set login name
dops_molecule_owners.app.group yes string "molecule" Set group name
dops_molecule_owners.app.home yes string "/home/molecule" Set home directory

Deployment

OS Compatibility

  • CentOS8
  • RedHat8
  • AlmaLinux8
  • OracleLinux8
  • Ubuntu20
  • Ubuntu21
  • Fedora33
  • Fedora35
  • Debian10
  • Debian11

Dependencies

  • Ansible Collections:
    • serdigital64.backup
      • bkp_archive
    • serdigital64.system
      • sys_package
      • sys_repository

Prerequisites

The Ansible engine must be already installed and configured for privileged access and remote execution.

In addition the following prerequisites can be automatically solved when running the playbook by setting the role action: resolve_prereq: true

  • Package manager for the target application is installed and enabled.

Installation Procedure

Manually install Ansible Collections from the Ansible Galaxy repository:

ansible-galaxy collection install serdigital64.devops

Automatic installation is also available by deploying A:Platform64

Contributing

Help on implementing new features and maintaining the code base is welcomed.

Please see the guidelines for further details.

Author

License

GPL-3.0-or-later