forked from cloudfoundry/docs-services
-
Notifications
You must be signed in to change notification settings - Fork 0
/
volume-services.html.md.erb
107 lines (97 loc) · 2.38 KB
/
volume-services.html.md.erb
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
---
title: Volume Services (Experimental)
owner: Core Services
---
<strong><%= modified_date %></strong>
## <a id='introduction'></a>Introduction ##
Cloud Foundry application developers may want their applications to mount one or more volumes in order to write to a reliable, non-ephemeral file system. By integrating with service brokers and the Cloud Foundry runtime, providers can offer these services to developers through an automated, self-service, and on-demand user experience.
<p class="note"><strong>Note</strong>: This feature is experimental.</p>
## <a id='schema'></a>Schema ##
### Service Broker Bind Response ###
<table border="1" class="nice">
<thead>
<tr>
<th>Field</th>
<th>Type</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>volume_mounts*</td>
<td>volume_mount[]</td>
<td>An array of <i>volume_mount</i> JSON objects</td>
</tr>
</tbody>
</table>
### volume_mount ###
<table border="1" class="nice">
<thead>
<tr>
<th>Field</th>
<th>Type</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>container_path</td>
<td>string</td>
<td>The path to mount inside the application container</td>
</tr>
<tr>
<td>mode</td>
<td>string</td>
<td>Indicates whether the volume should be read-only or read-write</td>
</tr>
<tr>
<td>private</td>
<td>private</td>
<td>A <i>private</i> JSON object</td>
</tr>
</tbody>
</table>
### private ###
<table border="1" class="nice">
<thead>
<tr>
<th>Field</th>
<th>Type</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>driver</td>
<td>string</td>
<td>The path to mount inside the application container</td>
</tr>
<tr>
<td>group_id</td>
<td>string</td>
<td>Indicates whether the volume should be read-only or read-write</td>
</tr>
<tr>
<td>config</td>
<td>string</td>
<td>A configuration string associated with a particular broker/driver pair. The broker is free to return any string here and it will be passed through the volume driver identified in the `driver` field</td>
</tr>
</tbody>
</table>
### Example ###
<pre class="terminal">
{
...
"volume_mounts": [
{
"container_path": "/data/images",
"mode": "r",
"private": {
"driver": "cephdriver",
"group_id": "bc2c1eab-05b9-482d-b0cf-750ee07de311",
"config": "Some arbitrary configuration string. Could be a marshalled json"
}
}
]
}
</pre>