[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Draft 1 of PEP005 - Highly available web applications - is available for review



----- Original Message -----
> From: "Clayton Coleman" <ccoleman redhat com>
> To: "Thomas Wiest" <twiest redhat com>
> Cc: dev lists openshift redhat com
> Sent: Thursday, July 4, 2013 12:28:49 PM
> Subject: Re: Draft 1 of PEP005 - Highly available web applications - is	available for review
> 
> Depends, but I would say it might be better to put that intelligence in the
> component that handles app create events.  However, there's nothing
> preventing the plugin receiving the routing spi events from making a
> decision and recording it in the brokers mongo.
> 
> Arguably you need to make the sharding decision based on the current volume
> of traffic flowing through that router.  For instance, a router that is
> servicing a high volume app (50+ gears, 1k req/sec) might not be the best
> place to colocate another high volume app - it may be an operational
> responsibility to periodically rebalance proxies manually or via scripts.
> 
> The assumption is that the routers must scale to handle the highest possible
> individual volume app deployed in Openshift - well tuned proxies should be
> able to handle hundreds of thousands of requests a second, but the placement
> of a high volume app is going to be an important decision.
> 
> This part of the pep is a bit vague - mike was planning on flushing out the
> details of that more.
> 

Multi-geo support should help here too for the widely distributed applications.

   -Mike

> On Jul 4, 2013, at 1:15 PM, Thomas Wiest <twiest redhat com> wrote:
> 
> > Very interesting PEP.
> > 
> > In the PEP, you say that the proxy layer would likely be sharded in some
> > fashion for large deploys.
> > 
> > Is the sharding something that the broker will manage?
> > 
> > Thomas
> > 
> > 
> > On 07/03/2013 07:59 PM, Clayton Coleman wrote:
> >> As part of the long term evolution of the OpenShift platform, we intend to
> >> introduce support for highly available web applications.  A PEP has been
> >> drafted in the public repository to describe some of the design
> >> considerations and general intent:
> >> 
> >>   https://github.com/openshift/openshift-pep/blob/master/openshift-pep-005.md
> >> 
> >> This is an early draft, and there are topics that are deliberately
> >> considered out of scope of the document at the current time, or are
> >> insufficiently specified.  If you have questions, comments, or feedback,
> >> please reply to this thread.
> >> 
> >> Thanks!
> >> 
> >> _______________________________________________
> >> dev mailing list
> >> dev lists openshift redhat com
> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> > 
> 
> _______________________________________________
> dev mailing list
> dev lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]