Add util to validate namespaced names

Fix e2e.

Improve error reporting

Follow-up of changes introduced in commit 72c92266

Don't assume every AWS VPC has tags

Default ENABLE_CLUSTER_MONITORING to false

Add --pushup to e2e.go

Silly but hopefully memorable name for an option to --push OR --up
depending on cluster state.

Kubelet directory-name builder funcs

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.

Query hostIP for Nodes

Make multivalued requirement parser more whitespace tolerant

Check if cluster is up before e2e test without -up

Wait/reap build container before removing it

Fix e2e-suite/certs.sh unbound variables

Fixes e2e failure on GCE

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.

Fixes: https://github.com/GoogleCloudPlatform/kubernetes/issues/1853

Gets rid of some magic constants and makes volume plugins (coming later)
cleaner.

make selfLink namespace aware

Fix detect-minions.

Fix the update test.

Make certs.sh executable.

Add script to build ui assets, rebuild with latest go-bindata

Print SyncCloud errors

Log ErrUnexpectedEOF from watches as warnings

avoid panics when docker CT has no name

Added a New test case for GetMinion

reenable update test

Watches are often established via long-running HTTP GET requests which
will inevitably time out during the normal course of operations. When
the watches time out, an io.EOF or an io.ErrUnexpectedEOF will bubble
up to client components such as StreamWatcher and Reflector. Treat EOF
as a clean watch termination. Treat ErrUnexpectedEOF as a less-clean
but non-fatal watch termination and log the event at the warning level.

This greatly reduces the amount of log noise generated during what is
ultimately normal operation, and adds the flexibility for the operator
to make a distinction between the EOF conditions if so desired (by
adjusting the logging level).