红帽全球峰会此内容没有您所选择的语言版本。
2.0 Release Notes
Release Notes for OpenShift Enterprise
Abstract
Chapter 1. Introduction to OpenShift Enterprise
1.1. Installing OpenShift Enterprise 2.0
1.2. Upgrading to OpenShift Enterprise 2.0
Chapter 2. New Features
2.1. What's New in OpenShift Enterprise 2.0
OpenShift Enterprise now supports the following new or updated cartridges:
- Node.js 0.10
- Python 2.7
- PostgreSQL 9.2
- Ruby 1.9 (now supported through the use of Software Collections)
Users can now set one or more custom environment variables for their applications. Set, view, and remove environment variables with the rhc env commands. See the OpenShift Enterprise User Guide for more information on using environment variables.
OpenShift Enterprise now features an optional Administration Console, providing administrators with a read-only view of their deployment data. Administrators can view gear profiles and resource management, and can receive suggestions on how to improve performance. See the OpenShift Enterprise Deployment Guide for the installation procedure, and the OpenShift Enterprise Administration Guide for usage instructions.
Users can now create multiple domains. See the OpenShift Enterprise User Guide for information on using domains, including creating and maintaining domains, and the OpenShift Enterprise Administration Guide for information on administering domains for users, such as configuring domain settings.
Users can now work collaboratively on applications within a domain. Add another user to your domain with view, edit, or administer access. See the OpenShift Enterprise User Guide for more information on members.
Users can now configure an application's deployment process. Use the rhc configure-app command to enable or disable automatic deployments, deploy from different Git branches, keep deployment metadata, and switch between Git and binary deployments. These new features also enable users to rollback an application to a previous deployment, or deploy using a binary snapshot. See the OpenShift Enterprise User Guide for more information on deployments.
OpenShift Enterprise 2.0 allows external load balancing by introducing pluggable web routing for high-availability instances. See the OpenShift Enterprise Deployment Guide for a more information on external load balancing.
2.2. Notable Technical Changes
OpenShift Enterprise 2.0 has new channels in both RHN Classic and Red Hat Subscription Management. See the OpenShift Enterprise Deployment Guide for an updated list of channel names and for more information on available repositories.
iptables Port Proxy Solution
OpenShift Enterprise now uses iptables instead of HAProxy as the port proxy solution. See the OpenShift Enterprise Deployment Guide for details on configuring the port proxy.
OpenShift Enterprise's MCollective infrastructure now utilizes the Software Collection Library (SCL). This includes the MCollective agent on node hosts and the MCollective client on broker hosts. MCollective packages and services now use a ruby193-mcollective prefix, which results in changes to relevant commands and file locations. See the OpenShift Enterprise Deployment Guide for more information on MCollective updates.
Previously, all deployed applications used a single front-end HTTP service. Now, administrators can configure their front-end server through a set of available plug-ins. See the OpenShift Enterprise Deployment Guide for more information on changing the front-end server plug-ins.
OpenShift Enterprise 2.0 introduces enhancements which minimize downtime for scaled applications during deployments and restarts. Scaled web cartridge restarts experience zero downtime. Application deployments experience minimized downtime when using a single HAProxy cartridge, and zero downtime when using multiple HAProxy cartridges.
Chapter 3. Known Issues
IPv6 is not supported for the 2.0 release, and OpenShift Enterprise has not been tested using IPv6. Some components that may be affected are listed in the bug report.
If you delete the Jenkins builder gear (from JBoss Developer Studio) and try to rebuild an application, the build fails because the build can not be found. This seems to be caused because Jenkins keeps a list of builders, and upon builder deletion (using REST calls), Jenkins does not get cleaned up.
Jenkins Server fails to build a re-created application that uses the same name as a previously deleted application. To workaround this issue, delete the Jenkins job before creating an application using the same name as a deleted application.
Chapter 4. Asynchronous Errata Updates
Note
The latest OpenShift Enterprise Deployment Guide provides general instructions on how to apply asynchronous errata updates within a minor release:
yum update command on a host installs packages for all pending updates at once. If you are applying multiple asynchronous errata updates at once, any additional update instructions for all releases being installed must be performed. However, the steps can be aggregated in this situation when commands would be unnecessarily repeated. When evaluating which additional steps must be performed for multiple pending asynchronous errata updates, consider the following general workflow:
- Run the
yum updatecommand on each host. - Restart relevant services.
- Clear the broker and console cache on the broker host, if relevant.
- Run the
oo-admin-upgradecommand on the broker host to upgrade existing gears, if relevant.
Example 4.1. Applying Multiple Asynchronous Errata Updates at Once
- After running the
yum updatecommand on each host, run the following on each node host:service ruby193-mcollective restart
# service ruby193-mcollective restartCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Run the following on the broker host:
service openshift-broker restart service openshift-console restart oo-admin-broker-cache --console oo-admin-upgrade archive oo-admin-upgrade upgrade-node --version=2.0.7
# service openshift-broker restart # service openshift-console restart # oo-admin-broker-cache --console # oo-admin-upgrade archive # oo-admin-upgrade upgrade-node --version=2.0.7Copy to Clipboard Copied! Toggle word wrap Toggle overflow Note that theoo-admin-upgrade upgrade-nodecommand is only run once, using the version for the latest release being applied.
| Release | Advisory | Additional Instructions |
|---|---|---|
| 2.0.1 | RHBA-2014:0020 |
After running the
yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host:
service ruby193-mcollective restart |
| 2.0.2 | RHBA-2014:0102 |
After running the
yum update command and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host:
service ruby193-mcollective restart
On the broker host, restart the broker service and, if installed, the console service:
service openshift-broker restart service openshift-console restart |
| RHBA-2014:0117 |
After running the
yum update command and ensuring all packages have been updated, restart the broker service on the broker host:
service openshift-broker restart | |
| 2.0.3 | RHBA-2014:0209 |
After running the
yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host:
service ruby193-mcollective restart
On the broker host, upgrade all nodes using the following commands. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for alternate
oo-admin-upgrade command usage and use 2.0.3 as the target --version.
rm -rf /tmp/oo-upgrade oo-admin-upgrade upgrade-node --version=2.0.3 |
| RHBA-2014:0210 |
After running the
yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host:
service ruby193-mcollective restart
On the broker host, upgrade all nodes using the following commands. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for alternate
oo-admin-upgrade command usage and use 2.0.3 as the target --version.
rm -rf /tmp/oo-upgrade oo-admin-upgrade upgrade-node --version=2.0.3 | |
| 2.0.4 | RHBA-2014:0309 |
After running the
yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host:
service ruby193-mcollective restart
On the broker host, restart the broker service:
service openshift-broker restart |
| 2.0.5 | RHBA-2014:0417 |
After running the
yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host:
service ruby193-mcollective restart |
| 2.0.6 | RHEA-2014:0599 |
After running the
yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host:
service ruby193-mcollective restart
On the broker host, restart the broker service and, if installed, the console service:
service openshift-broker restart service openshift-console restart
Clear the broker cache and, if installed, the console cache:
oo-admin-broker-cache --console
On the broker host, archive previous upgrade data and upgrade all nodes using the following commands. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for alternate
oo-admin-upgrade command usage and use 2.0.6 as the target --version.
oo-admin-upgrade archive oo-admin-upgrade upgrade-node --version=2.0.6 |
| 2.0.7 | RHBA-2014:1097 |
After running the
yum update command on each host and ensuring all packages have been updated, there are no additional update instructions for this release.
|
| 2.0.8 | RHBA-2015:0053 |
After running the
yum update command on each host and ensuring all packages have been updated, there are no additional update instructions for this release.
|
| 2.0.9 | RHBA-2015:1588 |
After running the
yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host:
service ruby193-mcollective restart
Clear the broker cache and, if installed, the console cache:
oo-admin-broker-cache --console |
| 2.0.10 | RHEA-2015:1587 |
After running the
yum update command on each host and ensuring all packages have been updated, there are no additional update instructions for this release.
|
Chapter 5. Product Support and Documentation
Product support is available at http://www.redhat.com/support.
Product documentation for OpenShift Enterprise is available at https://access.redhat.com/knowledge/docs/OpenShift_Enterprise/.
Appendix A. Revision History
| Revision History | |||||
|---|---|---|---|---|---|
| Revision 2.0-11 | Wed Aug 12 2015 | ||||
| |||||
| Revision 2.0-10 | Tue Aug 11 2015 | ||||
| |||||
| Revision 2.0-9 | Fri Sep 12 2014 | ||||
| |||||
| Revision 2.0-8 | Fri Jun 6 2014 | ||||
| |||||
| Revision 2.0-7 | Mon Apr 21 2014 | ||||
| |||||
| Revision 2.0-6 | Fri Mar 28 2014 | ||||
| |||||
| Revision 2.0-5 | Tue Mar 18 2014 | ||||
| |||||
| Revision 2.0-4 | Tue Feb 25 2014 | ||||
| |||||
| Revision 2.0-3 | Thu Jan 30 2014 | ||||
| |||||
| Revision 2.0-2 | Tue Jan 28 2014 | ||||
| |||||
| Revision 2.0-1 | Tue Jan 14 2014 | ||||
| |||||
| Revision 2.0-0 | Mon Dec 9 2013 | ||||
| |||||
Legal Notice
Copyright © 2025 Red Hat
OpenShift documentation is licensed under the Apache License 2.0 (https://www.apache.org/licenses/LICENSE-2.0).
Modified versions must remove all Red Hat trademarks.
Portions adapted from https://github.com/kubernetes-incubator/service-catalog/ with modifications by Red Hat.
Red Hat, Red Hat Enterprise Linux, the Red Hat logo, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation’s permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}