Refactor gec-pd to seperate builder and cleaner

Extracting out the code to versionize docs from mark-new-version and fixing a bunch of issues

Refector iscsi volume to seperate builder and cleaner

Dump stdin to a temporary file in kubectl replace --force

Use a service between e2e volume tests clients and servers.

Vagrant: Allow env override of IP addresses

Fix hits in help strings of kubectl get command

Allow specification of a network plugins directory when starting kubelet

Extract EtcdHelper interface

Ansible updates

Move sourcing of provider-specific util.sh into kube-util.sh

Remove v1beta3

add originator to reflector logging

[WIP]upgrade ubuntu bare-metal k8s to 1.0.1

Revert revert of #11379

Close resp.Body before returning error

rbd mount fencing

Print env vars in kubectl describe pod

pass along status errors for upgrades

Fix races in mesos scheduler plugin test

Default --ignore-not-found to true for delete --all

change shell var MINION_SCOPES to user setable

Signed-off-by: Huamin Chen <hchen@redhat.com>

Rolling updater configurability enhancements

Fix NewNotFound method name in comments

kubectl resource builder: don't check extension for single files

Fix up check for min memory for parallel builds

Update comments to remove etcd specificity and minion term

Creating a cluster from scratch takes about 7 minutes. But if you just
rebuild the binaries and want to update those you don't want to have to
rerun the entire thing. There is an ansible tag 'binary-update' which
will do that. Now one can do
```
ANSIBLE_TAGS=binary-update vagrant provision
```
And it will push the new binaries.

If you are using locally build binaries as a developer you likely will
want to just push those binaries to an existing cluster, not rerun the
entire playbook.  Add a tag to do just that.

Do the /etc/host creation with vagrant, so it uses internal instead of
external ips (hostmanager only knew about the public ip)

Ignore errors on docker failure when 'restarting' docker in flannel
handler. If this is a clean install, we haven't run 'node' yet so docker
isn't installed so it doesn't need to be started. It would be better to
be more specific in ignoring errors though...