vaquero_io 0.1.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: f0e69aebc6def71efb9a7cd91cf5b64766077a11
+  data.tar.gz: 05ce0aeb4dea579da2030acadb23a7b1dd415a42
+SHA512:
+  metadata.gz: 030f3c2e95d43d9d757fe65b1ff21a8a7fd1537961a7256ca8cb1960425afe6c29f682003a09d1102538bef377acba66bb0bd15eb875020600bb1534d822f64b
+  data.tar.gz: 4352daaa8dc7a608024346f4c8a257915e7bbb7ac550202f97030485590c6de3d0589558713d0c67e750a8a85ef8fe8c5e9e2643d27a8a7d461474a0c5cf9c67

data/.coveralls.yml

@@ -0,0 +1 @@
+service_name: travis-ci

data/.gitignore

@@ -0,0 +1,20 @@
+# bundler workings
+Gemfile.lock
+.bundle/
+vendor/
+
+
+# Misc things
+environments/
+infrastructure/
+required/
+platform.yml
+.idea/
+.ruby-version
+.yardoc/
+doc/
+coverage/
+pkg/
+lib/providers/
+.DS_Store
+tmp/

data/.rubocop.yml

@@ -0,0 +1,9 @@
+AllCops:
+  Exclude:
+    - Guardfile
+    - vendor/**/*
+    - example.rb
+Metrics/AbcSize:
+  Enabled: false
+#Style/SpecialGlobalVars:
+#  Enabled: false

data/.simplecov

@@ -0,0 +1,8 @@
+require 'simplecov'
+require 'coveralls'
+
+SimpleCov.formatter = Coveralls::SimpleCov::Formatter
+SimpleCov.start do
+  add_filter '/yardoc/'
+  add_filter '/bin/'
+end

data/.travis.yml

@@ -0,0 +1,3 @@
+language: ruby
+rvm:
+  - "2.1.5"

data/CHANGELOG.md

