[WIP][DO NOT MERGE] Proposal: Auto-scaling

Auto-scaling is a feature that allows users to increase capacity as needed by controlling the number of replicas deployed within the system based on request statistics. Auto-scaling is bidirectional, it will scale up to a specified limit as requests increase and scale down to minimal capacity as the requests decrease.

https://github.com/pweil-/origin/blob/035e0351a838a6ec6dcd65cc1977c85fca98ae5f/docs/autoscaling.md



Gathering qps and other stats may take many forms.  We'll use Kube proxy as inter service connection, and it may have optional features that we add at a later point.


> On Dec 8, 2014, at 5:13 PM, Paul <notifications@github.com> wrote:
> 
> In docs/autoscaling.md:
> 
> > +
> > +[example from Rajat using socat](https://github.com/rajatchopra/geard-router-haproxy/blob/rc/autoscaler.rb)
> > +
> > +#### NGINX Implementation
> > +TODO
> > +
> > +#### Apache Implementation
> > +TODO
> > +mod_status http://httpd.apache.org/docs/2.2/mod/mod_status.html, http://www.tecmint.com/monitor-apache-web-server-load-and-page-statistics/, http://freecode.com/projects/apachetop/, http://www.opennms.org/wiki/Monitoring_Apache_with_the_HTTP_collector
> > +
> > +#### Kube Proxy Implementation
> > +
> > +TODO (will need to make stats implementation for proxy and register it as a non-replication controller controller
> > +piece of infa - ie. do not try and manage these routers)
> > +
> > +The intention is to have the OpenShift router be able to run in a mode that will allow it to replace the Kube Proxy in 
> The line about replacing the proxy with a router was pulled from another PR that I can't seem to find so I guess we can scratch it. That said, it seems to make sense that if we end up moving routers upstream that we could use a base impl for the proxy to allow us to gather stats.
> 
> —
> Reply to this email directly or view it on GitHub.
>