kitchen-vcair 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 795c6c4ab44475c53e864812dace3e69c6177437
+  data.tar.gz: 776badc46e81d8e63d8b641ddeb92b9e96083403
+SHA512:
+  metadata.gz: 9fe2794583e98129127a580ed9534d2f39d1cd3b8fbac14f87216a56af918cafc5e0f615c3df85e45f062bab92d6838953bd28cb294e2ebc59065de7d6cdb9fe
+  data.tar.gz: 2bf503afddd35f11b00c875ff4eff1f423dd6dcdebe677352941182a50619405bc7fa211f8b90633c12983f23593c849abe91a427d1efe5a894627cfaa804edb

data/.gitignore

@@ -0,0 +1,21 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+.kitchen
+*.sw?
+*~
+.env.sh

data/.rubocop.yml

@@ -0,0 +1,14 @@
+Metrics/AbcSize:
+  Max: 50
+Metrics/ClassLength:
+  Max: 300
+Metrics/LineLength:
+  Max: 130
+Metrics/MethodLength:
+  Max: 25
+Style/Documentation:
+  Enabled: false
+Style/SignalException:
+  Enabled: false
+Style/SpaceInsideBrackets:
+  Enabled: false

data/CHANGELOG.md

@@ -0,0 +1,16 @@
+# kitchen-vcair Changelog
+
+## Release: 1.0.0 / 2015-08-21
+* Initial public release
+* Refactor by Chef Partner Engineering to match style of other VMware plugins
+* Support for vCloud Air OnDemand
+
+## Release: 0.1.1 / 2015-06-04
+* Destroy working
+* Password updates
+* Documentation updates
+* Cleanup and refactoring
+
+## Release: 0.1.0 / 2015-05-xx
+
+* Initial release by Vulk.

data/Gemfile

@@ -0,0 +1,6 @@
+# Encoding: UTF-8
+
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in kitchen-rackspace.gemspec
+gemspec

data/LICENSE.txt

