Dynamic profile provider

[grobie]

Once the dust has settled around #180 and we have a good feeling for dashboard templates with different profiles (incarnations might be a fun word for them, too), the next logical step is of course to provide profiles in a dynamic way. This will allow for a wide range of use cases, for example:

• node templates (node profile list from collins, chef, puppet, etc.)
• docker templates (profile list from docker)
• service templates (service profiles retrieved via service discovery like consul, etcd, ...)
• SoundCloud's bazooka container environment, etc.

The profiles of the first iteration will be the static profiles. In the end we'll end up with something like profile providers. Could be ruby or javascript libraries to include, or also an HTTP interface or unix pipe.

[grobie]

One of the first dynamic providers to implement should actually be a prometheus provider. For example to provide all available values for label key, e.g. node or instance.