Ansible Role: serdigital64.system.sys_mc¶

Purpose¶

Manage provisioning of the Midnight Commander tool

Supported features in the current version:

• Deploy application. Packages are defined in the variable sys_mc_profiles.
• Setup application:
  • Create default user configuration

The sys_mc Ansible-Role is part of the A:Platform64 project and is available in the system 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: "System / MC / Usage example"
  hosts: "localhost"
  gather_facts: true
  vars:
    target_user: "{{ lookup('env','USER') }}"
    target_users:
      - name: "{{ target_user }}"
        group: "{{ target_user }}"
        home: "/home/{{ target_user }}"

  tasks:
    - name: "Example: Install MC tool and deploy default user configuration"
      vars:
        sys_mc:
          resolve_prereq: true
          deploy: true
          setup: true
        sys_mc_users: "{{ target_users }}"
      ansible.builtin.include_role:
        name: "serdigital64.system.sys_mc"
...

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/system/playbooks/sys_mc.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.

sys_mc:
  resolve_prereq:
  deploy:
  setup:

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.

sys_mc_application:
  name:
  type:
  version:
  installed:
sys_mc_actions:
  setup:
    overwrite:
sys_mc_users:
  - name:
    group:
    home:

Deployment¶

OS Compatibility¶

The operating system compatibility list is defined in the variable: sys_mc_platforms

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.system

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¶

• SerDigital64

License¶

Apache-2.0