From 0b2120c65f9fabf12150be0d58a8d4050df33c70 Mon Sep 17 00:00:00 2001 From: Adam Miller Date: Oct 20 2016 22:11:15 +0000 Subject: add initial README with some information as to why we're doing this Signed-off-by: Adam Miller --- diff --git a/README.md b/README.md deleted file mode 100644 index c953eb2..0000000 --- a/README.md +++ /dev/null @@ -1,3 +0,0 @@ -# ansible-ansible-openshift-ansible - -Ansible playbooks to run ansible on a remote "openshift control" what will run openshift-ansible to deploy a cluster \ No newline at end of file diff --git a/README.rst b/README.rst new file mode 100644 index 0000000..8ce7217 --- /dev/null +++ b/README.rst @@ -0,0 +1,43 @@ +ansible-ansible-openshift-ansible +################################# + +Ansible playbooks to run ansible on a remote "openshift control" what will run +`openshift-ansible`_ to deploy a cluster. + +What? Why? +---------- + +The `openshift-ansible`_ playbooks require that various tasks be run on +``localhost`` in order to build their internal abstracted representation of the +inventory list. Running potentially arbitrary code from external sources on a +bastion host (which is what ``localhost`` would be as the ansible control +machine) is often frowned upon. The goal here is to allow for the deployment of +`openshift-ansible`_ via an intermediate host. + + +:: + + +---------------+ +-------------------+ + | | | | + | bastion host +----[ansible]----->| openshift control | + | | | | + +---------------+ +---------+---------+ + | + | + [ansible] + | + | + V + +--------------------------------------------------------------------------+ + | | + | openshift cluster | + | | + | +-----------+ +-----------+ +-----------+ | + | | | | | | | | + | | openshift | ...[masters] | openshift | | openshift | ...[nodes] | + | | master | | node | | node | | + | | | | | | | | + | +-----------+ +-----------+ +-----------+ | + | | + +--------------------------------------------------------------------------+ +