Chapter 3. Usage
This chapter describes the necessary steps for rebuilding and using Red Hat Software Collections 2.1, and deploying applications that use Red Hat Software Collections.
3.1. Using Red Hat Software Collections
3.1.1. Running an Executable from a Software Collection
To run an executable from a particular Software Collection, type the following command at a shell prompt:
scl enable software_collection... 'command...'
Or, alternatively, use the following command:
scl enable software_collection... -- command...
Replace software_collection with a space-separated list of Software Collections you want to use and command with the command you want to run. For example, to execute a Perl program stored in a file named
hello.pl with the Perl interpreter from the perl516 Software Collection, type:
~]$ scl enable perl516 'perl hello.pl'
Hello, World!
You can execute any command using the
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 2.1 Components”.
3.1.2. Running a Shell Session with a Software Collection as Default
To start a new shell session with executables from a selected Software Collection in preference to their Red Hat Enterprise Linux equivalents, type the following at a shell prompt:
scl enable software_collection... bash
Replace software_collection with a space-separated list of Software Collections you want to use. For example, to start a new shell session with the python27 and postgresql92 Software Collections as default, type:
~]$ scl enable python27 postgresql92 bash
The list of Software Collections that are enabled in the current session is stored in the
$X_SCLS environment variable, for instance:
~]$ echo $X_SCLS
python27 postgresql92
For a complete list of Software Collections that are distributed with Red Hat Software Collections, see Table 1.1, “Red Hat Software Collections 2.1 Components”.
3.1.3. Running a System Service from a Software Collection
Software Collections that include system services install corresponding init scripts in the
/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
Replace software_collection with the name of the Software Collection and service_name with the name of the service you want to start. To configure this service to start automatically at boot time, type the following command as
root:
chkconfig software_collection-service_name on
For example, to start the
postgresql service from the postgresql92 Software Collection and enable it in runlevels 2, 3, 4, and 5, type as root:
~]#service postgresql92-postgresql startStarting postgresql92-postgresql service: [ OK ] ~]#chkconfig postgresql92-postgresql on
For more information on how to manage system services in Red Hat Enterprise Linux 6, refer to the Red Hat Enterprise Linux 6 Deployment Guide. For a complete list of Software Collections that are distributed with Red Hat Software Collections, see Table 1.1, “Red Hat Software Collections 2.1 Components”.
3.2. Accessing a Manual Page from a Software Collection
Every Software Collection contains a general manual page that describes the content of this component. Each manual page has the same name as the component and it is located in the
/opt/rh directory.
To read a manual page for a Software Collection, type the following command:
scl enable software_collection 'man software_collection'
Replace software_collection with the particular Red Hat Software Collections component. For example, to display the manual page for mariadb55, type:
~]$ scl enable mariadb55 "man mariadb55"3.3. Deploying Applications That Use Red Hat Software Collections
In general, you can use one of the following two approaches to deploy an application that depends on a component from Red Hat Software Collections in production:
- 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.
For more information on how to manually install individual Red Hat Software Collections components, see Section 2.2, “Installing Red Hat Software Collections”. For further details on how to use Red Hat Software Collections, see Section 3.1, “Using Red Hat Software Collections”. For a detailed explanation of how to create a custom Software Collection or extend an existing one, read the Red Hat Software Collections Packaging Guide.
3.4. Dockerfiles for Red Hat Software Collections
Red Hat Software Collections is shipped with Dockerfiles for the following Software Collections:
- httpd24
- mariadb55
- mongodb24
- mysql55
- nginx16
- nodejs010
- perl516
- php54
- php55
- postgresql92
- python27
- python33
- rh-mariadb100
- rh-mongodb26
- rh-mysql56
- rh-passenger40
- rh-perl520
- rh-php56
- rh-postgresql94
- rh-python34
- rh-ror41
- rh-ruby22
- ror40
- ruby193
- ruby200
The Dockerfiles are included in the rhscl-dockerfiles package distributed with Red Hat Software Collections. Dockerfiles are text files that define how a Docker image is created. Note that the rhscl-dockerfiles package has not been updated since Red Hat Software Collections 2.0.
Note
The docker package, which contains the
Docker daemon, command line tool, and other necessary components for building and using docker-formatted container images, is currently only available for the Server variant of the Red Hat Enterprise Linux 7 product. Red Hat Software Collections Dockerfiles are distributed for Red Hat Enterprise Linux 6 as well, but the images built using them can only be deployed on Red Hat Enterprise Linux 7 Server.
Each Dockerfile creates a minimal Docker image from Red Hat Enterprise Linux 6 or Red Hat Enterprise Linux 7 plus the Software Collection. Each Dockerfile will create an image which:
- Installs the basic set of packages from each Software Collection,
- Exposes some TCP ports; for example, port
80and443for the httpd24 collection.
The Dockerfiles are provided as examples, using which customers can build more complex containers.
Dockerfiles are available also for previously released Software Collections. For detailed information about them, refer to the Red Hat Software Collections documentation and the Red Hat Software Collections Product Life Cycle document.
3.4.1. Installation and Usage
To install the rhscl-dockerfiles package, type the following command as
root:
yum install rhscl-dockerfiles
Use these Dockerfiles to create Docker images for the covered Software Collections.
For more information about building an image from a Dockerfile, see the Get Started with Docker Formatted Container Images chapter in the Getting Started with Containers documentation.
3.4.2. Deploying Software Collections Dependent on the Red Hat Software Collections Docker Images
You can use a Red Hat Software Collections Docker image as a base image and create your own containerized Software Collection on top of it as a separate image.
For more information about creating a new Docker image, see the Creating Docker Images section in the Getting Started with Containers documentation.
