Update Patching docs

Update patching docs.
Make repos configuration a separate chapter
in the ops guide.

Change-Id: I91cdd350d806c6da447b661601d29094d4d07179
This commit is contained in:
evkonstantinov
2015-06-24 15:30:16 +03:00
committed by Evgeny Konstantinov
parent 0e26e7d7cc
commit a441690c99
10 changed files with 120 additions and 109 deletions

BIN
_images/errataPatching.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 67 KiB

BIN
_images/patchingRepos.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 97 KiB

View File

@@ -38,5 +38,6 @@
.. include:: /pages/operations/isoUSB-ops.rst
.. include:: /pages/operations/external-ubuntu-ops.rst
.. include:: /pages/operations/empty-role.rst
.. include:: /pages/operations/streamlined-patching.rst
.. include:: /pages/operations/configuring-repos-ops.rst
.. include:: /pages/operations/patching-ops.rst

View File

@@ -12,4 +12,4 @@
.. include:: /pages/user-guide/9000-role-operations.rst
.. include:: /pages/user-guide/cli.rst
.. include:: /pages/user-guide/vmware-integration-notes.rst
.. include:: /pages/user-guide/streamlined-patching-ug.rst
.. include:: /pages/user-guide/patching-ug.rst

View File

@@ -0,0 +1,47 @@
.. _configuring-repos-ops:
Configuring repositories
========================
By default, your environments will have the configuration of the
repositories that point to the Mirantis update and security
repository mirrors. There is also an 'Auxiliary' repository configured
on the Fuel Master node which can be used to deliver packages
to the nodes.
.. image:: /_images/patchingRepos.png
To change the list of repositories, you will need to
amend the three fields which contain the required information
for the repositories configuration depending on the
distribution you install.
For CentOS
----------
::
|repo-name|repo-baseurl|repo-priority|
e.g
::
my-repo http://my-domain.local/repo 10
For Ubuntu
----------
::
|repo-name|apt-sources-list-string|repo-priority|
my-repo deb http://my-domain.local/repo trusty main 1200
Repository priorities
---------------------
For information on repository priorities read the following:
* Ubuntu: `PinningHowto <https://help.ubuntu.com/community/PinningHowto>`_
* CentOS: `yum-plugin-priorities <http://wiki.centos.org/PackageManagement/Yum/Priorities>`_

View File

@@ -0,0 +1,56 @@
.. _patching-ops:
Applying patches
================
.. note::
The primary user of the the patching feature is
the Linux system administrator. If you are not confident enough,
you may want to skip this.
With the patching feature in Mirantis OpenStack 6.1 you can
now keep your environment up-to-date in a customized fashion without
the need to upgrade to the latest version.
.. note::
The patching feature is introduced in
Mirantis OpenStack 6.1 and will not work in older releases.
There are two types of officially supported updates:
1. Bugfix updates -- These are released in an aggregated form and
consist of bug fixes and security updates. The bugfix updates
are run through our internal testing to ensure that they work
without breaking each other.
2. Security updates -- These are released as soon as they are available.
Patching prerequisites
----------------------
* Make sure you are registered at at the `official Mirantis website <https://software.mirantis.com/openstack-download-form/>`_.
Once you are registered, you will receive regular email notifications
on the available patches in an aggregate form. Once you receive the email,
you can click on the patching items listed there. This will lead you to
the `errata portal <http://errata.mirantis.com/>`_.
* Make sure you have the repositories configured correctly as
described in :ref:`Configuring repositories<configuring-repos-ops>`.
* At the portal you will see a list of all the available patches.
Each patching item will have detailed instructions on how to
download and apply each of them.
Applying the patches
--------------------
Each patch item listed at the the `errata portal <http://errata.mirantis.com/>`_
will have the exact commands you need to run to download and apply
the patch -- usually ``yum`` or ``apt-get``, followed by restarting
the associated service. The listed commands need to be executed on
every node that you need to patch.
In addition to the patch itself, Mirantis will also provide steps to verify that the patch was applied successfully.
See below for an example.
.. image:: /_images/errataPatching.png

