Description of problem:
The node RPM ships only one default profile with no variations. Ship some variations and enable the installer to use them.
Steps to Reproduce:
1. Install via openshift.sh / oo-install with a node profile set to medium or large (or xpaas)
2. Check /etc/openshift/resource_limits.conf
Same default (small) profile with just the name changed.
Settings in the file actually different from the small, copied from example files.
Commit pushed to master at https://github.com/openshift/origin-server
node conf: supply resource_limit.conf examples
Bug 1133936 - Provide some usable canned resource_limits profiles
Additionally, reorganizes resource_limits.conf a little bit to make it a
little easier for an administrator to find common things they want to
Finally, modified resource_limits.conf defaults to be in line with
a small m3.xlarge host. The CPU constraints are relaxed a bit and
max_active_gears is lowered to be more conservative. A README is added
to indicate that customers are expected to customize this.
Please test along with https://github.com/openshift/openshift-extras/pull/442
Verified and pass on puddle-2014-08-29.11 using openshift.sh/oo-install.
1) The resource are installed.
[root@rhel65 openshift]# ls -1 resource_limits.conf*
2) The resource resource_limits file can be deployed correctly.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.