【mac】ansible安裝及基礎使用

安裝

環境釋放
　　mac　　10.12.5

#more /System/Library/CoreServices/SystemVersion.plist

安裝命令

#ruby -e "$(curl --insecure -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
#brew update
#brew install Ansible

安裝後hosts默認訪問位置

/usr/local/etc/ansible/hosts

公私鑰配置

建立公私鑰

ssh-keygen -t rsa -C 'yat_ho@163.com'

-t 指定密鑰類型，默認即 rsa ，能夠省略
-C 設置註釋文字，好比你的郵箱

默認存放位置

/Users/jenkins/.ssh/id_rsa

將公鑰複製到ssh服務器

ssh-copy-id jenkins@192.168.1.236

hosts配置

定義主機與組
定義一個IP爲192.168.1.21, SSH端口爲2135的主機

192.168.1.21:2135

定義一個別名爲jumper, SSH端口爲22, IP爲192.168.1.50的主機

jumper ansible_ssh_port=22 ansible_ssh_host=192.168.1.50

組成員主機名稱範例:

　　[test]
　　jenkis236 ansible_ssh_port=22 ansible_ssh_host=192.168.1.236

假如你有不少主機遵循某一種模式，你還能夠這樣來表示他們：

　　[webservers]
　　web[1:50].lightcloud.com


　　[database]
　　db-[a:f].lightcloud.com

定義主機變量

主機能夠指定變量, 後面能夠供Playbooks調用

　　[test]
　　jenkis236 ansible_ssh_port=22 ansible_ssh_host=192.168.1.236 http_port=8080　

定義組變量

[atlanta]
host1
host2
[atlanta:vars]
ntp_server=ntp.atlanta.example.com
proxy=proxy.atlanta.example.com

Ansible內置鏈接主機的變量

ansible_ssh_host
  ansible經過ssh鏈接的IP或者FQDN
ansible_ssh_port
  SSH鏈接端口
ansible_ssh_user
  默認SSH鏈接用戶
ansible_ssh_pass
  SSH鏈接的密碼（這是不安全的，ansible極力推薦使用--ask-pass選項或使用SSH keys）
ansible_sudo_pass
  sudo用戶的密碼
ansible_connection
  SSH鏈接的類型：local,ssh,paramiko，在ansible 1.2以前默認是paramiko，後來智能選擇，優先使用基於ControlPersist的ssh（支持的前提）
ansible_ssh_private_key_file
  SSH鏈接的公鑰文件
ansible_shell_type
  指定主機所使用的shell解釋器，默認是sh，你能夠設置成csh, fish等shell解釋器
ansible_python_interpreter
  用來指定python解釋器的路徑
ansible\_\*\_interpreter
  用來指定主機上其餘語法解釋器的路徑，例如ruby，perl等

　Ansible經常使用模塊及API

command: 執行遠程主機SHELL命令

ansible all -i /Users/jenkins/jenkins/lirbary/ansible_hosts/hosts_test -m command -a "ifconfig"

script: 遠程執行MASTER本地SHELL腳本.(相似scp+shell)

ansible test -i /Users/jenkins/jenkins/lirbary/ansible_hosts/hosts_test -m script -a "../Env_update_shell/test.sh"

copy：實現主控端向目標主機拷貝文件, 相似scp功能.

ansible test -i /Users/jenkins/jenkins/lirbary/ansible_hosts/hosts -m copy -a "src=~/test.sh dest=/tmp/ owner=root group=root mode=0755"

stat：獲取遠程文件狀態信息, 包括atime, ctime, mtime, md5, uid, gid等信息.

ansible test -i /Users/jenkins/jenkins/lirbary/ansible_hosts/hosts_test -m stat -a "path=/Users/jenkins/jenkins/"

get_url:實如今遠程主機下載指定URL到本地.

ansible test -i /Users/jenkins/jenkins/lirbary/ansible_hosts/hosts_test -m get_url -a "url=http://www.cnblogs.com/yatho dest=/tmp/index.html mode=0400 force=yes"

yum:Linux包管理平臺操做, 常見都會有yum和apt, 此處會調用yum管理模式

ansible servers -m yum -a "name=curl state=latest"

cron:遠程主機crontab配置

ansible webservers -m cron -a "name='check dir' hour='5,2' job='ls -alh > /dev/null'"

service:遠程主機系統服務管理

# ansible webservers -m service -a "name=crond state=stopped"
# ansible webservers -m service -a "name=crond state=restarted"
# ansible webservers -m service -a "name=crond state=reloaded"

user:user

添加用戶:
# ansible webservers -m user -a "name=johnd comment='John Doe'"
刪除用戶:
# ansible webservers -m user -a "name=johnd state=absent remove=yes"

　playbook

playbook介紹

playbook是一個不一樣於使用Ansible命令行執行方式的模式, 其功能是將大量命令行配置集成到一塊兒造成一個可定製的多主機配置管理部署工具.

