vcloud-launcher 0.0.2 → 0.0.3

data/CHANGELOG.md

@@ -0,0 +1,13 @@
+## 0.0.3 (2014-04-22)
+
+Features:
+
+- Allows use of FOG_VCLOUD_TOKEN via ENV to authenticate, as an alternative to a .fog file
+
+Bugfixes:
+
+ - Requires vCloud Core v0.0.12 which fixes issue with progress bar falling over when progress is not returned
+
+## 0.0.2 (2014-04-04)
+
+  - First release of gem

data/README.md

@@ -5,19 +5,19 @@ the vApps and VMs contained within.
 
 ### Supports
 
-    Configuration of multiple vApps/VMs with:
-        multiple NICs
-        custom CPU and memory size
-        multiple additional disks
-        custom VM metadata
-    Basic idempotent operation - vApps that already exist are skipped.
+- Configuration of multiple vApps/VMs with:
+  - multiple NICs
+  - custom CPU and memory size
+  - multiple additional disks
+  - custom VM metadata
+- Basic idempotent operation - vApps that already exist are skipped.
 
 ### Limitations
 
-    Source vApp Template must contain a single VM. This is VMware's recommended 'simple' method of vApp creation. Complex multi-VM vApps are not supported.
-    Org vDC Networks must be precreated.
-    IP addresses are assigned manually (recommended) or via DHCP. VM IP pools are not supported.
-    vCloud has some interesting ideas about the size of potential 'guest customisation scripts' (aka preambles). You may need to use an external minify tool to reduce the size, or speak to your provider to up the limit. 2048 bytes seems to be a practical default maximum.
+- Source vApp Template must contain a single VM. This is VMware's recommended 'simple' method of vApp creation. Complex multi-VM vApps are not supported.
+- Org vDC Networks must be precreated.
+- IP addresses are assigned manually (recommended) or via DHCP. VM IP pools are not supported.
+- vCloud has some interesting ideas about the size of potential 'guest customisation scripts' (aka preambles). You may need to use an external minify tool to reduce the size, or speak to your provider to up the limit. 2048 bytes seems to be a practical default maximum.
 
 ## Installation
 
@@ -36,34 +36,64 @@ Or install it yourself as:
 
 ## Usage
 
