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.
Great to see some of this code finally making it out into the world, although it seems to have changed a bit over the last few years. (I still recognize a few low-level functions.)
Comments
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.
p.s. Hello menage! Nice to see you commenting here :)
Great to see some of this code finally making it out into the world, although it seems to have changed a bit over the last few years. (I still recognize a few low-level functions.)
Who came up with the name?
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.