fidget

As if this can't happen on physical machines also.

Oh, I'm aware I can read it. I'm just not convinced about sharing it on such a broad public forum.

> LWN subscriber-only content

kinda shitty

Given how, you know, polio is still a thing, it seems to be the whole distribution area that we're struggling the most with, and less the raw scientific aspects.

Seems fairly obvious that market making would become almost full automated eventually

Didn't realise this was an editorial

The Litvinenko death occurred prior to the Russian Georgian war, prior to Obama's grand reset, prior to the failure of that reset, prior to the Crimean crisis, in essence, prior to the current political situation. And there has never been any real doubt that it was orchestrated by the KGB, with (at the very least) the knowledge of Putin.

It's redshift, based on the contents of previous blogs.

Github kills Bitbucket with this one feature: uptime

Nice to finally see it in writing: "Throughout this investigation Docker has made it clear that they’re not very open to ideas that deviate from their current course or that delegate control"

    Takeaways:
    Don't store strong chemicals in your bedroom

Some of these seem the wrong side of irresponsible

For those of us more dictionary oriented, there is https://pypi.python.org/pypi/voluptuous (which is OK for the most part, as long as you are only trying to do validation, and nothing too crazy)

Sure. I'm still paying it once per box lifetime, which really isn't too bad. And given I'm orchestrating stuff etc etc, I can use fairly large boxes and get quite a lot of work out of one lifetime.

Except, well, I don't care. All my images derive from ubuntu, so I pay the download cost once, due to docker having this whole delta thing going on, and storage cost really isn't a problem. Developers know how to apt-get usually, so that's less support cost on me. In fact, most of them run ubuntu themselves, which is a massive help with dev to prod parity. Oh and of course, there are more packages and a whole lot more forums/community etc etc.

A lot of the GP's concerns are around libraries breaking compatability, and upgrading deps being hard, but Go doesn't exactly have all the answers in that regard.

It wouldn't be particuarly hard for avast to operate this system without having the key for the CA leaving your machine.

Which would be `$0.067 * 32 * 24 * 30 = $1543.68` on demand

Probably worth noting that seccomp bpf programs are pretty far from turing complete.

Though they are a bit complex.

Seems a bit childish

We had a cluster last week spend 7 hours in a DB health 'unknown' state. Response from AWS? Spin up a new cluster from snapshot.

I use it post reload to persist the state of health checks, which I thought was pretty cool. However, I don't believe you can add a (new) server to a backend via the stats socket.

Unfortunately consul integration isn't useful for us.

That's egress traffic :) And yeah, https://github.com/QubitProducts/bamboo/issues/143#issuecomm... is currently my best idea (with some additional nfq stuff). Doesn't help when requests span the entirety of the reload though.

I'm moving away from HAProxy. The lack of zero downtime config reloads is consistently causing problems, especially in a high reload environment (i.e. using bamboo [0]). One team deploys an application that goes into a restart loop, changing our routing table constantly? Well there goes our 99th percentile out the window.

That said, would prefer not to be using nginx, so if anyone has any recommendations for high quality zero-downtime-reloadable HTTP proxies, I'd be very interested.

[0]: https://github.com/QubitProducts/bamboo

I wonder what those numbers would look like if you included private companies

Christ the amount of native advertising in these threads is getting annoying

It's also not uncommon to tell your employees they don't need to come in to work during that last month.

The ones _it_ has requested.

No solution for persistent/statefull applications, which is a real disapointment, seeing as this is where I see orchestration systems currently breaking new ground and coming up with interesting solutions. The contraint systems also doesn't look too impressive; can I do the equiq of Marathon's GROUP_BY contraint (i.e. AZ GROUP_BY 2 -> ensure I have instances running on >=2 machines w/ different AZ values)?

Also no maintenance primitives, but that's just me being in love with Mesos.

Is there any reason that IPv6 in the UK seems Manchester based, while IPv4 is London based?