Bug 1265423
| Summary: | .gitconfig is not configurable for application create | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Eric Rich <erich> |
| Component: | Containers | Assignee: | Timothy Williams <tiwillia> |
| Status: | CLOSED ERRATA | QA Contact: | Chao Yang <chaoyang> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.2.0 | CC: | erich, jialiu, jokerman, mmasters, mmccomas, rthrashe, tiwillia |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
Feature: Allows for .gitconfig of gears to be configurable by an admin on the system, through the use of skeleton files.
Reason: This is needed to allow for an existing Git repository with a large amount of data to be more easily used in OpenShift. Without this change, some Git repositories could not be imported into OpenShift using --from-code, due to their size or memory consumption during the clone process.
Result: This enhancement allows for an administrator to use concepts in https://access.redhat.com/solutions/535653 configuration as defined by https://access.redhat.com/solutions/693593. It should be noted that when setting up a custom .gitconfig that:
1) The .gitconfig file can now be overwritten by a .gitconfig file provided in the user's git repository
2) The user-provided .gitconfig "should" contain the following options to ensure the Git repository can be cloned when the gear is close to its memory limits:
[gc]
auto=100
[pack]
windowMemory = 10m
packSizeLimit = 20m
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-22 16:51:15 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
Eric Rich
2015-09-22 22:00:45 UTC
Eric, to clarify, is it possible to use a custom .gitconfig under /etc/openshift/skel/ as described in the original description for this Bugzilla report, or does your change *only* enable the user or administrator to provide a custom .gitconfig by putting it in the Git repository specified by the user or configured by the administrator? We need to clone this Bugzilla report to track the required modifications to the documentation, but first I want to clarify that point. Thanks! Miciah, This change simply allows for an "administrator" to set a "default" for a gear using a skeleton file. If a default is not specified then the system will use the hard coded values. - in the case of the customer asking for this to be change the hard coded values were not what were needed to use "--from-code" to launch an application. QE, Please verify that a custom .gitconfig file, if provided, will be used instead of the default .gitconfig file. 1. Set up .gitconfig in /etc/openshift/USER with a custom .gitconfig. It should contain the [gc] and [pack] sections as outlined in comment #4. 2. The values from this custom .gitconfig should be used instead of the default .gitconfig. Puddle: http://etherpad.corp.redhat.com/puddle-2-2-2016-02-19 Thank you Verified this bug with OpenShiftEnterpriseErrata/2.2/2016-02-25.2 puddle, and PASS. # cat /etc/openshift/skel/.gitconfig [user] name = 111 [gc] auto = 100 [pack] windowMemory = 10m packSizeLimit = 20m Create an app, then log into it to check its gitconfig. [perlapp-jialiu.ose22-auto.com.cn jialiu-perlapp-1]\> cat .gitconfig [user] name = 111 [gc] auto = 100 [pack] windowMemory = 10m packSizeLimit = 20m User's customized .gitconfig take effect. 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. https://rhn.redhat.com/errata/RHSA-2016-0489.html |