Ignore:
Timestamp:
20 Apr 2016, 14:13:07 (9 years ago)
Author:
uli
Message:

Tell about what we learned.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • main/waeup-ansible/README.rst

    r13839 r13843  
    105105daemon and then add important accounts: "uli", "henrik", "ansible".
    106106
     107To make sure, the connection to a "freshmech" works, you should at
     108least one time login via SSH before proceeding with ansible and all
     109bells and whistles::
     110
     111  ssh -l root 192.168.36.10
     112
     113(with the real IP of the machine you want to reach, of course).
     114
    107115Any host you want to "bootstrap" must be entered in a local hosts
    108116file, normally ``hosts-virtual``, with a line like this:
     
    120128the provider on the commandline. For the local `vagrant` machines this
    121129will be `vagrant`.
     130
     131If run on local virtual machines, you might want to make sure that
     132your local `known_hosts` file does not contain an old ssh host
     133fingerprint. Otherwise you have to remove entries for::
     134
     135  192.168.36.10
     136  192.168.36.11
     137  192.168.36.12
     138
     139respectively before running `bootstrap.yml`.
     140
     141Alternatively you can run everything with the
     142`ANSIBLE_HOST_KEY_CHECKING` environment variable set to ``False``::
     143
     144  $ ANSIBLE_HOST_KEY_CHECKING=False  ansible-playbook -i hosts-virtual --ask-pass bootstrap.yml
     145
     146This will suppress host fingerprint checking.
Note: See TracChangeset for help on using the changeset viewer.