kitchen-ansible 0.0.22 → 0.0.23

Sign up to get free protection for your applications and to get access to all the features.
Files changed (9) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +195 -195
  3. data/kitchen-ansible.gemspec +35 -35
  4. data/lib/kitchen-ansible/version.rb +5 -5
  5. data/lib/kitchen/provisioner/ansible/config.rb +156 -150
  6. data/lib/kitchen/provisioner/ansible/librarian.rb +83 -83
  7. data/lib/kitchen/provisioner/ansible_playbook.rb +768 -709
  8. data/provisioner_options.md +99 -96
  9. metadata +3 -3
data/provisioner_options.md CHANGED
@@ -1,96 +1,99 @@
1
-
2
- # Provisioner Options
3
-
4
- key | default value | Notes
5
- ----|---------------|--------
6
- ansible_version | "latest"| desired version, affects apt installs
7
- ansible_sudo | true | drives whether ansible-playbook is executed as root or as the current authenticated user
8
- ansible_platform | naively tries to determine | OS platform of server
9
- require_ansible_repo | true | Set if using a ansible install from yum or apt repo
10
- ansible_apt_repo | "ppa:ansible/ansible" | apt repo. see https://launchpad.net /~ansible/+archive/ubuntu/ansible or rquillo/ansible
11
- ansible_yum_repo | https://download.fedoraproject.org /pub/epel/6/i386/epel-release-6-8.noarch.rpm | yum repo
12
- roles_path | roles | ansible repo roles directory
13
- group_vars_path | group_vars | ansible repo group_vars directory
14
- host_vars_path | host_vars | ansible repo hosts directory
15
- filter_plugins | filter_plugins | ansible repo filter_plugins directory
16
- additional_copy_path | | arbitrary array of files and directories to copy into test environment, relative to CWD. (eg, vars or included playbooks)
17
- extra_vars | Hash.new | Hash to set the extra_vars passed to ansibile-playbook command
18
- playbook | 'default.yml' | playbook for ansible-playbook to run
19
- modules_path | | ansible repo manifests directory
20
- ansible_verbose| false| Extra information logging
21
- ansible_verbosity| 1| Sets the verbosity flag appropriately (e.g.: `1 => '-v', 2 => '-vv', 3 => '-vvv" ...`) Valid values are one of: `1, 2, 3, 4` OR `:info, :warn, :debug, :trace`.
22
- ansible_check| false| Sets the `--check` flag when running Ansible
23
- ansible_diff| false| Sets the `--diff` flag when running Ansible
24
- update_package_repos| true| update OS repository metadata
25
- require_ruby_for_busser|true|install ruby to run busser for tests
26
- ansiblefile_path | | Path to Ansiblefile
27
- requirements_path | | Path to ansible-galaxy requirements
28
- ansible_vault_password_file| | Path of Ansible Vault Password File
29
- ansible_connection | local | Connection for Hosts and Groups
30
- ansible_inventory_file | hosts | Custom inventory file
31
- require_ansible_omnibus | false | Set if using omnibus ansible install
32
- ansible_omnibus_url | | omnibus ansible install location.
33
- ansible_omnibus_remote_path | "/opt/ansible" | Server Installation location of an omnibus ansible install.
34
- require_chef_for_busser|false|install chef to run busser for tests. NOTE: kitchen 1.4 only requires ruby to run busser so this is not required.
35
- chef_bootstrap_url |https://www.getchef.com /chef/install.sh| the chef install
36
- require_ansible_source | false | Install Ansible from source using method described here: http://docs.ansible.com/intro_installation.html#running-from-source. Only works on Debian/Ubuntu at present.
37
-
38
- ## Configuring Provisioner Options
39
-
40
- The provisioner can be configured globally or per suite, global settings act as defaults for all suites, you can then customise per suite, for example:
41
-
42
- ```yaml
43
- ---
44
- driver:
45
- name: vagrant
46
-
47
- provisioner:
48
- name: ansible_playbook
49
- roles_path: roles
50
- hosts: tomcat-servers
51
- require_ansible_repo: true
52
- ansible_verbose: true
53
- ansible_verbosity: 2
54
- ansible_diff: true
55
-
56
- platforms:
57
- - name: nocm_ubuntu-12.04
58
- driver_plugin: vagrant
59
- driver_config:
60
- box: nocm_ubuntu-12.04
61
- box_url: http://puppet-vagrant-boxes.puppetlabs.com/ubuntu-server-12042-x64-vbox4210-nocm.box
62
-
63
- suites:
64
- - name: default
65
- ```
66
-
67
- **NOTE:** With Test-Kitchen 1.4 you not longer need chef install to run the tests. You just need ruby installed version 1.9 or higher and also add to the .kitchen.yml file
68
-
69
- ```yaml
70
- verifier:
71
- ruby_bindir: '/usr/bin'
72
- ```
73
- where /usr/bin is the location of the ruby command.
74
-
75
-
76
- in this example, vagrant will download a box for ubuntu 1204 with no configuration management installed, then install the latest ansible and ansible playbook against a ansible repo from the /repository/ansible_repo directory using the default manifest site.yml
77
-
78
- To override a setting at the suite-level, specify the setting name under the suite's attributes:
79
-
80
- ```yaml
81
- suites:
82
- - name: server
83
- attributes:
84
- extra_vars:
85
- server_installer_url: http://downloads.app.com/v1.0
86
- tags:
87
- - server
88
- ```
89
-
90
- ### Per-suite Structure
91
-
92
- It can be beneficial to keep different Ansible layouts for different suites. Rather than having to specify the roles, modules, etc for each suite, you can create the following directory structure and they will automatically be found:
93
-
94
- $kitchen_root/ansible/$suite_name/roles
95
- $kitchen_root/ansible/$suite_name/modules
96
- $kitchen_root/ansible/$suite_name/Ansiblefile
1
+
2
+ # Provisioner Options
3
+
4
+ key | default value | Notes
5
+ ----|---------------|--------
6
+ ansible_version | "latest"| desired version, affects apt installs
7
+ ansible_sudo | true | drives whether ansible-playbook is executed as root or as the current authenticated user
8
+ ansible_platform | naively tries to determine | OS platform of server
9
+ require_ansible_repo | true | Set if using a ansible install from yum or apt repo
10
+ ansible_apt_repo | "ppa:ansible/ansible" | apt repo. see https://launchpad.net /~ansible/+archive/ubuntu/ansible or rquillo/ansible
11
+ ansible_yum_repo | https://download.fedoraproject.org /pub/epel/6/i386/epel-release-6-8.noarch.rpm | yum repo
12
+ ansible_sles_repo | http://download.opensuse.org/repositories/systemsmanagement/SLE_12/systemsmanagement.repo | zypper suse ansible repo
13
+ python_sles_repo | http://download.opensuse.org/repositories/devel:/languages:/python/SLE_12/devel:languages:python.repo | zypper suse python repo
14
+ roles_path | roles | ansible repo roles directory
15
+ group_vars_path | group_vars | ansible repo group_vars directory
16
+ host_vars_path | host_vars | ansible repo hosts directory
17
+ filter_plugins | filter_plugins | ansible repo filter_plugins directory
18
+ lookup_plugins | lookup_plugins | ansible repo lookup_plugins directory
19
+ additional_copy_path | | arbitrary array of files and directories to copy into test environment, relative to CWD. (eg, vars or included playbooks)
20
+ extra_vars | Hash.new | Hash to set the extra_vars passed to ansibile-playbook command
21
+ playbook | 'default.yml' | playbook for ansible-playbook to run
22
+ modules_path | | ansible repo manifests directory
23
+ ansible_verbose| false| Extra information logging
24
+ ansible_verbosity| 1| Sets the verbosity flag appropriately (e.g.: `1 => '-v', 2 => '-vv', 3 => '-vvv" ...`) Valid values are one of: `1, 2, 3, 4` OR `:info, :warn, :debug, :trace`.
25
+ ansible_check| false| Sets the `--check` flag when running Ansible
26
+ ansible_diff| false| Sets the `--diff` flag when running Ansible
27
+ update_package_repos| true| update OS repository metadata
28
+ require_ruby_for_busser|true|install ruby to run busser for tests
29
+ ansiblefile_path | | Path to Ansiblefile
30
+ requirements_path | | Path to ansible-galaxy requirements
31
+ ansible_vault_password_file| | Path of Ansible Vault Password File
32
+ ansible_connection | local | Connection for Hosts and Groups
33
+ ansible_inventory_file | hosts | Custom inventory file
34
+ require_ansible_omnibus | false | Set if using omnibus ansible install
35
+ ansible_omnibus_url | | omnibus ansible install location.
36
+ ansible_omnibus_remote_path | "/opt/ansible" | Server Installation location of an omnibus ansible install.
37
+ require_chef_for_busser|false|install chef to run busser for tests. NOTE: kitchen 1.4 only requires ruby to run busser so this is not required.
38
+ chef_bootstrap_url |https://www.getchef.com /chef/install.sh| the chef install
39
+ require_ansible_source | false | Install Ansible from source using method described here: http://docs.ansible.com/intro_installation.html#running-from-source. Only works on Debian/Ubuntu at present.
40
+
41
+ ## Configuring Provisioner Options
42
+
43
+ The provisioner can be configured globally or per suite, global settings act as defaults for all suites, you can then customise per suite, for example:
44
+
45
+ ```yaml
46
+ ---
47
+ driver:
48
+ name: vagrant
49
+
50
+ provisioner:
51
+ name: ansible_playbook
52
+ roles_path: roles
53
+ hosts: tomcat-servers
54
+ require_ansible_repo: true
55
+ ansible_verbose: true
56
+ ansible_verbosity: 2
57
+ ansible_diff: true
58
+
59
+ platforms:
60
+ - name: nocm_ubuntu-12.04
61
+ driver_plugin: vagrant
62
+ driver_config:
63
+ box: nocm_ubuntu-12.04
64
+ box_url: http://puppet-vagrant-boxes.puppetlabs.com/ubuntu-server-12042-x64-vbox4210-nocm.box
65
+
66
+ suites:
67
+ - name: default
68
+ ```
69
+
70
+ **NOTE:** With Test-Kitchen 1.4 you not longer need chef install to run the tests. You just need ruby installed version 1.9 or higher and also add to the .kitchen.yml file
71
+
72
+ ```yaml
73
+ verifier:
74
+ ruby_bindir: '/usr/bin'
75
+ ```
76
+ where /usr/bin is the location of the ruby command.
77
+
78
+
79
+ in this example, vagrant will download a box for ubuntu 1204 with no configuration management installed, then install the latest ansible and ansible playbook against a ansible repo from the /repository/ansible_repo directory using the default manifest site.yml
80
+
81
+ To override a setting at the suite-level, specify the setting name under the suite's attributes:
82
+
83
+ ```yaml
84
+ suites:
85
+ - name: server
86
+ attributes:
87
+ extra_vars:
88
+ server_installer_url: http://downloads.app.com/v1.0
89
+ tags:
90
+ - server
91
+ ```
92
+
93
+ ### Per-suite Structure
94
+
95
+ It can be beneficial to keep different Ansible layouts for different suites. Rather than having to specify the roles, modules, etc for each suite, you can create the following directory structure and they will automatically be found:
96
+
97
+ $kitchen_root/ansible/$suite_name/roles
98
+ $kitchen_root/ansible/$suite_name/modules
99
+ $kitchen_root/ansible/$suite_name/Ansiblefile
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: kitchen-ansible
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.22
4
+ version: 0.0.23
5
5
  platform: ruby
6
6
  authors:
7
7
  - Neill Turner
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2015-07-24 00:00:00.000000000 Z
11
+ date: 2015-08-15 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: test-kitchen
@@ -122,7 +122,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
122
122
  version: '0'
123
123
  requirements: []
124
124
  rubyforge_project: "[none]"
125
- rubygems_version: 2.4.8
125
+ rubygems_version: 2.2.2
126
126
  signing_key:
127
127
  specification_version: 4
128
128
  summary: ansible provisioner for test-kitchen