openstack/openstack-manuals
Code Issues Proposed changes

[arch-guide] Correct paragraph about vertical upgrades in compute

Browse Source 
Added more clarity to paragraph and deleted any sentence fragments
that didn't make sense. This clarifies the point of rolling upgrades
for vertical scaling of individual compute nodes.

Change-Id: I182f799bbbf2ffa88bcf7c16fd580c52274f88a4
Closes-Bug: #1739438
This commit is contained in:
Ben Silverman 2018-01-18 12:49:24 -07:00 committed by Ben Silverman
parent 4b4bfa5346
commit 74318ccd18
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/arch-design/source/design-compute/design-compute-arch.rst
View File

@ -54,9 +54,11 @@ upgraded to account for increases in
demand, known as vertical scaling. Upgrading CPUs with more
cores, or increasing the overall server memory, can add extra needed
capacity depending on whether the running applications are more CPU
intensive or memory intensive. Since OpenStack schedules workload placement
based on capacity and technical requirements, removing compute nodes from
availability and upgrading them using a rolling upgrade design.
intensive or memory intensive. We recommend a rolling upgrade of compute
nodes for redundancy and availability.
After the upgrade, when compute nodes return to the OpenStack cluster, they
will be re-scanned and the new resources will be discovered adjusted in the
OpenStack database.
When selecting a processor, compare features and performance
characteristics. Some processors include features specific to