vagrant-aws-detiber 0.7.2.pre.2

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/hyperv/boxes.html.md

@@ -0,0 +1,103 @@
+---
+layout: "docs"
+page_title: "Creating a Base Box - Hyper-V Provider"
+sidebar_current: "providers-hyperv-boxes"
+description: |-
+  As with every Vagrant provider, the Vagrant Hyper-V provider has a custom box
+  format that affects how base boxes are made.
+---
+
+# Creating a Base Box
+
+As with [every Vagrant provider](/docs/providers/basic_usage.html), the
+Vagrant Hyper-V provider has a custom box format that affects how base boxes are made.
+
+Prior to reading this, you should read the
+[general guide to creating base boxes](/docs/boxes/base.html). Actually,
+it would probably be most useful to keep this open in a separate tab
+as you may be referencing it frequently while creating a base box. That
+page contains important information about common software to install
+on the box.
+
+Additionally, it is helpful to understand the
+[basics of the box file format](/docs/boxes/format.html).
+
+<div class="alert alert-warning">
+  <strong>Advanced topic!</strong> This is a reasonably advanced topic that
+  a beginning user of Vagrant does not need to understand. If you are
+  just getting started with Vagrant, skip this and use an available
+  box. If you are an experienced user of Vagrant and want to create
+  your own custom boxes, this is for you.
+</div>
+
+## Additional Software
+
+In addition to the software that should be installed based on the
+[general guide to creating base boxes](/docs/boxes/base.html),
+Hyper-V base boxes require some additional software.
+
+### Hyper-V Kernel Modules
+
+You will need to install Hyper-V kernel modules. While this improves performance,
+it also enables necessary features such as reporting its IP address so that
+Vagrant can access it.
+
+You can verify Hyper-V kernel modules are properly installed by
+running `lsmod` on Linux machines and looking for modules prefixed with
+`hv_`. Additionally, you will need to verify that the "Network" tab for your
+virtual machine in the Hyper-V manager is reporting an IP address. If it
+is not reporting an IP address, Vagrant will not be able to access it.
+
+For most newer Linux distributions, the Hyper-V modules will be available
+out of the box.
+
+Ubuntu 12.04 requires some special steps to make networking work. These
+are reproduced here in case similar steps are needed with other distributions.
+Without these commands, Ubuntu 12.04 will not report an IP address to
+Hyper-V:
+
+```
+$ sudo apt-get install linux-tools-3.11.0-15-generic
+$ sudo apt-get install hv-kvp-daemon-init
+$ sudo cp /usr/lib/linux-tools/3.11.0-15/hv_* /usr/sbin/
+```
+
+## Packaging the Box
+
+To package a Hyper-V box, export the virtual machine from the
+Hyper-V Manager using the "Export" feature. This will create a directory
+with a structure similar to the following:
+
+```
+.
+|-- Snapshots
+|-- Virtual Hard drives
+|-- Virtual Machines
+```
+
+Delete the "Snapshots" folder. It is of no use to the Vagrant Hyper-V
+provider and can only add to the size of the box if there are snapshots
+in that folder.
+
+Then, create the "metadata.json" file necessary for the box, as documented
+in [basics of the box file format](/docs/boxes/format.html). The proper
+provider value to use for the metadata is "hyperv".
+
+Finally, create an archive of those contents (but _not_ the parent folder)
+using a tool such as `tar`:
+
+```
+$ tar cvzf ~/custom.box ./*
+```
+
+A common mistake is to also package the parent folder by accident. Vagrant
+will not work in this case. To verify you've packaged it properly, add the
+box to Vagrant and try to bring up the machine.
+
+## Additional Help
+
+There is also some less structured help available from the experience of
+other users. These are not official documentation but if you are running
+into trouble they may help you:
+
+  * [Ubuntu 14.04.2 without secure boot](https://github.com/hashicorp/vagrant/issues/5419#issuecomment-86235427)

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/hyperv/configuration.html.md

@@ -0,0 +1,52 @@
+---
+layout: "docs"
+page_title: "Configuration- Hyper-V Provider"
+sidebar_current: "providers-hyperv-configuration"
+description: |-
+  The Vagrant Hyper-V provider has some provider-specific configuration options
+  you may set.
+---
+
+# Configuration
+
+The Vagrant Hyper-V provider has some provider-specific configuration options
+you may set. A complete reference is shown below:
+
+  * `vmname` (string) - Name of virtual machine as shown in Hyper-V manager.
+    Defaults is taken from box image XML.
+  * `cpus` (integer) - Number of virtual CPU given to machine.
+    Defaults is taken from box image XML.
+  * `memory` (integer) - Number of MegaBytes allocated to VM at startup.
+    Defaults is taken from box image XML.
+  * `maxmemory` (integer) - Number of MegaBytes maximal allowed to allocate for VM
+    This parameter is switch on Dynamic Allocation of memory.
+    Defaults is taken from box image XML.
+  * `vlan_id` (integer) - Number of Vlan ID for your guest network interface
+    Defaults is not defined, vlan configuration will be untouched if not set.
+  * `mac` (string) - MAC address for your guest network interface
+    Default is not defined, MAC address will be dynamically assigned by Hyper-V if not set.
+  * `ip_address_timeout` (integer) - The time in seconds to wait for the
+    virtual machine to report an IP address. This defaults to 120 seconds.
+    This may have to be increased if your VM takes longer to boot.
+  * `differencing_disk` (boolean) - Switch to use differencing disk intead of cloning whole VHD.
+  * `enable_virtualization_extensions` (boolean) - Enable virtualization extensions for the virtual CPUs.
+    This allows Hyper-V to be nested and run inside another Hyper-VM VM. It requires Windows 10  - 1511 (build 10586) or newer.
+    Default is not defined. This will be disabled if not set.
+  * `auto_start_action` (Nothing, StartIfRunning, Start) - Action on automatic start of VM when booting OS
+  * `auto_stop_action` (ShutDown, TurnOff, Save) - Action on automatic stop of VM when shutting down OS.    
+  * `vm_integration_services` (Hash) - Hash to set the state of integration services.
+     
+    Example: 
+        
+    ```ruby
+    config.vm.provider "hyperv" do |h|
+      h.vm_integration_services = {
+          guest_service_interface: true,
+          heartbeat: true,
+          key_value_pair_exchange: true,
+          shutdown: true,
+          time_synchronization: true,
+          vss: true
+      }
+    end
+    ```

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/hyperv/index.html.md

@@ -0,0 +1,33 @@
+---
+layout: "docs"
+page_title: "Hyper-V Provider"
+sidebar_current: "providers-hyperv"
+description: |-
+  Vagrant comes with support out of the box for Hyper-V, a native hypervisor
+  written by Microsoft. Hyper-V is available by default for almost all
+  Windows 8.1 and later installs.
+---
+
+# Hyper-V
+
+Vagrant comes with support out of the box for [Hyper-V](https://en.wikipedia.org/wiki/Hyper-V),
+a native hypervisor written by Microsoft. Hyper-V is available by default for
+almost all Windows 8.1 and later installs.
+
+The Hyper-V provider is compatible with Windows 8.1 and later only. Prior versions
+of Hyper-V do not include the necessary APIs for Vagrant to work.
+
+Hyper-V must be enabled prior to using the provider. Most Windows installations
+will not have Hyper-V enabled by default. To enable Hyper-V, go to
+"Programs and Features", click on "Turn Windows features on or off" and check
+the box next to "Hyper-V".  Or install via PowerShell with
+
+<code>Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All</code>.
+
+<div class="alert alert-warning">
+  <strong>Warning:</strong> Enabling Hyper-V will cause VirtualBox, VMware,
+  and any other virtualization technology to no longer work. See
+  <a href="http://www.hanselman.com/blog/SwitchEasilyBetweenVirtualBoxAndHyperVWithABCDEditBootEntryInWindows81.aspx">this blog post</a>
+  for an easy way to create a boot entry to boot Windows without Hyper-V
+  enabled, if there will be times you will need other hypervisors.
+</div>

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/hyperv/limitations.html.md

@@ -0,0 +1,37 @@
+---
+layout: "docs"
+page_title: "Limitations - Hyper-V Provider"
+sidebar_current: "providers-hyperv-limitations"
+description: |-
+  The Hyper-V provider works in almost every way like the VirtualBox
+  or VMware provider would, but has some limitations that are inherent to
+  Hyper-V itself.
+---
+
+# Limitations
+
+The Vagrant Hyper-V provider works in almost every way like the VirtualBox
+or VMware provider would, but has some limitations that are inherent to
+Hyper-V itself.
+
+## Limited Networking
+
+Vagrant does not yet know how to create and configure new networks for
+Hyper-V. When launching a machine with Hyper-V, Vagrant will prompt you
+asking what virtual switch you want to connect the virtual machine to.
+
+A result of this is that networking configurations in the Vagrantfile
+are completely ignored with Hyper-V. Vagrant cannot enforce a static IP
+or automatically configure a NAT.
+
+However, the IP address of the machine will be reported as part of
+the `vagrant up`, and you can use that IP address as if it were
+a host only network.
+
+## Snapshots
+
+Restoring snapshot VMs using `vagrant snapshot pop` or 
+`vagrant snapshot restore` will sometimes raise errors when mounting
+SMB shared folders, however these mounts will still work inside the guest.
+
+

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/hyperv/usage.html.md

@@ -0,0 +1,25 @@
+---
+layout: "docs"
+page_title: "Usage - Hyper-V Provider"
+sidebar_current: "providers-hyperv-usage"
+description: |-
+  The Hyper-V provider is used just like any other provider. Please read the
+  general basic usage page for providers.
+---
+
+# Usage
+
+The Vagrant Hyper-V provider is used just like any other provider. Please
+read the general [basic usage](/docs/providers/basic_usage.html) page for
+providers.
+
+The value to use for the `--provider` flag is `hyperv`.
+
+Hyper-V also requires that you execute Vagrant with administrative
+privileges. Creating and managing virtual machines with Hyper-V requires
+admin rights. Vagrant will show you an error if it does not have the proper
+permissions.
+
+Boxes for Hyper-V can be easily found on
+[HashiCorp's Vagrant Cloud](https://vagrantcloud.com/boxes/search). To get started, you might
+want to try the `hashicorp/precise64` box.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/index.html.md

@@ -0,0 +1,24 @@
+---
+layout: "docs"
+sidebar_current: "overview"
+page_title: "Documentation"
+description: |-
+  Welcome to the documentation for Vagrant - the command line utility for
+  managing the lifecycle of virtual machines. This website aims to document
+  every feature of Vagrant from top-to-bottom, covering as much detail as
+  possible.  
+---
+
+# Vagrant Documentation
+
+Welcome to the documentation for Vagrant - the command line utility for managing
+the lifecycle of virtual machines. This website aims to document every feature
+of Vagrant from top-to-bottom, covering as much detail as possible. If you are
+just getting started with Vagrant, it is highly recommended that you start with
+the [getting started guide](/intro/getting-started/index.html) first, and then
+return to this page.
+
+The navigation will take you through each component of Vagrant. Click on a
+navigation item to get started, or read more about
+[why developers, designers, and operators choose Vagrant](/intro/index.html)
+for their needs.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/installation/backwards-compatibility.html.md

@@ -0,0 +1,41 @@
+---
+layout: "docs"
+page_title: "Backwards Compatibility"
+sidebar_current: "installation-backwards-compatibility"
+description: |-
+  Vagrant makes a very strict backwards-compatability promise.
+---
+
+# Backwards Compatibility
+
+## For 1.0.x
+
+Vagrant 1.1+ provides full backwards compatibility for valid Vagrant 1.0.x
+Vagrantfiles which do not use plugins. After installing Vagrant 1.1, your 1.0.x
+environments should continue working without modifications, and existing running
+machines will continue to be managed properly.
+
+This compatibility layer will remain in Vagrant up to and including Vagrant 2.0.
+It may still exist after that, but Vagrant's compatibility promise is only for
+two versions. Seeing that major Vagrant releases take years to develop and
+release, it is safe to stick with your version 1.0.x Vagrantfile for the
+time being.
+
+If you use any Vagrant 1.0.x plugins, you must remove references to these from
+your Vagrantfile prior to upgrading. Vagrant 1.1+ introduces a new plugin
+format that will protect against this sort of incompatibility from ever
+happening again.
+
+## For 1.x
+
+Backwards compatibility between 1.x is not promised, and Vagrantfile
+syntax stability is not promised until 2.0 final. Any backwards
+incompatibilities within 1.x will be clearly documented.
+
+This is similar to how Vagrant 0.x was handled. In practice, Vagrant 0.x
+only introduced a handful of backwards incompatibilities during the entire
+development cycle, but the possibility of backwards incompatibilities
+is made clear so people are not surprised.
+
+Vagrant 2.0 final will have a stable Vagrantfile format that will
+remain backwards compatible, just as 1.0 is considered stable.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/installation/index.html.md

@@ -0,0 +1,38 @@
+---
+layout: "docs"
+page_title: "Installing Vagrant"
+sidebar_current: "installation"
+description: |-
+  Installing Vagrant is extremely easy. Head over to the Vagrant downloads page
+  and get the appropriate installer or package for your platform. Install the
+  package using standard procedures for your operating system.
+---
+
+# Installing Vagrant
+
+Installing Vagrant is extremely easy. Head over to the
+[Vagrant downloads page](/downloads.html) and get the appropriate installer or
+package for your platform. Install the package using standard procedures for
+your operating system.
+
+The installer will automatically add `vagrant` to your system path
+so that it is available in terminals. If it is not found, please try
+logging out and logging back in to your system (this is particularly
+necessary sometimes for Windows).
+
+<div class="alert alert-warning" role="alert">
+  <strong>Looking for the gem install?</strong> Vagrant 1.0.x had the option to
+  be installed as a <a href="https://en.wikipedia.org/wiki/RubyGems">RubyGem</a>.
+  This installation method is no longer supported. If you have an old version
+  of Vagrant installed via Rubygems, please remove it prior to installing newer
+  versions of Vagrant.
+</div>
+
+<div class="alert alert-warning" role="alert">
+  <strong>Beware of system package managers!</strong> Some operating system
+  distributions include a vagrant package in their upstream package repos.
+  Please do not install Vagrant in this manner. Typically these packages are
+  missing dependencies or include very outdated versions of Vagrant. If you
+  install via your system's package manager, it is very likely that you will
+  experience issues. Please use the official installers on the downloads page.
+</div>

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/installation/source.html.md

@@ -0,0 +1,78 @@
+---
+layout: "docs"
+page_title: "Installing Vagrant from Source"
+sidebar_current: "installation-source"
+description: |-
+  Installing Vagrant from source is an advanced topic and is only recommended
+  when using the official installer is not an option. This page details the
+  steps and prerequisites for installing Vagrant from source.
+---
+
+# Installing Vagrant from Source
+
+Installing Vagrant from source is an advanced topic and is only recommended
+when using the official installer is not an option. This page details the
+steps and prerequisites for installing Vagrant from source.
+
+## Install Ruby
+You must have a modern Ruby (>= 2.2) in order to develop and build Vagrant. The
+specific Ruby version is documented in the Vagrant's `gemspec`. Please refer to
+the `vagrant.gemspec` in the repository on GitHub, as it will contain the most
+up-to-date requirement. This guide will not discuss how to install and manage Ruby.
+However, beware of the following pitfalls:
+
+- Do **NOT** use the system Ruby - use a Ruby version manager like rvm or chruby
+- Vagrant plugins are configured based on current environment. If plugins are installed
+  using Vagrant from source, they will not work from the package based Vagrant installation.
+
+## Clone Vagrant
+Clone Vagrant's repository from GitHub into the directory where you keep code on your machine:
+
+
+```shell
+$ git clone https://github.com/hashicorp/vagrant.git
+```
+
+Next, `cd` into that path. All commands will be run from this path:
+
+```shell
+$ cd /path/to/your/vagrant/clone
+```
+
+Run the `bundle` command with a required version* to install the requirements:
+
+```shell
+$ bundle install
+```
+
+You can now run Vagrant by running `bundle exec vagrant` from inside that
+directory.
+
+## Use Locally
+In order to use your locally-installed version of Vagrant in other projects, you will need to create a binstub and add it to your path.
+
+First, run the following command from the Vagrant repo:
+
+```shell
+$ bundle --binstubs exec
+```
+
+This will generate files in `exec/`, including `vagrant`. You can now specify
+the full path to the `exec/vagrant` anywhere on your operating system:
+
+```shell
+$ /path/to/vagrant/exec/vagrant init -m hashicorp/precise64
+```
+
+Note that you _will_ receive warnings that running Vagrant like this is not
+supported. It's true. It's not. You should listen to those warnings.
+
+If you do not want to specify the full path to Vagrant (i.e. you just want to
+run `vagrant`), you can create a symbolic link to your exec:
+
+```shell
+$ ln -sf /path/to/vagrant/exec/vagrant /usr/local/bin/vagrant
+```
+
+When you want to switch back to the official Vagrant version, simply
+remove the symlink.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/installation/uninstallation.html.md

@@ -0,0 +1,55 @@
+---
+layout: "docs"
+page_title: "Uninstalling Vagrant"
+sidebar_current: "installation-uninstallation"
+description: |-
+  Uninstalling Vagrant is easy and straightforward. You can either uninstall
+  the Vagrant binary, the user data, or both. The sections below cover how to
+  do this on every platform.
+---
+
+# Uninstalling Vagrant
+
+Uninstalling Vagrant is easy and straightforward. You can either uninstall
+the Vagrant binary, the user data, or both. The sections below cover how to
+do this on every platform.
+
+## Removing the Vagrant Program
+
+Removing the Vagrant program will remove the `vagrant` binary and all
+dependencies from your machine. After uninstalling the program, you can
+always [reinstall](/docs/installation/) again using standard
+methods.
+
+On **Windows**
+
+> Uninstall using the add/remove programs section of the control panel
+
+On **Mac OS X**:
+
+```sh
+rm -rf /opt/vagrant
+rm -f /usr/local/bin/vagrant
+sudo pkgutil --forget com.vagrant.vagrant
+```
+
+On **Linux**:
+
+```sh
+rm -rf /opt/vagrant
+rm -f /usr/bin/vagrant
+```
+
+## Removing User Data
+
+Removing the user data will remove all [boxes](/docs/boxes.html),
+[plugins](/docs/plugins/), license files, and any stored state that may be used
+by Vagrant. Removing the user data effectively makes Vagrant think it
+is a fresh install.
+
+On all platforms, remove the `~/.vagrant.d` directory to delete the user
+data. When debugging, the Vagrant support team may ask you to remove this
+directory. Before removing this directory, please make a backup.
+
+Running Vagrant will automatically regenerate any data necessary to run,
+so it is safe to remove the user data at any time.

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/installation/upgrading-from-1-0.html.md

@@ -0,0 +1,33 @@
+---
+layout: "docs"
+page_title: "Upgrading from Vagrant 1.0"
+sidebar_current: "installation-1-0-upgrading"
+description: |-
+  The upgrade process from 1.0.x to 1.x is straightforward. Vagrant is
+  backwards compatible with Vagrant 1.0.x, so you can simply reinstall Vagrant
+  over your previous installation by downloading the latest package and
+  installing it using standard procedures for your operating system.
+---
+
+# Upgrading From Vagrant 1.0.x
+
+The upgrade process from 1.0.x to 1.x is straightforward. Vagrant is quite
+[backwards compatible](/docs/installation/backwards-compatibility.html)
+with Vagrant 1.0.x, so you can simply reinstall Vagrant
+over your previous installation by downloading the latest package and
+installing it using standard procedures for your operating system.
+
+As the [backwards compatibility](/docs/installation/backwards-compatibility.html)
+page says, **Vagrant 1.0.x plugins will not work with Vagrant 1.1+**. Many
+of these plugins have been updated to work with newer versions of Vagrant,
+so you can look to see if they've been updated. If not however, you will have
+to remove them before upgrading.
+
+It is recommended you remove _all_ plugins before upgrading, and then slowly
+add back the plugins. This usually makes for a smoother upgrade process.
+
+<div class="alert alert-warning" role="alert">
+  <strong>If your version of Vagrant was installed via Rubygems</strong>, you
+  must uninstall the old version prior to installing the package for the
+  new version of Vagrant. The Rubygems installation is no longer supported.
+</div>

data/vendor/bundle/ruby/2.3.0/bundler/gems/vagrant-419afb4dcffe/website/source/docs/installation/upgrading.html.md

@@ -0,0 +1,35 @@
+---
+layout: "docs"
+page_title: "Upgrading Vagrant"
+sidebar_current: "installation-upgrading"
+description: |-
+  If you are upgrading from Vagrant 1.0.x, please read the specific page
+  dedicated to that. This page covers upgrading Vagrant in general during the
+  1.x series.
+---
+
+# Upgrading Vagrant
+
+If you are upgrading from Vagrant 1.0.x, please read the
+[specific page dedicated to that](/docs/installation/upgrading-from-1-0.html).
+This page covers upgrading Vagrant in general during the 1.x series.
+
+Vagrant upgrades during the 1.x release series are straightforward:
+
+1. [Download](/downloads.html) the new package
+2. Install it over the existing package
+
+The installers will properly overwrite and remove old files. It is recommended
+that no other Vagrant processes are running during the upgrade process.
+
+Note that Vagrantfile stability for the new Vagrantfile syntax is not
+promised until 2.0 final. So while Vagrantfiles made for 1.0.x will
+[continue to work](/docs/installation/backwards-compatibility.html),
+newer Vagrantfiles may have backwards incompatible changes until 2.0 final.
+
+<div class="alert alert-info alert-block">
+  <strong>Run into troubles upgrading?</strong> Please
+  <a href="https://github.com/hashicorp/vagrant/issues" class="alert-link">report an issue</a>
+  if you run into problems upgrading. Upgrades are meant to be a smooth
+  process and we consider it a bug if it was not.
+</div>