cf66f5d279
First pass - generic updates only. (command input/output to be done) Address patchset 1 review comments. Replace examples using openstack with metrics server Remove DS app from application-list output Additional migration to FluxCD (snmp, auditd) Minor textual change. Fix merge conflict. Revert install r5 change. Story: 2009138 Task: 45238 Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: Ia40ff45f12ec7b7ffa859e0d8bb5535303870d83
27 lines
1002 B
ReStructuredText
27 lines
1002 B
ReStructuredText
|
|
.. dqn1590002648435
|
|
.. _software-updates-and-upgrades-overview:
|
|
|
|
========
|
|
Overview
|
|
========
|
|
|
|
The system application-update -n |prefix|-openstack -v <new-app-version>
|
|
command is used for corrective content \(bug fixes\) -type updates to the
|
|
running containerized openstack application.
|
|
|
|
This means that the system application-update -n |prefix|-openstack is **not**
|
|
used for upgrading between OpenStack releases \(e.g. Train to Ussuri\). The
|
|
:command:`system application-update` assumes that there is no data schema
|
|
changes or data migration required in order to update to the new openstack
|
|
container image\(s\).
|
|
|
|
The system application-update -n |prefix|-openstack effectively performs a
|
|
helm upgrade of one or more of the OpenStack Helm chart releases within the
|
|
FluxCD Application. One or all of the containerized OpenStack deployments will
|
|
be updated according to their deployment specification.
|
|
|
|
.. note::
|
|
Compute nodes do not need to be reset, and hosted application |VMs| are not impacted.
|
|
|