forked from pivotal-cf/docs-pcf-install
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path_advanced-features.html.md.erb
106 lines (57 loc) · 4.95 KB
/
_advanced-features.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
The **Advanced Features** section of Pivotal Application Service (PAS) includes new functionality that may have certain constraints. Although these features are fully supported, Pivotal recommends caution when using them in production environments.
### <a id="disk-memory-overcommit"></a> Diego Cell Memory and Disk Overcommit
If your apps do not use the full allocation of disk space and memory set in the **Resource Config** tab, you might want use this feature. These fields control the amount to overcommit disk and memory resources to each Diego Cell VM.
For example, you might want to use the overcommit if your apps use a small amount of disk and memory capacity compared to the amounts set in the **Resource Config** settings for **Diego Cell**.
<p class="note"><strong>Note:</strong> Due to the risk of app failure and the deployment-specific nature of disk and memory use, Pivotal has no recommendation about how much, if any, memory or disk space to overcommit.</p>
To enable overcommit, do the following:
1. Select **Advanced Features**.
<%= image_tag("./disk-memory-overcommit.png") %>
1. Enter the total desired amount of Diego cell memory value in the **Cell Memory Capacity (MB)** field. Refer to the **Diego Cell** row in the **Resource Config** tab for the current Cell memory capacity settings that this field overrides.
1. Enter the total desired amount of Diego cell disk capacity value in the **Cell Disk Capacity (MB)** field. Refer to the **Diego Cell** row in the **Resource Config** tab for the current Cell disk capacity settings that this field overrides.
1. Click **Save**.
<p class="note"><strong>Note:</strong> Entries made to each of these two fields set the total amount of resources allocated, not the overage.</p>
<% if current_page.data.deployment != "IST" %>
### <a id="rfc_whitelist"></a> Whitelist for Non-RFC-1918 Private Networks
Some private networks require extra configuration so that internal file storage (WebDAV) can communicate with other PCF processes.
The **Whitelist for non-RFC-1918 Private Networks** field is provided for deployments that use a non-RFC 1918 private network. This is typically a private network other than `10.0.0.0/8`, `172.16.0.0/12`, or `192.168.0.0/16`.
Most PCF deployments do not require any modifications to this field.
To add your private network to the whitelist, do the following:
1. Select **Advanced Features**.
1. Append a new `allow` rule to the existing contents of the **Whitelist for non-RFC-1918 Private Networks** field.
<%= image_tag("./nonrfc_whitelist.png") %>
Include the word `allow`, the network CIDR range to allow, and a semi-colon (`;`) at the end. For example:
```
allow 172.99.0.0/24;
```
1. Click **Save**.
### <a id="cf_cli_timeout"></a> CF CLI Connection Timeout
The **CF CLI Connection Timeout** field allows you to override the default five second timeout of the Cloud Foundry Command Line Interface (cf CLI) used within your PCF deployment. This timeout affects the cf CLI command used to push PAS errand apps such as Notifications, Autoscaler, and Apps Manager.
Set the value of this field to a higher value, in seconds, if you are experiencing domain name resolution timeouts when pushing errands in PAS.
To modify the value of the **CF CLI Connection Timeout**, perform the following steps:
1. Select **Advanced Features**.
1. Add a value, in seconds, to the **CF CLI Connection Timeout** field.
<%= image_tag("./cf_cli_connection_timeout.png") %>
1. Click **Save**.
<% end %>
### <a id="smb"></a> SMB Volume Services
You can optionally enable SMB volume services so developers can bind existing SMB shares to their apps. For more information, see the [Enabling Volume Services](../opsguide/enable-vol-services.html) topic.
To enable SMB volume services, do the following:
1. Select **Enable SMB volume services**.<br>
<img src="images/enable-smb.png" width="250">
1. Click **Save**.
1. In the **Errands** pane, set the **SMB Broker Errand** to **On**.
1. Click **Save**.
<% if current_page.data.deployment != "IST" %>
### <a id='tls'></a> Enable TLS for Internal System Database
You can optionally enable TLS for clients of the internal system database. This feature is in beta, and the checkbox is disabled by default. For more information about the internal system database, see [Migrating to Internal Percona MySQL](../opsguide/migrate-percona-mysql.html).
<img src="images/enable-tls-beta.png" width="300">
To enable TLS for clients of the internal system database, do the following:
1. Select **BETA: Enable TLS for internal system database**.
1. Click **Save**.
### <a id="zdt-app-deployments"></a> Rolling App Deployments
You can optionally disable rolling app deployments. For more information, see the [Rolling App Deployments (Beta)](../devguide/deploy-apps/rolling-deploy.html) topic.
<img src="images/zero-downtime.png" width="250">
To disable zero downtime app deployments, do the following:
1. Select **Disable Zero Downtime App Deployments**.
1. Click **Save**.
<% end %>