Bug 907741
| Summary: | Administrator cannot create a district with a custom gear size until it is included in VALID_GEAR_SIZE | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | xjia <xjia> |
| Component: | Documentation | Assignee: | bmoss |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.0.0 | CC: | bleanhar, bmoss, jialiu, jokerman, lcarlon, libra-onpremise-devel, lmeyer, mmccomas, xtian |
| Target Milestone: | --- | Keywords: | Documentation, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-20 02:39:03 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
xjia
2013-02-05 07:33:26 UTC
It would certainly be nice if changing /etc/openshift/resource_limits.conf was the only thing that was needed. However, currently the oo-admin-crl-district code relies on the VALID_GEAR_SIZES setting in /etc/openshift/broker.conf. The node profile has to be set there too. This is getting reworked quite a bit upstream so we'll make sure this gets taken into account there. VALID_GEAR_SIZES is mentioned briefly in the admin guide https://access.redhat.com/knowledge/docs/en-US/OpenShift_Enterprise/1/html-single/Administration_Guide/index.html#sect-OpenShift_Enterprise-Administration_Guide-Setting_Default_Gear_Quotas_and_Sizes It probably deserves a mention in the Deployment Guide section about this as well. https://access.redhat.com/knowledge/docs/en-US/OpenShift_Enterprise/1/html-single/Deployment_Guide/index.html#sect-OpenShift_Enterprise-Deployment_Guide-Continuing_Node_Installation_for_Enterprise-Gear_Profiles Given the upstream changes for this are indeterminate, I am switching this to a docs bug. The work to be done is: 1. In the admin guide linked above, mention that gear profiles can't be used by admins to create districts, or develoeprs to create applications / gears, until they are listed in VALID_GEAR_SIZES. 2. Likewise in the deploy guide section above. |