vagrant-hp 0.1.0 → 0.1.1

data/.gitignore

@@ -1,60 +1,60 @@
-# Compiled source #
-###################
-*.com
-*.class
-*.dll
-*.exe
-*.o
-*.so
-
-# Packages #
-############
-# it's better to unpack these files and commit the raw source
-# git has its own built in compression methods
-*.7z
-*.dmg
-*.gz
-*.iso
-*.jar
-*.rar
-*.tar
-*.zip
-
-# Logs and databases #
-######################
-*.log
-*.sql
-*.sqlite
-
-# OS generated files #
-######################
-.DS_Store
-.DS_Store?
-._*
-.Spotlight-V100
-.Trashes
-Icon?
-ehthumbs.db
-Thumbs.db
-
-# Ruby file #
-#############
-Gemfile.lock
-*.gem
-*.rbc
-.bundle
-.config
-coverage
-InstalledFiles
-lib/bundler/man
-pkg
-rdoc
-spec/reports
-test/tmp
-test/version_tmp
-tmp
-
-# YARD artifacts
-.yardoc
-_yardoc
+# Compiled source #
+###################
+*.com
+*.class
+*.dll
+*.exe
+*.o
+*.so
+
+# Packages #
+############
+# it's better to unpack these files and commit the raw source
+# git has its own built in compression methods
+*.7z
+*.dmg
+*.gz
+*.iso
+*.jar
+*.rar
+*.tar
+*.zip
+
+# Logs and databases #
+######################
+*.log
+*.sql
+*.sqlite
+
+# OS generated files #
+######################
+.DS_Store
+.DS_Store?
+._*
+.Spotlight-V100
+.Trashes
+Icon?
+ehthumbs.db
+Thumbs.db
+
+# Ruby file #
+#############
+Gemfile.lock
+*.gem
+*.rbc
+.bundle
+.config
+coverage
+InstalledFiles
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+
+# YARD artifacts
+.yardoc
+_yardoc
 doc/

data/CHANGELOG.md

@@ -1,3 +1,6 @@
-# 0.0.1 (March 31, 2013)
-* Vagrant-Hp
-* Initial release.
+# 0.1.1 (May 22, 2013)
+* Added support to specify security groups.
+
+# 0.1.0 (March 31, 2013)
+* Vagrant-Hp
+* Initial release.

data/Gemfile

@@ -1,10 +1,10 @@
-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/mohitsethi/vagrant.git"
-end
+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/mohitsethi/vagrant.git"
+end

data/LICENSE

