forked from pivotal-cf/docs-pcf-install
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathazure.html.md.erb
141 lines (101 loc) · 5.36 KB
/
azure.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
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
---
title: Installing Pivotal Cloud Foundry on Azure
owner: Ops Manager
---
<strong><%= modified_date %></strong>
This guide describes how to install [Pivotal Cloud Foundry](https://network.pivotal.io/products/pivotal-cf) (PCF) on Azure.
To view production-level deployment options for PCF on Azure, see the [Reference Architecture for Pivotal Cloud Foundry on Azure](../refarch/azure/azure_ref_arch.html).
## <a id="general"></a> General Requirements
<%= partial 'requirements' %>
## <a id="azure"></a> Azure Requirements
The following are the minimum resource requirements for deploying a PCF deployment with Ops Manager and Pivotal Application Service (PAS) on Azure:
* VMs:
- **PAS**: At a minimum, a new Azure deployment requires the following VMs for PAS:
<table border='1' class='nice'>
<tr>
<th rowspan=6>PAS and Ops Manager</th>
<th>VM Type</th>
<th>VM Count</th>
</tr><tr>
<td>F1s</td>
<td>27</td>
</tr><tr>
<td>F2s</td>
<td>4</td>
</tr><tr>
<td>F4s</td>
<td>4</td>
</tr><tr>
<td>DS11 v2</td>
<td>1</td>
</tr><tr>
<td>DS12 v2</td>
<td>1</td>
</tr>
</table>
By default, PAS deploys the number of VM instances required to run a highly available configuration of PCF. If you are deploying a test or sandbox PCF that does not require HA, then you can scale down the number of instances in your deployment. For information about the number of instances required to run a minimal, non-HA PCF deployment, see [Scaling PAS](../opsguide/scaling-ert-components.html).
- **Small Footprint PAS**: To run Small Footprint PAS, an Azure deployment requires:
<table id='azure-requirements' border="1" class="nice">
<tr>
</tr></tr>
<th>Azure Requirements</th>
<th>VM Type</th>
<th>VM Count</th>
<th>Notes</th>
</tr><tr>
<th rowspan=4>Small Footprint PAS</th>
<td>DS11 v2</td>
<td>1</td>
<td></td>
</tr><tr>
<td>DS12 v2</td>
<td>2</td>
<td></td>
</tr><tr>
<td>F2s</td>
<td>0</td>
<td>Add 1 to count if using HAProxy</td>
</tr><tr>
<td>F1s</td>
<td>5</td>
<td></td>
</tr><tr>
<th rowspan=2>Ops Manager</th>
<td>DS2 v2</td>
<td>1</td>
<td></td>
</tr><tr>
<td>F4s</td>
<td>4</td>
<td></td>
</tr>
</table>
<p class="note"><strong>Note:</strong> Specific instance types are only supported in certain regions. See the <a href="https://azure.microsoft.com/en-us/regions/services/">Azure documentation</a> for a complete list. If you are deploying PCF in a region that does not support the above instance types, see the <a href="https://docs.pivotal.io/pivotalcf/2-2/opsman-api#overriding-defaults-with-custom-disk-types">Ops Manager API documentation</a> for instructions on how to override the default VM sizes. Changing the default VM sizes may increase the cost of your deployment. </p>
* An OS disk of 120 GB for the Ops Manager VM.
<p class="note"><strong>Note:</strong> Ops Manager v1.11 requires a Director VM with at least 8 GB memory.</p>
* To deploy PCF on Azure, you must have the Azure CLI v2.0. For instructions on how to install the Azure CLI for your operating system, see [Preparing to Deploy Ops Manager on Azure Manually](../om/azure/prepare-env-manual.html#install).
## <a id="permissions"></a> Azure Permissions Guidelines
Pivotal recommends following the principle of least privilege by scoping privileges to the most restrictive permissions possible for a given role. See [IaaS Permissions Guidelines](./iaas-user-roles.html) for recommendations on how to create and scope Azure accounts for PCF.
## <a id="security"></a> Azure Security Documents
* [Azure security documentation](https://docs.microsoft.com/en-us/azure/security/)<br />
This site has documentation on Azure security tools. It provides a general guide to how to manage IaaS users and credentials.
## <a id='install'></a> Install PCF on Azure
Complete the following procedures to install PCF on Azure:
1. [Preparing to Deploy Ops Manager on Azure Manually](../om/azure/prepare-env-manual.html)
1. You can choose to deploy BOSH Director with Terraform or manually:
* [Deploying BOSH and Ops Manager on Azure Using Terraform](../om/azure/prepare-env-terraform.html) (Recommended)
* [Deploying Ops Manager on Azure Manually](../om/azure/deploy-manual.html)
1. [Configuring BOSH Director on Azure Manually](../om/azure/config-manual.html)
1. [Configuring PAS](configure-pas.html)
## <a id='install-gov'></a> Install PCF on Azure Government Cloud
To deploy PCF on Azure Government Cloud, see the [Deploying PCF on Azure Government Cloud](../om/azure/gov-cloud.html) topic.
## <a id='install-germany'></a> Install PCF in Azure Germany
To deploy PCF in Azure Germany, see the [Deploying PCF in Azure Germany](../om/azure/german-cloud.html) topic.
## <a id='troubleshoot'></a> Troubleshoot PCF on Azure
To troubleshoot known issues when deploying PCF on Azure, see the [Troubleshooting PCF on Azure](azure-troubleshooting.html) topic.
## <a id='delete'></a> Delete PCF on Azure
You can use the Azure Portal console to remove all the components of a PCF on Azure installation.
* [Deleting a PCF on Azure Installation](deleting-azure-install.html)
## <a id='upgrade'></a> Upgrade PCF on Azure
Upgrade your BOSH Director as part of the upgrade process documented in the [Upgrading Pivotal Cloud Foundry](upgrading-pcf.html) topic.
* [Upgrading BOSH Director on Azure](azure-om-upgrade.html)