Bug 848275

Summary: Need update README file to add disable_auto_scaling comment
Product: OKD Reporter: Rony Gong 🔥 <qgong>
Component: ContainersAssignee: Ram Ranganathan <ramr>
Status: CLOSED DUPLICATE QA Contact: libra bugs <libra-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 2.xCC: mfisher, pmorie, ramr
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-14 18:18:31 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 Rony Gong 🔥 2012-08-15 06:09:10 UTC 
Description of problem:
Since bug https://bugzilla.redhat.com/show_bug.cgi?id=844089  is fixed
now we could disable auto scaling by:

create new file $APP_Dir/.openshift/markers/disable_auto_scaling

So need to add comment about disable_auto_scaling in  $APP_Dir/.openshift/marker/README

for all cartridges.

Version-Release number of selected component (if applicable):
devenv_1990

How reproducible:
always


Steps to Reproduce:
1.Create scalable app
2.Check  $APP_Dir/.openshift/marker/README
3.
  
Actual results:
no comment about disable_auto_scaling 


Expected results:
should have comment about disable_auto_scaling


Additional info:
Comment 1 Ram Ranganathan 2012-08-15 18:57:42 UTC 
This marker in the README doesn't make sense for "non-scalable" apps today. 
Since we use the same sample app repo [per app type] irrespective of scale -- adding it to the repos for each app type would not really work.

Maybe when the distinction between scale/non-scale goes away (and limits of min/max gears control scale [1-n] or non-scale [1-1]) we can add this in.

For now, IMHO it would be confusing to add it to each of the repo READMEs.
Comment 2 Paul Morie 2013-01-14 18:18:31 UTC 
This is a duplicate of issue 864797

*** This bug has been marked as a duplicate of bug 864797 ***