forked from pivotal-cf/docs-pcf-install
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathupgrading-pcf.html.md.erb
209 lines (142 loc) · 12.5 KB
/
upgrading-pcf.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
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
---
title: Upgrading Pivotal Cloud Foundry
owner: Ops Manager
---
<style>
.note.warning {
background-color: #fdd;
border-color: #fbb
}
.note.warning:before {
color: #f99;
}
</style>
<strong><%= modified_date %></strong>
This topic describes upgrading Pivotal Cloud Foundry® to version 1.7. The upgrade procedures below describe upgrading Ops Manager, Elastic Runtime, and product tiles.
If you have already upgraded your Ops Manager to version 1.7 and want to upgrade
individual products such as PCF Elastic Runtime, <a href="https://network.pivotal.io/products/p-mysql">Pivotal MySQL</a>, or <a
href="https://network.pivotal.io/products/pivotal-rabbitmq-service">RabbitMQ</a> in your PCF deployment, see the <a href="./upgrading-products.html">Upgrading
Products in a PCF Deployment</a> topic.
<p class="note warning">
<strong>WARNING: </strong> Before you upgrade to Pivotal Cloud Foundry 1.7, you must migrate all apps that are currently running on DEA architecture to run on Diego architecture. All apps that do not already run on Diego will terminate during an upgrade from 1.6 to 1.7.
</p>
<p class="note"><strong>Note</strong>: The apps in your deployment continue to run during the upgrade. However, you cannot write to your deployment or make changes to apps during the upgrade.</p>
**Important**: Read the Known Issues section of the [Pivotal Cloud Foundry®](https://network.pivotal.io/products/pivotal-cf) (PCF)
[Release Notes](../pcf-release-notes/index.html) before getting started.
## <a id="beforeupgrade"></a>Before You Upgrade
This section contains important guidelines that you must follow before beginning an upgrade to PCF 1.7. Failure to follow these instructions may jeopardize your existing deployment data or cause your upgrade to fail.
The tasks you need to complete before upgrade fall into three categories:
+ [Choose Single-AZ or Multi-AZ](#choose-az) - choose a single-AZ or multi-AZ deployment.
+ [Prepare Your Environment](#prepare-env) — includes making sure you have sufficient disk space.
+ [Prepare Databases and Apps](#prepare-db) — includes backing up data and migrating any apps.
that currently use the DEA architecture to use the Diego architecture.
+ [Check System Health](#check-health) — perform a health check of your system, from virtual machines (VMs) to service tiles.
###<a id="choose-az"></a>Choose Single-AZ or Multi-AZ
Ops Manager 1.7 ships with a new multi-AZ functionality that results in multiple networks.
When you upgrade to PCF 1.7 from a previous version instead of performing a new full install, you have a single-AZ deployment. If you want to use PCF 1.7 with multi-AZ functionality, choose one of the following procedures:
* Upgrade and then apply multi-AZ:
1. Follow the upgrade instructions on this page to upgrade to PCF 1.7.
2. Follow the instructions in this [Knowledge Base article](https://discuss.zendesk.com/hc/en-us/articles/219118768-How-to-enable-advanced-mode-in-the-Ops-Manager) to enable advanced mode in Ops Manager.
3. Follow the instructions in this [Knowledge Base article](https://discuss.zendesk.com/hc/en-us/articles/219119508-How-to-add-or-modify-my-Availability-Zones-without-the-need-to-reinstall-Pivotal-Cloud-Foundry-) to apply the multi-AZ feature to your deployment.
* Perform a [new installation](../installing/index.html) of PCF 1.7.
### <a id="prepare-env"></a>Prepare Your Environment for Upgrade
1. Install the releases from your currently deployed
version to the target version in sequential order. For example, if your deployment uses Ops Manager release 1.5 and you are upgrading to 1.7,
you must sequentially install 1.6 and 1.7.
1. Ensure that you are using [Elastic Runtime (ERT)](./upgrading-products.html) v. 1.6.9 or higher.
2. Ensure that every product tile on the Installation Dashboard is compatible with the new version of Ops Manager. For specific compatibility information, refer to the full [Product Version Matrix](http://docs-pivotal.io/compatibility-matrix.pdf).
If a product does not meet this requirement, you must upgrade the product or
remove the tile before upgrading Ops Manager.
3. For each product tile you have installed, review the upgrade documentation that is specific to the tile. For example, if you have RabbitMQ, you need to increase the number of HAproxy instances from one to two. See [RabbitMQ for Pivotal Cloud Foundry Upgrades](http://docs.pivotal.io/rabbitmq-cf/upgrade.html).
4. <%= partial 'check_disk_before_upgrade' %>
5. If you have disabled lifecycle errands for any installed product in order to reduce deployment time, Pivotal recommends that you re-enable these errands before upgrading. See <a href="./add-delete.html#add-import">Adding and Deleting Products</a> for more information.
6. Ensure that the VM resurrector is turned off:
1. From your Installation Dashboard, select the **Ops Manager Director** tile.
2. Click **Director Config**.
3. Clear the **Enable VM resurrector plugin** checkbox.
7. If you are upgrading a vSphere environment, ensure that you have the following information about your existing environment before starting the upgrade:
* Note these IP addresses, which can be found in the vSphere web client, **Manage** > **Settings** > **vApp Options**.
This is the same information you entered at the end of deploying [Ops Manager on vSphere](http://docs.pivotal.io/1.6/pivotalcf/customizing/deploying-vm.html).
* IP Address of the Ops Manager
* Netmask
* Default Gateway
* DNS Servers
* NTP Servers
* Note this VM hardware information so you can set up the new VM with similar settings. You can find this in the vSphere web
client, **Manage** > **Settings** > **VM Hardware**.
* CPU
* Memory
* Hard Disk 1
* Network Adapter 1 - When you set up the new VM, ensure your network adapters are configured properly and are on the same network.
### <a id="prepare-db"></a>Prepare Databases and Apps for Upgrade
1. Back up all critical data prior to upgrading to PCF 1.7. For example, to backup a 1.6 environment, follow these instructions <a href="http://docs.pivotal.io/pivotalcf/1.6/customizing/backup-restore/backup-pcf.html">Backing Up Pivotal Cloud Foundry</a>. <br>
2. Before you upgrade to Pivotal Cloud Foundry 1.7, you must migrate all apps that are currently running on DEA architecture to run on Diego architecture. Pivotal does not support DEA architecture in Pivotal Cloud Foundry 1.7. See the [Migrating Apps to Diego](../adminguide/apps-enable-diego.html) topic for information.
### <a id="check-health"></a>Check System Health Before Upgrade
5. Run `bosh cloudcheck` to confirm that the VMs are healthy. See the [BOSH Cloudcheck](./trouble-advanced.html#cck) topic.
6. Check the system health of installed products. In the Installation Dashboard, select the **Status** tab for each service tile. Confirm that all jobs are healthy.
7. (Optional) Check the logs for errors before proceeding with the upgrade.
See the [Viewing Logs in the Command Line Interface](../devguide/deploy-apps/streaming-logs.html#view) topic.
8. There should be no outstanding changes in Ops Manager or any other tile. All tiles should be green.
Click **Apply Changes** if necessary.
9. After applying changes, click **Recent Install Logs** to confirm that the changes completed cleanly:
```
Cleanup complete
{"type": "step\_finished", "id": "clean\_up\_bosh.cleaning\_up"}
Exited with 0.
```
## <a id="keep"></a>Upgrading with Installed Products ##
Follow the steps below to upgrade Ops Manager and keep all installed products.
<p class="note"><strong>Note</strong>: Ops Manager 1.7 uses the User Account and Authentication (UAA), instead of only local user account authentication. When you import your pre-1.7 file to Ops Manager, your user name changes to <code>admin</code> and your password remains the same. It also prompts you to create a shared passphrase, which is distinct from your password. Your passphrase on a new import will be the same as your password. However, you must change the passphrase for security purposes. </p>
1. From the Product Dashboard, select **Actions > Export installation
settings**.
<%= image_tag("./images/upgrading/upgrade_to_1.7.png") %>
This exports the current PCF installation with all of its assets.
When you export an installation, the export contains the base VM images and
necessary packages, and references to the installation IP addresses.
As a result, an exported file can be very large, as much as 5 GB or more.
* The export time depends on the size of the exported file.
* Some browsers do not provide feedback on the status of the export
process, and may appear to hang.
* Some operating systems may automatically unzip the exported installation.
If this occurs, create a zip file of the unzipped export.
<p class="note"><strong>Note</strong>: When creating a zip file of an
unzipped export, do not start compressing at the “installation” folder
level.
Instead, start compressing at the level containing the <code>config.yml</code> file:</p>
<%= image_tag("./images/upgrading/compress.png") %>
2. Download the latest Ops Manager VM Template from the [Pivotal
Network](https://network.pivotal.io/products/pivotal-cf) site.
1. Record the IP address of the existing Ops Manager VM.
1. To avoid IP conflicts, power off the existing Ops Manager VM.
1. Deploy the new Ops Manager VM:
* [Launching an Ops Manager Director Instance on AWS](./cloudform-om-deploy.html)
* [Provisioning the OpenStack Infrastructure](./openstack-setup.html)
* [Deploying Operations Manager to vSphere](./deploying-vm.html)
* [Deploying Operations Manager to vCloud Air and vCloud](./pcf-vchs-vcloud.html)
1. When redirected to the **Welcome to Ops Manager** page, select **Import Existing Installation**.
<%= image_tag("./images/upgrading/welcome.png") %>
1. When prompted, enter the following:
* **Decryption Passphrase**, which is the same as your password.
* Click **Choose File** and browse to the installation zip file exported in Step 3 above.
<%= image_tag("./images/upgrading/decryption_passphrase.png") %>
1. Click **Import**.
<p class="note"><strong>Note</strong>:
Some browsers do not provide feedback on the status of the import process,
and may appear to hang.</p>
1. Before you see the new PCF 1.7 **Installation Dashboard**, a Security Features alert appears. Take note of your new **username**. Ensure you change your decryption passphrase before sharing it with other users. Click **Continue**.
<%= image_tag("./images/upgrading/security_features.png") %>
1. A "Successfully imported installation" message appears upon completion.
<%= image_tag("./images/upgrading/success.png") %>
1. Click **Apply Changes**. This immediately imports and applies upgrades to all tiles in a single transaction.
1. Click each service tile, select the **Status** tab, and confirm that all VMs appear and are in good health.
1. Remove the original Ops Manager VM from your IaaS if the new installation functions correctly.
## <a id="aftertheupgrade"></a>After the Upgrade
* Advise your application developers about the Diego architecture. See the [Migrating Apps to Diego](../adminguide/apps-enable-diego.html) and [Diego Architecture](./../concepts/diego/diego-architecture.html) topics for more information.
* Ops Manager 1.7 defines specific instance types instead of custom sizes for vSphere or vCloud. Each instance adopts an instance type that is the closest match to its previous custom size for CPU, memory, and disk space. After the upgrade, you can modify the automatically selected instance size by selecting a different <code>type</code> under <strong>Resource Config</strong> for each of your installed tiles.
* In Ops Manager 1.7, all product tiles use floating stemcells by default. This increases the security of your deployment by enabling tiles to automatically use the latest patched version of a stemcell, but it may significantly increase the amount of time required by a tile upgrade. Review the [Understanding Floating Stemcells](./understanding-stemcells.html) topic for more information.
* (Optional) You can review your product tiles and configure values accordingly. For example, for Elastic Runtime, review the installation topic for new features:
* [Launching an Ops Manager Director Instance on AWS](./cloudform-om-deploy.html)
* [Provisioning the OpenStack Infrastructure](./openstack-setup.html)
* [Deploying Operations Manager to vSphere](./deploying-vm.html)
* [Deploying Operations Manager to vCloud Air and
vCloud](./pcf-vchs-vcloud.html)