tcr-vagrant-google 0.1.4

data/.gitignore

@@ -0,0 +1,17 @@
+# Editor/OS-specific
+.DS_Store
+.swp
+
+# Bundler/Rubygems
+*.gem
+.bundle
+pkg/*
+tags
+Gemfile.lock
+/vagrant-google/*
+
+# Vagrant
+.vagrant
+Vagrantfile*
+!example_box/Vagrantfile
+!vagrantfile_examples/*

data/CHANGELOG.md

@@ -0,0 +1,20 @@
+# 0.1.4 (October 2014)
+
+* Add option for disk size [franzs]
+* Add tags [ptone]
+* Updated default for latest Debian image
+
+# 0.1.3 (July 2014)
+
+* Updated all image references
+* Fixed fog deprecation warning
+* Updated example box `google.box`
+* Got spec tests passing again
+
+# 0.1.1 (October 11, 2013)
+
+* Fixed bug with instance ready/SSH
+
+# 0.1.0 (August 14, 2013)
+
+* Initial release.

data/CONTRIB.md

@@ -0,0 +1,64 @@
+# How to become a contributor and submit your own code
+
+## Contributor License Agreements
+
+We'd love to accept your sample apps and patches! Before we can take them, we
+have to jump a couple of legal hurdles.
+
+Please fill out either the individual or corporate Contributor License Agreement
+(CLA).
+
+  * If you are an individual writing original source code and you're sure you
+    own the intellectual property, then you'll need to sign an [individual CLA]
+    (https://developers.google.com/open-source/cla/individual).
+  * If you work for a company that wants to allow you to contribute your work,
+    then you'll need to sign a [corporate CLA]
+    (https://developers.google.com/open-source/cla/corporate).
+
+Follow either of the two links above to access the appropriate CLA and
+instructions for how to sign and return it. Once we receive it, we'll be able to
+accept your pull requests.
+
+## Contributing A Patch
+
+1. Submit an issue describing your proposed change to the repo in question.
+1. The repo owner will respond to your issue promptly.
+1. If your proposed change is accepted, and you haven't already done so, sign a
+   Contributor License Agreement (see details above).
+1. Fork the desired repo, develop and test your code changes.
+1. Ensure that your code adheres to the existing style in the sample to which
+   you are contributing. Refer to the
+   [Google Cloud Platform Samples Style Guide]
+   (https://github.com/GoogleCloudPlatform/Template/wiki/style.html) for the
+   recommended coding standards for this organization.
+1. Ensure that your code has an appropriate set of unit tests which all pass.
+1. Submit a pull request.
+
+## Contributing A New Sample App
+
+1. Submit an issue to the GoogleCloudPlatform/Template repo describing your
+   proposed sample app.
+1. The Template repo owner will respond to your enhancement issue promptly.
+   Instructional value is the top priority when evaluating new app proposals for
+   this collection of repos.
+1. If your proposal is accepted, and you haven't already done so, sign a
+   Contributor License Agreement (see details above).
+1. Create your own repo for your app following this naming convention:
+    * {product}-{app-name}-{language}
+    * products: appengine, compute, storage, bigquery, prediction, cloudsql
+    * example:  appengine-guestbook-python
+    * For multi-product apps, concatenate the primary products, like this:
+      compute-appengine-demo-suite-python.
+    * For multi-language apps, concatenate the primary languages like this:
+      appengine-sockets-python-java-go.
+
+1. Clone the README.md, CONTRIB.md and LICENSE files from the
+   GoogleCloudPlatform/Template repo.
+1. Ensure that your code adheres to the existing style in the sample to which
+   you are contributing. Refer to the
+   [Google Cloud Platform Samples Style Guide]
+   (https://github.com/GoogleCloudPlatform/Template/wiki/style.html) for the
+   recommended coding standards for this organization.
+1. Ensure that your code has an appropriate set of unit tests which all pass.
+1. Submit a request to fork your repo in GoogleCloudPlatform organizationt via
+   your proposal issue.

data/Gemfile

@@ -0,0 +1,24 @@
+# Copyright 2013 Google Inc. All Rights Reserved.
+# 
+# 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.
+
+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", :tag => "v1.2.7"
+end

data/LICENSE

@@ -0,0 +1,201 @@
+                              Apache License
+                        Version 2.0, January 2004
+                     http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+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,237 @@
+# Vagrant Google Compute Engine (GCE) Provider
+
+This is a [Vagrant](http://www.vagrantup.com) 1.2+ plugin that adds an
+[Google Compute Engine](http://cloud.google.com/compute/) (GCE) provider to
+Vagrant, allowing Vagrant to control and provision instances in GCE.
+
+**NOTE:** This plugin requires Vagrant 1.2+,
+
+## Features
+
+* Boot Google Compute Engine instances.
+* SSH into the instances.
+* Provision the instances with any built-in Vagrant provisioner.
+* Minimal synced folder support via `rsync`.
+* Define zone-specific configurations so Vagrant can manage machines in
+  multiple zones.
+
+## Usage
+
+Install using standard Vagrant 1.1+ plugin installation methods.  After
+installing, `vagrant up` and specify the `google` provider.  For example,
+
+```sh
+$ vagrant plugin install vagrant-google
+...
+$ vagrant up --provider=google
+...
+```
+
+Of course, prior to this you'll need to obtain a GCE-compatible box file for
+Vagrant. You may also need to ensure you have a ruby-dev and other utilities
+such as GNU make installed prior to installing the plugin.
+
+## Google Cloud Platform Setup
+
+Prior to using this plugin, you will first need to make sure you have a
+Google Cloud Platform account, enable Google Compute Engine, and create a
+Service Account for API Access.
+
+1. Log in with your Google Account and go to
+   [Google Cloud Platform](https://cloud.google.com) and click on the
+   `Try it now` button.
+1. Create a new project and remember to record the `Project ID` you
+   specify.
+1. Next, visit the [Developers Console](https://console.developers.google.com)
+   make sure to enable the `Google Compute Engine` service for your project
+   If prompted, review and agree to the terms of service.
+1. While still in the Developers Console, go to `API & AUTH`, `Credentials`
+   section and click the `Create new Client ID` button.  In the pop-up dialog,
+   select the `Service Account` radio button and the click the `Create Client ID`
+   button.
+1. When prompted, select the `Download private key` button and make sure
+   to save this file in a secure and reliable location.  This key file
+   will be used to authorize all Vagrant commands available in this plugin.
+1. Still on the same page, find the newly created `Service Account` text
+   block on the API Access page.  Record the `Email address` (it should end
+   with `@developer.gserviceaccount.com`) associated with the new Service
+   Account you just created.  You will need this email address and the
+   location of the private key file to properly configure this Vagrant plugin.
+
+## Quick Start
+
+After installing the plugin (instructions above), the quickest way to get
+started is to actually use a dummy Google box and specify all the details
+manually within a `config.vm.provider` block. So first, add the Google box
+using any name you want:
+
+```sh
+$ vagrant box add gce https://github.com/mitchellh/vagrant-google/raw/master/google.box
+...
+```
+
+And then make a Vagrantfile that looks like the following, filling in
+your information where necessary.
+
+```ruby
+Vagrant.configure("2") do |config|
+  config.vm.box = "gce"
+
+  config.vm.provider :google do |google, override|
+    google.google_project_id = "YOUR_GOOGLE_CLOUD_PROJECT_ID"
+    google.google_client_email = "YOUR_SERVICE_ACCOUNT_EMAIL_ADDRESS"
+    google.google_key_location = "/PATH/TO/YOUR/PRIVATE_KEY.p12"
+
+    override.ssh.username = "USERNAME"
+    override.ssh.private_key_path = "~/.ssh/id_rsa"
+    #override.ssh.private_key_path = "~/.ssh/google_compute_engine"
+  end
+
+end
+```
+
+And then run `vagrant up --provider=google`.
+
+This will start an Debian 7 (Wheezy) instance in the us-central1-f zone,
+with an n1-standard-1 machine, and the "default" network within your project.
+And assuming your SSH information was filled in properly within your
+Vagrantfile, SSH and provisioning will work as well.
+
+Note that normally a lot of this boilerplate is encoded within the box file,
+but the box file used for the quick start, the "google" box, has no
+preconfigured defaults.
+
+## Box Format
+
+Every provider in Vagrant must introduce a custom box format. This provider
+introduces `google` boxes. You can view an example box in the
+[example_box/](https://github.com/mitchellh/vagrant-google/tree/master/example_box).
+That directory also contains instructions on how to build a box.
+
+The box format is basically just the required `metadata.json` file along with
+a `Vagrantfile` that does default settings for the provider-specific
+configuration for this provider.
+
+## Configuration
+
+This provider exposes quite a few provider-specific configuration options:
+
+* `google_client_email` - The Client Email address for your Service Account.
+* `google_key_location` - The location to the private key file matching your
+  Service Account.
+* `google_project_id` - The Project ID for your Google Cloud Platform account.
+* `image` - The image name to use when booting your instance.
+* `instance_ready_timeout` - The number of seconds to wait for the instance
+  to become "ready" in GCE. Defaults to 20 seconds.
+* `machine_type` - The machine type to use.  The default is "n1-standard-1".
+* `disk_size` - The disk size in GB.  The default is 10.
+* `metadata` - Custom key/value pairs of metadata to add to the instance.
+* `name` - The name of your instance.  The default is "i-yyyyMMddHH". Example 2014/10/01 10:00:00 is "i-2014100101".
+* `network` - The name of the network to use for the instance.  Default is
+ "default".
+* `tags` - An array of tags to apply to this instance.
+* `zone` - The zone name where the instance will be created.
+
+These can be set like typical provider-specific configuration:
+
+```ruby
+Vagrant.configure("2") do |config|
+  # ... other stuff
+
+  config.vm.provider :google do |google|
+    google.google_project_id = "my_project"
+    google.google_client_email = "hashstring@example.com"
+    google.google_key_location = "/tmp/private-key.p12"
+  end
+end
+```
+
+In addition to the above top-level configs, you can use the `zone_config`
+method to specify zone-specific overrides within your Vagrantfile. Note
+that the top-level `zone` config must always be specified to choose which
+zone you want to actually use, however. This looks like this:
+
+```ruby
+Vagrant.configure("2") do |config|
+
+  config.vm.box = "gce"
+
+  config.vm.provider :google do |google|
+    google.google_project_id = "my_project"
+    google.google_client_email = "hashstring@example.com"
+    google.google_key_location = "/tmp/private-key.p12"
+
+    # Make sure to set this to trigger the zone_config
+    google.zone = "us-central1-f"
+
+    google.zone_config "us-central1-f" do |zone1f|
+        zone1f.name = "testing-vagrant"
+        zone1f.image = "debian-7-wheezy-v20140926"
+        zone1f.machine_type = "n1-standard-4"
+        zone1f.zone = "us-central1-f"
+        zone1f.metadata = {'custom' => 'metadata', 'testing' => 'foobarbaz'}
+        zone1f.tags = ['web', 'app1']
+    end
+  end
+end
+```
+
+The zone-specific configurations will override the top-level configurations
+when that zone is used. They otherwise inherit the top-level configurations,
+as you would probably expect.
+
+There are a few example Vagrantfile's located in the
+[vagrantfile_examples/ directory](https://github.com/mitchellh/vagrant-google/tree/master/vagrantfile_examples/)
+
+## Networks
+
+Networking features in the form of `config.vm.network` are not supported
+with `vagrant-google`, currently. If any of these are specified, Vagrant will
+emit a warning, but will otherwise boot the GCE machine.
+
+## Synced Folders
+
+There is minimal support for synced folders. Upon `vagrant up`,
+`vagrant reload`, and `vagrant provision`, the Google provider will use
+`rsync` (if available) to uni-directionally sync the folder to the remote
+machine over SSH.
+
+This is good enough for all built-in Vagrant provisioners (shell, chef, and
+puppet) to work!
+
+## Known Issues
+
+* https://github.com/mitchellh/vagrant-google/issues/17
+
+## Development
+
+To work on the `vagrant-google` plugin, clone this repository out, and use
+[Bundler](http://gembundler.com) to get the dependencies:
+
+```
+$ bundle
+```
+
+Once you have the dependencies, verify the unit tests pass with `rake`:
+
+```
+$ bundle exec rake
+```
+
+If those pass, you're ready to start developing the plugin. You can test
+the plugin without installing it into your Vagrant environment by just
+creating a `Vagrantfile` in the top level of this directory (it is gitignored)
+that uses it, and uses bundler to execute Vagrant:
+
+```
+$ bundle exec vagrant up --provider=google
+```
+
+## Changelog
+ * See [CHANGELOG.md](https://github.com/mitchellh/vagrant-google/blob/master/CHANGELOG.md)
+
+## Contributing
+ * See [CONTRIB.md](https://github.com/mitchellh/vagrant-google/blob/master/CONTRIB.md)
+
+## Licensing
+ * See [LICENSE](https://github.com/mitchellh/vagrant-google/blob/master/LICENSE)