2.0 Release Notes

1. Display a list of all subscriptions that are available for your system and determine the pool ID of a subscription that provides Red Hat Software Collections. To do so, type the following at a shell prompt as root:

   subscription-manager list --available

   For each available subscription, this command displays its name, unique identifier, expiration date, and other details related to it. The pool ID is listed on a line beginning with Pool Id.
2. Attach the appropriate subscription to your system by running the following command as root:

   subscription-manager attach --pool=pool_id

   Replace pool_id with the pool ID you determined in the previous step. To verify the list of subscriptions your system has currently attached, type as root:

   subscription-manager list --consumed

3. Display the list of available Yum list repositories to retrieve repository metadata and determine the exact name of the Red Hat Software Collections repositories. As root, type:

   subscription-manager repos --list

   Or alternatively, run yum repolist all for a brief list.
   The repository names depend on the specific version of Red Hat Enterprise Linux you are using and are in the following format:

   rhel-variant-rhscl-6-rpms
   rhel-variant-rhscl-6-debug-rpms
   rhel-variant-rhscl-6-source-rpms
   
   rhel-server-rhscl-6-eus-rpms
   rhel-server-rhscl-6-eus-source-rpms
   rhel-server-rhscl-6-eus-debug-rpms
   
   rhel-variant-rhscl-7-rpms
   rhel-variant-rhscl-7-debug-rpms
   rhel-variant-rhscl-7-source-rpms
   
   rhel-server-rhscl-7-eus-rpms
   rhel-server-rhscl-7-eus-source-rpms
   rhel-server-rhscl-7-eus-debug-rpms

   Replace variant with the Red Hat Enterprise Linux system variant, that is, server or workstation. Note that Red Hat Software Collections is supported neither on the Client nor on the ComputeNode variant.
4. Enable the appropriate repository by running the following command as root:

   subscription-manager repos --enable repository

1. Display a list of all channels that are available to you and determine the exact name of the Red Hat Software Collections channel. To do so, type the following at a shell prompt as root:

   rhn-channel --available-channels

   The name of the channel depends on the specific version of Red Hat Enterprise Linux you are using and is in the following format, where variant is the Red Hat Enterprise Linux system variant (server or workstation):

   rhel-x86_64-variant-6-rhscl-1
   
   rhel-x86_64-server-6.5.z-rhscl-1
   rhel-x86_64-server-6.6.z-rhscl-1
   
   rhel-x86_64-variant-7-rhscl-1
   
   rhel-x86_64-server-7.1.eus-rhscl-1

   Red Hat Enterprise Linux 7 channels are accessible only through Red Hat Satellite instances.

   Note

   Red Hat Software Collections 2.x are distributed in the same channels as Red Hat Software Collections 1.x.
2. Subscribe the system to the Red Hat Software Collections channel by running the following command as root:

   rhn-channel --add --channel=channel_name

   Replace channel_name with the name you determined in the previous step.
3. Verify the list of channels you are subscribed to. As root, type:

   rhn-channel --list

1. Install the MongoDB server from the rh-mongodb26 Software Collection:

   yum install rh-mongodb26

2. Stop the mongodb24 server in Red Hat Enterprise Linux 6:

   service mongodb24-mongodb stop

   Use the systemctl stop mongodb24-mongodb.service command instead if you are using Red Hat Enterprise Linux 7.
3. Copy your data into the new location:

   cp -a /opt/rh/mongodb24/root/var/lib/mongodb/* /var/opt/rh/rh-mongodb26/lib/mongodb

4. Change the dbpath variable in the /opt/rh/mongodb24/root/etc/mongodb.conf file to /var/opt/rh/rh-mongodb26/lib/mongodb/.
5. Start the mongodb24 server in Red Hat Enterprise Linux 6:

   service mongodb24-mongodb start

   Use the systemctl start mongodb24-mongodb.service command if instead you are using Red Hat Enterprise Linux 7.
6. Install the mongo shell from the rh-mongodb26 Software Collection:

   yum install rh-mongodb26-mongodb

7. Connect the mongo shell from the rh-mongodb26 Software Collection to your mongodb24 server (for example, running on localhost, port 27017; you do not need root privileges for this step):

   scl enable rh-mongodb26 'mongo --host localhost --port 27017 admin'

8. In the mongo shell, run the db.upgradeCheckAllDBs() function to check your data set for compatibility:

   db.upgradeCheckAllDBs()

   See the MongoDB documentation for more information about the db.upgradeCheckAllDBs() function.
9. Resolve all issues identified by db.upgradeCheckAllDBs() and compatibility issues mentioned above that affect your application.
10. Stop the mongodb24 server in Red Hat Enterprise Linux 6:

    service mongodb24-mongodb stop

    Use the systemctl stop mongodb24-mongodb.service command instead if you are using Red Hat Enterprise Linux 7.
11. Make the mongodb24 Software Collection runnable after the upgrade by changing the dbpath variable back to the previous value (/opt/rh/mongodb24/root/var/lib/mongodb/ by default) in the /opt/rh/mongodb24/root/etc/mongodb.conf file.
12. Configure the rh-mongodb26-mongod daemon in the /etc/opt/rh/rh-mongodb26/mongod.conf configuration file.
13. Start the MongoDB server from the rh-mongodb26 Collection in Red Hat Enterprise Linux 6:

    service rh-mongodb26-mongod start

    Use the systemctl start rh-mongodb26-mongod.service instead if you are using Red Hat Enterprise Linux 7.
14. Upgrade the authorization model as described in the MongoDB documentation. Note that it is recommended to run your MongoDB deployment for a day or two before you upgrade the user authorization model because downgrades are more difficult after the user authorization model has been upgraded. Before you upgrade the authorization model, you will not be able to create or modify users or to use user-defined roles.

Procedure 5.1. Fast Upgrade Using the pg_upgrade Tool

1. Stop the old PostgreSQL server to ensure that the data is not in an inconsistent state. To do so, type the following at a shell prompt as root:

   service postgresql stop

   To verify that the server is not running, type:

   service postgresql status

2. Verify that the old directory /var/lib/pgsql/data/ exists:

   file /var/lib/pgsql/data/

   and back up your data.
3. Verify that the new data directory /var/opt/rh/rh-postgresql94/lib/pgsql/data/ does not exist:

   file /var/opt/rh/rh-postgresql94/lib/pgsql/data/

   If you are running a fresh installation of PostgreSQL 9.4, this directory should not be present in your system. If it is, back it up by running the following command as root:

   mv /var/opt/rh/rh-postgresql94/lib/pgsql/data{,-scl-backup}

4. Upgrade the database data for the new server by running the following command as root:

   scl enable rh-postgresql94 -- postgresql-setup --upgrade

   Alternatively, you can use the /opt/rh/rh-postgresql94/root/usr/bin/postgresql-setup --upgrade command.
   Note that you can use the --upgrade-from option for upgrade from different versions of PostgreSQL. The list of possible upgrade scenarios is available using the --upgrade-ids option.
   It is recommended that you read the resulting /var/lib/pgsql/upgrade_rh-postgresql94-postgresql.log log file to find out if any problems occurred during the upgrade.
5. Start the new server as root:

   service rh-postgresql94-postgresql start

   It is also advised that you run the analyze_new_cluster.sh script as follows:

   su - postgres -c 'scl enable rh-postgresql94 ~/analyze_new_cluster.sh'

6. Optionally, you can configure the PostgreSQL 9.4 server to start automatically at boot time. To disable the old system PostgreSQL server, type the following command as root:

   chkconfig postgresql off

   To enable the PostgreSQL 9.4 server, type as root:

   chkconfig rh-postgresql94-postgresql on

7. If your configuration differs from the default one, make sure to update configuration files, especially the /var/opt/rh/rh-postgresql94/lib/pgsql/data/pg_hba.conf configuration file. Otherwise only the postgres user will be allowed to access the database.

Procedure 5.2. Performing a Dump and Restore Upgrade

1. Ensure that the old PostgreSQL server is running by typing the following at a shell prompt as root:

   service postgresql start

2. Dump all data in the PostgreSQL database into a script file. As root, type:

   su - postgres -c 'pg_dumpall > ~/pgdump_file.sql'

3. Stop the old server by running the following command as root:

   service postgresql stop

4. Initialize the data directory for the new server as root:

   scl enable rh-postgresql94-postgresql -- postgresql-setup --initdb

5. Start the new server as root:

   service rh-postgresql94-postgresql start

6. Import data from the previously created SQL file:

   su - postgres -c 'scl enable rh-postgresql94 "psql -f ~/pgdump_file.sql postgres"'

7. Optionally, you can configure the PostgreSQL 9.4 server to start automatically at boot time. To disable the old system PostgreSQL server, type the following command as root:

   chkconfig postgresql off

   To enable the PostgreSQL 9.4 server, type as root:

   chkconfig rh-postgresql94-postgresql on

8. If your configuration differs from the default one, make sure to update configuration files, especially the /var/opt/rh/rh-postgresql94/lib/pgsql/data/pg_hba.conf configuration file. Otherwise only the postgres user will be allowed to access the database.

Procedure 5.3. Fast Upgrade Using the pg_upgrade Tool

1. Stop the old PostgreSQL server to ensure that the data is not in an inconsistent state. To do so, type the following at a shell prompt as root:

   service postgresql92-postgresql stop

   To verify that the server is not running, type:

   service postgresql92-postgresql status

2. Verify that the old directory /opt/rh/postgresql92/var/lib/pgsql/data/ exists:

   file /opt/rh/postgresql92/var/lib/pgsql/data/

   and back up your data.
3. Verify that the new data directory /var/opt/rh/rh-postgresql94/lib/pgsql/data/ does not exist:

   file /var/opt/rh/rh-postgresql94/lib/pgsql/data/

   If you are running a fresh installation of PostgreSQL 9.4, this directory should not be present in your system. If it is, back it up by running the following command as root:

   mv /var/opt/rh/rh-postgresql94/lib/pgsql/data{,-scl-backup}

4. Upgrade the database data for the new server by running the following command as root:

   scl enable rh-postgresql94 -- postgresql-setup --upgrade --upgrade-from=postgresql92-postgresql

   Alternatively, you can use the /opt/rh/rh-postgresql94/root/usr/bin/postgresql-setup --upgrade --upgrade-from=postgresql92-postgresql command.
   Note that you can use the --upgrade-from option for upgrading from different versions of PostgreSQL. The list of possible upgrade scenarios is available using the --upgrade-ids option.
   It is recommended that you read the resulting /var/lib/pgsql/upgrade_rh-postgresql94-postgresql.log log file to find out if any problems occurred during the upgrade.
5. Start the new server as root:

   service rh-postgresql94-postgresql start

   It is also advised that you run the analyze_new_cluster.sh script as follows:

   su - postgres -c 'scl enable rh-postgresql94 ~/analyze_new_cluster.sh'

6. Optionally, you can configure the PostgreSQL 9.4 server to start automatically at boot time. To disable the old PostgreSQL 9.2 server, type the following command as root:

   chkconfig postgresql92-postgreqsql off

   To enable the PostgreSQL 9.4 server, type as root:

   chkconfig rh-postgresql94-postgresql on

7. If your configuration differs from the default one, make sure to update configuration files, especially the /var/opt/rh/rh-postgresql94/lib/pgsql/data/pg_hba.conf configuration file. Otherwise only the postgres user will be allowed to access the database.

Procedure 5.4. Performing a Dump and Restore Upgrade

1. Ensure that the old PostgreSQL server is running by typing the following at a shell prompt as root:

   service postgresql92-postgresql start

2. Dump all data in the PostgreSQL database into a script file. As root, type:

   su - postgres -c 'scl enable postgresql92 "pg_dumpall" > ~/pgdump_file.sql'

3. Stop the old server by running the following command as root:

   service postgresql92-postgresql stop

4. Initialize the data directory for the new server as root:

   scl enable rh-postgresql94-postgresql -- postgresql-setup --initdb

5. Start the new server as root:

   service rh-postgresql94-postgresql start

6. Import data from the previously created SQL file:

   su - postgres -c 'scl enable rh-postgresql94 "psql -f ~/pgdump_file.sql postgres"'

7. Optionally, you can configure the PostgreSQL 9.4 server to start automatically at boot time. To disable the old PostgreSQL 9.2 server, type the following command as root:

   chkconfig postgresql92-postgresql off

   To enable the PostgreSQL 9.4 server, type as root:

   chkconfig rh-postgresql94-postgresql on

8. If your configuration differs from the default one, make sure to update configuration files, especially the /var/opt/rh/rh-postgresql94/lib/pgsql/data/pg_hba.conf configuration file. Otherwise only the postgres user will be allowed to access the database.