-
Notifications
You must be signed in to change notification settings - Fork 34
/
Copy path_on-demand-service-table.html.md.erb
59 lines (49 loc) · 1.63 KB
/
_on-demand-service-table.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
Some PCF services offer *on-demand* service plans.
These plans let developers provision service instances when they want.
These contrast with the more common *pre-provisioned* service plans,
which require operators to provision the service instances during installation
and configuration through the service tile UI.
The following PCF services offer on-demand service plans:
* MySQL for PCF v2.0 and later
* RabbitMQ for PCF
* Redis for PCF
* Pivotal Cloud Cache (PCC)
These services package and deliver their on-demand service offerings differently.
For example, some services, like Redis for PCF, have one tile,
and you configure the tile differently depending on whether you want on-demand
service plans or pre-provisioned service plans.
For other services, like PCC and MySQL for PCF, only on-demand service plans are available.
The following table lists and contrasts the different ways that PCF services
package on-demand and pre-provisioned service offerings.
<table class="nice">
<tr>
<th>PCF service tile</th>
<th>Standalone product related to the service</th>
<th>Versions supporting on demand</th>
<th>Versions supporting pre-provisioned</th>
</tr>
<tr>
<td>RabbitMQ for PCF</td>
<td>Pivotal RabbitMQ</td>
<td>v1.8 and later</td>
<td>All versions</td>
</tr>
<tr>
<td>Redis for PCF</td>
<td>Redis</td>
<td>v1.8 and later</td>
<td>All versions</td>
</tr>
<tr>
<td>MySQL for PCF</td>
<td>MySQL </td>
<td>v2.x<br></td>
<td><em>NA</em></td>
</tr>
<tr>
<td>PCC</td>
<td>Pivotal GemFire</td>
<td>All versions</td>
<td><em>NA</em></td>
</tr>
</table>