vagrant-masonry 0.13.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: f70083dc0e5b9557ca2f5ac0c69396d563dd1940
+  data.tar.gz: 0b1a113f963a73d8aef8f6f94b8b8f4ecc72928d
+SHA512:
+  metadata.gz: 2b6d2d39c277264a06e50cf8e96689fc87054c6c698fd2b250f42d2cf94b8b86e7ca6ab2a4cecc16a471332c039e58ee92d530015a52f9e7f791ee708bd717d0
+  data.tar.gz: e1c6fcdf439e40b332b430d668bf27b10124ec05901e02792119cda062da2c7b2680750462b1f781600fd2e40de2e9e5dd5f32ad76dae368c7318bd7ff96e2e5

data/.gitignore

@@ -0,0 +1,3 @@
+.bundle
+.yardoc
+doc

data/.yardopts

@@ -0,0 +1,6 @@
+--markup markdown
+-
+README.md
+docs/GettingStarted.markdown
+CHANGELOG
+LICENSE

data/CHANGELOG

@@ -0,0 +1,190 @@
+CHANGELOG
+=========
+
+0.13.0
+------
+
+2014-11-23
+
+New feature:
+
+  * Added support for Vagrant Azure provider
+
+0.12.0
+------
+
+2014-10-07
+
+This is a backwards feature release.
+
+  * (GH-22) Support for VMware Workstation providers.
+
+  * (GH-24) New YAML loader which pre-processes data using ERB to enable
+    dynamic interpolation of values.
+
+  * (GH-25) Support for VMware vSphere providers.
+
+  * (GH-28) Support for libvirt providers.
+
+  * Support for the file provisioner.
+
+Thanks to Nan Liu and Lukas Stanek for their contributions to this release.
+
+0.11.0
+------
+
+2014-09-17
+
+This is a backwards feature release.
+
+  * (GH-23) Fix misspelling of `disabled` option for synced folders.
+
+  * (GH-26) Enable configuration of global WinRM options.
+
+  * Enable configuration of global SSH options.
+
+  * Enable configuration of additional box download options such as
+    checksumming and versioning.
+
+Thanks to Nan Liu and Ethan Brown for their contributions to this release.
+
+0.10.1
+------
+
+2014-07-08
+
+This is a backwards bugfix release.
+
+  * Fixed an issue where VM definitions would end up with linked copies of an
+    array because cloning was not used.
+
+  * The `id` attribute can now be specified for `forwarded_port`.
+
+0.10.0
+------
+
+2014-05-22
+
+This is a backwards compatible feature release.
+
+  * (GH-20) Add `communicator` to the VM model. This supports Windows machines
+	  running under Vagrant 1.6.
+
+0.9.0
+-----
+
+2014-05-21
+
+This is a backwards compatible feature release.
+
+  * (GH-19) Multiple providers can be configured by specifying an array of
+	  options.
+
+0.8.0
+-----
+
+2014-05-02
+
+  * (GH-16) Add vmware_fusion provider implementation.
+
+0.7.1
+-----
+
+2014-04-22
+
+  * (GH-17) Call DeepMerge directly to avoid shadowing during loading
+
+### Thanks
+
+Thanks to Charlie Sharpsteen creating this release.
+
+0.7.0
+-----
+
+2014-03-19
+
+This is a backwards compatible feature release.
+
+  * (GH-15) Deep merge data when loading configurations. This allows
+    individual top level keys to be split up between files.
+
+Thanks to Charlie Sharpsteen creating this release.
+
+0.6.0
+-----
+
+2013-10-17
+
+This is a backwards incompatible feature release.
+
+  * Loader::YAML#yamldir can now accept a list of directories to use for
+    configuration.
+
+Thanks to Charlie Sharpsteen for his help on this release.
+
+0.5.0
+-----
+
+2013-09-18
+
+This is a backwards compatible feature release.
+
+  * (GH-12) Add vm 'guest' platform parameter
+
+0.4.0
+-----
+
+2013-08-28
+
+This is a backwards compatible feature release.
+
+  * (GH-11) Register puppet and puppet_server as provisioners
+
+0.3.1
+-----
+
+This is a backwards compatible bugfix release.
+
+  * Fixed the whole missing variable for ClassRegistry::DuplicateEntry.
+    This time, for realsies.
+
+0.3.0
+-----
+
+This is a backwards compatible bugfix and feature release
+
+### User notes
+
+#### Enhancements
+
+  * (GH-6) New filter: `boxes`
+  * box_url is now a supported vm attribute
+
+#### Bugfixes
+
+  * Better error handling when no configuration is set
+  * Add missing variable when raising ClassRegistry::DuplicateEntry error
+
+0.2.0
+-----
+
+2013-08-16
+
+This is a backwards compatible bugfix and feature release.
+
+### User notes
+
+#### Enhancements
+
+  * (GH-10) Add support to vm model for hostname.
+
+#### Bugfixes
+
+  * (GH-9) Correctly merge VM attributes by concatentating arrays.
+
+0.1.0
+-----
+
+2013-08-08
+
+Initial release.

