Break out a separate file for the control role.

AKA cluster services.
Bump AMIs to latest CoreOS alpha release.
Schedule zookeeper.presence whereever zookeeper.data is.
Restart Zookeeper when it dies.

It’s supposed to be fail-fast and self-healing, so
hopefully there are some things it can successfully
recover from.
Annotate the design principle for DNS registrations.
Remove unused ‘skydns’ service user from CoreOS host.
Target an explicit version of SkyDNS.
Parameterize logspout container tag. First step to pegged.
Parameterize syslog_gollector container tag.
Set logspout container hostname to cluster hostname.
Declare that data units want to start after logspout.
Switch kafka topic from ’syslog’ to ’logspout’.
Daydream in Zookeeper config.
Trust the round-robin DNS.
Be noisier about data volume startup (for logspout).
Rename influxdb.db_create -> influxdb.create_db.

What can I say? I like it better. Also, Kafka is
already set up that way (kafka.create_topics).
Only reference host within one “canonical” registration.

Let recursive lookups do their thing.
Start ElasticSearch presence after the service.
Target an explicit cadvisor version (latest -> 0.6.2).
Downgrade dependencies across the board (Requires->Wants).