Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added upgrade specific instructions for 3.3 #1028

Merged
merged 4 commits into from
Oct 16, 2020
Merged

Added upgrade specific instructions for 3.3 #1028

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e9efafa
Added upgrade specific instructions for 3.3
nmaludy Oct 13, 2020
f9befc6
Updated upgrade steps for EL
amanda11 Oct 16, 2020
4f8d3da
Minor change, but still problem on mongo upgrade
amanda11 Oct 16, 2020
bfcf6c5
Updated with warning that may need to restart mongod on Ubuntu
amanda11 Oct 16, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
114 changes: 105 additions & 9 deletions docs/source/install/upgrades.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Update GPG Key
The GPG keys used for signing our apt and yum repository metadata have been updated. If you are upgrading
an existing system that has the old keys installed, it will need updating. See the instructions below for
how to do this.

Failure to update the keys will result in signature verification errors during package update.

For |st2| community version on Ubuntu, run the following command to update your keys. If you
Expand Down Expand Up @@ -48,7 +48,7 @@ note the URLs that failed on retrieval should be ``https://packagecloud.io/Stack
Get:7 https://packagecloud.io/StackStorm/stable/ubuntu xenial InRelease [23.2 kB]
Err:7 https://packagecloud.io/StackStorm/stable/ubuntu xenial InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C2E73424D59097AB
Hit:8 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:8 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:9 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:10 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
Fetched 23.2 kB in 1s (12.3 kB/s)
Expand Down Expand Up @@ -88,24 +88,24 @@ is retrieved from should be ``https://packagecloud.io/StackStorm/stable`` for th
$ sudo yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
StackStorm_stable/x86_64/signature | 836 B 00:00:00
StackStorm_stable/x86_64/signature | 836 B 00:00:00
Retrieving key from https://packagecloud.io/StackStorm/stable/gpgkey
Importing GPG key 0xF6C28448:
Userid : "https://packagecloud.io/StackStorm/stable (https://packagecloud.io/docs#gpg_signing) <[email protected]>"
Fingerprint: 2664 b321 ca26 c6be fe81 aa46 723c b7a7 f6c2 8448
From : https://packagecloud.io/StackStorm/stable/gpgkey
Is this ok [y/N]: y
StackStorm_stable/x86_64/signature | 1.0 kB 00:00:15 !!!
StackStorm_stable-source/signature | 836 B 00:00:00
StackStorm_stable/x86_64/signature | 1.0 kB 00:00:15 !!!
StackStorm_stable-source/signature | 836 B 00:00:00
Retrieving key from https://packagecloud.io/StackStorm/stable/gpgkey
Importing GPG key 0xF6C28448:
Userid : "https://packagecloud.io/StackStorm/stable (https://packagecloud.io/docs#gpg_signing) <[email protected]>"
Fingerprint: 2664 b321 ca26 c6be fe81 aa46 723c b7a7 f6c2 8448
From : https://packagecloud.io/StackStorm/stable/gpgkey
Is this ok [y/N]: y
StackStorm_stable-source/signature | 951 B 00:00:10 !!!
(1/2): StackStorm_stable-source/primary | 175 B 00:00:00
(2/2): StackStorm_stable/x86_64/primary | 27 kB 00:00:00
StackStorm_stable-source/signature | 951 B 00:00:10 !!!
(1/2): StackStorm_stable-source/primary | 175 B 00:00:00
(2/2): StackStorm_stable/x86_64/primary | 27 kB 00:00:00
StackStorm_stable 124/124

General Upgrade Procedure
Expand All @@ -119,7 +119,7 @@ This is the standard upgrade procedure:

sudo st2ctl stop
ps auxww | grep st2

If any `st2`-related processes are still running, kill them with `kill -9`.

2. Upgrade |st2| packages using distro-specific tools:
Expand Down Expand Up @@ -167,6 +167,102 @@ The following sections call out the migration scripts that need to be run when u
respective version. If you are upgrading across multiple versions, make sure you run the scripts for
any skipped versions:


