Changeset 14693 for main/waeup-ansible

Timestamp:

14 Jun 2017, 14:29:20 (8 years ago)

Author:

uli

Message:

In README, describe host setup after bootstrapping.

Give hints how we do host setup, the 2nd step in server lifecycle after bootstrapping.

File:

• main/waeup-ansible/README.rst (modified) (1 diff)

main/waeup-ansible/README.rst

@@ -100 +100 @@
    to see, whether setup is fine (dry run) and::
 
-     $ ansible-playbooj -i hosts bootstrap.yml
+     $ ansible-playbook -i hosts bootstrap.yml
 
    to actually perform the changes.
+
+6) In `hosts` move the host we handle from ``[yet-untouched]`` over to
+   ``[bootstapped]``.
+
+
+Setup
+=====
+
+After bootstrapping, there should be a user account we can use.
+
+1) Create a local SSH key to connect to the new server and copy it over::
+
+     $ ssh-keygen -t ed25519 -C "uli@foo to myremote" -f ~/.ssh/id_myremote
+
+   Where ``myremote`` is normally one of h1, h2, ...., hN. Then::
+
+     $ ssh-copy-id -i ~/.ssh/id_myremote user@myremote.waeup.org
+
+   and eventually edit ``~/.ssh/config`` to register your new key.
+   If you are out for adventure, do not create a new key but use the one you
+   use on all other machines as well. This is, of course, not recommended.
+
+2) Update the entry of the handled host in the local `hosts` inventory:
+   - Remove ``ansible_user=root``
+   - Remove ``ansible_ssh_pass``.
+   - Set ``ansible_sudo_pass`` to the password of the user you connect as.
+
+3) Update the server::
+
+     $ ansible -i hosts hmyremote.waeup.org -b -m apt -a "upgrade=safe update_cache=yes"
+
+   This way we can ensure that your SSH setup works correctly.
+
+4) Run setup.py::
+
+     $ ansible-playbook -i hosts -l hmyremote.waeup.org -C setup.yml
+
+   (for a dry run) and::
+
+     $ ansible-playbook -i hosts -l hmyremote.waeup.org setup.yml
+
+   for the real run.