Changeset 13839
- Timestamp:
- 20 Apr 2016, 08:24:23 (9 years ago)
- Location:
- main/waeup-ansible
- Files:
-
- 1 added
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
main/waeup-ansible/README.rst
r13837 r13839 91 91 https://docs.ansible.com/ansible/playbooks_best_practices.html#directory-layout 92 92 93 94 Bootstrapping - Freshmechs 95 -------------------------- 96 97 We call those nachines "freshmech" that are freshly delivered from the 98 hosting provider or that were freshly provisioned by `vagrant` (see 99 above). 100 101 These machines are expected to have only a single root account and 102 normally a (security-wise) poor SSH configuration. 103 104 Bootstrapping these machines means we secure SSH, restart the SSH 105 daemon and then add important accounts: "uli", "henrik", "ansible". 106 107 Any host you want to "bootstrap" must be entered in a local hosts 108 file, normally ``hosts-virtual``, with a line like this: 109 110 [yet-untouched] 111 vh5.sample.org ansible_host=192.168.36.10 ansible_user=root 112 113 in the "yet-untouched" section. 114 115 Afterwards try: 116 117 $ ansible-playbook -i hosts-virtual --ask-pass bootstrap.yml 118 119 The ``ask-pass`` parameter is needed to enter the password given by 120 the provider on the commandline. For the local `vagrant` machines this 121 will be `vagrant`.
Note: See TracChangeset for help on using the changeset viewer.