LILiK
/
lilik_playbook
5
0
Fork 0
Code Issues 0 Pull Requests 0 Releases 0 Wiki Activity
Playbooks to a new Lilik
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
319 Commits
12 Branches
967 KiB
Tree: 32e9eeb91f
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '32e9eeb91f'
${ noResults }
lilik_playbook/projects.yaml

27 lines
607 B
Raw Normal View History

add gitlab roles
8 years ago
connection/ssh_lxc: new style for containers Now which *host* is hosting a specific container is not defined in the playbook yaml file but centrally in the invetory under the `ansible_lxc_host` variable. The `lxc_guest` role is runned directly against the guest, even if it doesn't exist yet, and lxc tasks are delegated to the lxc-running physical host. In this way it should be easier to scale-up and configure multiple istance of a service on different containers without changing the playbook. Look at `/ldap.yaml` for a commented example.
4 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
add gitlab roles
8 years ago
use gitlab from debian repositories, temp vm name: projects2
7 years ago
​
connection/ssh_lxc: new style for containers Now which *host* is hosting a specific container is not defined in the playbook yaml file but centrally in the invetory under the `ansible_lxc_host` variable. The `lxc_guest` role is runned directly against the guest, even if it doesn't exist yet, and lxc tasks are delegated to the lxc-running physical host. In this way it should be easier to scale-up and configure multiple istance of a service on different containers without changing the playbook. Look at `/ldap.yaml` for a commented example.
4 years ago
use gitlab from debian repositories, temp vm name: projects2
7 years ago
connection/ssh_lxc: new style for containers Now which *host* is hosting a specific container is not defined in the playbook yaml file but centrally in the invetory under the `ansible_lxc_host` variable. The `lxc_guest` role is runned directly against the guest, even if it doesn't exist yet, and lxc tasks are delegated to the lxc-running physical host. In this way it should be easier to scale-up and configure multiple istance of a service on different containers without changing the playbook. Look at `/ldap.yaml` for a commented example.
4 years ago
add monitoring role to playbooks
7 years ago
​
​
 
  1. ---

  2. - hosts: projects

  3.   gather_facts: false

  4.   tags:

  5.     - lxc

  6.   tasks:

  7.     - import_role: name='lxc_guest'

  8.       vars:

  9.         vm_name: '{{ inventory_hostname }}'

  10.         vm_size: '4G'

  11.         vg_name: '{{ hostvars[ansible_lxc_host]["vg_name"] }}'

  12.       delegate_to: '{{ ansible_lxc_host }}'

  13.     - set_fact: ansible_connection='ssh_lxc'

  14.     - setup:

  15.     - include_role: name='ssh_server'

  16.     - set_fact: ansible_connection='ssh'

  17. 

  18. - hosts: projects

  19.   roles:

  20.     - role: dns_record

  21.     - role: reverse_proxy

  22.       hostname: projects

  23.     - role: gitlab

  24. 

  25. - hosts: status

  26.   roles:

  27.     - role: icinga2-monitoring