-vCloud Launcher uses [Fog](http://fog.io/).
+`vcloud-launch node.yaml`
 
-To use it you need a .fog file in your home directory.
+## Credentials
+
+vCloud Launcher uses [Fog](http://fog.io/). To use it you'll need to give it credentials that allow it to talk to a VMware environment. Fog offers two ways to do this.
+
+### 1. Create a `.fog` file containing your credentials
+
+To use this method, you need a `.fog` file in your home directory.
 
 For example:
 
-test:
-  vcloud_director_username: 'username@org_name'
-  vcloud_director_password: 'password'
-  vcloud_director_host: 'host.api.example.com'
+    test:
+      vcloud_director_username: 'username@org_name'
+      vcloud_director_password: 'password'
+      vcloud_director_host: 'host.api.example.com'
 
 Unfortunately current usage of fog requires the password in this file. Multiple sets of credentials can be specified in the fog file, using the following format:
 
-test:
-  vcloud_director_username: 'username@org_name'
-  vcloud_director_password: 'password'
-  vcloud_director_host: 'host.api.example.com'
+    test:
+      vcloud_director_username: 'username@org_name'
+      vcloud_director_password: 'password'
+      vcloud_director_host: 'host.api.example.com'
+
+    test2:
+      vcloud_director_username: 'username@org_name'
+      vcloud_director_password: 'password'
+      vcloud_director_host: 'host.api.vendor.net'
+
+You can then pass the `FOG_CREDENTIAL` environment variable at the start of your command. The value of the `FOG_CREDENTIAL` environment variable is the name of the credential set in your fog file which you wish to use.  For instance:
+
+    FOG_CREDENTIAL=test2 bundle exec vcloud-launch node.yaml
+
+To understand more about `.fog` files, visit the 'Credentials' section here => http://fog.io/about/getting_started.html.
+
+### 2. Log on externally and supply your session token
+
+You can choose to log on externally by interacting independently with the API and supplying your session token to the
+tool by setting the `FOG_VCLOUD_TOKEN` ENV variable. This option reduces the risk footprint by allowing the user to
+store their credentials in safe storage. The default token lifetime is '30 minutes idle' - any activity extends the life by another 30 mins.
+
+A basic example of this would be the following:
+
+    curl
+       -D-
+       -d ''
+       -H 'Accept: application/*+xml;version=5.1' -u '<user>@<org>'
+       https://host.com/api/sessions
+
+This will prompt for your password.
 
-test2:
-  vcloud_director_username: 'username@org_name'
-  vcloud_director_password: 'password'
-  vcloud_director_host: 'host.api.vendor.net'
+From the headers returned, select the header below
 
-You can then pass the FOG_CREDENTIAL environment variable at the start of your command. The value of the FOG_CREDENTIAL environment variable is the name of the credential set in your fog file which you wish to use. For instance:
+     x-vcloud-authorization: AAAABBBBBCCCCCCDDDDDDEEEEEEFFFFF=
 
-FOG_CREDENTIAL=test2 vcloud-launch node.yaml
+Use token as ENV var FOG_VCLOUD_TOKEN
 
-An example configuration file is located in examples/vcloud-launch
+    FOG_VCLOUD_TOKEN=AAAABBBBBCCCCCCDDDDDDEEEEEEFFFFF= bundle exec ...
 
 ## Contributing
 
@@ -93,16 +123,16 @@ environment, unless care is taken with the entities being tested.
 The easiest thing to do is create a local shell script called
 `vcloud_env.sh` and set the contents:
 
-    export FOG\_CREDENTIAL=test
-    export VCLOUD\_VDC\_NAME="Name of the VDC"
-    export VCLOUD\_CATALOG\_NAME="catalog-name"
-    export VCLOUD\_TEMPLATE\_NAME="name-of-template"
-    export VCLOUD\_NETWORK1\_NAME="name-of-primary-network"
-    export VCLOUD\_NETWORK2\_NAME="name-of-secondary-network"
-    export VCLOUD\_NETWORK1\_IP="ip-on-primary-network"
-    export VCLOUD\_NETWORK2\_IP="ip-on-secondary-network"
-    export VCLOUD\_TEST\_STORAGE\_PROFILE="storage-profile-name"
-    export VCLOUD\_EDGE\_GATEWAY="name-of-edge-gateway-in-vdc"
+    export FOG_CREDENTIAL=test
+    export VCLOUD_VDC_NAME="Name of the VDC"
+    export VCLOUD_CATALOG_NAME="catalog-name"
+    export VCLOUD_TEMPLATE_NAME="name-of-template"
+    export VCLOUD_NETWORK1_NAME="name-of-primary-network"
+    export VCLOUD_NETWORK2_NAME="name-of-secondary-network"
+    export VCLOUD_NETWORK1_IP="ip-on-primary-network"
+    export VCLOUD_NETWORK2_IP="ip-on-secondary-network"
+    export VCLOUD_STORAGE_PROFILE_NAME="storage-profile-name"
+    export VCLOUD_EDGE_GATEWAY="name-of-edge-gateway-in-vdc"
 
 Then run this before you run the integration tests.
 
@@ -114,14 +144,14 @@ There is an integration test to check storage profile behaviour, but it requires
 
 You will need to set the following environment variables:
 
-      export VDC\_NAME\_1="Name of the first vDC"
-      export VDC\_NAME\_2="Name of the second vDC"
-      export VCLOUD\_CATALOG\_NAME="Catalog name" # Can be the same as above settings if appropriate
-      export VCLOUD\_TEMPLATE\_NAME="Template name" # Can be the same as above setting if appropriate
-      export VCLOUD\_STORAGE\_PROFILE\_NAME="Storage profile name" # This needs to exist in both vDCs
-      export VDC\_1\_STORAGE\_PROFILE\_HREF="Href of the named storage profile in vDC 1"
-      export VDC\_2\_STORAGE\_PROFILE\_HREF="Href of the named storage profile in vDC 2"
-      export DEFAULT\_STORAGE\_PROFILE\_NAME="Default storage profile name"
-      export DEFAULT\_STORAGE\_PROFILE\_HREF="Href of default storage profile"
+      export VDC_NAME_1="Name of the first vDC"
+      export VDC_NAME_2="Name of the second vDC"
+      export VCLOUD_CATALOG_NAME="Catalog name" # Can be the same as above settings if appropriate
+      export VCLOUD_TEMPLATE_NAME="Template name" # Can be the same as above setting if appropriate
+      export VCLOUD_STORAGE_PROFILE_NAME="Storage profile name" # This needs to exist in both vDCs
+      export VDC_1_STORAGE_PROFILE_HREF="Href of the named storage profile in vDC 1"
+      export VDC_2_STORAGE_PROFILE_HREF="Href of the named storage profile in vDC 2"
+      export DEFAULT_STORAGE_PROFILE_NAME="Default storage profile name"
+      export DEFAULT_STORAGE_PROFILE_HREF="Href of default storage profile"
 
 To run this test: `rspec spec/integration/launcher/storage_profile_integration_test.rb`

data/lib/vcloud/launcher/version.rb

@@ -1,5 +1,5 @@
 module Vcloud
   module Launcher
-    VERSION = '0.0.2'
+    VERSION = '0.0.3'
   end
 end

data/spec/integration/launcher/vcloud_launcher_spec.rb

@@ -135,7 +135,7 @@ describe Vcloud::Launcher::Launch do
 
   def extract_disks(vm)
     vm[:'ovf:VirtualHardwareSection'][:'ovf:Item'].collect { |d|
-      {:name => d[:"rasd:ElementName"], :size => d[:"rasd:HostResource"][:ns12_capacity]} if d[:'rasd:ResourceType'] == '17'
+      {:name => d[:"rasd:ElementName"], :size => (d[:"rasd:HostResource"][:ns12_capacity] || d[:"rasd:HostResource"][:vcloud_capacity])} if d[:'rasd:ResourceType'] == '17'
     }.compact
   end
 

data/vcloud-launcher.gemspec

@@ -21,7 +21,7 @@ Gem::Specification.new do |s|
   s.required_ruby_version = '>= 1.9.2'
 
   s.add_runtime_dependency 'methadone'
-  s.add_runtime_dependency 'vcloud-core', '>= 0.0.9'
+  s.add_runtime_dependency 'vcloud-core', '>= 0.0.12'
   s.add_development_dependency 'aruba', '~> 0.5.3'
   s.add_development_dependency 'cucumber', '~> 1.3.10'
   s.add_development_dependency 'gem_publisher', '1.2.0'

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: vcloud-launcher
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.3
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-04-03 00:00:00.000000000 Z
+date: 2014-04-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: methadone
@@ -34,7 +34,7 @@ dependencies:
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 0.0.9
+        version: 0.0.12
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -42,7 +42,7 @@ dependencies:
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 0.0.9
+        version: 0.0.12
 - !ruby/object:Gem::Dependency
   name: aruba
   requirement: !ruby/object:Gem::Requirement
@@ -132,6 +132,7 @@ extensions: []
 extra_rdoc_files: []
 files:
 - .gitignore
+- CHANGELOG.md
 - Gemfile
 - LICENSE.txt
 - README.md
@@ -189,7 +190,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: -109681801331986801
+      hash: 8814923118188880
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.23