Thanks Brenton sharing overview page to see what are upcoming features or changes. Very handy ..
-- Srinivas Kotaru On 1/15/16, 1:49 PM, "Brenton Leanhardt" <blean...@redhat.com> wrote: >On Fri, Jan 15, 2016 at 3:53 PM, Srinivas Naga Kotaru (skotaru) ><skot...@cisco.com> wrote: >> Thanks Brenton. It is clear now. When this feature will be released? 3.2? > >That card has the 'committed-3.3' label in trello so that's really the >best guidance I can give. > >In general https://ci.openshift.redhat.com/releases_overview.html is a >great place to see how cards across all the various trello boards map >to releases. > >> >> >> -- >> Srinivas Kotaru >> >> >> >> >> >> >> On 1/15/16, 12:30 PM, "Brenton Leanhardt" <blean...@redhat.com> wrote: >> >>>On Fri, Jan 15, 2016 at 12:47 PM, Srinivas Naga Kotaru (skotaru) >>><skot...@cisco.com> wrote: >>>> >>>> Brenton said you guys are working on router sharding >>>> >>>> https://trello.com/c/DtPlixdb/49-8-router-sharding-traffic-ingress >>>> >>>> I didn’t get quite well description. What is this feature, how it is >>>> useful, >>>> what are the use cases and when it will be released? >>> >>>One use case would be for large scale deployments it's not practical >>>to have hundreds of thousands of routes loaded in a single haproxy >>>instance. Sharding allows the problem to be carved up in to smaller >>>pieces. >>> >>>Other use case would simply be to have routing images that are tuned >>>for specific workloads. If I create a custom router image that is >>>only useful for a certain class of applications this feature would >>>allow the router to only listen to the correct subset. >>> >>>> >>>> Can we create separate routers for internal or external apps, or more >>>> control on grouping routes by labels or node selector ( region or zone) ? >>> >>>My understanding is that this would all be possible. >>> >>>> >>>> -- >>>> Srinivas Kotaru _______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