@@ -0,0 +1,12 @@
+vaquero CHANGELOG
+================
+
+## 0.1.0
+
+* Initial setup of gem framework.
+
+*note, at this point the guard implementation throws errors when running. Not sure what the cause is...
+
+
+Check the [Markdown Syntax Guide](http://daringfireball.net/projects/markdown/syntax) for help with Markdown.
+The [Github Flavored Markdown page](http://github.github.com/github-flavored-markdown/) describes the differences between markdown on github and standard markdown.

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# gem dependencies in vaquero_io.gemspec
+gemspec

data/Guardfile

@@ -0,0 +1,41 @@
+# A sample Guardfile
+# More info at https://github.com/guard/guard#readme
+
+# notification :growl, sticky: true
+
+guard :rubocop do
+  watch(%r{.+\.rb$})
+  watch(%r{(?:.+/)?\.rubocop\.yml$}) { |m| File.dirname(m[0]) }
+end
+
+guard :rspec, cmd: 'bundle exec rspec' do
+  require 'guard/rspec/dsl'
+  dsl = Guard::RSpec::Dsl.new(self)
+
+  # Feel free to open issues for suggestions and improvements
+
+  # RSpec files
+  rspec = dsl.rspec
+  watch(rspec.spec_helper) { rspec.spec_dir }
+  watch(rspec.spec_support) { rspec.spec_dir }
+  watch(rspec.spec_files)
+
+  # Ruby files
+  ruby = dsl.ruby
+  dsl.watch_spec_files_for(ruby.lib_files)
+end
+
+guard 'cucumber' do
+  watch(%r{^features/.+\.feature$})
+  watch(%r{^features/support/.+$})          { 'features' }
+
+  watch(%r{^features/step_definitions/(.+)_steps\.rb$}) do |m|
+    Dir[File.join("**/#{m[1]}.feature")][0] || 'features'
+  end
+end
+
+guard 'yard' do
+  watch(%r{app/.+\.rb})
+  watch(%r{lib/.+\.rb})
+  watch(%r{ext/.+\.c})
+end

data/LICENSE.txt

@@ -0,0 +1,203 @@
+
+                                 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 2014
+
+   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,19 @@
+[![Stories in Ready](https://badge.waffle.io/vaquero-io/vaquero_io.svg?label=ready&title=Ready)](http://waffle.io/vaquero-io/vaquero_io)
+[![Join the chat at https://gitter.im/vaquero_io-io/vaquero_io](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/vaquero-io/vaquero_io?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+
+[![Build Status](https://travis-ci.org/vaquero-io/vaquero_io.svg?branch=master)][travis]
+[![Dependency Status](https://gemnasium.com/vaquero-io/vaquero_io.png?travis)][gemnasium]
+[![Coverage Status](https://coveralls.io/repos/vaquero-io/vaquero_io/badge.png?branch=master)][coveralls]
+[![Inline docs](http://inch-ci.org/github/vaquero-io/vaquero_io.png?branch=master)][inch]
+
+[travis]: http://travis-ci.org/vaquero-io/vaquero_io
+[gemnasium]: https://gemnasium.com/vaquero-io/vaquero_io
+[coveralls]: https://coveralls.io/r/vaquero-io/vaquero_io
+[inch]: http://inch-ci.org/github/vaquero-io/vaquero_io
+
+# vaquero: environment provisioning
+
+vaquero_io is envisioned as an extensible vm provisioning and bootstrap automation tool for managing the multiple servers, roles, and environments that make up a typical continuous delivery architectural design for a web based software-as-a-service application.
+
+#### under development
+This tool is the re-write of the elevage tool that will incorporate a plug-in architecture to enable easier use of mutltiple virtualization infrastructures.

data/Rakefile

@@ -0,0 +1,20 @@
+require 'bundler'
+require 'rspec/core/rake_task'
+require 'cucumber/rake/task'
+require 'coveralls/rake/task'
+require 'yard'
+
+Bundler::GemHelper.install_tasks
+RSpec::Core::RakeTask.new(:spec)
+Cucumber::Rake::Task.new(:features)
+Coveralls::RakeTask.new
+
+task :style do
+  sh 'rubocop'
+end
+
+task :doc do
+  sh 'yard'
+end
+
+task default: [:spec, :features, :style, :doc, 'coveralls:push']

data/bin/vaquero

@@ -0,0 +1,4 @@
+#!/usr/bin/env ruby
+require 'vaquero_io/runner'
+
+VaqueroIo::Runner.new(ARGV.dup).execute!

data/features/health.feature

@@ -0,0 +1,276 @@
+Feature: Provider Health check
+
+  As an Infracoder developing the vaquero command line tool
+  I want to routinely test the syntactic health of the platform definition files against the plugin definition
+  In order to support consistent maintenance of large and multi-environment platforms
+
+  Scenario: Health check of a correctly defined platform
+
+    Given a file named "platform.yml" with:
+    """
+    platform:
+      product: test
+      provider: vaquero_io-plugin-test
+      plugin_version: 0.1.1
+
+      environments:
+        - dev
+        - prod
+
+      #
+      # environment    environment name from the key above
+      # component      component name
+      # instance       single leading zero 0..9, up to count of component pool
+      # geo            first letter of geo key value
+      # 'string'       any single quoted string, escape char not evaluated
+      #
+
+      nodename:
+        - 'node'
+        - instance
+
+      # You can add any other custom attributes to the platform definition
+      # by creating additional yml files with key values. The referenced
+      # files are, by convention, assumed to have the following structure:
+      #
+      # tags:
+      #
+      #   tagset1: &tagset1
+      #     key1: value
+      #     key2: value
+      #     ...
+      #
+      #   tagset2:
+      #     <<: *tagset1
+      #     key2: override value
+      #
+      #
+      # Example: array of string
+      #
+      # references:
+      #   path: 'infrastructure/'
+      #   keyfiles:
+      #     - tags
+      #
+
+      pools:
+
+        defaultpool: &defaultpool
+          file1: devweb
+          file2: nonprodweb
+          count: 2
+          run_list:
+            - 'role[loc_uswest]'
+            - 'recipe[loc_uswest]'
+          component_role: 'role[aw_#]'
+          chef_server: https://manage.chef.io
+          addresses:
+            -
+
+      components:
+
+        api:
+          <<: *defaultpool
+          addresses:
+            - 10.10.10.1
+            - 10.10.10.2
+
+        aui:
+          <<: *defaultpool
+          addresses:
+            - 10.10.10.10
+            - 10.10.10.20
+    """
+    Given a file named "required/file1.yml" with:
+    """
+    file1:
+      #
+      file1record1:
+        any_alphanumeric: DEV_WEB_NET
+        any_IP: 10.10.128.1
+        any_integer: 19
+        any_boolean: true
+
+      file1record2:
+        any_alphanumeric: PROD_WEB_NET
+        any_IP: 10.10.20.1
+        any_integer: 24
+        any_boolean: false
+    """
+    Given a file named "required/file2.yml" with:
+    """
+    file2:
+      #
+      default: &default
+        cpu: 1
+        ram: 2048
+        drive:
+          mount: '/media/data'
+          capacity: 8192
+        image: 'centos_2015.xxx'
+
+      nonprodweb:
+        <<: *default
+
+      prodweb:
+        <<: *default
+        ram: 4096
+        drive:
+          capacity: 28192
+
+    """
+    Given a file named "environments/dev.yml" with:
+    """
+
+    """
+    Given a file named "environments/prod.yml" with:
+    """
+
+    """
+    When I run `vaquero plugin install https://github.com/vaquero-io/vaquero_io-plugin-test.git`
+    When I run `vaquero health -p vaquero_io-plugin-test`
+    Then the exit status should be 0
+    And the output should contain "Success:"
+    And I will clean up the test plugin "lib/providers/vaquero_io-plugin-test" when finished
+
+  Scenario: Health check of a incorrectly defined platform (stress each param in test platform.yml)
+
+    # for required files: this test only omits. See later test for validation of provided entries
+    # for run_lists: test empty array
+    # for component_role: test mismatch regex
+
+    Given a file named "platform.yml" with:
+    """
+    platform:
+      product: test
+      provider: vaquero_io-plugin-test
+      plugin_version: 0.1.1
+
+      environments:
+        -
+
+      #
+      # environment    environment name from the key above
+      # component      component name
+      # instance       single leading zero 0..9, up to count of component pool
+      # geo            first letter of geo key value
+      # 'string'       any single quoted string, escape char not evaluated
+      #
+
+      nodename:
+        -
+
+      # You can add any other custom attributes to the platform definition
+      # by creating additional yml files with key values. The referenced
+      # files are, by convention, assumed to have the following structure:
+      #
+      # tags:
+      #
+      #   tagset1: &tagset1
+      #     key1: value
+      #     key2: value
+      #     ...
+      #
+      #   tagset2:
+      #     <<: *tagset1
+      #     key2: override value
+      #
+      #
+      # Example: array of string
+      #
+      # references:
+      #   path: 'infrastructure/'
+      #   keyfiles:
+      #     - tags
+      #
+
+      pools:
+
+        defaultpool: &defaultpool
+          count: 25
+          run_list: 'string instead of array'
+          component_role: 'role[aw_%]'
+          chef_server: 10.10.10.1
+          addresses:
+            -
+
+      components:
+
+        api:
+          <<: *defaultpool
+          addresses:
+            - 10.10.300.1
+            - 10.10.10.2
+
+        aui:
+          <<: *defaultpool
+          addresses:
+            - 10.10.10.10
+            - 10.10.10.20
+    """
+    Given a file named "required/file1.yml" with:
+    """
+    file1:
+      #
+      file1record1:
+        any_alphanumeric: 0
+        any_IP: 10.10.300.1
+        any_integer: 30
+        any_boolean: random
+
+      file1record2:
+        any_alphanumeric: PROD_WEB_NET
+        any_IP: 10.10.20.1
+        any_integer: 24
+        any_boolean: false
+    """
+    Given a file named "required/file2.yml" with:
+    """
+    file2:
+      #
+      default: &default
+        cpu: 100
+        ram: 0
+        drive:
+          mount: 0
+          capacity: 0
+        image:
+
+      nonprodweb:
+        <<: *default
+
+      prodweb:
+        <<: *default
+        ram: 4096
+        drive:
+          capacity: 28192
+
+    """
+    Given a file named "environments/dev.yml" with:
+    """
+
+    """
+    Given a file named "environments/prod.yml" with:
+    """
+
+    """
+    When I run `vaquero plugin install https://github.com/vaquero-io/vaquero_io-plugin-test.git`
+    When I run `vaquero health -p vaquero_io-plugin-test`
+    And the output should contain "Empty environments definition"
+    And the output should contain "Empty nodename convention"
+    And the output should contain "No references to required file:file1"
+    And the output should contain "No references to required file:file2"
+    And the output should contain "Validation error: api:count"
+    And the output should contain "Validation error: api:run_list"
+    And the output should contain "Validation error: api:component_role"
+    And the output should contain "Validation error: api:chef_server"
+    And the output should contain "Validation error: api:addresses"
+    And the output should contain "Validation error: file1record1:any_alphanumeric"
+    And the output should contain "Validation error: file1record1:any_IP"
+    And the output should contain "Validation error: file1record1:any_integer"
+    And the output should contain "Validation error: file1record1:any_boolean"
+    And the output should contain "Validation error: default:cpu"
+    And the output should contain "Validation error: default:ram"
+    And the output should contain "Validation error: default:drive"
+    And the output should contain "Validation error: default:image"
+    And I will clean up the test plugin "lib/providers/vaquero_io-plugin-test" when finished