use mesos DiscoveryInfo to cut down on the number of returned ports in mesos-dns

[spacejam]

Kubernetes-mesos is currently unable to use etcd-mesos, as the etcd proxy that will be local to the k8s components fails to parse the mesos-dns response if it is larger than 512 bytes (presumed 512, 768 failed but 112 worked). We need to cut down on the number of ports returned, which is currently 6 per etcd instance (udp, tcp * client, peer, and reseed listener).

[spacejam]

#71

[jdef]

#71 has merged, can this be closed?

[spacejam]

yes!