2461001642

18 ms·

1.
by 2461001642 10y ago
a: mind blown b: isn't this a terrible UX? I mean, these features are GREAT but unless I randomly caught this comment in an HN thread, I would never have known about them. And when I option-click an icon, I have no idea what's goi
2.
by 2461001642 10y ago
This is an excellent point - kind of goes against my earlier comment. Maybe they have to move this way because that's their only choice - if they don't move into automating this, containers will disrupt them (or already has)
3.
by 2461001642 10y ago
I love the Chef ppl, but... Is it just me or are there a ton of other folks doing this? The idea of introducing yet another layer of stuff is scary, and there's lots of work left to do on Chef. In a lot of ways, they feel just like Nom
4.
by 2461001642 11y ago
When I'm balancing a single deployment across multiple AZs (e.g. US-East -> US-West), the latencies between the containers seem far higher than just the 200-300ms predicted by speed of light. Am I doing something wrong?
5.
by 2461001642 11y ago
Thanks again - this is really helpful. I had talked to someone who had left Amazon but knew the internal workings who said ECS was Mesos just privately branded like Chef -> OpsWorks, but I guess I must have misunderstood. Thanks for clar
6.
by 2461001642 11y ago
Thanks for responding! Can you say how you deal with the significant latencies over multiple AZs? Also, would you mind answering my other question about whether or not I can run Marathon or Chronos against ECS since it runs Mesos under the
7.
by 2461001642 11y ago
I've heard that it just runs Mesos under the hood, how does this differ than me running Mesos on my own? Can I run Chronos or Marathon against it?