View File

@@ -1,93 +0,0 @@
.. _streamlined-patching-ops:
Applying streamlined patching
=============================
.. note::
The primary user of the the streamlined patching feature is
the Linux system administrator. If you are not confident enough,
you may want to skip this.
With the streamlined patching feature in Mirantis OpenStack 6.1 you can
now keep your environment up-to-date in a customized fashion without
the need to upgrade to the latest version.
.. note::
The streamlined patching feature is introduced in
Mirantis OpenStack 6.1 and will not work in older releases.
There are two types of officially supported updates:
1. Bugfix updates -- These are released in an aggregated form and
consist of bug fixes and security updates. The bugfix updates
are run through our internal testing to ensure that they work
without breaking each other.
2. Security updates -- These are released as soon as they are available.
Streamlined patching prerequisites
----------------------------------
* Make sure you are registered at at the `official Mirantis website <https://software.mirantis.com/openstack-download-form/>`_.
Once you are registered, you will receive regular email notifications
on the available patches in an aggregate form. Once you receive the email,
you can click on the patching items listed there. This will lead you to
the `errata portal <http://errata.mirantis.com/>`_.
* At the portal you will see a list of all the available patches.
Each patching item will have detailed instructions on how to
download and apply each of them.
* Make sure you have the repositories configured correctly as
described below.
Configuring repositories
------------------------
By default, your environments will have the configuration of the
repositories that point to the Mirantis update and security
repository mirrors. There is also an 'Auxiliary' repository configured
on the Fuel Master node which can be used to deliver packages
to the nodes.
To change the list of repositories, you will need to
amend the three fields which contain the required information
for the repositories configuration depending on the
distribution you install.
For CentOS
++++++++++
::
|repo-name|repo-baseurl|repo-priority|
e.g
::
my-repo http://my-domain.local/repo 10
For Ubuntu
++++++++++
::
|repo-name|apt-sources-list-string|repo-priority|
my-repo deb http://my-domain.local/repo trusty main 1200
Additional information
++++++++++++++++++++++
For additional information read the following:
* Ubuntu: `PinningHowto <https://help.ubuntu.com/community/PinningHowto>`_
* CentOS: `yum-plugin-priorities <http://wiki.centos.org/PackageManagement/Yum/Priorities>`_
Applying the patches
--------------------
Each patch item listed at the the `errata portal <http://errata.mirantis.com/>`_
will have the exact commands you need to run to download and apply
the patch -- usually ``yum`` or ``apt-get``.
The listed commands need to be executed on every node that you need to patch.

View File

@@ -1,17 +1,17 @@
Streamlined patching
++++++++++++++++++++
Patching
++++++++
The streamlined patching feature introduced in Mirantis OpenStack 6.1
The patching feature introduced in Mirantis OpenStack 6.1
is the process of delivering product updates to users which can be
applied using standard Linux commands (e.g. ``apt-get`` and ``yum``).
The streamlined patching feature allows you to keep your
The patching feature allows you to keep your
environment up-to-date in a customized fashion without
the need to upgrade to the latest version.
For your user experience and how-to see :ref:`Applying streamlined patching<streamlined-patching-ops>`.
For your user experience and how-to see :ref:`Applying patches<patching-ops>`.
.. note::
The streamlined patching feature is introduced in
The patching feature is introduced in
Mirantis OpenStack 6.1 and will not work in older releases.

View File

@@ -0,0 +1,8 @@
.. _patching-ug:
Patching
--------
For your user experience and how-to see :ref:`Applying patches<patching-ops>`.

View File

@@ -1,8 +0,0 @@
.. _streamlined-patching-ug:
Streamlined patching
--------------------
For your user experience and how-to see :ref:`Applying streamlined patching<streamlined-patching-ops>`.