它經過YAML格式定義, 能夠實現向多臺主機的分發應用部署.

 

如下給你們詳細介紹一個針對nginx嵌套複用結構的playbook部署實例:

1. 構建目錄結構

# cd /etc/ansible/

# mkdir group_vars

# mkdir roles

2.定義host

# vi /etc/ansible/hosts

[webservers]
client01.example.com
client02.example.com
[nginx01]
client01.example.com
[nginx02]
client02.example.com

3.定義變量

# vi /etc/ansible/group_vars/nginx01

worker_processes: 4
num_cpus: 4
max_open_file: 65506
root: /data
remote_user: root

# vi /etc/ansible/group_vars/nginx02

worker_processes: 2
num_cpus: 2
max_open_file: 35506
root: /www
remote_user: root

Tips:這裏在group_vars下定義的文件名必須對應hosts文件下的group標籤, 經過這裏定義的不一樣參數從而部署不一樣類型的主機配置.

 

4.建立roles入口文件

# vi /etc/ansible/site.yml

- hosts: webservers
  roles:
  - base_env
- hosts: nginx01
  roles:
  - nginx01
- hosts: nginx02
  roles:
  - nginx02

　　

Tips: 這裏的roles:下的字符串需對應roles目錄下的目錄名.

 

5.定義全局role base_env

建立目錄結構

# mkdir -p /etc/ansible/roles/base_env/tasks 

# vi /etc/ansible/roles/base_env/tasks/main.yml

 

# 將EPEL的yum源配置文件傳送到客戶端
- name: Create the contains common plays that will run on all nodes 
  copy: src=epel.repo dest=/etc/yum.repos.d/epel.repo
- name: Create the GPG key for EPEL
  copy: src=RPM-GPG-KEY-EPEL-6 dest=/etc/pki/rpm-gpg
  
# 關閉SELINUX
- name: test to see if selling is running
  command: getenforce
  register: sestatus
  changed_when: false

# 刪除iptables默認規則並保存
- name: remove the default iptables rules
  command: iptables -F
- name: save iptables rules
  command: service iptables save

將對應須要拷貝到遠程的文件複製到base_env/files目錄下

# mkdir -p  /etc/ansible/roles/base_env/files

# cp /etc/yum.repos.d/epel.repo /etc/ansible/roles/base_env/files

# cp /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6 /etc/ansible/roles/base_env/files

6. 定義nginx01和ngnix02 role

建立目錄結構

# mkdir -p /etc/ansible/roles/nginx{01,02}

# mkdir -p /etc/ansible/roles/nginx01/tasks

# mkdir -p /etc/ansible/roles/nginx02/tasks

# vi /etc/ansible/roles/nginx01/tasks/main.yml

 

# 安裝nginx最新版本
- name: ensure nginx is at the latest version
  yum: pkg=nginx state=latest

# 將nginx配置文件傳送到遠程目錄
- name: write the nginx config file
  template: src=nginx.conf dest=/etc/nginx/nginx.conf
  notify: restart nginx # 重啓nginx

# 建立nginx根目錄
- name: Create Web Root
  file: dest={{ root }} mode=775 state=directory owner=nginx group=nginx
  notify: reload nginx
- name: ensure nginx is running
  service: name=nginx state=restarted
 

 

# cp /home/ansible/roles/nginx01/tasks/main.yml /home/ansible/roles/nginx02/tasks/main.yml

　　

7.定義files

# mkdir -p /etc/ansible/roles/nginx01/templates

# mkdir -p /etc/ansible/roles/nginx02/templates

# vi /etc/ansible/roles/nginx01/templates/nginx.conf

# For more information on configuration, see: 

user              nginx;  
worker_processes  {{ worker_processes }};  
{% if num_cpus == 2 %}  
worker_cpu_affinity 01 10;  
{% elif num_cpus == 4 %}  
worker_cpu_affinity 1000 0100 0010 0001;  
{% elif num_cpus >= 8 %}  
worker_cpu_affinity 00000001 00000010 00000100 00001000 00010000 00100000 01000000 10000000;  
{% else %}  
worker_cpu_affinity 1000 0100 0010 0001;  
{% endif %}  
worker_rlimit_nofile {{ max_open_file }};  
  
error_log  /var/log/nginx/error.log;  
#error_log  /var/log/nginx/error.log  notice;  
#error_log  /var/log/nginx/error.log  info;  
  
pid        /var/run/nginx.pid;  
  
