Commit 4a32f227 authored by Etienne Allovon's avatar Etienne Allovon

Add notes for postgres upgrade

parent 2f1e6c99
......@@ -17,9 +17,16 @@ Before Upgrade
On XiVO PBX
-----------
* You MUST have enough free disk space for postgres upgrade.
* Asterisk database roles must correspond to the installed (old) XiVO version. Migration can fail if some table
is owned by an unexpected role.
* Postgres upgrade:
* You MUST have enough free disk space for postgres upgrade.
* The upgrade duration will depend on the size of the database (and mainly on the size of `cel` and `queue_log` tables).
As an example, for a database with 9M cel and 1M queue_log, the upgrade took 4 hours (on a server with 4 CPUs and 4 Gb of RAM).
* Asterisk database roles must correspond to the installed (old) XiVO version. Migration can fail if some table
is owned by an unexpected role.
* If there is any specific postgresql parameters (e.g. in files :file:`/etc/postgresql/9.4/postgresql.conf` or
or :file:`/etc/postgresql/9.4/pg_ha.conf`) you MUST save them to be able to restore them after the upgrade
(see note After Upgrade below).
After Upgrade
......@@ -35,12 +42,19 @@ On XiVO PBX
xivo-dcomp logs -t db | grep '\[MIGRATE_OUTCALL\].*WARNING'
#. if yes, follow our :ref:`migration guide <callisto_route_upgrade_guide>`.
* Postgresql: postgresql service now runs inside a container. During upgrade the database was re-imported
**BUT NOT** the postgresql configuration (i.e. parameters in file :file:`postgresql.conf`). If you have any
specific parameters you should add them to the postgresql container configuration as documented in the
:ref:`database_configuration` section.
* High availibility: If you have XiVO CC installed, follow the :ref:`ha_interconnection_with_cc` procedure
to install DB Replic on the slave XiVO.
.. warning:: **Security warning:** Asterisk HTTP server (used for WebRTC and xivo-outcall) was reconfigured
to accept websocket connections from outside. See the :ref:`asterisk_http_server` documentation
and ensure that the configuration is secure.
* Asterisk HTTP server configuration **security warning**:
.. warning:: **Security warning:** Asterisk HTTP server (used for WebRTC and xivo-outcall) was reconfigured
to accept websocket connections from outside. See the :ref:`asterisk_http_server` documentation
and ensure that the configuration is secure.
* XDS: if you had an XDS installation you MUST remove SIP trunks added for intra-mds routing
(that is the SIP trunks named `default`, and `mdsX` - e.g. `mds0`, `mds1` ...).
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment