1.2 Release Notes
Release Notes for Red Hat Software Collections 1.2
Edition 0
Abstract
Chapter 1. Red Hat Software Collections 1.2
1.1. About Red Hat Software Collections
/opt/
directory and can be optionally enabled per application by the user using the supplied scl
utility. The default versions of Perl or PostgreSQL, for example, remain those provided by the base Red Hat Enterprise Linux system.
1.2. Main Features
Table 1.1. Red Hat Software Collections 1.2 Components
Component | Software Collection | Description |
---|---|---|
Red Hat Developer Toolset 3.0 | devtoolset-3 | Red Hat Developer Toolset is designed for developers working on the Red Hat Enterprise Linux platform. It provides current versions of the GNU Compiler Collection, GNU Debugger, Eclipse development platform, and other development, debugging, and performance monitoring tools. For a complete list of components, see the Red Hat Developer Toolset Components table in the Red Hat Developer Toolset User Guide. |
Perl 5.16.3 | perl516 | A release of Perl with a number of additional utilities, scripts, and database connectors for MySQL and PostgreSQL. This version provides a large number of new features and enhancements, including new debugging options, improved Unicode support, and better performance. Also, it adds perl-DateTime and mod_perl, which is supported only with the httpd24 Software Collection package. |
PHP 5.4.16 | php54 | A release of PHP with PEAR 1.9.4 and a number of additional extensions. PHP 5.4 provides a number of language and interface improvements. The APC, memcache, and Zend OPcache extensions are also included. |
PHP 5.5.6 | php55 | A release of PHP with enhanced language features including better exception handling, generators, and Zend OPcache. The memcache and mongodb extensions are also included. |
Python 2.7.5 | python27 | A release of Python 2.7 with a number of additional utilities. This Python version provides various new features and enhancements, including a new ordered dictionary type, faster I/O operations, and improved forward compatibility with Python 3. The python27 Software Collections contains the Python 2.7.5 interpreter, a set of extension libraries useful for programming web applications and mod_wsgi (only supported with the httpd24 Software Collection), MySQL and PostgreSQL database connectors, and numpy and scipy. |
Python 3.3.2 | python33 | A release of Python 3 with a number of additional utilities. This Software Collection gives developers on Red Hat Enterprise Linux access to Python 3 and allows them to benefit from various advantages and new features of this version. The python33 Software Collection contains Python 3.3.2 interpreter, a set of extension libraries useful for programming web applications and mod_wsgi (only supported with the httpd24 Software Collection), PostgreSQL database connector, and numpy and scipy. |
Ruby 1.9.3[a] | ruby193 | A release of Ruby 1.9.3 and Ruby on Rails 3.2.8 with a large collection of Ruby gems. This Software Collection gives developers on Red Hat Enterprise Linux access to Ruby 1.9, which provides a number of new features and enhancements, including improved Unicode support, enhanced threading, faster load times, and mod_passenger, which is supported only with the httpd24 Software Collection package. |
Ruby 2.0.0 | ruby200 | A release of Ruby 2.0.0. This version provides substantial performance and reliability improvements and includes a number of new features and improved debugging capabilities, while maintaining source level backward compatibility with Ruby 1.9.3. |
Ruby on Rails 4.0.2[a] | ror40 | A release of Ruby on Rails 4.0, a web application development framework written in the Ruby language. This version provides a number of new features and improvements and adds live streaming for persistent connections. This Software Collection is supported together with the ruby200 collection. |
MariaDB 5.5.37 | mariadb55 | A release of MariaDB, an alternative to MySQL for users of Red Hat Enterprise Linux. MySQL is binary compatible with MariaDB and can be replaced with it without any data conversions. This version adds the PAM authentication plugin to MariaDB. |
MongoDB 2.4.9[b] | mongodb24 | A release of MongoDB, a cross-platform document-oriented database system classified as a NoSQL database. This Software Collection includes the mongo-java-driver package. |
MySQL 5.5.37 | mysql55 | A release of MySQL, which provides a number of new features and enhancements, including improved performance. |
PostgreSQL 9.2.8 | postgresql92 | A release of PostgreSQL, which provides a number of new features and enhancements, including cascading replication, native JSON support, improved scalability, and better performance. |
Node.js 0.10[b][c] | nodejs010 | A release of Node.js with npm 1.3.24. This Software Collection gives users of Red Hat Enterprise Linux access to this programming platform. |
nginx 1.6.1 | nginx16 | A release of nginx, a web and proxy server with a focus on high concurrency, performance and low memory usage. This version introduces a number of new features, including various SSL improvements, support for SPDY 3.1 (limited to Red Hat Enterprise Linux 7), cache revalidation with conditional requests, and authentication request module. |
Apache httpd 2.4.6 | httpd24 | A release of the Apache HTTP Server (httpd), including a high performance event-based processing model, enhanced SSL module and FastCGI support. The mod_auth_kerb module is also included. |
Thermostat 1.0.4 | thermostat1 | A release of Thermostat, a monitoring and instrumentation tool for the OpenJDK HotSpot JVM, with support for monitoring multiple JVM instances. This Software Collection depends on the mongodb24 component. |
Git 1.9.4 | git19 | A release of Git, a distributed revision control system with a decentralized architecture. As opposed to centralized version control systems with a client-server model, Git ensures that each working copy of a Git repository is its exact copy with complete revision history. |
DevAssistant 0.9.1 | devassist09 | A release of DevAssistant, a tool designed to assist developers with creating and setting up basic projects in various programming languages, installing dependencies, setting up a development environment, and working with source control. DevAssistant supports the C, C++, Java, and Python programming languages but it is able to support working with any other language, framework, or tool due to its modular architecture. |
Maven 3.0.5 | maven30 | A release of Maven, a software project management and comprehension tool used primarily for Java projects. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting, and documentation from a central piece of information. |
[a]
A part of this Software Collection requires a JavaScript engine. The v8314 Software Collection included in Red Hat Software Collections 1.2 provides the V8 JavaScript engine and is supported only as the Software Collection's dependency.
[b]
This Software Collection also requires v8314. The v8314 Software Collection included in Red Hat Software Collections 1.2 provides the V8 JavaScript engine and is supported only as the Software Collection's dependency.
[c]
In Red Hat Software Collections 1.2, Node.js is included as a Technology Preview. For more information about Red Hat Technology Previews, see https://access.redhat.com/support/offerings/techpreview/.
|
1.3. Changes in Red Hat Software Collections 1.2
1.3.1. New Components
- devtoolset-3 — see Section 4.1, “Red Hat Developer Toolset”
- git19 — see Section 4.5, “Git”
- devassist09 — see Section 4.6, “DevAssistant”
- maven30 — see Section 4.7, “Maven”
1.3.2. Changes in nginx
1.3.3. Changes in Ruby on Rails 4.0
1.3.4. Changes in Thermostat
1.3.5. Dockerfiles
- httpd24
- mariadb55
- mongodb24
- mysql55
- nginx16
- nodejs010
- perl516
- php54
- php55
- postgresql92
- python27
- python33
- ror40
- ruby193
- ruby200
1.4. Compatibility Information
1.5. Known Issues
-
nodejs-hawk
component - The nodejs-hawk package uses an implementation of the SHA-1 and SHA-256 algorithms adopted from the CryptoJS project. In this release, the client-side JavaScript is obfuscated. The future fix will involve using crypto features directly from the CryptoJS library.
-
postgresql
component - The postgresql92 package for Red Hat Enterprise Linux 6 does not provide the
sepgsql
module as this feature requires installation of libselinux version 2.0.99, which is not available in Red Hat Enterprise Linux 6. -
coreutils
component - Some utilities, for example, su, login, or screen, do not export environment settings in all cases, which can lead to unexpected results. It is therefore recommended to use sudo instead of su and set the
env_keep
environment variable in the/etc/sudoers
file. Alternatively, you can run commands in a reverse order; for example:su -l postgres -c "scl enable postgresql92 psql"
instead ofscl enable postgresql92 bash
su -l postgres -c psql
When using tools like screen or login, you can use the following command to preserve the environment settings:source /opt/rh/<collection_name>/enable
. -
httpd
,mariadb
,mongodb
,mysql
,nodejs
,perl
,php55
,python27
,python33
,ruby193
,ror40
,ruby200
,thermostat
, andv8314
components - When uninstalling the httpd24, mariadb55, mongodb24, mysql55, nodejs010, perl516, php55, python27, python33, ruby193, ror40, ruby200, thermostat1, or v8314 packages, the order of uninstalling can be relevant due to ownership of dependent packages. As a consequence, some directories and files might not be removed properly and might remain on the system.
-
mariadb
,mysql
,postgresql
,mongodb
components - Red Hat Software Collections contains the MySQL 5.5, MariaDB 5.5, PostgreSQL 9.2 and MongoDB 2.4 databases. The core Red Hat Enterprise Linux 6 provides earlier versions of the MySQL and PostgreSQL databases (client library and daemon). The core Red Hat Enterprise Linux 7 provides the same versions of the MariaDB and PostgreSQL databases (client library and daemon). Client libraries are also used in database connectors for dynamic languages, libraries, and so on.The client library packaged in the Red Hat Software Collections database packages in the PostgreSQL component is not supposed to be used, as it is included only for purposes of server utilities and the daemon. Users are instead expected to use the system library and the database connectors provided with the core system.A protocol, which is used between the client library and the daemon, is stable across database versions, so, for example, using the PostgreSQL 8.4 client library with the PostgreSQL 9.2 daemon works as expected.The core Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7 does not include the client library for MongoDB. In order to use this client library for your application, you should use the client library from Red Hat Software Collections and always use the
scl enable ...
call every time you run an application linked against this MongoDB client library. -
mariadb
,mysql
,mongodb
components - MariaDB, MySQL, and MongoDB do not make use of the
/opt/<provider>/<collection>/root
prefix when creating log files. Note that log files are saved in the/var/log/
directory, not/opt/<provider>/<collection>/root/var/log/
. -
httpd
component - Compiling external applications against the Apache Portable Runtime (APR) and APR-util libraries from the httpd24 Software Collection is not supported. The LD_LIBRARY_PATH is not set in httpd24 because it is not required by any application in this Software Collection.
-
httpd
,ruby193
components - In Red Hat Enterprise Linux 6.5 and earlier versions, httpd is unable to execute the binary files in the mod_passenger module, namely
PassengerWatchdog
,PassengerHelperAgent
,PassengerLoggingAgent
, andSpawnPreparer
in the/opt/rh/ruby193/root/usr/lib64/gems/exts/passenger-4.0.18/agents/
directory. To work around this problem, disable SELinux by running the following command asroot
:setenforce 0
-
nginx
component - In Red Hat Enterprise Linux 6.5 and earlier versions, no SELinux policy is applied for the nginx daemon.
-
mariadb
component - The permissions for the
/var/log/mariadb55-mariadb/
directory, in which the log file is stored, are set incorrectly. Consequently, when the/var/log/mariadb55-mariadb/mariadb.log
file is removed in Red Hat Enterprise Linux 7, the service fails to start because themysqld
daemon does not have permission to create log files. To work around this problem, either do not remove the log file or change the owner of the/var/log/mariadb55-mariadb/
directory tomysql:mysql
. -
mysql, mariadb
components - In Red Hat Enterprise Linux 7, the
mariadb55-mariadb
andmysql55-mysqld
services run under themysql
user account by default. When the/var/lib/mysql/mysql.sock
UNIX socket file is created by a different user, the services have insufficient permissions to check whether a process is listening on the socket but the services have sufficient permissions to delete the socket file. Consequently, themariadb55-mariadb
andmysql55-mysqld
services can delete the socket file while a process is still using it. -
perl
component - In Red Hat Enterprise Linux 7, the perl516 Software Collection tapset conflicts with the core system tapset. As a consequence, the
systemtap
utility does not work correctly for perl516. To work around this problem:- Either copy the perl516 tapset to a file renamed by adding the Software Collection's prefix - to do so, use the following command:
cp /opt/rh/perl516/root/usr/share/systemtap/tapset/libperl5.16.3-64.stp /opt/rh/perl516/root/usr/share/systemtap/tapset/perl516-libperl5.16.3-64.stp
- Or uninstall the core system perl-devel package.
-
python27
component - In Red Hat Enterprise Linux 7, when the user tries to install the python27-python-debuginfo package, the
/usr/src/debug/Python-2.7.5/Modules/socketmodule.c
file conflicts with the corresponding file from the python-debuginfo package installed on the core system. Consequently, installation of the python27-python-debuginfo fails. To work around this problem, uninstall the python-debuginfo package and then install the python27-python-debuginfo package. -
devassist
component - When the user tries to rebuild the devassist09-PyYAML package on Red Hat Enterprise Linux 6, the build fails due to a soft dependency, if the Pyrex or Cython programming languages are detected. To work around this problem, make sure the pyrex or cython packages are not installed on your system.
Other Notes
-
php54
component - Note that Alternative PHP Cache (APC) in Red Hat Software Collections 1.2 is provided for user data cache only. For opcode cache, Zend OPcache is provided.
-
nodejs
component - The nodejs-tobi-cookie package has been renamed to nodejs-cookie-jar.
-
ruby
component - Previously, in Red Hat Software Collections 1.0, the V8 JavaScript engine was part of the ruby193 Software Collection. Since Red Hat Software Collections 1.1, the v8 packages have been replaced by the v8314 Software Collection, which is installed as a dependency. In order to use therubyracer, it is necessary to enable the v8314 Software Collection as well.
-
nodejs
component - Previously, in Red Hat Software Collections 1.0, the V8 JavaScript engine was part of the nodejs010 Software Collection. Since Red Hat Software Collections 1.1, the v8 packages have been replaced by the v8314 Software Collection, which is installed as a dependency.
-
python
component - When the user tries to install both the python27-scldevel and python33-scldevel packages, a transaction check error message is returned. This is an expected behavior because the user can install only one set of the macro files provided by the packages (
%scl_python
,%scl_prefix_python
). -
php
component - When the user tries to install both the php54-scldevel and php55-scldevel packages, a transaction check error message is returned. This is an expected behavior because the user can install only one set of the macro files provided by the packages (
%scl_php
,%scl_prefix_php
). -
ruby
component - When the user tries to install both the ruby193-scldevel and ruby200-scldevel packages, a transaction check error message is returned. This is an expected behavior because the user can install only one set of the macro files provided by the packages (
%scl_ruby
,%scl_prefix_ruby
). -
libyaml
component - A newer version of the libyaml package is provided with Red Hat Software Collections 1.2 for use by Red Hat Software Collections.
-
nodejs
component - When installing the nodejs010 Software Collection, nodejs010 installs GCC in the base Red Hat Enterprise Linux system as a dependency, unless the gcc packages are already installed.
-
mariadb
component - In Red Hat Software Collections for Red Hat Enterprise Linux 7, since version 1.1, the
mariadb55-mysqld.service
file has been renamed tomariadb55-mariadb.service
and the/var/log/mariadb55-mysqld.log
file has been moved to/var/log/mariadb55-mariadb/mariadb55-mariadb.log
, for the sake of consistency with Red Hat Enterprise Linux 7.
Chapter 2. Installation
2.1. Getting Access to Red Hat Software Collections
Important
2.1.1. Using Red Hat Subscription Management
- 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 withPool Id
. - Attach the appropriate subscription to your system by running the following command as
root
:subscription-manager subscribe --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 asroot
:subscription-manager list --consumed
- 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:yum repolist all
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
Replace variant with the Red Hat Enterprise Linux system variant, that is,server
orworkstation
. Note that Red Hat Software Collections is supported neither on theClient
nor on theComputeNode
variant. - Enable the appropriate repository by running the following command as
root
:yum-config-manager --enable repository
2.1.2. Using RHN Classic
- 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
orworkstation
):rhel-x86_64-variant-6-rhscl-1 rhel-x86_64-server-6.4.z-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
Note that Red Hat Enterprise Linux 7 channels are accessible only through Red Hat Satellite instances. - 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. - Verify the list of channels you are subscribed to. As
root
, type:rhn-channel --list
2.2. Installing Red Hat Software Collections
Important
Optional
channel to be enabled in order to complete the full installation of these packages:
- The php54-php-imap and php55-php-imap packages require the libc-client package from the Optional channel.
- The php54-php-recode and php55-php-recode packages require the recode package from the Optional channel.
- The perl516-perl-devel package requires the gdbm-devel package from the Optional channel.
- The mariadb55-mariadb-bench package requires the perl-GD package from the Optional channel.
Optional
channel are required:
- The Node.js Software Collection depends on the nodejs010-nodejs-devel package, which requires the c-ares-devel package from the Optional channel (applicable to minimal install).
- The httpd24-mod_ldap package requires the apr-util-ldap package from the Optional channel.
- The php54-php-pspell and php55-php-pspell packages require the aspell package from the Optional channel.
- The python27-python-debug package requires the tix package from the Optional channel.
- The thermostat1-thermostat package requires the apache-commons-beanutils, jansi, hawtjni, jansi-native, and objectweb-asm packages from the Optional channel (applicable to minimal install).
- The thermostat1-thermostat-webapp package requires the felix-framework package from the Optional channel (applicable to minimal install).
- The thermostat1-netty package requires the jzlib package from the Optional channel (applicable to minimal install).
- The apache-commons-logging package requires the xerces-j2 package from the Optional channel (applicable to minimal install).
Important
Important
2.2.1. Installing Individual Software Collections
root
:
yum install software_collection...
root
:
~]# yum install php54 mariadb55
2.2.2. Installing Optional Packages
yum list available software_collection-\*
root
:
yum install package_name...
~]# yum install perl516-perl-CPAN perl516-perl-Archive-Tar
2.2.3. Installing Debugging Information
root
:
debuginfo-install package_name
~]# debuginfo-install ruby193-ruby
rhel-variant-rhscl-6-debug-rpms
or rhel-variant-rhscl-7-debug-rpms
repository as described in Section 2.1.1, “Using Red Hat Subscription Management”. If your system is registered with RHN Classic, subscribe the system to the rhel-x86_64-variant-6-rhscl-1-debuginfo
or rhel-x86_64-variant-7-rhscl-1-debuginfo
channel as described in Section 2.1.2, “Using RHN Classic”. For more information on how to get access to debuginfo packages, see https://access.redhat.com/solutions/9907.
2.3. Uninstalling Red Hat Software Collections
root
:
yum remove software_collection\*
2.4. Rebuilding Red Hat Software Collections
rpmbuild --define 'scl foo'
command, you first need to rebuild the metapackage, which provides the <collection>-build package.
Chapter 3. Usage
3.1. Using Red Hat Software Collections
3.1.1. Running an Executable from a Software Collection
scl enable software_collection... 'command...'
scl enable software_collection... -- command...
hello.pl
with the Perl interpreter from the perl516 Software Collection, type:
~]$ scl enable perl516 'perl hello.pl'
Hello, World!
scl
utility, causing it to be run with the executables from a selected Software Collection in preference to their possible Red Hat Enterprise Linux system equivalents. For a complete list of Software Collections that are distributed with Red Hat Software Collections, see Table 1.1, “Red Hat Software Collections 1.2 Components”.
3.1.2. Running a Shell Session with a Software Collection as Default
scl enable software_collection... bash
~]$ scl enable python27 postgresql92 bash
$X_SCLS
environment variable, for instance:
~]$ echo $X_SCLS
python27 postgresql92
3.1.3. Running a System Service from a Software Collection
/etc/rc.d/init.d/
directory. To start such a service in the current session, type the following at a shell prompt as root
:
service software_collection-service_name start
root
:
chkconfig software_collection-service_name on
postgresql
service from the postgresql92 Software Collection and enable it in runlevels 2, 3, 4, and 5, type as root
:
~]#service postgresql92-postgresql start
Starting postgresql92-postgresql service: [ OK ] ~]#chkconfig postgresql92-postgresql on
3.2. Accessing a Manual Page from a Software Collection
/opt/rh
directory.
scl enable software_collection 'man software_collection'
~]$ scl enable mariadb55 "man mariadb55"
3.3. Deploying Applications That Use Red Hat Software Collections
- Install all required Software Collections and packages manually and then deploy your application, or
- Create a new Software Collection for your application and specify all required Software Collections and other packages as dependencies.
3.4. Dockerfiles for Red Hat Software Collections
- httpd24
- mariadb55
- mongodb24
- mysql55
- nginx16
- nodejs010
- perl516
- php54
- php55
- postgresql92
- python27
- python33
- ror40
- ruby193
- ruby200
- Installs the basic set of packages from each Software Collection,
- Exposes some TCP ports; for example, port 80 and 443 for the httpd24 collection.
3.4.1. Installation and usage
root
:
yum install rhscl-dockerfiles
3.4.2. Deploying Software Collections dependent on the Red Hat Software Collections Docker images
Chapter 4. Specifics of Individual Software Collections
4.1. Red Hat Developer Toolset
/opt/
directory. These tools are enabled by the user on demand using the supplied scl utility. Similarly to other Software Collections, these do not replace the Red Hat Enterprise Linux system versions of these tools, nor will they be used in preference to those system versions unless explicitly invoked using the scl utility.
4.2. Thermostat 1
Agent
, which collects data, and a Client
, which allows users to visualize collected data. These components communicate via a storage layer: either directly via MongoDB or indirectly via a Web layer for increased security. A pluggable agent and GUI framework allows for collection and visualization of performance data beyond what is included out of the box.
root
:
yum install thermostat1
scl enable thermostat1 bash
root
:
service thermostat1-thermostat-tomcat start
4.3. Ruby on Rails 4.0
scl enable ror40 bash
4.4. MongoDB 2.4.9
root
:
yum install mongodb24
scl enable mongodb24 'mongo'
4.4.1. MongoDB 2.4.9 on Red Hat Enterprise Linux 6
root
:
service mongodb24-mongodb start
root
:
chkconfig mongodb24-mongodb on
root
:
service mongodb24-mongodb-shard start
root
:
chkconfig mongodb24-mongodb-shard on
4.4.2. MongoDB 2.4.9 on Red Hat Enterprise Linux 7
root
:
systemctl start mongodb24-mongodb.service
root
:
systemctl enable mongodb24-mongodb.service
root
:
systemctl start mongodb24-mongodb-shard.service
root
:
systemctl enable mongodb24-mongodb-shard.service
4.5. Git
4.6. DevAssistant
4.6.1. Getting Started with DevAssistant
root
:
yum install devassist09
scl enable devassist09 bash
devassistant --help
da -h
--help
option on each level to list your possible next steps, until you reach the level of an executable subassistant (see Example 4.1, “Creating a New Python Library Project”).
devassistant-gui
da-gui
devassistant
and da
commands are equal. Further in the text, we will use only the shorter variant, the da
command.
4.6.2. Running Assistants
create
, modify
, prepare
, and task
. To run an assistant, use the following command:
da [--debug] {create,modify,prepare,task} [assistant [arguments]] ...
Table 4.1. Functionalities of DevAssistant
Command | Shortened Command | Description |
---|---|---|
da create | da crt | Creating a new project from scratch |
da modify | da mod | Working with an existing project |
da prepare | da prep | Preparing a development environment for an upstream project |
da task | Performing a custom task not related to a specific project |
modify
, prepare
, and task
functionalities. These categories are available for users who want to create their own assistants.
4.6.3. Creating Projects with DevAssistant
Table 4.2. Assistants for Creating Projects
Assistant | Subassistant | Description |
---|---|---|
c | app | An application in C |
lib | A dynamically linked library in C | |
cpp | app | An application in C++ |
lib | A dynamically linked library in C++ | |
java | maven | A simple project using Maven |
python | lib | A simple library for Python |
--help
option.
Example 4.1. Creating a New Python Library Project
- Enable the devassist09 Software Collection by running this command:
~]$
scl enable devassist09 bash
- Display help about DevAssistant by using the
--help
option:~]$
da --help
You can either run assistants with: da [--debug] {create,modify,prepare,task} [ASSISTANT [ARGUMENTS]] ... Where: create used for creating new projects modify used for working with existing projects prepare used for preparing environment for upstream projects task used for performing custom tasks not related to a specific project You can shorten "create" to "crt", "modify" to "mod" and "prepare" to "prep". Or you can run a custom action: da [--debug] [ACTION] [ARGUMENTS] Available actions: help Print detailed help version Print version - List the possible next steps for creating a project by typing:
~]$
da create --help
usage: create [-h] [--deps-only] {c,cpp,java,python} ... Kickstart new projects easily with DevAssistant. optional arguments: -h, --help show this help message and exit --deps-only Only install dependencies subassistants: Following subassistants will help you with setting up your project. {c,cpp,java,python} - Display help on the
python
assistant by typing at a shell prompt:~]$
da create python --help
usage: create python [-h] {lib} ... This is a base Python assistant, you have to select a subassistant. optional arguments: -h, --help show this help message and exit subassistants: Following subassistants will help you with setting up your project. {lib} - List your choices for the only
python
subassistant,lib
, by running this command:~]$
da create python lib --help
usage: create python lib [-h] [-e [ECLIPSE]] -n NAME Scaffolds a simple Python library project. optional arguments: -h, --help show this help message and exit -e [ECLIPSE], --eclipse [ECLIPSE] Configure as Eclipse project (uses ~/workspace or specified directory) -n NAME, --name NAME Name of project to create - Run the assistant to create your new Python library project named
mypythonlib
by using the following command:~]$
da create python lib -n mypythonlib
4.7. Maven
root
:
yum install maven30
scl enable maven30 bash
/opt/rh/maven30/root/etc/maven/settings.xml
file.
Chapter 5. Migration
5.1. Migrating from MySQL 5.1 to MySQL 5.5
5.1.1. Notable Differences Between MySQL 5.1 and MySQL 5.5
- Starting with MySQL 5.5, the InnoDB storage engine (formerly known as InnoDB Plugin) is the default storage engine.
- InnoDB and some other plug-ins (for example, archive, blackhole and federated) were installable plug-ins in MySQL 5.1. Starting with MySQL 5.5, these plug-ins became compiled-in storage engines, that is, they cannot be installed or uninstalled by default.
- If you used InnoDB Plugin and it was loaded using the
plugin-load=innodb=ha_innodb_plugin.so
configuration option, you need to remove this configuration option as it does not work in MySQL 5.5. - In MySQL 5.1, InnoDB Plugin included a configuration variable
innodb_file_io_threads
. However, this variable does not exist in MySQL 5.5; new variables,innodb_read_io_threads
andinnodb_write_io_threads
, are used instead. To ensure proper functionality, either remove the former variable from the configuration file or replace it with the current variables. - When upgrading from MySQL 5.1 to MySQL 5.5 using the in-place upgrading method, the
mysql.proxies_priv
table will not exist. To create the missing table, the mysql_upgrade utility has to be run as soon as the new daemon is started. - MySQL 5.5 uses latin1 for the
stopword
file if thecharacter_set_server
variable is ucs2, utf16 or utf32. Thus, if the table uses FULLTEXT indexes in these cases, users should repair the table using theREPAIR TABLE table_name QUICK
. - MySQL 5.1 used the
language
variable for specifying the directory which included the error message file. This option is now deprecated and has been replaced by thelc_messages_dir
andlc_messages
options. This also applies for configuration options. Also, error messages no longer contain mixed set of character sets and error messages are returned in the set following thecharacter_set_results
system variable instead. That is, some error messages can be different in MySQL 5.5.
Important
5.1.2. Upgrading from MySQL 5.1 to MySQL 5.5
- In the first scenario, the whole dump of all databases from one database is generated, mysql is run with the dump file as an input, using mysqlimport or the
LOAD DATA INFILE
SQL command within the other database. At the same time, the appropriate daemons have to be running during both dumping and restoring. You can use the--all-databases
option in the mysqldump call to include all databases in the dump. The--routines
,--triggers
and--events
options can also be used if needed. - During the in-place upgrade, the data files are copied from one database directory to another database directory. The daemons should not be running at the time of copying. Set the appropriate permissions and SELinux context for copied files.
mysql_upgrade
command. Running mysql_upgrade
is necessary to check and repair internal tables.
Important
mysql_upgrade
script, should be run inside the scl enable
environment.
root
user has a non-empty password defined (it should have it defined), it is necessary to call the mysql_upgrade utility with the -p
option and specify the password.
my.cnf
file to reflect the environment.
Example 5.1. Dump and Restore Upgrade
~]#service mysqld start
Starting mysqld: [ OK ] ~]#mysqldump --all-databases --routines --events > dump.sql
~]#service mysqld stop
Stopping mysqld: [ OK ] ~]#service mysql55-mysqld start
Starting mysql55-mysqld: [ OK ] ~]#scl enable mysql55 'mysql' < dump.sql
~]#scl enable mysql55 'mysql_upgrade -u root -p'
Enter password: Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck with default connection arguments Running 'mysqlcheck with default connection arguments a.t1 OK mysql.columns_priv OK <skipped tables list> mysql.user OK Running 'mysql_fix_privilege_tables'... OK
Example 5.2. In-place Upgrade
~]#service mysqld stop
Stopping mysqld: [ OK ] ~]#service mysql55-mysqld stop
Stopping mysql55-mysqld: [ OK ] ~]#rm -rf /opt/rh/mysql55/root/var/lib/mysql/
~]#cp -r /var/lib/mysql/ /opt/rh/mysql55/root/var/lib/
~]#chown -R mysql:mysql /opt/rh/mysql55/root/var/lib/mysql/
~]#restorecon -R /opt/rh/mysql55/root/var/lib/mysql/
~]#service mysql55-mysqld start
Starting mysql55-mysqld: [ OK ] ~]#scl enable mysql55 'mysql_upgrade -u root -p'
Enter password: Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck with default connection arguments Running 'mysqlcheck with default connection arguments a.t1 OK mysql.columns_priv OK <skipped tables list> mysql.user OK Running 'mysql_fix_privilege_tables'... OK
Important
- The mariadb55 component name should be used instead of the mysql55, so replace all occurrences of
mysql55
withmariadb55
. - The
systemd
unit name for MariaDB 5.5. ismariadb55-mariadb
in Red Hat Enterprise Linux 7, while theSysV
unit script for MariaDB 5.5 is calledmariadb55-mysqld
in Red Hat Enterprise Linux 6.
5.1.3. Using the mysql55-mysql-devel Package
5.1.3.1. Using Database Connectors for Dynamic Languages
Important
mysqlnd
driver will not be able to connect to the database. This is because the old_password
setting in the /etc/my.cnf
file is turned off by default on Red Hat Enterprise Linux 6 while it is enabled on Red Hat Enterprise Linux 5. To work around this problem, set old_password
to 0, restart the MariaDB or MySQL service and set a new password for each user.
5.1.3.2. Building Applications for MySQL 5.5 from Red Hat Software Collections
scl enable mysql55 '...'
call.
5.2. Migrating from PostgreSQL 8.4 to PostgreSQL 9.2
5.2.1. Notable Differences Between PostgreSQL 8.4 and PostgreSQL 9.2
- The following server configuration parameters have been removed and are no longer supported:
add_missing_from
,regex_flavor
,silent_mode
,wal_sender_delay
, andcustom_variable_classes
. Do not use any of these parameters in the new configuration file. - The
unix_socket_directory
parameter has been renamed tounix_socket_directories
and can now be used to specify more than one UNIX socket to listen on. To do so, provide a list of comma-separated directories as the value of this option. The default value remains unchanged and is/tmp
. - New configuration parameters
ssl_ca_file
,ssl_cert_file
,ssl_crl_file
, andssl_key_file
have been added. These configuration parameters can be used to specify the locations of server-side SSL files that were previously hard-coded as relative paths to theroot.crt
,server.crt
,root.crl
, andserver.key
files in the data directory.Note that the PostgreSQL server no longer reads theroot.crt
androot.crl
files by default. To load these files, change the corresponding parameters to non-default values. - The
=>
operator has been removed and users are now advised to use thehstore(text, text)
function. - The default value of the
standard_conforming_strings
configuration parameter is nowon
. This configuration parameter controls if ordinary string literals (strings enclosed in single quotes) treat backslashes literally as specified in the SQL standard. - A new configuration parameter,
backslash_quote
, has been added. This configuration parameter can be used to control whether a single quotation mark can be represented by\'
in string literals. The default value issafe_encoding
, which permits the use of\'
only when the client encoding does not allow ASCII backslashes in multi-byte characters. As a consequence,\'
can now be interpreted differently only in specific cases and only in string literals that do not conform to standards, including escape string syntax,E'value'
. - PostgreSQL 9.0 introduced access privileges for large objects. Consequently, a new configuration parameter,
lo_compat_privileges
, has been added to allow you to disable security checks related to the large objects affected by this change. To disable these security checks, change the value of this configuration parameter toon
. The default value isoff
.
5.2.2. Upgrading from PostgreSQL 8.4 to PostgreSQL 9.2
Important
/var/lib/pgsql/data/
directory.
Procedure 5.1. Performing In-place Upgrade
- 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
- Verify that the new data directory located in
/opt/rh/postgresql92/root/var/lib/pgsql/data/
does not exist:file /opt/rh/postgresql92/root/var/lib/pgsql/data/
If you are running a fresh installation of PostgreSQL 9.2, this directory should not be present in your system. If it is, back it up by running the following command asroot
:mv /opt/rh/postgresql92/root/var/lib/pgsql/data{,-scl-backup}
- Copy the old database data to the new location by typing the following at a shell prompt as
root
:cp -ra /var/lib/pgsql/data/ /opt/rh/postgresql92/root/var/lib/pgsql/
- Open the
/opt/rh/postgresql92/root/var/lib/pgsql/data/pg_hba.conf
configuration file and verify that thepostgres
user is allowed to connect to the PostgreSQL server fromlocalhost
without a password. If not, you can edit this file and temporarily set the authentication method for thepostgres
user totrust
orident
. For a detailed description of thepg_hba.conf
file and a complete list of available configuration options, see the official documentation. - Upgrade the database data for the new server by running the following command as
root
:service postgresql92-postgresql upgrade
It is recommended that you read the resulting/opt/rh/postgresql92/root/var/lib/pgsql/pgupgrade.log
log file to see if there were any problems with the upgrade. - Start the new server as
root
:service postgresql92-postgresql start
It is also advised that you run theanalyze_new_cluster.sh
script as follows:su - postgres -c 'scl enable postgresql92 ~/analyze_new_cluster.sh'
- Optionally, you can configure the PostgreSQL 9.2 server to start automatically at boot time. To disable the old PostgreSQL 8.4 server, type the following command as
root
:chkconfig postgresql off
To enable the PostgreSQL 9.2 server, type asroot
:chkconfig postgresql92-postgresql on
Procedure 5.2. Performing a Dump and Restore Upgrade
- Ensure that the old PostgreSQL server is running by typing the following at a shell prompt as
root
:service postgresql start
- Dump all data in the PostgreSQL database into a script file. As
root
, type:su - postgres -c 'pg_dumpall > ~/pgdump_file.sql'
- Stop the old server by running the following command as
root
:service postgresql stop
- Initialize the data directory for the new server as
root
:service postgresql92-postgresql initdb
- Start the new server as
root
:service postgresql92-postgresql start
- Import data from the previously created SQL file:
su - postgres -c 'scl enable postgresql92 "psql -f ~/pgdump_file.sql postgres"'
- Optionally, you can configure the PostgreSQL 9.2 server to start automatically at boot time. To disable the old PostgreSQL 8.4 server, type the following command as
root
:chkconfig postgresql off
To enable the PostgreSQL 9.2 server, type asroot
:chkconfig postgresql92-postgresql on
- If your configuration differs from the default one, make sure to update configuration files, especially the
/opt/rh/postgresql92/root/var/lib/pgsql/data/pg_hba.conf
configuration file. Otherwise only thepostgres
user will be allowed to access the database.
5.3. Migrating from nginx 1.4 to nginx 1.6
/opt/rh/nginx16/root/
. The error log is now stored in /var/log/nginx16/error.log
by default, and the initscript is called nginx16-nginx
.
Important
/opt/rh/nginx14/root/
tree.
/opt/rh/nginx14/root/
tree, replicate those changes in the new /opt/rh/nginx16/root/
directory, too.
Chapter 6. Additional Resources
6.1. Red Hat Enterprise Linux Developer Program Group
6.2. Red Hat Product Documentation
- Red Hat Software Collections 1.2 Packaging Guide — The Packaging Guide for Red Hat Software Collections explains the concept of Software Collections, documents the
scl
utility, and provides a detailed explanation of how to create a custom Software Collection or extend an existing one. - Red Hat Developer Toolset 3.0 Release Notes — The Release Notes for Red Hat Developer Toolset document known problems, possible issues, changes, and other important information about this Software Collection.
- Red Hat Developer Toolset 3.0 User Guide — The User Guide for Red Hat Developer Toolset contains more information about installing and using this Software Collection.
- Using and Configuring Red Hat Subscription Manager — The Using and Configuring Red Hat Subscription Manager book provides detailed information on how to register Red Hat Enterprise Linux systems, manage subscriptions, and view notifications for the registered systems.
- Red Hat Enterprise Linux 6 Developer Guide — The Developer Guide for Red Hat Enterprise Linux 6 provides more information for developers on the Red Hat Enterprise Linux platform.
- Red Hat Enterprise Linux 7 Developer Guide — The Developer Guide for Red Hat Enterprise Linux 7 provides an introduction to application development tools in Red Hat Enterprise Linux 7.
- Red Hat Enterprise Linux 6 Deployment Guide — The Deployment Guide for Red Hat Enterprise Linux 6 provides relevant information regarding the deployment, configuration, and administration of this system.
- Red Hat Enterprise Linux 7 System Administrator's Guide — The System Administrator's Guide for Red Hat Enterprise Linux 7 provides information on deployment, configuration, and administration of this system.
6.3. Red Hat Developer Blog
Appendix A. Revision History
Revision History | |||
---|---|---|---|
Revision 1.1-27 | Thu 09 Jun 2016 | ||
| |||
Revision 1.1-23 | Tue Nov 11 2014 | ||
| |||
Revision 1.1-22 | Thu Oct 30 2014 | ||
| |||
Revision 1.1-20 | Tue Oct 07 2014 | ||
| |||
Revision 1.1-19 | Tue Sep 09 2014 | ||
|