kitchen-ansible 0.0.22 → 0.0.23

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 74e679fe4df9c78f74ed295604bbe568ca442886
-  data.tar.gz: 5da1d01055c7f7656eedb5b07ca2ab0ff75a67e7
+  metadata.gz: 7bd5d03676603db05fb892388318d229f975c887
+  data.tar.gz: 467e3c95ed635db2fbf3c335a07ab4c9c448e2bb
 SHA512:
-  metadata.gz: 46c98276669a89b8e9520bc233fac1dbf1b1bc763b1f94c5dc1014ee11d6d122eefe8f2353b7031a511b656e5222e4cfa6c7f922186b3e102a73144c2379ac4f
-  data.tar.gz: 19b621bc52217111af748ea94295cd2c04e5afd11502cc950a12798c95e72fc64a73298822b7271f44492d11c10553fe857d6473985d9471afee01d255af7c98
+  metadata.gz: c5df42d3b62176caebc820e2fb27ec5a1f4851d6c5905409b72d09a5d779fda9bbc8c3e2236f1d99a4a5f03980969b51d0dcdb7fdc621a0837cb1cf86273fe83
+  data.tar.gz: eb0c56c645a1f84d583c65c47db0f4bd66bc1458bfc2a52b2c9de402e0d294a07eec8707f647ec67ebba3dcdd6fc5f275d54750686ca491aabeb11fad1f163e0

data/README.md