@@ -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,188 @@
+# kitchen-vcair
+
+A driver to allow Test Kitchen to consume vCloud Air resources to perform testing.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'kitchen-vcair'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install kitchen-vcair
+
+Or even better, install it via ChefDK:
+
+    $ chef gem install kitchen-vcair
+
+## Usage
+
+After installing the gem as described above, edit your .kitchen.yml file to set the driver to 'vcair' and supply your login credentials:
+
+```yaml
+driver:
+  name: vcair
+  vcair_username: user@domain.com
+  vcair_password: MyS33kretPassword
+  vcair_api_host: some-host.vchs.vmware.com
+  vcair_org: M12345678-4321
+```
+
+Additionally, the following parameters are required:
+
+ * **vdc_id** or **vdc_name**: The ID or name of the vDC in which to create your vApp/VM.
+ * **catalog_id** or **catalog_name**: The ID or name of the catalog that contains your image/template.
+ * **image_id** or **image_name**: The ID or name of the image you wish to use to create your VM.
+ * **network_id** or **network_name**: The ID or name of the network to which to attach to your VM.
+
+There are a number of optional parameters you can configure as well:
+
+ * **cpus**: The number of vCPUs to configure for your VM. Default: 1
+ * **memory**: The amount of RAM, in MB, to configure for your VM. Default: 1024
+ * **vcair_api_path**: The URI path for the compute API. This needs to be set when using vCloud Air OnDemand. Default: /api
+ * **vm_password**: The password to set via VM customization for the root/administrator user.
+   * Be sure to set the same password in your `transport` section, too!
+   * NOTE: see the *known issues* section below regarding Windows and passwords.
+
+All of the above settings can be set globally (in the top-level `driver` section), or can be set individually for each platform. For example, you may wish to set your vDC and network globally, but set your catalog and image for each individual platform, and increase the vCPUs/RAM assigned to your windows node:
+
+```yaml
+driver:
+  name: vcair
+  vcair_username: user@domain.com
+  vcair_password: MyS33kretPassword
+  vcair_api_host: some-host.vchs.vmware.com
+  vcair_org: M12345678-4321
+  vdc_name: MyCompany VDC 1
+  network_name: vdc1-default-routed
+
+platforms:
+  - name: centos
+    driver:
+      catalog_name: Public Catalog
+      image_name: CentOS64-64BIT
+  - name: windows
+    driver:
+      catalog_name: Public Catalog
+      image_name: W2K12-STD-R2-64BIT
+      cpus: 2
+      memory: 4096
+```
+
+### vCloud Air Subscription vs. OnDemand
+
+kitchen-vcair works as-is with vCloud Air Subscription. In vCloud Air OnDemand,
+the API path is different. To use this plugin with vCloud Air OnDemand, you
+will need to set the `vcair_api_path` configuration parameter to `/api/compute/api`:
+
+```yaml
+driver:
+  vcair_api_path: /api/compute/api
+```
+
+Also, in our testing, we found many of the VMware-provided images are missing
+core configurations, such as properly-configured DNS resolvers. We strongly
+recommend building your own images off the VMware-provided images with proper
+configurations.
+
+## Known Issues and Workarounds
+
+### SSH Authentication - passwords vs. public-key
+
+vCloud Air does not natively support deploying SSH keys to new VMs like other
+cloud providers. Therefore, many of the images in the vCloud Air public catalog
+only support password authentication.
+
+#### Setting your own password
+
+Through VM customization, vCloud Air allows you to specify a password that should
+be set for the root account.  You can use the `vm_password` config parameter to
+specify that password:
+
+```yaml
+driver:
+  vm_password: mysupersecretpassword
+```
+
+... and then tell the transport to use that same password:
+
+```yaml
+transport:
+  password: mysupersecretpassword
+```
+
+#### Using the pre-generated password by vCloud Air
+
+**This is not supported.** Unfortunately, a bug in Fog prevents us from
+retrieving that password, and a issue/PR will be logged to address this.
+
+### WinRM Authentication
+
+#### Setup
+
+Many of the images in the vCloud Air public catalog do not have WinRM enabled.
+You will need to provide a customization script to enable WinRM.  An example
+can be found in the `examples/` directory in this repo.  Note that multiple
+reboots are required for the VM to become ready for Test Kitchen to use, so
+the time required for a Windows VM to be ready is fairly long.
+
+A potential workaround to this would be to create your own VM with WinRM enabled
+and configured properly and publish it in your own catalog.
+
+#### Setting your own password
+
+The same customization function that works for Linux does not appear to work for
+Windows in vCloud Air. Additionally, Windows does not appear to honor the
+customization setting that disables the forced password change on first login.
+
+Therefore, a customization script will need to be used to set your Administrator
+password. See the `examples/` directory for a sample customization script that
+enables WinRM and sets the Administrator password.
+
+### NAT and Public IP Support
+
+Unlike other cloud providers, vCloud Air does not treat public IPs as objects
+that can be associated with VMs. Instead, those IPs are associated with network
+objects called "gateways" which then require NAT and firewall rules to be
+created.  The Fog library does not support the creation of those objects.
+
+Therefore, only routed networks are supported, and it is required that Test
+Kitchen be executed on a network within vCloud Air that has access to the
+destination network on which your test VMs will be deployed.
+
+## License and Authors
+
+Author:: Chef Partner Engineering (<partnereng@chef.io>)
+
+Copyright:: Copyright (c) 2015 Chef Software, Inc.
+
+License:: Apache License, Version 2.0
+
+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.
+
+## Contributing
+
+We'd love to hear from you if this doesn't perform in the manner you expect. Please log a GitHub issue, or even better, submit a Pull Request with a fix!
+
+1. Fork it ( https://github.com/chef-partners/kitchen-vcair/fork )
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create a new Pull Request