User Tools
Writing /app/www/public/data/meta/development/applications/ansible/roles.meta failed
development:applications:ansible:roles
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| development:applications:ansible:roles [2017/12/04 17:17] – adsilva | development:applications:ansible:roles [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Ansible Roles ====== | ||
| + | Roles are a way of organising tasks for reuse with a defined file structure. They are more or less like re-usable libraries/ | ||
| + | |||
| + | These roles can then be used by one or more deployment playbooks. | ||
| + | |||
| + | To learn how these roles are used, refer the README file here: [[https:// | ||
| + | |||
| + | |||
| + | ====== 1. Database backup Role ====== | ||
| + | |||
| + | This role is used to Backup DB Tables to a defined folder. | ||
| + | |||
| + | **example usage:** | ||
| + | |||
| + | <code yaml> | ||
| + | - hosts: servers | ||
| + | roles: | ||
| + | | ||
| + | username: reader | ||
| + | password: localpassword | ||
| + | database: ticketer | ||
| + | tables: 'user role' | ||
| + | target: '/ | ||
| + | |||
| + | </ | ||
| + | |||
| + | Refer: https:// | ||
| + | |||
| + | ====== 2. java8 Role ====== | ||
| + | |||
| + | Installs oracle java8 jdk to a defined folder. | ||
| + | |||
| + | **example usage:** | ||
| + | |||
| + | <code yaml> | ||
| + | - hosts: servers | ||
| + | roles: | ||
| + | - { role: java8, target: / | ||
| + | </ | ||
| + | |||
| + | Refer: https:// | ||
| + | |||
| + | ====== 3. Filebeat Role ====== | ||
| + | |||
| + | Deploy, configures and starts Filebeat on one or more servers. | ||
| + | |||
| + | **example usage:** | ||
| + | |||
| + | <code yaml> | ||
| + | - hosts: servers | ||
| + | roles: | ||
| + | | ||
| + | log_file_paths: | ||
| + | - / | ||
| + | elastic_search_server: | ||
| + | kibana_server: | ||
| + | url: https:// | ||
| + | target: / | ||
| + | become: true | ||
| + | </ | ||
| + | |||
| + | Refer: https:// | ||
| + | |||
| + | |||
| + | ====== 4. MailHog Role ====== | ||
| + | |||
| + | Deploys and Installs MailHog on one or more servers. | ||
| + | |||
| + | **example usage:** | ||
| + | |||
| + | <code yaml> | ||
| + | - hosts: servers | ||
| + | roles: | ||
| + | - { role: mailhogrole } | ||
| + | </ | ||
| + | |||
| + | Refer: https:// | ||
| + | |||
| + | |||
| + | ====== 5. Process-Control ====== | ||
| + | |||
| + | - A role, which allows starting, stopping and restarting our apps. | ||
| + | - It also ensures applications have started successfully by tailing one or more logs. | ||
| + | |||
| + | **example usage:** | ||
| + | |||
| + | <code yaml> | ||
| + | - hosts: servers | ||
| + | roles: | ||
| + | - { role: ../.., action: stop, proces_name: | ||
| + | - { role: ../.., | ||
| + | action: start, | ||
| + | proces_name: | ||
| + | process_start_script: | ||
| + | process_log_paths: | ||
| + | required_process_startup_time: | ||
| + | process_success_log_msgs: | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | Refer: https:// | ||
| + | |||
| + | ====== 6. Startup-Shutdown-Script ====== | ||
| + | |||
| + | - A role, which deploys startup.sh, shutdown.sh and config.groovy scripts | ||
| + | |||
| + | **example usage:** | ||
| + | |||
| + | <code yaml> | ||
| + | - hosts: servers | ||
| + | roles: | ||
| + | - role: startup-shutdown-script | ||
| + | | ||
| + | - ebonding | ||
| + | - SnmpManager | ||
| + | - Ticketer | ||
| + | - ReportingManager | ||
| + | - NocPortal | ||
| + | - alarmCache | ||
| + | - soap | ||
| + | - cas | ||
| + | </ | ||
| + | |||
| + | Refer: https:// | ||