Shulou(Shulou.com)06/03 Report--

Common modules of Ansible

The modules included in this section:

(1) package management module yum

(2) configure yum source module yum_repository

(3) Service management module service

(4) systemd module

(5) user management module user

(6) debug module

(7) timing task module cron

Package management module yum

Yum--Ansible official instruction document

Ansible-doc-s yum- name: Manages packages with the `yum' package manager yum: disable_gpg_check: # forbids gpgcheck when installing the package, and only takes effect when state=present or latest is used. Disablerepo: # disables the specified repoid, and multiple repoid are separated by commas. Enablerepo: # explicitly use the repoid exclude: # to exclude which packages are not installed, only for state=present or latest. List: # is similar to yum list. Name: # specifies the package name of the installation, with the version number. Multiple packages can be separated by commas. State: # status. ('present',' installed','latest') is used to install packages, and # ('absent',' removed') is used to remove installed packages. Update_cache: # forces the cache of yum to be updated.

Name needs to be used with state. If state is specified as present/installed/latest, the package will be installed, where latest is the latest package installed, and the default is present. Used to uninstall packages if specified as absent/removed.

In ansible, the states of present and absent appear in many places, which generally indicate whether the target should exist or not, that is, the action to be done is to create and delete.

The packages related to nginx are listed by the controller, as follows:

Ansible test-m yum-a "list=nginx"-f 10

The controlled side installs the tree package as follows:

Ansible test-m yum-a "name=tree state=installed"-o-f 8

The controlled side installs local packages and excludes some packages from being installed, as follows:

Ansible centos-m yum-a "name=/tmp/*.rpm exclude=*unix* state=present"

The controlled side uninstalls the package:

Ansible test-m yum-a "name=tree state=removed"-o-f 8

Configure yum source module yum_repository

Yum_repository--Ansible official instruction document

Used to configure the yum source. A very complete yum repository configuration can be achieved. But in general, you can simply add a yum source. So, here are the usage and examples of the simple version.

Ansible-doc-s yum_repository- name: Add or remove YUM repositories yum_repository: baseurl: # address mirrorlist: # set mirrorlist address description: # description information enabled: # whether to enable the warehouse, the default is yes file: # to save the files of this warehouse. If this item is not set, it will be named after the name in the name option by default. Will automatically end with the suffix ".repo". Gpgcheck: # whether to carry out the name of the gpgcheck name: # repository, to ensure the uniqueness of the name reposdir: # the directory where the .repo file is saved, the default / etc/yum.repos.d/ state: # repo file status, present/absent, default present.

Examples are as follows:

Ansible test-m yum_repository-a 'name=aliyun_epel description= "epel repo" baseurl= http://mirrors.aliyun.com/epel/7/$basearch/ gpgcheck=no enabled=yes'

Ansible test-m yum_repository-a 'name=rpmforge description= "RPMforge YUM repo" file= "external_repos" baseurl= http://apt.sw.be/redhat/el7/en/$basearch/rpmforge mirrorlist= http://mirrorlist.repoforge.org/el7/mirrors-rpmforge gpgcheck=no enabled=yes'

For the difference between baseurl and mirrorlist, please refer to the difference between baseurl and mirrorlist in the yum configuration file

-name: Add multiple repositories into the same file (2amp 2) yum_repository: name: rpmforge description: RPMforge YUM repo file: external_repos baseurl: http://apt.sw.be/redhat/el7/en/$basearch/rpmforge mirrorlist: http://mirrorlist.repoforge.org/el7/mirrors-rpmforge enabled: no Service Management Module service

Service--Ansible official instruction document

Ansible-doc-s service- name: Manage services service: enabled: # sets the service to boot. The default is no name: # service name state: # 'started' and' stoped' start and stop the service, respectively. They are idempotent operations. The result of starting or stopping the service multiple times is the same, # that is, no startup operation will be performed for the running service. In the same way, it's the same with stopping.' Restarted' always restarts the service, # 'reloaded' always rereads the configuration file, and if the service is not running,' reloaded starts the service. # (at least one of state and enabled)

Set nginx to boot:

Ansible test-m service-a "name=nginx enabled=yes"-o-f 8

Start the nginx service:

Ansible test-m service-a "name=nginx state=started"-o-f 8

Systemd module

Manage systemd-style services. Systemd--Ansible official instruction document

Ansible-doc-s systemd- name: Manage services systemd: daemon_reload: # determine whether you want to reload once before performing all the actions. The value is yes/no. Enabled: # whether to set boot self-boot. Masked: # whether to do mask (hiding, masking) processing on this unit. Unit after mask will not start. Name: # name of service to be operated. It can be name or name.service. State: # 'started'/'stopped' is idempotent. But restarted and reloaded always execute

With regard to masked, let me give you an example. When we use docker, we sometimes encounter errors like this:

Failed to start docker.service: Unit docker.service is masked.

At this time, we cannot use restart/start to start docker, because docker has been mask ~, we can use the following command to start docker:

Systemctl unmask docker.servicesystemctl unmask docker.socketsystemctl start docker.service user Management Module user

In the same way, there is also a group management module group, so there is no need to explain it. Similarly, when you create a user, a group with the same name is created by default.

User--Ansible official instruction document

Group--Ansible official instruction document

Ansible-doc-s user- name: Manage user accounts user: name: # the user name to create, modify, and remove. Password: # sets the user password. Only an encrypted password can be used as a value here. System: # state=present set to yes means to create a system user, which can only be used to create and cannot be used to modify an existing user as a system user. State: # create user (present) or delete user (absent). The default is present. Create_home: # create a home directory, or an existing user but a home directory does not exist. If set to no, the home directory is not created. Home: # specify the home directory path to be created move_home: # if set to yes, "home=" means to move the home directory to the path specified by this option. Uid: # set the user's uid group: # set the user's primary group groups: # add the user to the auxiliary group list. If you set groups=, the user is removed from all auxiliary groups. Shell: # sets the user's shell. Force: # in conjunction with 'state=absent', it is equivalent to' userdel-- force', which forces the deletion of users, home directories, and mailing lists. Remove: # when working with 'state=absent', it's equivalent to' userdel-- remove', which deletes home directories and mailing lists. Update_password: # user is an idempotent module. "always" will always change the password. "on_create" will only set the password when the user is created.

Create a system user and specify shell:

Ansible test-m user-a "name=wtf system=yes shell=/bin/bash"

Delete a user:

Ansible test-m user-a "name=wtf state=absent"

Specify that update_password=always will always change the user's password, regardless of whether the user already exists. Update_password=on_create, on the other hand, sets the password only when a new user is created, and does not change the user's password if the user already exists. The default value is always.

# # generate encrypted password openssl passwd-1 123456 $1 $U0LHGwj5 $bMocUtBQtkBwdplK.FIYe1

Ansible test-m user-a 'name=wtf_test password= "$1 $U0LHGwj5 $bMocUtBQtkBwdplK.FIYe1" update_password=always'

Create a user and specify a password, but do not change the password if the user already exists.

# # generate encrypted password openssl passwd-1 12345678 $1$ IPjg/uyu$YmJzqBHkqYrDHgrQ9zdJs/

Ansible test-m user-a 'name=wtf_td password= "$1$ IPjg/uyu$YmJzqBHkqYrDHgrQ9zdJs/" update_password=on_create'

Debug module

Used to output custom information, similar to echo, print and other output commands. Debug in ansible is mainly used to output variable value, expression value, and when condition judgment. The method of use is very simple.

Debug--Ansible official instruction document

Ansible-doc-s debug- name: Print statements during execution debug: msg: # outputs custom information. If omitted, normal characters are output. Var: # specifies the variables to debug. You can only specify variables, not custom information, and variables cannot be surrounded by {{}}, but direct variable names. Verbosity: # controls the debug level at which debug runs, with a valid value of N.

Examples are as follows:

Ansible test-m debug-a 'msg= "this is a test"'

Ansible test-m debug-a 'var=ansible_eth0.ipv4.address'

You can output the value of a variable, but the debug module is usually used in playbook when using a variable. Here is an example:

Tasks:-name: print any messages debug: msg= "you name is {{name}}" scheduled task module cron

The cron module is used to set up scheduled tasks and to manage environment variables in scheduled tasks. Cron--Ansible official instruction document

Ansible-doc-s cron- name: Manage cron.d and crontab entries cron: backup: # (yes/no) if set, the file names of these files cron_file: # custom cron_file are backed up before modifying the remote cron_file, which is indicated in / etc/cron.d using a relative path. You must also specify the user option user: # to specify which user's crontab will be modified. It defaults to root disabled: # disable a job in crontab and requires state=present env: # (yes/no) to set an environment variable that will be added at the top of the crontab. Use name and value to define the variable name and value job: # commands to be executed. If env is set, it represents the value of the environment variable, where job= "XXXX" is equivalent to value= "XXXX". # state=present minute: # (0-59, *, * / N) is required. If you don't write, default is * hour: # (0-23, *, * / N). If you don't write, default is * day: # (1-31, *, * / N). The default is * month: July (1-12, *, * / N). If it is not written, it defaults to * weekday: # week (0-6 for Sunday-Saturday, *). If it is not written, it defaults to * name: # string that describes the crontab task. However, if env is set, name is the name of the environment variable. Ask state=absent # to note that if name is not set and state=present is set, a new job entry will always be created, even if # the same entry special_time: # a nickname for the timing task already exists in cron_file to define when to run the job entry. # valid values are reboot/hourly/daily/weekly/monthly/yearly/annually. State: whether the status of # job or env is present (default) or absent. Present is used to create, absent is used to remove instructions

This blog is a reference to Ma long Shuai boss article collation and generation, belongs to the blogger reading notes, if there is infringement, please contact me, delete!

Finally, thank open source, embrace open source ~

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.