Changeset 13843 for main/waeup-ansible

Timestamp:

20 Apr 2016, 14:13:07 (8 years ago)

Author:

uli

Message:

Tell about what we learned.

File:

• main/waeup-ansible/README.rst (modified) (2 diffs)

main/waeup-ansible/README.rst

@@ -105 +105 @@
 daemon and then add important accounts: "uli", "henrik", "ansible".
 
+To make sure, the connection to a "freshmech" works, you should at
+least one time login via SSH before proceeding with ansible and all
+bells and whistles::
+
+  ssh -l root 192.168.36.10
+
+(with the real IP of the machine you want to reach, of course).
+
 Any host you want to "bootstrap" must be entered in a local hosts
 file, normally ``hosts-virtual``, with a line like this:
@@ -120 +128 @@
 the provider on the commandline. For the local `vagrant` machines this
 will be `vagrant`.
+
+If run on local virtual machines, you might want to make sure that
+your local `known_hosts` file does not contain an old ssh host
+fingerprint. Otherwise you have to remove entries for::
+
+  192.168.36.10
+  192.168.36.11
+  192.168.36.12
+
+respectively before running `bootstrap.yml`.
+
+Alternatively you can run everything with the
+`ANSIBLE_HOST_KEY_CHECKING` environment variable set to ``False``::
+
+  $ ANSIBLE_HOST_KEY_CHECKING=False  ansible-playbook -i hosts-virtual --ask-pass bootstrap.yml
+
+This will suppress host fingerprint checking.