Ansible Playbook: manage_file_servers¶
Manage file servers.
Supported features in the current version:
- Create file repository structure
- Install NFS server
- Export NFS shares
Deploy file server¶
- Verify that target nodes are registered in the inventory file: file_service.ini
- Verify that target tools are selected in the playbook endstate file: manage_file_servers.yml
- Run the playbook. Use the
-s <SITE>parameter to select the target site.
/opt/aplatform64/bin/ap64.sh -n -p manage_file_servers -s <SITE>
Register the hosts that will consume the service in the Ansible Inventory file:
- Host Group:
A dedicated group_vars directory is used to store end-state configuration settings for both the playbook and related Ansible Roles.
Set playbook specific settings in the file:
manage_file_servers_apps: repository: nfs:
|Parameter||Required?||Type||Default||Purpose / Value|
|manage_file_servers_apps||no||dictionary||Define what applications will be deployed|
|manage_file_servers_apps.repository||no||boolean|| ||Deploy the application?|
|manage_file_servers_apps.nfs||no||boolean|| ||Deploy the application?|
Additional role specific settings are available to further customize the playbook:
|A:Platform64 role||group_vars file|
OS compatibility is role dependant. Please refer to the respective role documentation. - Ubuntu20 - Ubuntu21 - Fedora33 - Debian10 - Debian11
Dependencies in this section are automatically solved during the installation process.
- Ansible Collections:
- Control Node: A:Platform64 installed and configured
- Managed Nodes: target hosts prepared for A:Platform64 control
The playbook is automatically deployed during the A:Platform64 installation process
Help on implementing new features and maintaining the code base is welcomed.
Please see the guidelines for further details.