Hold serve_hostname code in kubernetes repo
multivalued requirement parser more whitespace tolerant
Update gophercloud dependency to v1.0.0
Update openstack provider to gophercloud v1.0 API
Implement TCPLoadBalancer OpenStack cloud provider

Also add a trivial implementation of Zones() too.

This only supports a single region/zone currently (the region where
kubernetes is running).
Add additional logging to openstack cloud provider

Turned out to be invaluable while debugging issues - I expect it will be
for others too.

Conflicts:
	pkg/cloudprovider/openstack/openstack.go
fix(aws): error with other instances without tags

while starting the cluster, and having already other non-kubernetes
instances active without tags, an KeyError throwed.
enhancement(aws): checks for existing kubernetes vpc first

without this check, kube-up creates a new vpc every time. Now it will
reuse the vpc tagged Kubernetes.
Update README.md

Fix incorrect  pod spec
enhancement(aws): using iam role to pass aws credentials
enhancement(aws): added logging variable and more verbose output
fix(aws): fix with non us standard region
fix(aws): cloud provider wasn't set, corrected cloud config syntax
Don't assume every AWS VPC has tags

The default VPC has no tags (by default), so we should use get()
Specify AWS_DEFAULT_REGION to match configured region

The AWS CLI is configured with a default region, but it might not match
the configured Kubernetes region.  Specify the region to be sure.
Default ENABLE_CLUSTER_MONITORING to false

Otherwise kube-down fails because the variable is not defined
Add a util.Forever variant that ends on a stop channel
No need to add two "containers" section for one pod

Fix issue #2664
Fixes #2681: update to cadvisor 0.6.2
Make credentialprovider less verbose about benign errors.

In particular, a few of the utilities used within the credentialprovider had the pattern:
   glog.Errorf("while blah %s: %v", s, err)
   return nil, err

This change propagates those error message and puts the burden of logging on the caller.

In particular, this allows us to squelch all output during kubelet startup when we are detecting whether certain credentialprovider plugins should even be enabled.

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