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
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
|
<!--
Copyright 2017-2019 Lars Wirzenius
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Affero General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
-->
# Controller worker management
The Ick2 controller manages information about workers. Workers are
things that actually do the builds. A worker is described by a resource
like this:
EXAMPLE project resource
{
"worker": "obelix",
"protocol": "ssh",
"address": "obelix.ick.example.com",
"user": "ick",
"keywords": {
"debian_release": "debian9",
"debian_codename": "stretch",
"debian_arch": "amd64"
}
}
In other words, there are several things that define a worker:
* The name, in the `worker` field. This is used for referreing to the
project in the API.
* Information for how to access the worker from the outside. The
worker manager needs this, in case it's running on a different host
from the worker.
* Some keywords to describe the worker. The controller will use this
to pick the appropriate worker to give a build to.
## Managing workers
Note that this only tests managing information about workers via the
controller API. It doesn't actually talk to the worker itself.
SCENARIO managing workers
GIVEN an access token for user with scopes
... uapi_workers_get
... uapi_workers_id_get
... uapi_workers_id_put
... uapi_workers_id_delete
AND an access token for obelix with scopes
... uapi_workers_post
AND a running ick controller
WHEN user makes request GET /workers
THEN result has status code 200
AND body matches { "workers": [] }
WHEN obelix makes request POST /workers with a valid token and body
... {
... "protocol": "ssh",
... "address": "obelix.ick.example",
... "user": "ick",
... "keywords": {
... "debian_codename": "stretch"
... }
... }
THEN result has status code 201
AND worker id is OBELIX
AND body matches
... {
... "worker": "${OBELIX}",
... "protocol": "ssh",
... "address": "obelix.ick.example",
... "user": "ick",
... "keywords": {
... "debian_codename": "stretch"
... }
... }
AND controller state directory contains worker obelix
WHEN user makes request GET /workers
THEN result has status code 200
AND body matches
... {
... "workers": [
... {
... "worker": "${OBELIX}",
... "protocol": "ssh",
... "address": "obelix.ick.example",
... "user": "ick",
... "keywords": {
... "debian_codename": "stretch"
... }
... }
... ]
... }
WHEN user stops ick controller
GIVEN a running ick controller
WHEN user makes request GET /workers/${OBELIX}
THEN result has status code 200
AND body matches
... {
... "worker": "${OBELIX}",
... "protocol": "ssh",
... "address": "obelix.ick.example",
... "user": "ick",
... "keywords": {
... "debian_codename": "stretch"
... }
... }
WHEN user makes request PUT /workers/${OBELIX} with a valid token
... and body
... {
... "worker": "${OBELIX}",
... "protocol": "local",
... "keywords": {
... "debian_codename": "unstable"
... }
... }
THEN result has status code 200
AND body matches
... {
... "worker": "${OBELIX}",
... "protocol": "local",
... "keywords": {
... "debian_codename": "unstable"
... }
... }
AND controller state directory contains worker obelix
WHEN user makes request GET /workers/${OBELIX}
THEN result has status code 200
AND body matches
... {
... "worker": "${OBELIX}",
... "protocol": "local",
... "keywords": {
... "debian_codename": "unstable"
... }
... }
WHEN user makes request DELETE /workers/${OBELIX}
THEN result has status code 200
WHEN user makes request GET /workers/${OBELIX}
THEN result has status code 404
FINALLY stop ick controller
|
