Haproxy 2.2
haproxy.com
Haproxy 2.2
1–10 of 61 posts
Re: Haproxy 2.2
#2Here is the announcement blogpost https://www.haproxy.com/blog/announcing-haproxy-2-2/
Re: Haproxy 2.2
#3Finally full SSL certs management at runtime through the API is here! No need to restart Haproxy anymore to add or update a cert! Brilliant, thanks!
Re: Haproxy 2.2
#4Haproxy is such a nice piece of software, sensible configuration, very stable and versatile. And, one thing that is highly appreciated, I've never seen it do something I wasn't expecting it to. This quality of minimal surprises in its operation isn't going unnoticed by any measure.
Re: Haproxy 2.2
#5Haproxy isn’t quite as fast as iptables (we switched because of this) but it was delightful to configure. The tradeoff is definitely worth it in most cases.
Re: Haproxy 2.2
#6Haproxy isn’t quite as fast as iptables (we switched because of this) but it was delightful to configure. The tradeoff is definitely worth it in most cases.
Just curious, what were you doing where you needed the performance of iptables over haproxy?
Re: Haproxy 2.2
#7Finally full SSL certs management at runtime through the API is here! No need to restart Haproxy anymore to add or update a cert! Brilliant, thanks!
FWIW the ability to send a SIGUSR2 to reload certs has been there for awhile.
Re: Haproxy 2.2
#8Haproxy isn’t quite as fast as iptables (we switched because of this) but it was delightful to configure. The tradeoff is definitely worth it in most cases.
Just curious, what were you doing where you needed the performance of iptables over haproxy?
We forward a cluster of 2,560 TPU pod cores from our GCE project to other GCE projects in europe-west4-a. Originally it was because we had a separate GCE project with a bunch of credits, but that project had no access to TPUs. The question was, could we still take advantage of the credits? It turns out, we could; the solution involved VPC Network Peering, which I later learned is how the TPUs themselves work. Some configuration details are here: https://www.shawwn.com/swarm#iptables
Nowadays we forward the TPU pods to pretty much anyone who wants to try them out, in hopes of getting more people involved in the TPU programming scene. The TPUs are managed via a website (https://www.tensorfork.com/tpus) and we coordinate TPU access via spreadsheet. Each researcher has their own GCE project, and we simply flip a switch to give them access.
If anyone reading this happens to be into ML and into programming for big hardware rigs, feel free to hop into the Tensorfork discord server and we can show you the ropes. https://github.com/shawwn/tpunicorn#ml-community
Re: Haproxy 2.2
#9Haproxy is such a nice piece of software, sensible configuration, very stable and versatile. And, one thing that is highly appreciated, I've never seen it do something I wasn't expecting it to. This quality of minimal surprises in its operation isn't going unnoticed by any measure.
Has it solved the reloading problem yet?
Re: Haproxy 2.2
#10It's amazing how much better the .org site is over the .com.