multivalued requirement parser more whitespace tolerant
Don't assume every AWS VPC has tags

The default VPC has no tags (by default), so we should use get()
Default ENABLE_CLUSTER_MONITORING to false

Otherwise kube-down fails because the variable is not defined
Use apiserver instead of etcd for kube-proxy.

For cloud-providers that use salt, have kube-proxy use
apiserver instead of etcd as a config source.
Implement apiserver communication for Vagrant

This implementation is based on the GCE impementation from
618a367dbb48dbaa9c3b50e877858d854322fd0b.
Query hostIP for instances
- make cadvisor port configurable on the kubelet.
- added cadvisor port documentation.
Add functions to get kubelet directories.

Gets rid of some magic constants and makes volume plugins (coming later)
cleaner.
Wait/reap build container before removing it

Fixes: https://github.com/GoogleCloudPlatform/kubernetes/issues/1853
Check if cluster is up before e2e test without -up

Minor usability nuisance: If you run:
  go run hack/e2e.go -v -test
.. and you don't happen to have an up e2e cluster, it should fail
fast, rather than chugging through every test and having them fall
over.
Fix e2e-suite/certs.sh unbound variables

Fixes e2e failure on GCE
Added two test cases for KubeletClient
Add python-cherrypy as explicit install for salt-api
Merge pull request #2785 from zmerlynn/certs

Fix e2e-suite/certs.sh unbound variables
Merge pull request #2780 from zmerlynn/issue.1853

Wait/reap build container before removing it
Merge pull request #2783 from zmerlynn/IsUp

Check if cluster is up before e2e test without -up
Update roadmap based on discussion at contributor meetup.
Merge pull request #2559 from meirf/add-whitespace-flexibility-to-multivalued-requirement-parser

Make multivalued requirement parser more whitespace tolerant
Merge pull request #2777 from ddysher/node-ip

Query hostIP for Nodes
Run e2e tests in deterministic random order

Currently, we run the e2e tests in whatever order readdir happens to
return, which is random on some filesystems, name sorted on others,
create order on others, etc. Eventually, we may want to be
automatically hermetic between e2e tests (especially as we introduce
more resource destructive tests), but until then, it would be useful
if we permute the test order randomly between runs to ensure that
developers don't accidentally rely on a particular order. This
introduces a form of forced hermeticism, since improper state cleanup
from one test may not perturb a given test, but there's probably *a*
test in the suite that the order will perturb, so the RNG will find
that order eventually.

Adds logging of the generated seed, and an --orderseed argument that
can be used to re-run in the same order. Also sorts the pass/fail list
now for easier human reading.