@@ -0,0 +1,9 @@
+The MIT License (MIT)
+Copyright (c) 2013 Mitchell Hashimoto
+Copyright (c) 2013 Mohit Sethi
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -1,167 +1,172 @@
-# Vagrant HP Provider
-
-This is a [Vagrant](http://www.vagrantup.com) 1.1+ plugin that adds an [HP](http://www.hpcloud.com)
-provider to Vagrant, allowing Vagrant to control and provision machines on HP Cloud.
-
-**NOTE:** This plugin requires Vagrant 1.1+,
-
-## Features
-
-* Boot Servers on HP Cloud
-* SSH into the instances.
-* Provision the instances with any built-in Vagrant provisioner.
-* Minimal synced folder support via `rsync`.
-
-## Usage
-
-Install using standard Vagrant 1.1+ plugin installation methods. After
-installing, `vagrant up` and specify the `hp` provider. An example is
-shown below.
-
-```
-$ vagrant plugin install vagrant-hp
-...
-$ vagrant up --provider=hp
-...
-```
-
-Of course prior to doing this, you'll need to obtain an HP-compatible
-box file for Vagrant.
-
-## Quick Start
-
-After installing the plugin (instructions above), the quickest way to get
-started is to actually use a dummy HP box and specify all the details
-manually within a `config.vm.provider` block. So first, add the dummy
-box using any name you want:
-
-```
-$ vagrant box add dummy https://github.com/mohitsethi/vagrant-hp/raw/master/dummy_hp.box
-...
-```
-
-And then make a Vagrantfile that looks like the following, filling in
-your information where necessary.
-
-```
-Vagrant.configure("2") do |config|
-  config.vm.box = "dummy"
-
-  config.vm.provider :hp do |rs|
-    rs.access_key  = "<hp_access_key>"
-    rs.secret_key = "<hp_secret_key>"
-    rs.flavor   = "standard.xsmall"
-    rs.tenant_id = "<hp_tenant_id>"
-    rs.server_name = "<server_name>"
-    rs.image    = "Ubuntu Precise 12.04 LTS Server 64-bit 20121026 (b)"
-    rs.keypair_name = "<your_key_pair_name_on_hpcloud>"
-    rs.ssh_private_key_path = "<private_key_location>"
-    rs.ssh_username = "<ssh_username>"
-    rs.availability_zone = "az1"
-  end
-end
-```
-
-And then run `vagrant up --provider=hp`.
-
-This will start an Ubuntu 12.04 instance in the az1 availability zone within
-your HP Cloud account. 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 "dummy" box, has
-no preconfigured defaults.
-
-## Box Format
-
-Every provider in Vagrant must introduce a custom box format. This
-provider introduces `hp` boxes. You can view an example box in
-the [example_box/ directory](https://github.com/mohitsethi/vagrant-hp/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:
-
-* `access_key` - The access key for accessing HP Cloud
-* `image` - The Image-id  or Image-Name to boot, such as 
-    "Ubuntu Precise 12.04 LTS Server 64-bit 20121026 (b)"
-* `availability_zone` - The availability zone to launch the server. 
-    If nil, it will use 'az1'.
-* `flavor` - The type of flavor, such as "standard.xsmall"
-* `keypair_name` - The name of the keypair to use to bootstrap image
-   which support it.
-* `secret_key` - The secret access key for accessing HP Cloud.
-* `ssh_private_key_path` - The path to the SSH private key. This overrides
-  `config.ssh.private_key_path`.
-* `ssh_username` - The SSH username, which overrides `config.ssh.username`.
-* `server_name` - The name of the server provisioned on HP Cloud.
-* `tenant_id` - The tenant_id to launch the server.
-
-These can be set like typical provider-specific configuration:
-
-
-```ruby
-Vagrant.configure("2") do |config|
-  # ... other stuff
-
-  config.vm.provider :hp do |rs|
-    rs.access_key  = "<hp_access_key>"
-    rs.secret_key = "<hp_secret_key>"
-    rs.flavor   = "standard.xsmall"
-    rs.tenant_id = "<hp_tenant_id>"
-    rs.server_name = "<server_name>"
-    rs.image    = "Ubuntu Precise 12.04 LTS Server 64-bit 20121026 (b)"
-    rs.keypair_name = "<your_key_pair_name_on_hpcloud>"
-    rs.ssh_private_key_path = "<private_key_location>"
-    rs.ssh_username = "<ssh_username>"
-    rs.availability_zone = "az1"
-  end
-
-end
-```
-
-## Networks
-
-Networking features in the form of `config.vm.network` are not
-supported with `vagrant-hp`, currently. If any of these are
-specified, Vagrant will emit a warning, but will otherwise boot
-the HP machine.
-
-## Synced Folders
-
-There is minimal support for synced folders. Upon `vagrant up`,
-`vagrant reload`, and `vagrant provision`, the HP 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!
-
-## Development
-
-To work on the `vagrant-hp` 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=hp
-```
+# Vagrant HP Provider
+
+This is a [Vagrant](http://www.vagrantup.com) 1.1+ plugin that adds an [HP](http://www.hpcloud.com)
+provider to Vagrant, allowing Vagrant to control and provision machines on HP Cloud.
+
+**NOTE:** This plugin requires Vagrant 1.1+,
+
+## Features
+
+* Boot Servers on HP Cloud
+* SSH into the instances.
+* Provision the instances with any built-in Vagrant provisioner.
+* Minimal synced folder support via `rsync`.
+
+## Usage
+
+Install using standard Vagrant 1.1+ plugin installation methods. After
+installing, `vagrant up` and specify the `hp` provider. An example is
+shown below.
+
+```
+$ vagrant plugin install vagrant-hp
+...
+$ vagrant up --provider=hp
+...
+```
+
+Of course prior to doing this, you'll need to obtain an HP-compatible
+box file for Vagrant.
+
+## Quick Start
+
+After installing the plugin (instructions above), the quickest way to get
+started is to actually use a dummy HP box and specify all the details
+manually within a `config.vm.provider` block. So first, add the dummy
+box using any name you want:
+
+```
+$ vagrant box add dummy https://github.com/mohitsethi/vagrant-hp/raw/master/dummy_hp.box
+...
+```
+
+And then make a Vagrantfile that looks like the following, filling in
+your information where necessary.
+
+```
+Vagrant.configure("2") do |config|
+  config.vm.box = "dummy"
+
+  config.vm.provider :hp do |rs|
+    rs.access_key  = "<hp_access_key>"
+    rs.secret_key = "<hp_secret_key>"
+    rs.flavor   = "standard.xsmall"
+    rs.tenant_id = "<hp_tenant_id>"
+    rs.server_name = "<server_name>"
+    rs.image    = "Ubuntu Precise 12.04 LTS Server 64-bit 20121026 (b)"
+    rs.keypair_name = "<your_key_pair_name_on_hpcloud>"
+    rs.ssh_private_key_path = "<private_key_location>"
+    rs.ssh_username = "<ssh_username>"
+    rs.availability_zone = "az1"
+    # Security Groups defaults to ["default"]
+    # rs.security_groups = ["group1", "group2"]
+  end
+end
+```
+
+And then run `vagrant up --provider=hp`.
+
+This will start an Ubuntu 12.04 instance in the az1 availability zone within
+your HP Cloud account. 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 "dummy" box, has
+no preconfigured defaults.
+
+## Box Format
+
+Every provider in Vagrant must introduce a custom box format. This
+provider introduces `hp` boxes. You can view an example box in
+the [example_box/ directory](https://github.com/mohitsethi/vagrant-hp/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:
+
+* `access_key` - The access key for accessing HP Cloud
+* `image` - The Image-id  or Image-Name to boot, such as 
+    "Ubuntu Precise 12.04 LTS Server 64-bit 20121026 (b)"
+* `availability_zone` - The availability zone to launch the server. 
+    If nil, it will use 'az1'.
+* `flavor` - The type of flavor, such as "standard.xsmall"
+* `keypair_name` - The name of the keypair to use to bootstrap image
+   which support it.
+* `secret_key` - The secret access key for accessing HP Cloud.
+* `ssh_private_key_path` - The path to the SSH private key. This overrides
+  `config.ssh.private_key_path`.
+* `ssh_username` - The SSH username, which overrides `config.ssh.username`.
+* `server_name` - The name of the server provisioned on HP Cloud.
+* `tenant_id` - The tenant_id to launch the server.
+* `security_groups` - An array of strings defining the security groups in which this VM is included.
+
+These can be set like typical provider-specific configuration:
+
+
+```ruby
+Vagrant.configure("2") do |config|
+  # ... other stuff
+
+  config.vm.provider :hp do |rs|
+    rs.access_key  = "<hp_access_key>"
+    rs.secret_key = "<hp_secret_key>"
+    rs.flavor   = "standard.xsmall"
+    rs.tenant_id = "<hp_tenant_id>"
+    rs.server_name = "<server_name>"
+    rs.image    = "Ubuntu Precise 12.04 LTS Server 64-bit 20121026 (b)"
+    rs.keypair_name = "<your_key_pair_name_on_hpcloud>"
+    rs.ssh_private_key_path = "<private_key_location>"
+    rs.ssh_username = "<ssh_username>"
+    rs.availability_zone = "az1"
+    # Security Groups defaults to ["default"]
+    # rs.security_groups = ["group1", "group2"]
+  end
+
+end
+```
+
+## Networks
+
+Networking features in the form of `config.vm.network` are not
+supported with `vagrant-hp`, currently. If any of these are
+specified, Vagrant will emit a warning, but will otherwise boot
+the HP machine.
+
+## Synced Folders
+
+There is minimal support for synced folders. Upon `vagrant up`,
+`vagrant reload`, and `vagrant provision`, the HP 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!
+
+## Development
+
+To work on the `vagrant-hp` 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=hp
+```