Fixes #1334

Fix docker restart in atomic

Adding flag for docker container in kubelet w/ rkt

Support provisioning vagrant k8s clusters with coreos

check if cloud_provider is defined

Adds note on versionlock to README

Resolve upgrade issues

add direct path for cert in AWS with RHEL family

Note to users that auto-updates break clusters that don't lock the docker version somehow.

add scale.yml to do minimum needed for a node bootstrap

adding --skip-exists flag for peer_with_router

Added dynamic inventory for AWS as contrib

upgrade k8s version to 1.6.4

Add host-based kubelet deployment

With live-restore: true, we don't need a special docker restart

Previous patch removed the step that sets live-restore
back to false, so don't try to notify that handler any more

Kubelet gets copied from hyperkube container and run locally.

Minor kubelet updates

Leave live-restore false to updates always pick
up new network configuration

Before restarting docker, instruct it to kill running
containers when it restarts.

Needs a second docker restart after we restore the original
behavior, otherwise the next time docker is restarted by
an operator, it will unexpectedly bring down all running
containers.

In atomic, containers are left running when docker is restarted.
When docker is restarted after the flannel config is put in place,
the docker0 interface isn't re-IPed because docker sees the running
containers and won't update the previous config.

This patch kills all the running containers after docker is stopped.
We can't simply `docker stop` the running containers, as they respawn
before we've got a chance to stop the docker daemon, so we need to
use runc to do this after dockerd is stopped.

issue raw yum command since we don't have facts in bootstrapping

Fixed nova command to get available flavors