You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: amber/amber_job_onedata.yaml
+142-99
Original file line number
Diff line number
Diff line change
@@ -7,106 +7,149 @@ description: >
7
7
TOSCA examples for specifying a Chronos Job that runs an application using Onedata storage.
8
8
9
9
topology_template:
10
-
inputs:
11
-
input_onedata_token:
12
-
type: string
13
-
description: User token required to mount the user's INPUT Onedata space
14
-
required: yes
15
-
default: ""
16
-
17
-
output_onedata_token:
18
-
type: string
19
-
description: User token required to mount the user's OUTPUT Onedata space. It can be the same as the input token
20
-
required: yes
21
-
default: ""
22
-
23
-
input_onedata_providers:
24
-
type: string
25
-
description: csv list of favorite Onedata providers to be used to mount the Input Onedata space. If not provided, data locality algo will be applied.
26
-
default: ''
27
-
required: no
28
-
29
-
output_onedata_providers:
30
-
type: string
31
-
description: csv list of favorite Onedata providers to be used to mount the Output Onedata space. If not provided, the same provider(s) used to mount the input space will be used.
32
-
default: ''
33
-
required: no
34
-
35
-
input_onedata_space:
36
-
type: string
37
-
description: Onedata space where the application input data are stored
38
-
required: yes
39
-
default: ""
40
-
41
-
input_path:
42
-
type: string
43
-
description: Path to the input data inside the Input Onedata space
44
-
required: yes
45
-
default: ""
46
-
47
-
output_onedata_space:
48
-
type: string
49
-
description: Onedata space where the application output will be stored. It can be the same as the Input Onedata space
50
-
required: yes
51
-
default: ""
10
+
inputs:
11
+
12
+
input_onedata_token:
13
+
type: string
14
+
description: User token required to mount the user's INPUT Onedata space
15
+
required: yes
16
+
17
+
output_onedata_token:
18
+
type: string
19
+
description: User token required to mount the user's OUTPUT Onedata space. It can be the same as the input token
20
+
required: yes
21
+
22
+
input_onedata_providers:
23
+
type: string
24
+
description: csv list of favorite Onedata providers to be used to mount the Input Onedata space. If not provided, data locality algo will be applied.
25
+
default: ''
26
+
required: no
27
+
28
+
output_onedata_providers:
29
+
type: string
30
+
description: csv list of favorite Onedata providers to be used to mount the Output Onedata space. If not provided, the same provider(s) used to mount the input space will be used.
31
+
default: ''
32
+
required: no
33
+
34
+
input_onedata_space:
35
+
type: string
36
+
description: Onedata space where the application input data are stored
37
+
required: yes
38
+
39
+
input_path:
40
+
type: string
41
+
description: Path to the input data inside the Input Onedata space
42
+
required: yes
43
+
44
+
output_onedata_space:
45
+
type: string
46
+
description: Onedata space where the application output will be stored. It can be the same as the Input Onedata space
47
+
required: yes
48
+
49
+
50
+
output_filenames:
51
+
type: string
52
+
description: csv list of filenames generated by the application run
53
+
default: ''
54
+
required: yes
55
+
56
+
cpus:
57
+
type: float
58
+
description: Amount of CPUs for this job
59
+
required: yes
60
+
61
+
mem:
62
+
type: scalar-unit.size
63
+
description: Amount of Memory for this job
64
+
required: yes
65
+
66
+
67
+
node_templates:
68
+
52
69
53
-
output_path:
54
-
type: string
55
-
description: Path to the output data inside the Output Onedata space
0 commit comments