WIP: simple configuration & metaconfiguration tool

[justinsb]

@mikedanese here is an example of a much simpler way to specify configuration. We have a simple go installer program, that walks a directory tree, and interprets that as task (ala Salt or Ansible). We have tasks that are a little smarter / more specialized for our use case than Salt or Ansible, such that most of the complexity here goes away.

So here we have a zero-dependency installer, with a very readable (IMO) installation specification. There are obviously still issues to resolve, e.g. the generation of options is funky, but I think we could use jsonnet for that.

The nice thing here is that this "filesystem tree as specification" is simple enough that it would be trivial to transform this into salt, ansible, or whatever people want.

But, at the same time, by having a simple golang tool that works without external dependencies we can package this however we want - in a container, running directly on the host, running over SSH/SFTP etc.

[justinsb]

Oh, and the included template is a translation of the salt configuration, except that I assumed we were using systemd, and that we were using default networking. Probably some other code paths I ripped out for sanity also.

I think only supporting systemd with kube-up v2 would be a great simplification, and would not really cost us anything given that everyone has gone systemd and docker needs a fairly modern kernel anyway.

[mikedanese]

extra ticks unneeded?

[justinsb]

Closing this - this became upup!