Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen Revision Vorhergehende Überarbeitung Nächste Überarbeitung | Vorhergehende Überarbeitung Nächste ÜberarbeitungBeide Seiten der Revision | ||
centos:ansible:first [14.01.2020 16:19. ] – [Zielverzeichnis anlegen und öffentlichen Schlüssel kopieren] django | centos:ansible:first [20.06.2020 18:49. ] – [hosts.yml] django | ||
---|---|---|---|
Zeile 2: | Zeile 2: | ||
{{: | {{: | ||
- | Nachdem wir uns bereits eingehend mit den **[[centos: | + | Nachdem wir uns bereits eingehend mit den **[[centos: |
===== Voraussetzung: | ===== Voraussetzung: | ||
- | Einer der wesentlichen Vorteil von Ansible ist, dass hierzu kein separater eigener Server | + | Einer der wesentlichen Vorteil von Ansible ist, dass hierzu kein separater eigener Server |
==== Dokumentation ==== | ==== Dokumentation ==== | ||
Zeile 46: | Zeile 46: | ||
</ | </ | ||
- | Auf diese RSA-Schlüssel muss man aber nicht mehr zwingend zurückgreifen, | + | Auf diese RSA-Schlüssel muss man aber nicht mehr zwingend zurückgreifen, |
Im zweiten Fall erstellen wir uns nun einen **ED25519**-Schlüssel (**'' | Im zweiten Fall erstellen wir uns nun einen **ED25519**-Schlüssel (**'' | ||
Zeile 83: | Zeile 83: | ||
| | ||
- | Anschließend | + | Anschliessend |
$ cat key.pub >> authorized_keys | $ cat key.pub >> authorized_keys | ||
Zeile 91: | Zeile 91: | ||
- | <WRAP round info> | + | <WRAP round info>**ssh-copy-id** |
- | Das Kopieren des Public-Keys auf unseren Zielhost mit Anpassen der Dateiberechtigungen kann man natürlich auch einfacher vornehmen. Man benutzt hierzu einfach den Befehl **ssh-copy-id** aus dem Paket //**openssh-clients**//. | + | Das Kopieren des Public-Keys auf unseren Zielhost mit Anpassen der Dateiberechtigungen kann man natürlich auch einfacher vornehmen. Man benutzt hierzu einfach den Befehl **ssh-copy-id** aus dem Paket **//openssh-clients// |
* RSA-Key < | * RSA-Key < | ||
* ed25519-Key < | * ed25519-Key < | ||
- | Mit der Angabe '' | + | Mit der Angabe '' |
</ | </ | ||
==== Verbindungstest via SSH ==== | ==== Verbindungstest via SSH ==== | ||
Nun können wir eine erste Testverbindung zu unserem Zielsystem aufbauen. | Nun können wir eine erste Testverbindung zu unserem Zielsystem aufbauen. | ||
- | $ ssh -l ansible -i ~/ | + | $ ssh -l ansible -i ~/ |
< | < | ||
# # | # # | ||
- | # ╭∩╮( ͡° ل͟ ͡° )╭∩╮ | + | # |
# # | # # | ||
# | # | ||
Zeile 115: | Zeile 115: | ||
Activate the web console with: systemctl enable --now cockpit.socket | Activate the web console with: systemctl enable --now cockpit.socket | ||
- | Last login: Mon Dec 30 21:43:35 2019</ | + | Last login: Mon Feb 30 21:43:35 2019</ |
===== (Grund-)Konfiguration ===== | ===== (Grund-)Konfiguration ===== | ||
Zeile 123: | Zeile 123: | ||
├── hosts | ├── hosts | ||
└── roles | └── roles | ||
+ | |||
+ | 1 directory, 2 files | ||
</ | </ | ||
==== / | ==== / | ||
- | Fast alle Parameter können in einem Ansible-playbook oder mit Kommandozeilenflags überschrieben werden. Ansible | + | Fast alle Parameter können in einem Ansible-playbook oder mit Kommandozeilenflags überschrieben werden. |
+ | |||
+ | Bei der Ermittlung der Konfigurationsdatei - **'' | ||
+ | - Erst durch die Umgebungsvariable '' | ||
+ | - dann die Datei **'' | ||
+ | - anschließend **'' | ||
+ | | ||
# vim / | # vim / | ||
Zeile 621: | Zeile 630: | ||
</ | </ | ||
- | {{page>centos: | + | ==== / |
+ | In der Konfigurationsdatei **''/ | ||
+ | |||
+ | In dieser Konfigurationsdatei gelten folgende Rahmenparameter: | ||
+ | * Kommentare beginnen mit dem Zeichen '#' | ||
+ | * Leere Zeilen werden ignoriert | ||
+ | * Gruppen von Hosts werden durch [header]-Elemente abgegrenzt | ||
+ | * Es können Hostnamen oder IP-Adressen verwendet werden | ||
+ | * Ein Hostname/ | ||
+ | |||
+ | # vim / | ||
+ | <file bash / | ||
+ | # It should live in / | ||
+ | # | ||
+ | # - Comments begin with the '#' | ||
+ | # - Blank lines are ignored | ||
+ | # - Groups of hosts are delimited by [header] elements | ||
+ | # - You can enter hostnames or ip addresses | ||
+ | # - A hostname/ip can be a member of multiple groups | ||
+ | |||
+ | # Ex 1: Ungrouped hosts, specify before any group headers. | ||
+ | |||
+ | ## green.example.com | ||
+ | ## blue.example.com | ||
+ | ## 192.168.100.1 | ||
+ | ## 192.168.100.10 | ||
+ | |||
+ | # Ex 2: A collection of hosts belonging to the ' | ||
+ | |||
+ | ## [webservers] | ||
+ | ## alpha.example.org | ||
+ | ## beta.example.org | ||
+ | ## 192.168.1.100 | ||
+ | ## 192.168.1.110 | ||
+ | |||
+ | # If you have multiple hosts following a pattern you can specify | ||
+ | # them like this: | ||
+ | |||
+ | ## www[001: | ||
+ | |||
+ | # Ex 3: A collection of database servers in the ' | ||
+ | |||
+ | ## [dbservers] | ||
+ | ## | ||
+ | ## db01.intranet.mydomain.net | ||
+ | ## db02.intranet.mydomain.net | ||
+ | ## 10.25.1.56 | ||
+ | ## 10.25.1.57 | ||
+ | |||
+ | # Here's another example of host ranges, this time there are no | ||
+ | # leading 0s: | ||
+ | |||
+ | ## db-[99: | ||
+ | |||
+ | </ | ||
+ | |||
+ | ==== Ansible: Directory Layout ===== | ||
+ | Gemäß **[[http:// | ||
+ | |||
+ | <WRAP center round tip 90%> | ||
+ | Jedoch empfiehlt es sich durchaus auf Empfohlenes zurückzugreifen! So empfiehlt es sich zum Beispiel auch, Rollen anstelle von Aufgaben zu verwenden, da dies wesentlich bei der Flexibilität und besseren Organisation der eigenen Playbooks/ | ||
+ | </ | ||
+ | |||
+ | Ansible bietet **[[https:// | ||
+ | |||
+ | Mit dieser Struktur sind wir dann in der Lage jede Inventardatei mit ihrer **'' | ||
+ | |||
+ | Werfen wir also einfach mal auf die beschrieben Verzeichnisstruktur einen genaueren Blick. Die entsprechende Verwendung der einzelnen Verzeichnisse und DAteien ist in der Aufstellung entsprechend angegeben. | ||
+ | < | ||
+ | ├── filter_plugins | ||
+ | ├── library | ||
+ | ├── module_utils | ||
+ | │ | ||
+ | ├── inventories | ||
+ | │ ├── production | ||
+ | │ │ ├── hosts.yml | ||
+ | │ │ ├── group_vars | ||
+ | │ │ └── host_vars | ||
+ | │ | ||
+ | │ └── staging | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | ├── roles # Verzeichnis für die einzelnen (unterschiedlichen) Rollen | ||
+ | │ └── common | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | │ | ||
+ | └── site.yml | ||
+ | </ | ||
+ | |||
+ | Um dieses Verzeichnis-Layout einfach und schnell auf den Weg zu bringen, verwenden wir die nachfolgend gezeigten zwei Befehle bzw. genauer gesagt die beiden Befehlskette: | ||
+ | $ mkdir -p ~/ | ||
+ | ~/ | ||
+ | ~/ | ||
+ | |||
+ | $ touch ~/ | ||
+ | ~/ | ||
+ | ~/ | ||
+ | |||
+ | ==== Musterkonfiguration ===== | ||
+ | === ansible.cfg === | ||
+ | Wie schon zuvor angemerkt sucht [[https:// | ||
+ | - Erst durch die Umgebungsvariable '' | ||
+ | - dann die Datei **'' | ||
+ | - anschließend **'' | ||
+ | - zum Schluss in der Konfigurationsdatei **''/ | ||
+ | |||
+ | Wir werden nun unsere Host- und Admin-spezifische Konfiguration also in der datei **'' | ||
+ | # cp / | ||
+ | Zuvor haten wir bereits die Datei **'' | ||
+ | # vim / | ||
+ | |||
+ | <file bash / | ||
+ | # =============================================== | ||
+ | |||
+ | # nearly all parameters can be overridden in ansible-playbook | ||
+ | # or with command line flags. ansible will read ANSIBLE_CONFIG, | ||
+ | # ansible.cfg in the current working directory, .ansible.cfg in | ||
+ | # the home directory or / | ||
+ | # finds first | ||
+ | |||
+ | [defaults] | ||
+ | |||
+ | # some basic default values... | ||
+ | |||
+ | # Django | ||
+ | # default: # | ||
+ | inventory | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | |||
+ | # plays will gather facts by default, which contain information about | ||
+ | # the remote system. | ||
+ | # | ||
+ | # smart - gather by default, but don't regather if already gathered | ||
+ | # implicit - gather by default, turn off with gather_facts: | ||
+ | # explicit - do not gather by default, must say gather_facts: | ||
+ | #gathering = implicit | ||
+ | |||
+ | # This only affects the gathering done by a play's gather_facts directive, | ||
+ | # by default gathering retrieves all facts subsets | ||
+ | # all - gather all subsets | ||
+ | # network - gather min and network facts | ||
+ | # hardware - gather hardware facts (longest facts to retrieve) | ||
+ | # virtual - gather min and virtual facts | ||
+ | # facter - import facts from facter | ||
+ | # ohai - import facts from ohai | ||
+ | # You can combine them using comma (ex: network, | ||
+ | # You can negate them using ! (ex: !hardware, | ||
+ | # A minimal set of facts is always gathered. | ||
+ | # | ||
+ | |||
+ | # some hardware related facts are collected | ||
+ | # with a maximum timeout of 10 seconds. This | ||
+ | # option lets you increase or decrease that | ||
+ | # timeout to something more suitable for the | ||
+ | # environment. | ||
+ | # gather_timeout = 10 | ||
+ | |||
+ | # Ansible facts are available inside the ansible_facts.* dictionary | ||
+ | # namespace. This setting maintains the behaviour which was the default prior | ||
+ | # to 2.5, duplicating these variables into the main namespace, each with a | ||
+ | # prefix of ' | ||
+ | # This variable is set to True by default for backwards compatibility. It | ||
+ | # will be changed to a default of ' | ||
+ | # ansible_facts. | ||
+ | # inject_facts_as_vars = True | ||
+ | |||
+ | # additional paths to search for roles in, colon separated | ||
+ | # | ||
+ | |||
+ | # uncomment this to disable SSH key host checking | ||
+ | # | ||
+ | |||
+ | # change the default callback, you can only have one ' | ||
+ | # | ||
+ | |||
+ | |||
+ | ## Ansible ships with some plugins that require whitelisting, | ||
+ | ## this is done to avoid running all of a type by default. | ||
+ | ## These setting lists those that you want enabled for your system. | ||
+ | ## Custom plugins should not need this unless plugin author specifies it. | ||
+ | |||
+ | # enable callback plugins, they can output to stdout but cannot be ' | ||
+ | # | ||
+ | |||
+ | # Determine whether includes in tasks and handlers are " | ||
+ | # default. As of 2.0, includes are dynamic by default. Setting these | ||
+ | # values to True will make includes behave more like they did in the | ||
+ | # 1.x versions. | ||
+ | # | ||
+ | # | ||
+ | |||
+ | # Controls if a missing handler for a notification event is an error or a warning | ||
+ | # | ||
+ | |||
+ | # change this for alternative sudo implementations | ||
+ | #sudo_exe = sudo | ||
+ | |||
+ | # What flags to pass to sudo | ||
+ | # WARNING: leaving out the defaults might create unexpected behaviours | ||
+ | #sudo_flags = -H -S -n | ||
+ | |||
+ | # SSH timeout | ||
+ | #timeout = 10 | ||
+ | |||
+ | # default user to use for playbooks if user is not specified | ||
+ | # (/ | ||
+ | # | ||
+ | |||
+ | # logging is off by default unless this path is defined | ||
+ | # if so defined, consider logrotate | ||
+ | #log_path = / | ||
+ | |||
+ | # default module name for / | ||
+ | # | ||
+ | |||
+ | # use this shell for commands executed under sudo | ||
+ | # you may need to change this to bin/bash in rare instances | ||
+ | # if sudo is constrained | ||
+ | #executable = /bin/sh | ||
+ | |||
+ | # if inventory variables overlap, does the higher precedence one win | ||
+ | # or are hash values merged together? | ||
+ | # this can also be set to ' | ||
+ | # | ||
+ | |||
+ | # by default, variables from roles will be visible in the global variable | ||
+ | # scope. To prevent this, the following option can be enabled, and only | ||
+ | # tasks and handlers within the role will see the variables there | ||
+ | # | ||
+ | |||
+ | # list any Jinja2 extensions to enable here: | ||
+ | # | ||
+ | |||
+ | # if set, always use this private key file for authentication, | ||
+ | # if passing --private-key to ansible or ansible-playbook | ||
+ | # | ||
+ | |||
+ | # If set, configures the path to the Vault password file as an alternative to | ||
+ | # specifying --vault-password-file on the command line. | ||
+ | # | ||
+ | |||
+ | # format of string {{ ansible_managed | ||
+ | # templates indicates to users editing templates files will be replaced. | ||
+ | # replacing {file}, {host} and {uid} and strftime codes with proper values. | ||
+ | # | ||
+ | # {file}, {host}, {uid}, and the timestamp can all interfere with idempotence | ||
+ | # in some situations so the default is a static string: | ||
+ | # | ||
+ | |||
+ | # by default, ansible-playbook will display " | ||
+ | # should not be run on a host. Set this to " | ||
+ | # messages. NOTE: the task header will still be shown regardless of whether or not the | ||
+ | # task is skipped. | ||
+ | # | ||
+ | |||
+ | # by default, if a task in a playbook does not include a name: field then | ||
+ | # ansible-playbook will construct a header that includes the task's action but | ||
+ | # not the task's args. This is a security feature because ansible cannot know | ||
+ | # if the *module* considers an argument to be no_log at the time that the | ||
+ | # header is printed. | ||
+ | # stdout from ansible-playbook (or you have manually specified no_log in your | ||
+ | # playbook on all of the tasks where you have secret information) then you can | ||
+ | # safely set this to True to get more informative messages. | ||
+ | # | ||
+ | |||
+ | # by default (as of 1.3), Ansible will raise errors when attempting to dereference | ||
+ | # Jinja2 variables that are not set in templates or action lines. Uncomment this line | ||
+ | # to revert the behavior to pre-1.3. | ||
+ | # | ||
+ | |||
+ | # by default (as of 1.6), Ansible may display warnings based on the configuration of the | ||
+ | # system running ansible itself. This may include warnings about 3rd party packages or | ||
+ | # other conditions that should be resolved if possible. | ||
+ | # to disable these warnings, set the following value to False: | ||
+ | # | ||
+ | |||
+ | # by default (as of 1.4), Ansible may display deprecation warnings for language | ||
+ | # features that should no longer be used and will be removed in future versions. | ||
+ | # to disable these warnings, set the following value to False: | ||
+ | # | ||
+ | |||
+ | # (as of 1.8), Ansible can optionally warn when usage of the shell and | ||
+ | # command module appear to be simplified by using a default Ansible module | ||
+ | # instead. | ||
+ | # setting or adding warn=yes or warn=no to the end of the command line | ||
+ | # parameter string. | ||
+ | # instead of shelling out to the git command. | ||
+ | # command_warnings = False | ||
+ | |||
+ | |||
+ | # set plugin path directories here, separate with colons | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | |||
+ | |||
+ | # by default, ansible will use the ' | ||
+ | # another one | ||
+ | #strategy = free | ||
+ | |||
+ | # by default callbacks are not loaded for / | ||
+ | # want, for example, a notification or logging callback to also apply to | ||
+ | # / | ||
+ | # | ||
+ | |||
+ | |||
+ | # don't like cows? that's unfortunate. | ||
+ | # set to 1 if you don't want cowsay support or export ANSIBLE_NOCOWS=1 | ||
+ | #nocows = 1 | ||
+ | |||
+ | # set which cowsay stencil you'd like to use by default. When set to ' | ||
+ | # a random stencil will be selected for each task. The selection will be filtered | ||
+ | # against the `cow_whitelist` option below. | ||
+ | # | ||
+ | # | ||
+ | |||
+ | # when using the ' | ||
+ | # it should be formatted as a comma-separated list with no spaces between names. | ||
+ | # NOTE: line continuations here are for formatting purposes only, as the INI parser | ||
+ | # in python does not support them. | ||
+ | # | ||
+ | # hellokitty, | ||
+ | # stimpy, | ||
+ | |||
+ | # don't like colors either? | ||
+ | # set to 1 if you don't want colors, or export ANSIBLE_NOCOLOR=1 | ||
+ | #nocolor = 1 | ||
+ | |||
+ | # if set to a persistent type (not ' | ||
+ | # from previous runs in Ansible will be stored. | ||
+ | # wanting to use, for example, IP information from one group of servers | ||
+ | # without having to talk to them in the same playbook run to get their | ||
+ | # current IP information. | ||
+ | # | ||
+ | |||
+ | #This option tells Ansible where to cache facts. The value is plugin dependent. | ||
+ | #For the jsonfile plugin, it should be a path to a local directory. | ||
+ | #For the redis plugin, the value is a host: | ||
+ | |||
+ | # | ||
+ | |||
+ | |||
+ | |||
+ | # retry files | ||
+ | # When a playbook fails a .retry file can be created that will be placed in ~/ | ||
+ | # You can enable this feature by setting retry_files_enabled to True | ||
+ | # and you can change the location of the files by setting retry_files_save_path | ||
+ | |||
+ | # | ||
+ | # | ||
+ | |||
+ | # squash actions | ||
+ | # Ansible can optimise actions that call modules with list parameters | ||
+ | # when looping. Instead of calling the module once per with_ item, the | ||
+ | # module is called once with all items at once. Currently this only works | ||
+ | # under limited circumstances, | ||
+ | # | ||
+ | |||
+ | # prevents logging of task data, off by default | ||
+ | #no_log = False | ||
+ | |||
+ | # prevents logging of tasks, but only on the targets, data is still logged on the master/ | ||
+ | # | ||
+ | |||
+ | # controls whether Ansible will raise an error or warning if a task has no | ||
+ | # choice but to create world readable temporary files to execute a module on | ||
+ | # the remote machine. | ||
+ | # turn this on to have behaviour more like Ansible prior to 2.1.x. | ||
+ | # https:// | ||
+ | # for more secure ways to fix this than enabling this option. | ||
+ | # | ||
+ | |||
+ | # controls the compression level of variables sent to | ||
+ | # worker processes. At the default of 0, no compression | ||
+ | # is used. This value must be an integer from 0 to 9. | ||
+ | # | ||
+ | |||
+ | # controls what compression method is used for new-style ansible modules when | ||
+ | # they are sent to the remote system. | ||
+ | # support compiled into both the controller' | ||
+ | # The names should match with the python Zipfile compression types: | ||
+ | # * ZIP_STORED (no compression. available everywhere) | ||
+ | # * ZIP_DEFLATED (uses zlib, the default) | ||
+ | # These values may be set per host via the ansible_module_compression inventory | ||
+ | # variable | ||
+ | # | ||
+ | |||
+ | # This controls the cutoff point (in bytes) on --diff for files | ||
+ | # set to 0 for unlimited (RAM may suffer!). | ||
+ | # | ||
+ | |||
+ | # This controls how ansible handles multiple --tags and --skip-tags arguments | ||
+ | # on the CLI. If this is True then multiple arguments are merged together. | ||
+ | # it is False, then the last specified argument is used and the others are ignored. | ||
+ | # This option will be removed in 2.8. | ||
+ | # | ||
+ | |||
+ | # Controls showing custom stats at the end, off by default | ||
+ | # | ||
+ | |||
+ | # Controls which files to ignore when using a directory as inventory with | ||
+ | # possibly multiple sources (both static and dynamic) | ||
+ | # | ||
+ | |||
+ | # This family of modules use an alternative execution path optimized for network appliances | ||
+ | # only update this setting if you know how this works, otherwise it can break module execution | ||
+ | # | ||
+ | |||
+ | # When enabled, this option allows lookups (via variables like {{lookup(' | ||
+ | # a loop with `with_foo`) to return data that is not marked " | ||
+ | # jinja2 templating language which will be run through the templating engine. | ||
+ | # ENABLING THIS COULD BE A SECURITY RISK | ||
+ | # | ||
+ | |||
+ | # set default errors for all plays | ||
+ | # | ||
+ | |||
+ | [inventory] | ||
+ | # enable inventory plugins, default: ' | ||
+ | # | ||
+ | |||
+ | # ignore these extensions when parsing a directory as inventory source | ||
+ | # | ||
+ | |||
+ | # ignore files matching these patterns when parsing a directory as inventory source | ||
+ | # | ||
+ | |||
+ | # If ' | ||
+ | # | ||
+ | |||
+ | [privilege_escalation] | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | |||
+ | [paramiko_connection] | ||
+ | |||
+ | # uncomment this line to cause the paramiko connection plugin to not record new host | ||
+ | # keys encountered. | ||
+ | # host key checking setting above. | ||
+ | # | ||
+ | |||
+ | # by default, Ansible requests a pseudo-terminal for commands executed under sudo. Uncomment this | ||
+ | # line to disable this behaviour. | ||
+ | # | ||
+ | |||
+ | # paramiko will default to looking for SSH keys initially when trying to | ||
+ | # authenticate to remote devices. | ||
+ | # that close the connection after a key failure. | ||
+ | # disable the Paramiko look for keys function | ||
+ | # | ||
+ | |||
+ | # When using persistent connections with Paramiko, the connection runs in a | ||
+ | # background process. | ||
+ | # default Ansible will prompt to add the host key. This will cause connections | ||
+ | # running in background processes to fail. Uncomment this line to have | ||
+ | # Paramiko automatically add host keys. | ||
+ | # | ||
+ | |||
+ | [ssh_connection] | ||
+ | |||
+ | # ssh arguments to use | ||
+ | # Leaving off ControlPersist will result in poor performance, | ||
+ | # paramiko on older platforms rather than removing it, -C controls compression use | ||
+ | #ssh_args = -C -o ControlMaster=auto -o ControlPersist=60s | ||
+ | |||
+ | # The base directory for the ControlPath sockets. | ||
+ | # This is the " | ||
+ | # | ||
+ | # Example: | ||
+ | # control_path_dir = / | ||
+ | # | ||
+ | |||
+ | # The path to use for the ControlPath sockets. This defaults to a hashed string of the hostname, | ||
+ | # port and username (empty string in the config). The hash mitigates a common problem users | ||
+ | # found with long hostnames and the conventional %(directory)s/ | ||
+ | # In those cases, a "too long for Unix domain socket" | ||
+ | # | ||
+ | # Example: | ||
+ | # control_path = %(directory)s/ | ||
+ | # | ||
+ | |||
+ | # Enabling pipelining reduces the number of SSH operations required to | ||
+ | # execute a module on the remote server. This can result in a significant | ||
+ | # performance improvement when enabled, however when using " | ||
+ | # first disable ' | ||
+ | # | ||
+ | # By default, this option is disabled to preserve compatibility with | ||
+ | # sudoers configurations that have requiretty (the default on many distros). | ||
+ | # | ||
+ | #pipelining = False | ||
+ | |||
+ | # Control the mechanism for transferring files (old) | ||
+ | # * smart = try sftp and then try scp [default] | ||
+ | # * True = use scp only | ||
+ | # * False = use sftp only | ||
+ | #scp_if_ssh = smart | ||
+ | |||
+ | # Control the mechanism for transferring files (new) | ||
+ | # If set, this will override the scp_if_ssh option | ||
+ | # * sftp = use sftp to transfer files | ||
+ | # * scp = use scp to transfer files | ||
+ | # * piped = use ' | ||
+ | # * smart = try sftp, scp, and piped, in that order [default] | ||
+ | # | ||
+ | |||
+ | # if False, sftp will not use batch mode to transfer files. This may cause some | ||
+ | # types of file transfer failures impossible to catch however, and should | ||
+ | # only be disabled if your sftp version has problems with batch mode | ||
+ | # | ||
+ | |||
+ | # The -tt argument is passed to ssh when pipelining is not enabled because sudo | ||
+ | # requires a tty by default. | ||
+ | #usetty = True | ||
+ | |||
+ | # Number of times to retry an SSH connection to a host, in case of UNREACHABLE. | ||
+ | # For each retry attempt, there is an exponential backoff, | ||
+ | # so after the first attempt there is 1s wait, then 2s, 4s etc. up to 30s (max). | ||
+ | #retries = 3 | ||
+ | |||
+ | [persistent_connection] | ||
+ | |||
+ | # Configures the persistent connection timeout value in seconds. | ||
+ | # how long the persistent connection will remain idle before it is destroyed. | ||
+ | # If the connection doesn' | ||
+ | # expires, the connection is shutdown. The default value is 30 seconds. | ||
+ | # | ||
+ | |||
+ | # The command timeout value defines the amount of time to wait for a command | ||
+ | # or RPC call before timing out. The value for the command timeout must | ||
+ | # be less than the value of the persistent connection idle timeout (connect_timeout) | ||
+ | # The default value is 30 second. | ||
+ | # | ||
+ | |||
+ | [accelerate] | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | |||
+ | # The daemon timeout is measured in minutes. This time is measured | ||
+ | # from the last activity to the accelerate daemon. | ||
+ | # | ||
+ | |||
+ | # If set to yes, accelerate_multi_key will allow multiple | ||
+ | # private keys to be uploaded to it, though each user must | ||
+ | # have access to the system via SSH to add a new key. The default | ||
+ | # is " | ||
+ | # | ||
+ | |||
+ | [selinux] | ||
+ | # file systems that require special treatment when dealing with security context | ||
+ | # the default behaviour that copies the existing context or uses the user default | ||
+ | # needs to be changed to use the file system dependent context. | ||
+ | # | ||
+ | |||
+ | # Set this to yes to allow libvirt_lxc connections to work without SELinux. | ||
+ | # | ||
+ | |||
+ | [colors] | ||
+ | #highlight = white | ||
+ | #verbose = blue | ||
+ | #warn = bright purple | ||
+ | #error = red | ||
+ | #debug = dark gray | ||
+ | #deprecate = purple | ||
+ | #skip = cyan | ||
+ | # | ||
+ | #ok = green | ||
+ | #changed = yellow | ||
+ | #diff_add = green | ||
+ | # | ||
+ | #diff_lines = cyan | ||
+ | |||
+ | |||
+ | [diff] | ||
+ | # Always print diff when running ( same as always running with -D/--diff ) | ||
+ | # always = no | ||
+ | |||
+ | # Set how many context lines to show in diff | ||
+ | # context = 3 | ||
+ | </ | ||
+ | |||
+ | === hosts.yml === | ||
+ | Im Abschnitt **[[# | ||
+ | |||
+ | Wir befüllen nun also die entsprechende Datei mit den Daten unserer Produktions-/ | ||
+ | $ vim ~/ | ||
+ | <file yml ~/ | ||
+ | centos7: | ||
+ | hosts: | ||
+ | bh7: | ||
+ | ansible_ssh_host: | ||
+ | |||
+ | centos8: | ||
+ | hosts: | ||
+ | ansible: | ||
+ | ansible_ssh_host: | ||
+ | demo: | ||
+ | ansible_ssh_host: | ||
+ | ansible_ssh_port: | ||
+ | ... #YAML ende syntax (optional)</ | ||
+ | |||
+ | |||
+ | Wir definieren damit folgende Hostgruppen: | ||
+ | * **'' | ||
+ | * **'' | ||
+ | * mit dem Host **'' | ||
+ | * mit dem Host **'' | ||
+ | |||
+ | Mit dem Befehl **'' | ||
+ | # ansible --list-hosts centos7 | ||
+ | < | ||
+ | bh7</ | ||
+ | # ansible --list-hosts centos8 | ||
+ | < | ||
+ | ansible | ||
+ | demo</ | ||
+ | |||
+ | |||
+ | ===== erste Verbindungstests ===== | ||
+ | Nachdem wir im Abschnitt **[[# | ||
- | ==== Verbindungstest ==== | ||
- | Nachdem wir im Abschnitt **[# | ||
Dies können wir mit Hilfe des Folgenden SSH-Aufrufes bewerkstelligen: | Dies können wir mit Hilfe des Folgenden SSH-Aufrufes bewerkstelligen: | ||
- | $ ssh -l ansible -i ~/ | + | $ ssh -l ansible -i ~/ |
< | < | ||
# # | # # | ||
Zeile 646: | Zeile 1314: | ||
-rw-------. 1 ansible ansible 793 Dec 30 21:47 .viminfo</ | -rw-------. 1 ansible ansible 793 Dec 30 21:47 .viminfo</ | ||
- | Im Abschnitt **[[centos: | + | Im Abschnitt **[[centos: |
- | $ ansible 10.0.0.90 -u ansible --private-key / | + | $ ansible 10.0.0.190 -u ansible --private-key / |
< | < | ||
- | <font style=" | + | <font style=" |
total 20 | total 20 | ||
drwx------. 4 ansible ansible 127 Dec 30 22:26 ./ | drwx------. 4 ansible ansible 127 Dec 30 22:26 ./ | ||
Zeile 663: | Zeile 1331: | ||
</ | </ | ||
- | Alternative dazu können wir natürlich auch den **Host** oder auch die definierten **Hostgruppen** aus unserer Konfigurationsdatei **'' | + | Alternative dazu können wir natürlich auch den **Host** oder auch die definierten **Hostgruppen** aus unserer |
- | $ ansible | + | $ ansible |
< | < | ||
<font style=" | <font style=" | ||
Zeile 688: | Zeile 1356: | ||
" | " | ||
}</ | }</ | ||
- | <font style=" | + | <font style=" |
" | " | ||
" | " | ||
Zeile 697: | Zeile 1365: | ||
</ | </ | ||
- | In dem gezeigten Fall ist der Host **bh7.dmz.nausch.org** aktuell nicht erreichbar und entsprechend **rot** gekennzeichnet. Der zweite **grün** markierte Host mit der IP-Adresse **10.0.0.90** hingegen ist erreichbar uns mit dem Zusatz **SUCCESS** versehen. | + | Im gezeigten Fall ist der Host **bh7.dmz.nausch.org** aktuell nicht erreichbar und entsprechend **rot** gekennzeichnet. Der zweite **grün** markierte Host mit der IP-Adresse **10.0.0.90** hingegen ist erreichbar uns mit dem Zusatz **SUCCESS** versehen. |
===== erweiterte Konfiguration - Anpassungen ===== | ===== erweiterte Konfiguration - Anpassungen ===== | ||
==== remote User-Anpassung via ansible.conf ==== | ==== remote User-Anpassung via ansible.conf ==== | ||
- | Um nun nicht bei jedem Aufruf den Remouteuser **'' | + | Um nun nicht bei jedem Aufruf den Remouteuser **'' |
Wie öffnen also unsere Konfigurationsdatei und ergänzen nachfolgende Abschnitte. | Wie öffnen also unsere Konfigurationsdatei und ergänzen nachfolgende Abschnitte. | ||
- | # vim /etc/ | + | # vim ~/.ansible.cfg |
=== remote_user === | === remote_user === | ||
<code bash># default user to use for playbooks if user is not specified | <code bash># default user to use for playbooks if user is not specified | ||
Zeile 718: | Zeile 1386: | ||
# | # | ||
# Django : 2019-12-30 | # Django : 2019-12-30 | ||
- | private_key_file = / | + | private_key_file = ~/ |
</ | </ | ||
=== (Verbindungs-)Tests === | === (Verbindungs-)Tests === | ||
- | Nun können wir schon mal viel einfacher ein [[centos: | + | Nun können wir schon mal viel einfacher ein [[centos: |
- | $ ansible | + | $ ansible |
< | < | ||
<font style=" | <font style=" | ||
- | CentOS Linux release | + | CentOS Linux release |
</ | </ | ||
Zeile 732: | Zeile 1400: | ||
Das vorgenannte Beispiel funktioniert natürlich nur, wenn wir uns in einem homogenen Systemumfeld befinden, in dem alle Zielsysteme z.B. den gleichen Schlüsseltyp verwenden. Haben wir aber Systeme, die z.B. nur RSA-Schlüssel verwenden wie z.B. CentOS 6 Systeme oder Knoten eines Freifunk Netzes, so müssen wir natürlich eine Möglichkeit schaffen, für unterschiedliche Hosts auch unterschiedliche Schlüsseldateien und/oder sogar unterschiedliche User angeben zu können. | Das vorgenannte Beispiel funktioniert natürlich nur, wenn wir uns in einem homogenen Systemumfeld befinden, in dem alle Zielsysteme z.B. den gleichen Schlüsseltyp verwenden. Haben wir aber Systeme, die z.B. nur RSA-Schlüssel verwenden wie z.B. CentOS 6 Systeme oder Knoten eines Freifunk Netzes, so müssen wir natürlich eine Möglichkeit schaffen, für unterschiedliche Hosts auch unterschiedliche Schlüsseldateien und/oder sogar unterschiedliche User angeben zu können. | ||
- | Wir verändern nun also unser Konfigurationsdatei **''/ | + | Wir verändern nun also unser Konfigurationsdatei **'' |
Wie öffnen also unsere Konfigurationsdatei und ergänzen nachfolgende Abschnitte. | Wie öffnen also unsere Konfigurationsdatei und ergänzen nachfolgende Abschnitte. | ||
- | # vim /etc/ | + | # vim ~/.ansible.cfg |
=== remote_user === | === remote_user === | ||
Zeile 756: | Zeile 1424: | ||
=== inventory === | === inventory === | ||
- | In der Konfigurationsdatei **'' | + | Zuvor hatten |
- | + | ||
- | Wir hinterlegen also dort, dass zukünftig die Inventory-Datei | + | |
- | < | + | |
- | + | ||
- | # some basic default values... | + | |
- | + | ||
- | # Django : 2020-01-01 | + | |
- | # default: # | + | |
- | inventory | + | |
- | </ | + | |
+ | In der Konfigurationsdatei **'' | ||
=== hosts.yml === | === hosts.yml === | ||
- | Unsere Hosts packen wir nun in der **[[centos: | + | Unsere Hosts packen wir nun in der **[[centos: |
- | '' | + | # vim ~/ansible/ |
- | # vim /etc/ | + | |
- | < | + | < |
centos8: | centos8: | ||
Zeile 875: | Zeile 1533: | ||
=== mit Abfrage eines Passwortes === | === mit Abfrage eines Passwortes === | ||
- | Dass eine Rechteerweiterung ohne Abfrage eines Passwortes nicht unbedingt erstrebenswert ist, wollen wir uns nun daran setzen unsere Konfiguration etwas optimieren. Aus Sicherheitsgründen wird ein user, sobald er mittels **'' | + | Da eine Rechteerweiterung ohne Abfrage eines Passwortes nicht unbedingt erstrebenswert ist, wollen wir uns nun daran setzen unsere Konfiguration etwas optimieren. Aus Sicherheitsgründen wird ein user, sobald er mittels **'' |
Unser Nutzer Ansible, den wir benutzen um per SSH auf die Zielsysteme zu gelangen, haben wir ja bereits in die Gruppe **'' | Unser Nutzer Ansible, den wir benutzen um per SSH auf die Zielsysteme zu gelangen, haben wir ja bereits in die Gruppe **'' | ||
Zeile 936: | Zeile 1594: | ||
\\ \\ | \\ \\ | ||
<WRAP center round tip 80%> | <WRAP center round tip 80%> | ||
- | Neben der Ansicherung | + | Neben der Absicherung |
</ | </ | ||
Zeile 1972: | Zeile 2630: | ||
Alle unsere eigenen definierten Freifunk Knoten haben nun auf der **[[https:// | Alle unsere eigenen definierten Freifunk Knoten haben nun auf der **[[https:// | ||
+ | ==== 07: Mit Hilfe von Ansible einen Offloader auf Basis eines Raspberry 4B bauen ==== | ||
+ | In diesem Konfigurationsbeispiel wollen wir möglichst einfach und schnell einen Offloader für **[[https:// | ||
+ | Das entsprechende **Howto** findet sich im Detail auf folgender Seite **[[centos: | ||
====== Links ====== | ====== Links ====== | ||
* **[[centos: | * **[[centos: |