events {  
    worker_connections  {{ max_open_file }};  
}  
  
  
http {  
    include       /etc/nginx/mime.types;  
    default_type  application/octet-stream;  
  
    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '  
                      '$status $body_bytes_sent "$http_referer" '  
                      '"$http_user_agent" "$http_x_forwarded_for"';  
  
    access_log  /var/log/nginx/access.log  main;  
  
    sendfile        on;  
    #tcp_nopush     on;  
  
    #keepalive_timeout  0;  
    keepalive_timeout  65;  
  
    #gzip  on;  
      
    # Load config files from the /etc/nginx/conf.d directory  
    # The default server is in conf.d/default.conf  
    #include /etc/nginx/conf.d/*.conf;  
    server {  
        listen       80 default_server;  
        server_name  _;  
  
        #charset koi8-r;  
  
        #access_log  logs/host.access.log  main;  
  
        location / {  
            root   {{ root }};  
            index  index.html index.htm;  
        }  
  
        error_page  404              /404.html;  
        location = /404.html {  
            root   /usr/share/nginx/html;  
        }  
  
        # redirect server error pages to the static page /50x.html  
        #  
        error_page   500 502 503 504  /50x.html;  
        location = /50x.html {  
            root   /usr/share/nginx/html;  
        }  
  
    }  
  
} 

　　

Tip: worker_processes, num_cpus, max_open_file, root等參數會調用group_vars目錄下配置文件中相應的變量值

# cp /etc/ansible/roles/nginx01/templates/nginx.conf  /etc/ansible/roles/nginx02/templates/nginx.conf

8.執行playbook

# ansible-playbook -i /etc/ansible/hosts /etc/ansible/site.yml -f 10

Tips: -f 爲啓動10個並行進程執行playbook, -i 定義inventory host文件, site.yml 爲入口文件 

 

PLAY [webservers] ************************************************************* 

GATHERING FACTS *************************************************************** 
ok: [client02.example.com]
ok: [client01.example.com]

TASK: [base_env | Create the contains common plays that will run on all nodes] *** 
ok: [client01.example.com]
ok: [client02.example.com]

TASK: [base_env | Create the GPG key for EPEL] ******************************** 
ok: [client02.example.com]
ok: [client01.example.com]

TASK: [base_env | test to see if selling is running] ************************** 
ok: [client01.example.com]
ok: [client02.example.com]

TASK: [base_env | remove the default iptables rules] ************************** 
changed: [client02.example.com]
changed: [client01.example.com]

TASK: [base_env | save iptables rules] **************************************** 
changed: [client01.example.com]
changed: [client02.example.com]

PLAY [nginx01] **************************************************************** 

GATHERING FACTS *************************************************************** 
ok: [client01.example.com]

TASK: [nginx01 | ensure nginx is at the latest version] *********************** 
ok: [client01.example.com]

TASK: [nginx01 | write the nginx config file] ********************************* 
ok: [client01.example.com]

TASK: [nginx01 | Create Web Root] ********************************************* 
ok: [client01.example.com]

TASK: [nginx01 | ensure nginx is running] ************************************* 
changed: [client01.example.com]

PLAY [nginx02] **************************************************************** 

GATHERING FACTS *************************************************************** 
ok: [client02.example.com]

TASK: [nginx02 | ensure nginx is at the latest version] *********************** 
ok: [client02.example.com]

TASK: [nginx02 | write the nginx config file] ********************************* 
ok: [client02.example.com]

TASK: [nginx02 | Create Web Root] ********************************************* 
ok: [client02.example.com]

TASK: [nginx02 | ensure nginx is running] ************************************* 
changed: [client02.example.com]

PLAY RECAP ******************************************************************** 
client01.example.com       : ok=11   changed=3    unreachable=0    failed=0   
client02.example.com       : ok=11   changed=3    unreachable=0    failed=0 

最終部署目錄結構以下

# tree /etc/ansible/

/etc/ansible/
├── ansible.cfg
├── group_vars
│   ├── nginx01
│   └── nginx02
├── hosts
├── hosts.bak
├── roles
│   ├── base_env
│   │   ├── files
│   │   │   ├── epel.repo
│   │   │   └── RPM-GPG-KEY-EPEL-6
│   │   └── tasks
│   │       └── main.yml
│   ├── nginx01
│   │   ├── tasks
│   │   │   └── main.yml
│   │   └── templates
│   │       └── nginx.conf
│   └── nginx02
│       ├── tasks
│       │   └── main.yml
│       └── templates
│           └── nginx.conf
└── site.yml

 jenkins關聯配置

Choice Parameter
　　deploy_environment　　定義部署環境名　dev,test,uat,pdt
Execute shell 　　開頭和結尾的set +x, set -x用來打開和關閉該部分的擴展參數及命令 　　cd $WORKSPACE/leon-playbook-phpcms1.1　　ansible --version　　ansible-playbook -i inventory/$deploy_environment ./deploy.yml -e project=phpcms -e branch=$branch_selector -e env=$deploy_environment 　　-i 用來自定義ansible host文件路徑, ./deploy.yml爲ansible-playbook入口文件, -e 後可跟給當前session添加的環境變量.