openstack/openstack-manuals
Code Issues Proposed changes

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

Browse Source
This commit is contained in:
Zuul 2018-01-19 00:31:19 +00:00 committed by Gerrit Code Review
commit 6a3becb445
1 changed files with 5 additions and 3 deletions

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

@ -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