any eta on getting more dedis? Wasn't the ETA yesterday? :P up_the_irons? toeshred? they are no longer on hold as far as i know. but i would still check with up_the_irons to confirm. Thanks toeshred :) I figured the guy to [probably] rack them would know ;) rackin n stakin! pepwepwpp yeah the sold out sign is no longer there qbit: ^ oh sweet i was waiting for a button to show up ?:D s/?// question for you guys. I'm giving a presentation on HAProxy to a local group in october. I kinda want to have a little bit in there for everyone, basic to advanced. the time slot is flecible between 45 - 90 minutes. what kinds of things would YOU guys be interesting in knowing? for basic stuff, I was planning on going over stats, load balancing, how it does "HA" and health checks for backend servers. for more advanced, I'd like to cover throttling, DDoS, network/latency diagnostics, load balancing things like mysql, redis, postgres, openvpn, etc. eliminating haproxy as a spof.. those kinds of things.. oh, ssl termination, and http vs tcp mode. that'll be towards the end of the beginner part. along with the different (and most common) LB algorithms. what about intermittent problems, fault-finding caveats etc. usually the simple getting things to work stuff is more obvious well, the biggest troubleshooting section was going to be on network issues/latency, and how to use haproxy to determine where the fault it. is that what you were thinking, or something else? well haproxy is going to multiple servers, right? so servers could be hitting issues that the other server isn't hit in theory, yes with pages half-loading sometimes etc. certainly aand health checks might not notice such properly. so knowing where a problem lays.. well, the part about health checks, I'm actually going to cover "full stack" checks. i assume it adds something to the headers saying what server it hit it does, in the logs i haven't used haproxy. i like the idea of ssl termination with distant locations though preferably with spdy/http2 so yeah, sounds like you'de be interested in the health checks portion. that is where I'm intending to mention.. you COULD just have it check if a port is open and responding. or.. lets say in a lamp environment, you write a small php script to query a DB, and return a result. if the result isn't what you expect, the chack fails and the server is removed from the pool yeah i prefer the php script to query db is there some kind of failover server too? for the advanced stuff, would you be at all interested in SSL/TLS stuff, like.. SHA1/SHA2 certs, wildcards, various ciphersuites? etc so if web site has too many problems in general can point to down for maintenance page temporarily and alert. multi-site ssl cuz part of me wants to cover that, and part of me thinks it's outside the scope of an haproxy talk. to just mention at high level that haproxy can handle the SSL termination, alloiwing you to manage it on a small number of frontends, instead of the dozens or hundreds of backends that you have yaeh i think it's outside of scope to go into detail can it do multisite ssl? ooh, yes. I should absolutely cover a way to let users know all backends are down or something, and how to fail over to backup servers, or return an "under maintenance" page. good call. yes, multisite SSL can it do name-only multisite ssl? or do they need extra ip's? it does SNI cool. i thikn generally for talks for me it's about seeing what's possible not about how to implement/do things. so for me i see it was a way to get a nice overview and get me thinking of other ways of doing things. yeah, I think for the basic part, I'll do a demonstration showing the very basics. for the advanced stuff, I'll turn off the slides and just talk. let them know what the possibilities ARE, rather than how to specifically do them. and when people go into details too much from questions, or during their talk i kidn of tune out, UNLESS it's something of biting significance say like BGP route limits. i wonder if you should also mention otehr solutions and what made you pick haproxy over them hehe that is almost always how I start a presentation ;) cool "this isn't the only tool, and I'm certainly not saying it's the best tool. However it's the tool I chose, for my use-case, and here are a few reasons why" yip yeah i've never seen any of your talks so i don't have anything to go on :) (in this, haproxy won out over using nginx or apache, for 2 primary reasons. #1) TCP mode, and #2) sheer performance. i like trafficserver myself no worries, I appreciate the suggestions regarldess :) it can do http2 termination now too :) I used trafficserver years ago, haven't touched it in a while brb, I need to feed some horses. thanks for the input. all good. http://blogs.windows.com/buildingapps/2015/08/06/windows-bridge-for-ios-lets-open-this-up/