Is it plan to support backend configuration with stats socket ?
2016-04-13 16:09 GMT+02:00 Smain Kahlouch :
> Ok thank you,
> I'll have a look to SmartStack.
>
> 2016-04-13 16:03 GMT+02:00 B. Heath Robinson :
>
>> SmartStack was mentioned earlier in
Ok thank you,
I'll have a look to SmartStack.
2016-04-13 16:03 GMT+02:00 B. Heath Robinson :
> SmartStack was mentioned earlier in the thread. It does a VERY good job
> of doing this. It rewrites the haproxy configuration and performs a reload
> based on changes in a
SmartStack was mentioned earlier in the thread. It does a VERY good job of
doing this. It rewrites the haproxy configuration and performs a reload
based on changes in a source database by a polling service on each
instance. The canonical DB is zookeeper.
We have been using this in production
Sorry to answer to this thread so late :p
due to the fact that this will be changed when the pod is recreated!
>
Alexis, as i mentionned earlier the idea is to detect these changes by
polling in a regular basis the API and change the backend configuration
automatically.
Using the DNS (addon) is
Hi.
Am 25-02-2016 16:15, schrieb Smain Kahlouch:
Hi !
Sorry to bother you again with this question, but still i think it
would
be a great feature to loadbalance directly to pods from haproxy :)
Is there any news on the roadmap about that ?
How about DNS as mentioned below?
Hi !
Sorry to bother you again with this question, but still i think it would be
a great feature to loadbalance directly to pods from haproxy :)
Is there any news on the roadmap about that ?
Regards,
Smana
2015-09-22 20:21 GMT+02:00 Joseph Lynch :
> Disclaimer: I help
Disclaimer: I help maintain SmartStack and this is a shameless plug
You can also achieve a fast and reliable dynamic backend system by
using something off the shelf like airbnb/Yelp SmartStack
(http://nerds.airbnb.com/smartstack-service-discovery-cloud/).
Basically there is nerve that runs on
On Fri, Sep 18, 2015 at 10:49 AM, Smain Kahlouch wrote:
> Hello all,
>
> I guess this question has been posted many times but maybe there is some new
> way to achieve this.
>
> I'm currently testing kubernetes with calico and i configured a fixed
> loadbalancing using
Hi Baptiste,
How do you do ? :)
Anyway my concern is more about changing dynamically parameters, by
fetching a source at regular intervals (api) than about kubernetes itself.
Actually, i only have one need currently : the list of servers part of a
backend.
This is the only thing i want to
> How do you do ? :)
I do :)
> Anyway my concern is more about changing dynamically parameters, by fetching
> a source at regular intervals (api) than about kubernetes itself.
Ok, this is important to know :)
> Actually, i only have one need currently : the list of servers part of a
>
If I may chime in here: Kubernetes supports service discovery through DNS
SRV records for most use-cases, so the dynamic DNS support that Baptiste is
currently working on would be a perfect fit. No special API support required.
Cheers,
Conrad
On 09/18/2015 01:53 PM, Smain Kahlouch wrote:
> Hi
>
> euh, I'm lost here, could you details who does what exactly???
I configure the backends given the underlying configured services (running
on kubernetes).
So at startup, i already have a list of servers for each backend.
Then this list can change as the number of instances can be scaled
>
> If I may chime in here: Kubernetes supports service discovery through DNS
> SRV records for most use-cases, so the dynamic DNS support that Baptiste is
> currently working on would be a perfect fit. No special API support
> required.
Well dns would be great but, as far as i know, kubernetes
On Fri, Sep 18, 2015 at 3:12 PM, Smain Kahlouch wrote:
>> euh, I'm lost here, could you details who does what exactly???
>
>
> I configure the backends given the underlying configured services (running
> on kubernetes).
> So at startup, i already have a list of servers for
On Fri, Sep 18, 2015 at 3:18 PM, Smain Kahlouch wrote:
>> If I may chime in here: Kubernetes supports service discovery through DNS
>> SRV records for most use-cases, so the dynamic DNS support that Baptiste
>> is
>> currently working on would be a perfect fit. No special API
I have implemented something similar to allow use to dynamically
load-balance between multiple backends that are all joined to each other as
part of a Hazelcast cluster. All of which is running in an AWS VPC, with
autoscaling groups to control spin up and down of new members of the
cluster based
16 matches
Mail list logo