@@ -1,195 +1,195 @@
-# kitchen-ansible
-
-[![Gem Version](https://badge.fury.io/rb/kitchen-ansible.svg)](http://badge.fury.io/rb/kitchen-ansible)
-[![Gem Downloads](http://ruby-gem-downloads-badge.herokuapp.com/kitchen-ansible?type=total&color=brightgreen)](https://rubygems.org/gems/kitchen-ansible)
-[![Build Status](https://travis-ci.org/neillturner/kitchen-ansible.png)](https://travis-ci.org/neillturner/kitchen-ansible)
-
-A Test Kitchen Provisioner for Ansible
-
-The provisioner works by passing the ansible repository based on attributes in .kitchen.yml & calling ansible-playbook.
-
-It installs Ansible on the server and runs ansible-playbook using host localhost.
-
-Has been tested against the Ubuntu 1204 and Centos 6.5 boxes running in vagrant/virtualbox.
-
-## Requirements
-You'll need a driver box without a chef installation so ansible can be installed.
-
-## Installation & Setup
-You'll need the test-kitchen & kitchen-ansible gem's installed in your system, along with kitchen-vagrant or some other suitable driver for test-kitchen.
-
-Please see the Provisioner Options (https://github.com/neillturner/kitchen-ansible/blob/master/provisioner_options.md).
-
-## Example kitchen.yml file
-
-based on the example ansible setup for tomcat at  https://github.com/ansible/ansible-examples/tree/master/tomcat-standalone
-
-```yaml
----
-driver:
-    name: vagrant
-
-provisioner:
-  name: ansible_playbook
-  roles_path: roles
-  hosts: tomcat-servers
-  require_ansible_repo: true
-  ansible_verbose: true
-  ansible_version:   1.6.2-1.el6
-  extra_vars:
-    a: b
-
-platforms:
-  - name: nocm_centos-6.5
-    driver_plugin: vagrant
-    driver_config:
-      box: nocm_centos-6.5
-      box_url: http://puppet-vagrant-boxes.puppetlabs.com/centos-65-x64-virtualbox-nocm.box
-      network:
-      - ['forwarded_port', {guest: 8080, host: 8080}]
-      - [ 'private_network', { ip: '192.168.33.11' } ]
-      
-verifier:
-  ruby_bindir: '/usr/bin'      
-```
-**NOTE:** With Test-Kitchen 1.4 you no 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
-
-```yaml
-  verifier:
-    ruby_bindir: '/usr/bin'
-```
-where /usr/bin is the location of the ruby command. 
-
-
-## Test-Kitchen/Ansible/Serverspec
-
-In the root directory for your Ansible role:
-
-Create a `.kitchen.yml`, much like one the described above:
-    
-```yaml
-  ---
-  driver:
-    name: vagrant
-
-  provisioner:
-    name: ansible_playbook
-    playbook: default.yml
-    ansible_yum_repo: "https://download.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm"
-    ansible_verbose: true
-    ansible_verbosity: 3
-    hosts: all
-
-  platforms:
-    - name: ubuntu-12.04
-      driver_config:
-        box: ubuntu/precise32
-    - name: centos-7
-      driver_config:
-         box: chef/centos-7.0
-
-  verifier:
-    ruby_bindir: '/usr/bin'    
-
-  suites:
-    - name: default
-```
-
-Then for serverspec:
-    
-```bash
-  mkdir -p test/integration/default/serverspec/localhost
-  echo "require 'serverspec'" >> test/integration/default/serverspec/spec_helper.rb
-  echo "set :backend, :exec" >> test/integration/default/serverspec/spec_helper.rb
-```
-
-Create a basic playbook `test/integration/default.yml` so that kitchen can use your role (this should include any dependencies for your role):
-    
-```yaml
-  ---
-  - name: wrapper playbook for kitchen testing "my_role"
-    hosts: localhost
-    roles:
-      - my_role
-```
-
-Create your serverspec tests in `test/integration/default/serverspec/localhost/my_roles_spec.rb`:
-    
-```ruby
-  require 'spec_helper'
-
-  if os[:family] == 'ubuntu'
-        describe '/etc/lsb-release' do
-          it "exists" do
-              expect(file('/etc/lsb-release')).to be_file
-          end
-        end
-  end
-
-  if os[:family] == 'redhat'
-    describe '/etc/redhat-release' do
-      it "exists" do
-          expect(file('/etc/redhat-release')).to be_file
-      end
-    end
-  end
-```
-
-### Testing multiple playbooks
-To test different playbooks in different suites you can easily overwrite the provisioner settings in each suite seperately.
-```yaml
----
-  driver:
-    name: vagrant
-
-  provisioner:
-    name: ansible_playbook
-
-  platforms:
-    - name: ubuntu-12.04
-      driver_config:
-        box: ubuntu/precise32
-    - name: centos-7
-      driver_config:
-         box: chef/centos-7.0
-
-  suites:
-    - name: database
-      provisioner:
-        playbook: postgres.yml
-        hosts: database
-    - name: application
-      provisioner:
-        playbook: web_app.yml
-        hosts: web_application
-```
-
-### Alternative Virtualization/Cloud providers for Vagrant
-This could be adapted to use alternative virtualization/cloud providers such as Openstack/AWS/VMware Fusion according to whatever is supported by Vagrant.
-```yaml
-platforms:
-    - name: ubuntu-12.04
-      driver_config:
-        provider: aws
-        box: my_base_box
-        # username is based on what is configured in your box/ami
-        username: ubuntu
-        customize:
-          access_key_id: "AKKJHG659868LHGLH"
-          secret_access_key: "G8t7o+6HLG876JGF/58"
-          ami: ami-7865ab765d
-          instance_type: t2.micro
-          # more customisation can go here, based on what the vagrant provider supports
-          #security-groups: []
-```
-
-*Notes*
-
-* The `default` in all of the above is the name of the test suite defined in the 'suites' section of your `.kitchen.yml`, so if you have more than suite of tests or change the name, you'll need to adapt my example accordingly.
-* serverspec test files *must* be named `_spec.rb`
-* Since I'm using Vagrant, my `box` definitions refer to Vagrant boxes, either standard, published boxes available from <http://atlas.hashicorp.com/boxes> or custom-created boxes (perhaps using [Packer][packer] and [bento][bento]), in which case you'll need to provide the url in `box_url`.
-
-[Serverspec]: http://serverspec.org
-[packer]: https://packer.io
-[bento]: https://github.com/chef/bento
-
+# kitchen-ansible
+
+[![Gem Version](https://badge.fury.io/rb/kitchen-ansible.svg)](http://badge.fury.io/rb/kitchen-ansible)
+[![Gem Downloads](http://ruby-gem-downloads-badge.herokuapp.com/kitchen-ansible?type=total&color=brightgreen)](https://rubygems.org/gems/kitchen-ansible)
+[![Build Status](https://travis-ci.org/neillturner/kitchen-ansible.png)](https://travis-ci.org/neillturner/kitchen-ansible)
+
+A Test Kitchen Provisioner for Ansible
+
+The provisioner works by passing the ansible repository based on attributes in .kitchen.yml & calling ansible-playbook.
+
+It installs Ansible on the server and runs ansible-playbook using host localhost.
+
+Has been tested against the Ubuntu 1204 and Centos 6.5 boxes running in vagrant/virtualbox.
+
+## Requirements
+You'll need a driver box without a chef installation so ansible can be installed.
+
+## Installation & Setup
+You'll need the test-kitchen & kitchen-ansible gem's installed in your system, along with kitchen-vagrant or some other suitable driver for test-kitchen.
+
+Please see the Provisioner Options (https://github.com/neillturner/kitchen-ansible/blob/master/provisioner_options.md).
+
+## Example kitchen.yml file
+
+based on the example ansible setup for tomcat at  https://github.com/ansible/ansible-examples/tree/master/tomcat-standalone
+
+```yaml
+---
+driver:
+    name: vagrant
+
+provisioner:
+  name: ansible_playbook
+  roles_path: roles
+  hosts: tomcat-servers
+  require_ansible_repo: true
+  ansible_verbose: true
+  ansible_version:   1.6.2-1.el6
+  extra_vars:
+    a: b
+
+platforms:
+  - name: nocm_centos-6.5
+    driver_plugin: vagrant
+    driver_config:
+      box: nocm_centos-6.5
+      box_url: http://puppet-vagrant-boxes.puppetlabs.com/centos-65-x64-virtualbox-nocm.box
+      network:
+      - ['forwarded_port', {guest: 8080, host: 8080}]
+      - [ 'private_network', { ip: '192.168.33.11' } ]
+      
+verifier:
+  ruby_bindir: '/usr/bin'      
+```
+**NOTE:** With Test-Kitchen 1.4 you no 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
+
+```yaml
+  verifier:
+    ruby_bindir: '/usr/bin'
+```
+where /usr/bin is the location of the ruby command. 
+
+
+## Test-Kitchen/Ansible/Serverspec
+
+In the root directory for your Ansible role:
+
+Create a `.kitchen.yml`, much like one the described above:
+    
+```yaml
+  ---
+  driver:
+    name: vagrant
+
+  provisioner:
+    name: ansible_playbook
+    playbook: default.yml
+    ansible_yum_repo: "https://download.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm"
+    ansible_verbose: true
+    ansible_verbosity: 3
+    hosts: all
+
+  platforms:
+    - name: ubuntu-12.04
+      driver_config:
+        box: ubuntu/precise32
+    - name: centos-7
+      driver_config:
+         box: chef/centos-7.0
+
+  verifier:
+    ruby_bindir: '/usr/bin'    
+
+  suites:
+    - name: default
+```
+
+Then for serverspec:
+    
+```bash
+  mkdir -p test/integration/default/serverspec/localhost
+  echo "require 'serverspec'" >> test/integration/default/serverspec/spec_helper.rb
+  echo "set :backend, :exec" >> test/integration/default/serverspec/spec_helper.rb
+```
+
+Create a basic playbook `test/integration/default.yml` so that kitchen can use your role (this should include any dependencies for your role):
+    
+```yaml
+  ---
+  - name: wrapper playbook for kitchen testing "my_role"
+    hosts: localhost
+    roles:
+      - my_role
+```
+
+Create your serverspec tests in `test/integration/default/serverspec/localhost/my_roles_spec.rb`:
+    
+```ruby
+  require 'spec_helper'
+
+  if os[:family] == 'ubuntu'
+        describe '/etc/lsb-release' do
+          it "exists" do
+              expect(file('/etc/lsb-release')).to be_file
+          end
+        end
+  end
+
+  if os[:family] == 'redhat'
+    describe '/etc/redhat-release' do
+      it "exists" do
+          expect(file('/etc/redhat-release')).to be_file
+      end
+    end
+  end
+```
+
+### Testing multiple playbooks
+To test different playbooks in different suites you can easily overwrite the provisioner settings in each suite seperately.
+```yaml
+---
+  driver:
+    name: vagrant
+
+  provisioner:
+    name: ansible_playbook
+
+  platforms:
+    - name: ubuntu-12.04
+      driver_config:
+        box: ubuntu/precise32
+    - name: centos-7
+      driver_config:
+         box: chef/centos-7.0
+
+  suites:
+    - name: database
+      provisioner:
+        playbook: postgres.yml
+        hosts: database
+    - name: application
+      provisioner:
+        playbook: web_app.yml
+        hosts: web_application
+```
+
+### Alternative Virtualization/Cloud providers for Vagrant
+This could be adapted to use alternative virtualization/cloud providers such as Openstack/AWS/VMware Fusion according to whatever is supported by Vagrant.
+```yaml
+platforms:
+    - name: ubuntu-12.04
+      driver_config:
+        provider: aws
+        box: my_base_box
+        # username is based on what is configured in your box/ami
+        username: ubuntu
+        customize:
+          access_key_id: "AKKJHG659868LHGLH"
+          secret_access_key: "G8t7o+6HLG876JGF/58"
+          ami: ami-7865ab765d
+          instance_type: t2.micro
+          # more customisation can go here, based on what the vagrant provider supports
+          #security-groups: []
+```
+
+*Notes*
+
+* The `default` in all of the above is the name of the test suite defined in the 'suites' section of your `.kitchen.yml`, so if you have more than suite of tests or change the name, you'll need to adapt my example accordingly.
+* serverspec test files *must* be named `_spec.rb`
+* Since I'm using Vagrant, my `box` definitions refer to Vagrant boxes, either standard, published boxes available from <http://atlas.hashicorp.com/boxes> or custom-created boxes (perhaps using [Packer][packer] and [bento][bento]), in which case you'll need to provide the url in `box_url`.
+
+[Serverspec]: http://serverspec.org
+[packer]: https://packer.io
+[bento]: https://github.com/chef/bento
+

data/kitchen-ansible.gemspec

@@ -1,35 +1,35 @@
-# encoding: utf-8
-
-$:.unshift File.expand_path('../lib', __FILE__)
-require 'kitchen-ansible/version'
-
-Gem::Specification.new do |s|
-  s.name          = "kitchen-ansible"
-  s.license       = "Apache-2.0"
-  s.version       = Kitchen::Ansible::VERSION
-  s.authors       = ["Neill Turner"]
-  s.email         = ["neillwturner@gmail.com"]
-  s.homepage      = "https://github.com/neillturner/kitchen-ansible"
-  s.summary       = "ansible provisioner for test-kitchen"
-  candidates = Dir.glob("{lib}/**/*") +  ['README.md', 'provisioner_options.md', 'kitchen-ansible.gemspec']
-  s.files = candidates.sort
-  s.platform      = Gem::Platform::RUBY
-  s.require_paths = ['lib']
-  s.rubyforge_project = '[none]'
-  s.description = <<-EOF
-== DESCRIPTION:
-
-Ansible Provisioner for Test Kitchen
-
-== FEATURES:
-
-Supports running ansible-playbook
-
-EOF
-  s.add_runtime_dependency 'test-kitchen'
-
-  s.add_development_dependency 'rspec'
-  s.add_development_dependency 'pry'
-  s.add_development_dependency 'rake'
-  s.add_runtime_dependency 'librarian-ansible'
-end
+# encoding: utf-8
+
+$:.unshift File.expand_path('../lib', __FILE__)
+require 'kitchen-ansible/version'
+
+Gem::Specification.new do |s|
+  s.name          = "kitchen-ansible"
+  s.license       = "Apache-2.0"
+  s.version       = Kitchen::Ansible::VERSION
+  s.authors       = ["Neill Turner"]
+  s.email         = ["neillwturner@gmail.com"]
+  s.homepage      = "https://github.com/neillturner/kitchen-ansible"
+  s.summary       = "ansible provisioner for test-kitchen"
+  candidates = Dir.glob("{lib}/**/*") +  ['README.md', 'provisioner_options.md', 'kitchen-ansible.gemspec']
+  s.files = candidates.sort
+  s.platform      = Gem::Platform::RUBY
+  s.require_paths = ['lib']
+  s.rubyforge_project = '[none]'
+  s.description = <<-EOF
+== DESCRIPTION:
+
+Ansible Provisioner for Test Kitchen
+
+== FEATURES:
+
+Supports running ansible-playbook
+
+EOF
+  s.add_runtime_dependency 'test-kitchen'
+
+  s.add_development_dependency 'rspec'
+  s.add_development_dependency 'pry'
+  s.add_development_dependency 'rake'
+  s.add_runtime_dependency 'librarian-ansible'
+end