Skip to content

Commit

Permalink
Upgrade guide for migration from version 1.0.x to 1.1
Browse files Browse the repository at this point in the history
Change-Id: Ib6cedec5bf69154f3fb729dd055cb6600e9fcd2e
  • Loading branch information
9seconds committed May 12, 2017
1 parent 8d64dd6 commit 4d47810
Show file tree
Hide file tree
Showing 4 changed files with 119 additions and 0 deletions.
1 change: 1 addition & 0 deletions docs/source/decapod/decapod-upgrade.rst
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ upgrade Decapod from version *X* to *X+3*, first upgrade to *X+1*, then to

decapod-upgrade/verify-decapod-version.rst
decapod-upgrade/upgrade-from-0-1-to-1-0.rst
decapod-upgrade/upgrade-from-1-0-to-1-1.rst

.. seealso::

Expand Down
18 changes: 18 additions & 0 deletions docs/source/decapod/decapod-upgrade/upgrade-from-1-0-to-1-1.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
.. _decapod_upgrade_1011:

=================================
Upgrade Decapod from 1.0.x to 1.1
=================================

Prior to upgrading Decapod, perform the steps described in
:ref:`decapod_upgrade_10_11_prerequisites`.

.. note::

You do not need to perform any changes in the existing Ceph deployments.

.. toctree::
:maxdepth: 1

upgrade-from-1-0-to-1-1/prerequisites.rst
upgrade-from-1-0-to-1-1/upgrade-procedure.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
.. _decapod_upgrade_10_11_prerequisites:

=============
Prerequisites
=============

Prior to upgrading Decapod from 1.0.x to 1.1.x verify that you
have :file:`~/decapod_runtime` directory and have a contents from
:ref:`decapod_upgrade_01_10_prerequisites`. If not, please create it
first following that article.
Original file line number Diff line number Diff line change
@@ -0,0 +1,90 @@
.. _decapod_upgrade_from_10_to_11:

===============
Upgrade Decapod
===============

**To upgrade Decapod from 1.0.x to 1.1.x:**

#. Back up the database.

* Follow procedure, described in :ref:`decapod_user_guide_backup_restore`.

* Try to restore database on another installation to verify that backup
is not corrupted.

#. Obtain images for Decapod 1.1.x. to do so, follow steps 1-2 in the
:ref:`decapod_install`

#. Create containers from existing images:

.. code-block:: console
$ docker-compose -p PROJECT create
decapod_database_1 is up-to-date
Recreating decapod_api_1
Recreating decapod_frontend_1
Recreating decapod_controller_1
Recreating decapod_admin_1
This command won't restart existing containers, just prepare new ones.

#. Restart services.

* If you can have a maintenence window, then restart all services
at once:

.. code-block:: console
$ docker-compose -p PROJECT restart
Restarting decapod_frontend_1 ... done
Restarting decapod_api_1 ... done
Restarting decapod_admin_1 ... done
Restarting decapod_controller_1 ... done
Restarting decapod_database_1 ... done
Restarting decapod_database_data_1 ... done
* Otherwise, please restart services in following sequence:

#. ``api`` service

.. code-block:: console
$ docker-compose -p PROJECT restart api
Restarting decapod_api_1 ... done
#. ``frontend`` service

.. code-block:: console
$ docker-compose -p PROJECT restart frontend
Restarting decapod_frontend_1 ... done
#. ``admin`` service

.. code-block:: console
$ docker-compose -p PROJECT restart admin
Restarting decapod_admin_1 ... done
#. ``controller`` service

.. code-block:: console
$ docker-compose -p PROJECT restart controller
Restarting decapod_controller_1 ... done
#. ``database`` service

.. code-block:: console
$ docker-compose -p PROJECT restart database
Restarting decapod_database_1 ... done
#. Run database migrations:

.. code-block:: console
$ docker-compose -p PROJECT exec -T admin decapod-admin migration apply

0 comments on commit 4d47810

Please sign in to comment.