forked from pivotal-cf/docs-pcf-install
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathunderstanding-stemcells.html.md.erb
16 lines (10 loc) · 1.35 KB
/
understanding-stemcells.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
---
title: Understanding Floating Stemcells
owner: Ops Manager
---
<strong><%= modified_date %></strong>
This topic describes how floating stemcells work in Pivotal Cloud Foundry® (PCF) version 1.7, and the consequences for upgrading product tiles in Ops Manager.
To increase the security of your deployment, all product tiles use floating stemcells by default. This enables tiles to automatically use the latest patched version of a stemcell.
When an operator upgrades a product tile, Ops Manager checks to see whether there is a new version of the stemcell. If an updated stemcell is available, Ops Manager installs the upgraded tile and all compatible product tiles in the deployment on the new stemcell. This ensures that when a vulnerability is discovered, PCF can quickly propagate a patched stemcell to all VMs in the deployment.
Operators can now perform certain deployment-wide updates, such as CVEs, by uploading a new stemcell instead of uploading `.pivotal` files for each tile, which reduces the time spent waiting for files to upload. Operators can upload new stemcells using the Ops Manager API or through a product tile in the Ops Manager Installation Dashboard.
However, operators who want to upgrade a single product tile may face significantly longer wait times, depending on the number of tiles in the deployment and the availability of a new stemcell.