thockin

The name was a collaborative effort. We suck at names :)

And yeah, it's been retooled a lot to extract it more cleanly from the surrounding code.

p.s. Hello menage! Nice to see you commenting here :)

What menage said is true. As it came time to clean up what we were using internally it became a decision of adapting the code and semantics we already have to be cleaner, or starting anew with something like LXC (which does more than we need in some ways and less in others).

We have a lot of really well tested and battle-hardened code and behavior, so we chose to keep that.

lmctfy is designed from the ground up as automation which can be used by humans, and never the other way around.

FWIW, we have a lot of these things done internally, but not in a releasable form yet.

This is more true than the idea that there's a competitive advantage. We would love to open-source more of our stack (and are working towards it), but it's all very tied to the rest of our cluster environment. Piece by piece.

Namespaces will be coming, but we're not there yet. This captures some of what we are already doing internally, but not all of it, yet.