-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathmain.yml
64 lines (54 loc) · 2.54 KB
/
main.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
---
# Which mode to run galaxy's web handlers in, there are three options: mule, zerg or gunicorn (zerglings/gunicorn + webless handlers)
galaxy_systemd_mode: "zerg"
galaxy_systemd_handlers: 12
galaxy_systemd_workflow_schedulers: 0
# Maximum memory limits (in GB) are set for every process in their systemd unit file, and applied through cgroups.
galaxy_systemd_memory_limit: 16
galaxy_systemd_memory_limit_celery: 5
galaxy_systemd_memory_limit_reports: 5
galaxy_systemd_memory_limit_handler: 5
galaxy_systemd_memory_limit_workflow: 5
galaxy_systemd_memory_limit_zp: 8
### Gunicorn Options
galaxy_systemd_gunicorn_workers: 2
galaxy_systemd_gunicorn_timeout: 300
# Where the socket for the zergling will be placed
galaxy_systemd_gunicorn_socket_name: gunicorn.sock
galaxy_systemd_gunicorn_listen_path: "{{ galaxy_mutable_data_dir }}/{{ galaxy_systemd_gunicorn_socket_name }}"
# Any extra env vars you wish to set for Gunicorn
galaxy_systemd_gunicorn_env: ""
# uncomment this if yuo want to disable the preload option
# galaxy_systemd_gunicorn_preload: ''
galaxy_systemd_gunicorn_preload_default: '--preload'
### Mule Options
galaxy_systemd_memory_limit_mule: 32
### Zergling Options
# How many zerglings to run, >1 means you should set galaxy_zergpool=true
galaxy_systemd_zerglings: 2
# If we're using the zerg method, do we just want to run a single zergling or a
# pool of them? If we're running multiple, then we need the zergpool interface.
galaxy_zergpool: true
# This is where nginx should send requests (if zergpool is enabled.)
galaxy_zergpool_listen_addr: "127.0.0.1:4001"
galaxy_zergpool_socket_name: zergpool.sock
# Where the socket for the zergling will be placed
galaxy_zergpool_listen_path: "{{ galaxy_mutable_data_dir }}/{{ galaxy_zergpool_socket_name }}"
galaxy_systemd_zergling_uwsgi_config_style: "{{ galaxy_config_style | default('ini')}}"
galaxy_systemd_zergling_uwsgi_config_file: "{{ galaxy_config_file }}"
# Any extra env vars you wish to set for Zerglings OR Mules (anything that runs web)
galaxy_systemd_zergling_env: ""
# Any extra env vars to pass to the handlers
galaxy_systemd_handler_env: ""
### Reports
# Do you want to deploy reports too? No, of course not.
galaxy_systemd_reports: false
galaxy_reports_path: "{{ galaxy_config_dir }}/reports.yml"
### Celery
galaxy_systemd_celery: false
galaxy_systemd_celery_pool: threads
galaxy_systemd_celery_workers: 2
galaxy_systemd_celery_concurrency: 2
galaxy_systemd_celery_log_level: DEBUG
galaxy_systemd_celery_env: ""
galaxy_systemd_celery_beat_schedule_path: "{{ galaxy_mutable_data_dir }}/celery-beat-schedule"