-
Notifications
You must be signed in to change notification settings - Fork 1
/
services.utf8
51 lines (33 loc) · 1.52 KB
/
services.utf8
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
QUESTION
========
SERVICES.1: There is talk about "services" which are called cms, lms, etc... Are these ubuntu upstart services? should they automatically be created by the playbooks?
SERVICES.2: How can we stop/start/restart "the services". is there a proposed procedure?
ANSWER
=============
SERVICES.1:
Yes, each role from the ansible playbooks provides different services, which are setup as Ubuntu upstart scripts.
For example, the edxapp role creates the following upstart services, using templates in `playbooks/roles/edxapp/templates/*.conf.j2`
```
# ls playbooks/roles/edxapp/templates/*.conf.j2
playbooks/roles/edxapp/templates/cms.conf.j2 playbooks/roles/edxapp/templates/edx-worker-lms.conf.j2 playbooks/roles/edxapp/templates/lms-preview.conf.j2
playbooks/roles/edxapp/templates/edx-worker-cms.conf.j2 playbooks/roles/edxapp/templates/edx-workers.conf.j2 playbooks/roles/edxapp/templates/lms-xml.conf.j2
playbooks/roles/edxapp/templates/edx-worker-lms-xml.conf.j2 playbooks/roles/edxapp/templates/edxapp.conf.j2 playbooks/roles/edxapp/templates/lms.conf.j2
```
These templates are evaluated and copied to `/etc/init` on the VM being configured.
SERVICES.2:
To stop a service:
```
# service <name> stop
```
To start a service:
```
# service <name> start
```
To restart:
```
# service <name> restart
```
Also, you can either start/stop the LMS & CMS services individually (ie, `service lms-xml restart`), or all at the same time using the `edxapp` service:
```
# service edxapp restart
```