data/Gemfile

@@ -0,0 +1,16 @@
+source 'https://rubygems.org'
+
+gemspec
+
+group :development do
+  # We depend on Vagrant for development, but we don't add it as a
+  # gem dependency because we expect to be installed within the
+  # Vagrant environment itself using `vagrant plugin`.
+  gem "vagrant", :git => "git://github.com/mitchellh/vagrant.git"
+  gem "yard"
+  gem "redcarpet"
+end
+
+if File.exists? "#{__FILE__}.local"
+  eval(File.read("#{__FILE__}.local"), binding)
+end

data/LICENSE

@@ -0,0 +1,15 @@
+Copyright 2013 Adrien Thebo (vagrant-config_builder)
+Copyright 2014 Jozef Izso (vagrant-masonry)
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+

data/README.md

@@ -0,0 +1,129 @@
+Vagrant Masonry - Config Builder
+======================
+
+Configure and manage your Vagrant environments using structured data.
+
+> Masonry is the craft of shaping rough pieces of rock into accurate geometrical shapes, at times simple, but some of considerable complexity, and then arranging the resulting stones to form structures.
+
+Synopsis
+--------
+
+This plugin provides an interface to the Vagrant configuration constructs in a
+logic free manner. You can format your input data to fit your needs and use
+`vagrant-masonry` to transform that into the needed Vagrant config.
+
+Example
+-------
+
+This example loads all yaml files in the config directory and generates a
+Vagrant config based on that information. File names are arbitrary and chosen
+for clarity.
+
+#### Directory structure
+
+```shell
+.
+├── config
+│   ├── roles.yaml
+│   └── vms.yaml
+└── Vagrantfile
+```
+
+#### Vagrantfile
+
+For pure yaml configurations, use yaml loader:
+```ruby
+require 'masonry'
+Vagrant.configure('2', &ConfigBuilder.load(
+  :yaml,
+  :yamldir,
+  File.expand_path('../config', __FILE__)
+))
+```
+
+For yaml erb configurations, use yaml_erb loader:
+```ruby
+require 'masonry'
+Vagrant.configure('2', &ConfigBuilder.load(
+  :yaml_erb,
+  :yamldir,
+  File.expand_path('../config', __FILE__)
+))
+```
+
+The yaml_erb loader would allow configuration such as:
+```yaml
+---
+roles:
+  puppet_apply:
+    provisioners:
+      - type: puppet
+        manifests_path: 'tests'
+        module_path: 'spec/fixtures/modules'
+        manifest_file: <%= ENV['VAGRANT_MANIFEST'] || 'init.pp' %>
+```
+
+#### config/roles.yaml
+
+```yaml
+---
+boxes:
+  centos-65-x64: http://puppet-vagrant-boxes.puppetlabs.com/centos-65-x64-virtualbox-puppet.box
+  debian-73-x64: http://puppet-vagrant-boxes.puppetlabs.com/debian-73-x64-virtualbox-puppet.box
+roles:
+  bigvm:
+    provider:
+      type: virtualbox
+      customize: [[modifyvm, !ruby/sym id, '--memory', 1024]]
+    synced_folders:
+      - host_path: '.'
+        guest_path: '/vagrant'
+        disabled: true
+  smallvm:
+    provider:
+      type: vmware
+      vmx:
+        memsize: 512
+        numvcpus: 1
+```
+
+#### config/vms.yaml
+
+```yaml
+---
+vms:
+  -
+    name: db
+    private_networks: [ {ip: '10.20.1.2'} ]
+    box: centos-65-x64
+    hostname: db.puppetlabs.vm
+    roles: bigvm
+  -
+    name: web
+    private_networks: [ {ip: '10.20.1.3'} ]
+    box: debian-73-x64
+```
+
+Installation
+------------
+
+### Installation into the Vagrant internal gems:
+
+  * `vagrant plugin install vagrant-masonry`
+
+### Installation from source
+
+Build the gem:
+
+  * `gem build vagrant-masonry.gemspec`
+
+Install the gem:
+
+  * `gem install vagrant-masonry-<version>.gem`
+
+License
+-------
+
+**Vagrant Masonry** plugin is based on [vagrant-config_builder](https://github.com/adrienthebo/vagrant-config_builder) plugin.
+
+**Vagrant Masonry** is licensed under [Apache 2.0](LICENSE) license.

data/docs/GettingStarted.markdown

@@ -0,0 +1,175 @@
+# @title Getting Started
+
+# Getting Started
+
+The vagrant-config_builder plugin is designed to ease the management of complex Vagrant setups.
+This goal is accomplished by moving configuration data out of the Vagrant DSL and into formats that excel at expressing hierarchical information.
+Moving the configuration to a dedicated data structure allows multiple VMs to be defined by composing and remixing a set of common components.
+This guide describes:
+
+  - How to transition a Vagrant configuration to a ConfigBuilder data structure.
+
+  - How vagrant-config_builder maps that structure back to a Vagrant configuration.
+
+  - The methodology that vagrant-config_builder uses to manage components of configuration shared by multiple VMs.
+
+
+## Expressing Configuration as Data
+
+This guide will walk through re-implementing the following Vagrantfile using vagrant-config_builder:
+
+```ruby
+# Vagrantfile
+
+# Requires the following plugins:
+#
+#   - vagrant-hosts
+#   - vagrant-auto_network
+#
+Vagrant.configure('2') do |config|
+
+  box_url = 'http://puppet-vagrant-boxes.puppetlabs.com/centos-64-x64-vbox4210-nocm.box'
+  box_name = 'centos-64-x64-vbox4210-nocm'
+
+  config.vm.define :puppetmaster do |node|
+    node.vm.box_url = box_url
+    node.vm.box = box_name
+
+    node.vm.hostname = 'puppetmaster.boxnet'
+
+    node.vm.network :private_network, :ip => '0.0.0.0', :auto_network => true
+    node.vm.provision :hosts
+
+    node.vm.provision :shell, :inline => <<-EOF
+    if which puppet > /dev/null 2>&1; then
+      echo 'Puppet Installed.'
+    else
+      echo 'Installing Puppet Master.'
+      rpm -ivh http://yum.puppetlabs.com/el/6/products/i386/puppetlabs-release-6-6.noarch.rpm
+      yum --nogpgcheck -y install puppet-server
+      echo '*.boxnet' > /etc/puppet/autosign.conf
+      /usr/bin/puppet resource service iptables ensure=stopped enable=false
+      /usr/bin/puppet resource service puppetmaster ensure=running enable=true
+    fi
+    EOF
+  end
+
+  config.vm.define :puppetagent do |node|
+    node.vm.box_url = box_url
+    node.vm.box = box_name
+
+    node.vm.hostname = 'puppetagent.boxnet'
+
+    node.vm.network :private_network, :ip => '0.0.0.0', :auto_network => true
+    node.vm.provision :hosts
+
+    node.vm.provision :shell, :inline => <<-EOF
+    if which puppet > /dev/null 2>&1; then
+      echo 'Puppet Installed.'
+    else
+      echo 'Installing Puppet Agent.'
+      rpm -ivh http://yum.puppetlabs.com/el/6/products/i386/puppetlabs-release-6-6.noarch.rpm
+      yum --nogpgcheck -y install puppet
+    fi
+    EOF
+  end
+
+end
+```
+
+The above listing showcases several examples of duplicated configuration: both VMs are using the same Vagrant box, both are configuring their networks in the same way and both are provisioned using nearly identical shell scripts.
+In fact, the only real difference between the VMs are the hostnames and the few lines of shell that install and configure the Puppet master instead or the Puppet agent.
+These little bits of shared configuration pop up constantly in multi-machine Vagrant environments and are commonly handled by a combination of copy-and-paste and factoring out bits of data and configuration into variables or methods (such as `box_name` and `box_url` used above).
+There are some significant drawbacks to this situation:
+
+  - Copy and paste quickly becomes expensive to maintain as the number of machines in the environment increases.
+
+  - Factoring configuration out to variables and methods can help, but requires care to produce something that is portable and reusable across environments.
+
+  - Determining which bits of configuration are shared among which machines is a challenging task to complete quickly and usually requires a careful reading of the Vagrantfile.
+
+vagrant-config_builder approaches this problem by storing every bit of configuration in a unified data structure.
+The structure can be loaded from any data source that is convertable to a hash such as YAML, JSON, XML (possibly [interpretive dance][oscar data sources]).
+Generation of configuration hashes from data sources is implemented through the `ConfigBuilder::Loader` module and is completely pluggable.
+This guide will use YAML as the configuration storage format as vagrant-config_builder includes a YAML Loader.
+
+If the Vagrantfile above were to be translated to YAML, it would look like this:
+
+```yaml
+# config/vms.yaml
+---
+vms:
+  - name: puppetmaster
+    box_url: http://puppet-vagrant-boxes.puppetlabs.com/centos-64-x64-vbox4210-nocm.box
+    box: centos-64-x64-vbox4210-nocm
+    hostname: puppetmaster.boxnet
+    private_networks:
+      - {ip: 0.0.0.0, auto_network: true}
+    provisioners:
+      - type: hosts
+      - type: shell
+        inline: |
+          if which puppet > /dev/null 2>&1; then
+            echo 'Puppet Installed.'
+          else
+            echo 'Installing Puppet Master.'
+            rpm -ivh http://yum.puppetlabs.com/el/6/products/i386/puppetlabs-release-6-6.noarch.rpm
+            yum --nogpgcheck -y install puppet-server
+            echo '*.boxnet' > /etc/puppet/autosign.conf
+            /usr/bin/puppet resource service iptables ensure=stopped enable=false
+            /usr/bin/puppet resource service puppetmaster ensure=running enable=true
+          fi
+
+  - name: puppetagent
+    box_url: http://puppet-vagrant-boxes.puppetlabs.com/centos-64-x64-vbox4210-nocm.box
+    box: centos-64-x64-vbox4210-nocm
+    hostname: puppetagent.boxnet
+    private_networks:
+      - {ip: 0.0.0.0, auto_network: true}
+    provisioners:
+      - type: hosts
+      - type: shell
+        inline: |
+          if which puppet > /dev/null 2>&1; then
+            echo 'Puppet Installed.'
+          else
+            echo 'Installing Puppet Master.'
+            rpm -ivh http://yum.puppetlabs.com/el/6/products/i386/puppetlabs-release-6-6.noarch.rpm
+            yum --nogpgcheck -y install puppet
+          fi
+```
+The YAML configuration above maps very closely to the original Vagrant DSL.
+The major differences are:
+
+  - Repetitive bits of syntax such as `config.vm.*` and `node.vm.*` are now expressed implicitly through the structure of the data.
+
+  - Operations that are executed multiple times are expressed as arrays. These are:
+
+    - Defining VMs.
+
+    - Defining network interfaces on VMs.
+
+    - Running provisioners on VMs.
+
+The mapping between the ConfigBuilder data and the original Vagrantfile will be covered in detail in the next section.
+With the YAML configuration saved in `config/vms.yaml`, the Vagrantfile can updated to invoke `ConfigBuilder.load`:
+
+```ruby
+# Vagrantfile
+
+# Requires the following plugins:
+#
+#  - vagrant-hosts
+#  - vagrant-auto_network
+#  - vagrant-config_builder
+#
+Vagrant.configure('2', &ConfigBuilder.load(
+  :yaml,
+  :yamldir,
+  File.expand_path('../config', __FILE__)
+))
+```
+
+This calls the `yamldir` method of the YAML Loader and passes a path to a `config` directory located adjacent to the Vagrantfile.
+
+  [oscar data sources]: http://www.youtube.com/watch?v=1TgGQjjLDXg&t=19m27s