[DannoHung]

Your assessment is accurate, unfortunately Triton does not address the issue of data locality, which is a pretty big problem unless you're already building your storage backend to be Smart Data Center aware.

To that extent, I'm not sure that tossing out the idea of hosts is great yet.

[pbowyer]

> Triton does not address the issue of data locality, which is a pretty big problem unless you're already building your storage backend to be Smart Data Center aware.

Can you expand on this please? I was not aware of the problem.

[DannoHung]

To put it as simply as possible: Triton does not have magic block storage. If you want to write anything that persists past a container's lifetime, it is tied to the machine instance the container was running on unless you manually move it around.

It's not any worse than you'd have if you were starting from scratch with your own hardware, but Bryan Cantrill is firmly against magic block storage. His suggestion is that you rewrite your persistence layer to know about SDC or "deal with it".

It's not necessarily that bad since a lot of containers don't need state, but my personal axe is that I work with databases almost exclusively.