v3.3
''''

* MongoDB 4.0 is the new default version. Previously the version of MongoDB was 3.4 and
nmaludy marked this conversation as resolved.
Show resolved Hide resolved
the supported upgrade path to MongoDB 4.0 is ``3.4 -> 3.6 -> 4.0``.
Official documentation on how to upgrade MongoDB can be found here:
* https://docs.mongodb.com/manual/release-notes/3.6-upgrade-standalone/
* https://docs.mongodb.com/manual/release-notes/4.0-upgrade-standalone/

A summary of the steps to take is outlined below assuming you will be migrating
through the path ``3.4 -> 3.6 -> 4.0``

Ubuntu:
nmaludy marked this conversation as resolved.
Show resolved Hide resolved

.. sourcecode:: bash

# Stop StackStorm
sudo st2ctl stop

# Ensure current MongoDB feature compatability level is set to 3.4
mongo admin --username admin --password Password --quiet --eval "db.adminCommand( { setFeatureCompatibilityVersion: '3.4' } )"

# Upgrade MongoDB packages to 3.6
# TODO how do we update the apt source?
sudo apt-get -y clean
sudo apt-get -y update
sudo apt-get -y install mongodb-*

# Set MongoDB feature compatability level to 3.6
mongo admin --username admin --password Password --quiet --eval "db.adminCommand( { setFeatureCompatibilityVersion: '3.6' } )"

# TODO Upgrade MongoDB packages to 4.0
# TODO how do we update the apt source?
sudo apt-get -y clean
sudo apt-get -y update
sudo apt-get -y install mongodb-*

# Set MongoDB feature compatability level to 4.0
mongo admin --username admin --password Password --quiet --eval "db.adminCommand( { setFeatureCompatibilityVersion: '4.0' } )"

# Start StackStorm
sudo st2ctl start


RHEL/CentOS:
nmaludy marked this conversation as resolved.
Show resolved Hide resolved

.. sourcecode:: bash

# Stop StackStorm
sudo st2ctl stop

# Ensure current MongoDB feature compatability level is set to 3.4
mongo admin --username admin --password Password --quiet --eval "db.adminCommand( { setFeatureCompatibilityVersion: '3.4' } )"

# Upgrade MongoDB packages to 3.6
sudo sed -i 's/3\.4/3\.6/' /etc/yum.repos.d/mongodb.repo
sudo yum clean all
sudo yum makecache fast
sudo yum upgrade -y mongodb-*

# Set MongoDB feature compatability level to 3.6
mongo admin --username admin --password Password --quiet --eval "db.adminCommand( { setFeatureCompatibilityVersion: '3.6' } )"

# Upgrade MongoDB packages to 4.0
sudo sed -i 's/3\.6/4\.0/' /etc/yum.repos.d/mongodb.repo
sudo yum clean all
sudo yum makecache fast
sudo yum upgrade -y mongodb-*

# Set MongoDB feature compatability level to 4.0
mongo admin --username admin --password Password --quiet --eval "db.adminCommand( { setFeatureCompatibilityVersion: '4.0' } )"

# Start StackStorm
sudo st2ctl start

* Mistral is no longer included in StackStorm and consequently Postgres is no longer required.
To uninstall Mistral and Postgres you may follow the procedure below (optional):


Ubuntu:
nmaludy marked this conversation as resolved.
Show resolved Hide resolved

.. sourcecode:: bash

# TODO: Stop the services
# TODO: Uninstall the packages
# TODO: Remove the repo

RHEL/CentOS:
nmaludy marked this conversation as resolved.
Show resolved Hide resolved

.. sourcecode:: bash

# TODO: Stop the services
# TODO: Uninstall the packages
# TODO: Remove the repo

v2.10
'''''

Expand Down