vagrant-service-manager 1.4.0 → 1.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 649f720bd5476d1eefde64dbbea8675afc14d30f
-  data.tar.gz: ed744a9624ac588790d00aa23467e34bba0f69a2
+  metadata.gz: 5865b4ded5fb8b167fb6bad3617ced706128d9ad
+  data.tar.gz: 50ee25f87f5008d4358fd8b530809c60688b535d
 SHA512:
-  metadata.gz: ae010abd5e3bd9d0272810eca811d78cfb5ff1ec023e47e46b1318daa7019629f44a1b364034a14bc43bca7f001ed3f5f4a0fb0cbbda0c70170b38bb3c0ecc0b
-  data.tar.gz: 8ec4d235277ad550b3b1adfadcb2822db3dbb463bc7b904c04a9ae1f891fa2f65313512d36749ad9f795d3cfc2e26c88f09cbc9ada5c9adea39ecde30471e943
+  metadata.gz: 7982fc202d71510528e996d352f5228ad422563447bc614c6f28936839390fd4df188d8f2df264d4b82155fe121a07cd575e00de76f5026a12ab03bb6b141b77
+  data.tar.gz: e137145f206dc26bb95ec8a8aeadceb54aab1e1a16e2938db2521f8f94801b7aa3baf0e0e63fded8b1cc409a126a8024a21e66247bf5693c30c61c8ae5fa5663

data/.config/cucumber.yml

@@ -1,14 +1,9 @@
 # config/cucumber.yml
 ##YAML Template
 ---
-default: --profile html --tags ~@ci-only
+default: --profile html --tags ~@ci-only --tags ~@todo
+ci:  --format CiFormatter --no-color -m -b --tags ~@todo
 all: --profile html
 
 pretty: --format pretty -b
 html: --format progress --format html --out=build/features_report.html -b
-ci: --format pretty --format html --out=build/features_report.html --no-color -b
-
-help: --tags @help --profile html
-box: --tags @box --profile html
-env: --tags @env --profile html
-openshift: --tags @openshift --profile html

data/CHANGELOG.adoc

@@ -1,20 +1,36 @@
 = Revision History
 :toc:
 
+[[v1.4.1-nov-17-2016]]
+== 1.4.1 November 17, 2016
+* Fix #346 Adding a Rake task for Asciidoctor and enabling Guard and Live Reload @hferentschik
+* Fix #389 Refactoring proxy test @hferentschik
+* Fix #389 Support the use of install-cli in HTTP proxy environment @budhrg
+* Fix #434 Align proxy config names similar to 'sccli' @budhrg
+* Fix #362 Adding OpenShift configuration options back into VSM Readme @Preeticp
+* Fix #335 'bundle exec vagrant up --provider=libvirt' should work @budhrg
+* Fix #429 Minor language and formatting edits to Proxy section etc @Preeticp
+* Fix #427 Add acceptance test for 'box version' command @budhrg
+* Fix #425 Disabling CDK OpenShift tests until issue #415 gets resolved @hferentschik
+* Fix #425 Organizing Cucumber features around service functionality @hferentschik
+* Fix #419 Adding additional column to example table to print status [passed|failure|skipped] @hferentschik
+* Fix #417 Updated rake task to download latest CDK version @budhrg
+* Fix #421 Correct the order of drafting the release and updating to dev version @budhrg
+
 [[v1.4.0-oct-21-2016]]
 == 1.4.0 October 21, 2016
-* Fix #376 --path option of install cli not working as expected
-* Fix #327 and #326: Tests and docs for --cli-version and --path options
-* Fix #412 Pin the rubocop version and minimize the offenses
-* Fix #409 fixes Openshift service failed message on vagrant up
-* Fix #406 Service hooks doesn't start in vagrant reload
-* Fix #338 Updating broken links in CONTRIBUTING.adoc
-* Fix #407 Converted CHANGELOG from markdown to asciidoc
-* Fix #402 rename open_shift.rb file to openshift
-* Fix #302 service-manager config options for HTTP proxy
-* Fix #393 Fix expectations for Kubernetes tests on OS X
-* Fix #394 Forcing used Bundler version to 1.12.5 as required by Vagrant.
-* Fix #397 Using a guard clause instead of wrapping the code inside a conditional
+* Fix #376 --path option of install cli not working as expected @budhrg
+* Fix #327 and #326: Tests and docs for --cli-version and --path options @budhrg
+* Fix #412 Pin the rubocop version and minimize the offenses @budhrg
+* Fix #409 fixes Openshift service failed message on vagrant up @budhrg
+* Fix #406 Service hooks doesn't start in vagrant reload @budhrg
+* Fix #338 Updating broken links in CONTRIBUTING.adoc @Preeticp
+* Fix #407 Converted CHANGELOG from markdown to asciidoc @thatdocslady
+* Fix #402 rename open_shift.rb file to openshift @budhrg
+* Fix #302 service-manager config options for HTTP proxy @budhrg
+* Fix #393 Fix expectations for Kubernetes tests on OS X @budhrg
+* Fix #394 Forcing used Bundler version to 1.12.5 as required by Vagrant @hferentschik
+* Fix #397 Using a guard clause instead of wrapping the code inside a conditional @hferentschik
 
 [[v1.3.3-sep-1-2016]]
 == 1.3.3 September 1, 2016
@@ -25,7 +41,7 @@ exist @alexeykazakov
 [[v1.3.2-aug-31-2016]]
 == 1.3.2 August 31, 2016
 
-* Fix #384 don't execute os_variant for unsupported box
+* Fix #384 don't execute os_variant for unsupported box @budhrg
 
 [[v1.3.1-aug-25-2016]]
 == 1.3.1 August 25, 2016

data/CONTRIBUTING.adoc

@@ -120,10 +120,10 @@ $ git push origin master
   `vagrant-service-manager version=<version>`
 * Push commit to upstream
 * Release the gem: `bundle exec rake release`
+* Create a Github https://github.com/projectatomic/vagrant-service-manager/releases[release] and paste change log for release
 * Update link:lib/vagrant-service-manager/version.rb[version.rb] with the next anticipated release version, eg _1.42.0.dev_
 * Commit with message: `vagrant-service-manager setting dev version <version>.dev`
 * Push upstream
-* Create a Github https://github.com/projectatomic/vagrant-service-manager/releases[release] and paste change log for release
 
 == Maintainers
 

data/Gemfile

@@ -4,8 +4,6 @@ group :development do
   gem 'vagrant',
       git: 'https://github.com/mitchellh/vagrant.git',
       ref: 'v1.8.4'
-  gem 'vagrant-libvirt'              if RUBY_PLATFORM =~ /linux/i
-  gem 'fog-libvirt', '0.0.3'         if RUBY_PLATFORM =~ /linux/i # https://github.com/pradels/vagrant-libvirt/issues/568
   gem 'mechanize'
   gem 'json'
   gem 'cucumber', '~> 2.1'
@@ -14,6 +12,9 @@ group :development do
   gem 'launchy'
   gem 'rake', '10.4.2'
   gem 'rubocop', '0.44.1'
+  gem 'guard-rake'
+  gem 'guard-livereload', '~> 2.5', require: false
+  gem 'asciidoctor'
 end
 
 group :test do
@@ -23,4 +24,6 @@ end
 
 group :plugins do
   gemspec
+  gem 'vagrant-libvirt'              if RUBY_PLATFORM =~ /linux/i
+  gem 'fog-libvirt', '0.0.3'         if RUBY_PLATFORM =~ /linux/i # https://github.com/pradels/vagrant-libvirt/issues/568
 end

data/Guardfile

@@ -0,0 +1,10 @@
+# A sample Guardfile
+# More info at https://github.com/guard/guard#readme
+
+guard 'rake', task: 'html' do
+  watch(/^.*.adoc/)
+end
+
+guard 'livereload' do
+  watch(/^.*.html/)
+end

data/README.adoc

@@ -47,14 +47,15 @@ https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/docs/in
 ----------------------------------------------
 vagrant plugin install vagrant-service-manager
 ----------------------------------------------
+
 1.  Download the relevant Vagrantfile for your
 https://github.com/projectatomic/adb-atomic-developer-bundle[ADB]
 vagrant box, from the
 https://github.com/projectatomic/adb-atomic-developer-bundle/tree/master/components/centos[repository].
 For further details on the usage of custom Vagrantfiles designed for
-specific use cases, refer to the
-https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/docs/using.rst[Usage
-Documentation].
+specific use cases, refer to the Download ADB section in the
+https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/docs/installing.adoc[Installing ADB] Documentation.
+
 1.  Start the ADB vagrant box using `vagrant up`. For detailed
 instructions consult the
 https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/docs/installing.rst[Installation
@@ -66,7 +67,7 @@ non NAT network interface declaration in the Vagrantfile. If the user
 does not provide a network declaration in the Vagrantfile, a private
 DHCP network is added by default and a warning is displayed.
 
-1.  Run the plugin to get environment variables and certificates:
+1.  Run the plugin to get the environment variables and certificates:
 +
 ----------------------------------------------------------------------------
 $ vagrant service-manager env docker
@@ -90,16 +91,13 @@ will also re-download the certificates onto the host machine.
 
 === Available commands
 
-The following section lists the high level commands available for the plugin,
-which enable you to:
-
-- set up your environment variables and get the TLS certificates to secure the
-Docker communication channel
-- identify the routable ip address as well as the version of your VM
-- and manage the life cycle of the configured services
-
 For a detailed list of all available commands and their explanations refer
- to the link:commands.adoc[Commands Document].
+ to the link:commands.adoc[Commands Document]. +
+The following section lists the high level commands available for the plugin.
+which enable you to set up your environment variables and get the TLS
+certificates to secure the Docker communication channel; identify the
+routable ip address as well as the version of your VM and manage the life
+cycle of the configured services.
 
 - `vagrant service-manager [command] [--help | -h]` +
 Displays the possible commands, options and other relevant information
@@ -154,31 +152,58 @@ have IPv4 addresses, the address on eth2 is used.
 
 === HTTP Proxy Settings
 
-In an environment where HTTP traffic needs pass through a HTTP proxy, Docker
-and OpenShift need to be aware of the required proxy settings in order to function.
-`http_proxy`, `http_proxy_user` and `http_proxy_password` configurations need to be
-specified through Vagrantfile. You can do so via:
+In an environment where the HTTP traffic needs to pass through an
+HTTP proxy server, set the `proxy`, `proxy_user` and
+`proxy_password` proxy configurations in the Vagrantfiles to enable
+services like Docker and OpenShift to function correctly. +
+You can do so via:
+ +
+-----
+config.servicemanager.proxy = <Proxy URL>
+config.servicemanager.proxy_user = <Proxy user name>
+config.servicemanager.proxy_password = <Proxy user password>
+-----
 
-----------------------------------------------------------------------------
-config.servicemanager.http_proxy = <Proxy URL>
-config.servicemanager.http_proxy_user = <Proxy user name>
-config.servicemanager.http_proxy_password = <Proxy user password>
-----------------------------------------------------------------------------
+When these settings are applied, they are passed through to the Docker and OpenShift services. In an unauthenticated proxy environment, the `proxy_user` and `proxy_password` configurations can be omitted.
+
+NOTE: `http_proxy`, `http_proxy_user` and `http_proxy_password` have been depreacted now.
+
+=== Configuring Services
+The vagrant-service-manager helps you configure the service of your choice:
+
+. Enable the desired service(s) in the ADB Vagrantfile as:
++
+`config.servicemanager.services = 'openshift'`
++
+[NOTE]
+====
+- Docker is the default service for the Atomic Developer Bundle and does not require any configuration to ensure it is started whereas, the Red Hat Enterprise Linux Container Development Kit, which is based on ADB, automatically starts OpenShift. +
+- You can use a comma-separated list to enable multiple services. For instance: docker, openshift.
+====
+
+. Enable the relevant option for the services you have selected in the Vagrantfile. For example, specific versions of OpenShift can be set using the following variables:
++
+
+- `config.servicemanager.openshift_docker_registry = "docker.io"` - Specifies the registry from where the OpenShift image is pulled.
++
+- `config.servicemanager.openshift_image_name = "openshift/origin"` - Specifies the image to be used.
++
+- `config.servicemanager.openshift_image_tag = "v1.3.0"` - Specifies the version of the image to be used.
 
-When these settings are applied, they are passed through to the Docker and
-OpenShift service. `http_proxy_user` and `http_proxy_password` can be omitted in an
-unauthenticated proxy environment.
 
 == Development
 
 === Setup
 
 1. After cloning the repository, install the http://bundler.io/[Bundler]
-gem (Note, you need to specify 1.12.5. It won't work with the latest version of Bundler):
+gem:
 +
 ---------------------
 $ gem install bundler -v 1.12.5
 ---------------------
++
+NOTE: You need to specify version 1.12.5. It will not work with the latest version of Bundler.
+
 
 1. Then setup your project dependencies:
 +
@@ -187,7 +212,7 @@ $ bundle install
 ----------------
 
 1. The build is driven via `rake`. All build related tasks should be executed
-in the Bundler environment, e.g. `bundle exec rake clean`. You can get a
+in the Bundler environment, for example `bundle exec rake clean`. You can get a
 list of available Rake tasks via:
 +
 ---------------------
@@ -303,6 +328,31 @@ _build/features_report.html_. They can be opened via:
 $ bundle exec rake features:open_report
 ---------------------------------------
 
+=== Asciidoc
+
+The documentation of this plugin is written in http://asciidoctor.org[Asciidoc]. If you need some syntax help,
+refer to the http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/[AsciiDoc Syntax Quick Reference].
+
+To build the documentation you can execute
+
+----
+$ bundle exec rake html
+----
+
+which will build the HTML documentation into the folder _build/html_.
+
+The source code also contains a link:Guardfile[Guardfile] for the https://github.com/guard/guard[Guard] library.
+You can execute
+
+----
+$ bundle exec guard
+----
+
+and your HTML documentation will be automatically updated on each change to an Asciidoc source file.
+https://github.com/guard/guard-livereload[Live reload] is also enabled, so you just need to install the right
+http://livereload.com/extensions/#installing-sections[LiveReload Safari/Chrome/Firefox extension] and your
+browser will refresh the page each time you save a change to your Asciidoc files.
+
 == Getting involved
 
 We welcome your input. You can submit issues or pull requests with

data/Rakefile

@@ -8,6 +8,7 @@ require 'fileutils'
 require 'yaml'
 require 'launchy'
 require 'date'
+require 'asciidoctor'
 
 CLOBBER.include('pkg')
 CLEAN.include('build')
@@ -43,6 +44,14 @@ namespace :features do
   end
 end
 
+desc 'Render Asciidoc into HTML'
+adoc_files = Rake::FileList['**/*.adoc']
+task html: adoc_files.ext('.html')
+rule '.html' => '.adoc' do |t|
+  FileUtils.mkdir_p 'build/html'
+  Asciidoctor.convert_file t.source, to_dir: 'build/html'
+end
+
 desc 'Download the required Vagrant boxes for the Cucumber tests'
 task get_boxes: :init do
   box_dir = File.join(File.dirname(__FILE__), BOX_DIR)
@@ -233,9 +242,9 @@ class NightlyCDKDownloader < DownloadTask
 end
 
 class PublicCDKDownloader < DownloadTask
-  CDK_DOWNLOAD_URL = 'https://access.redhat.com/downloads/content/293/ver=2.1/rhel---7/2.1.0/x86_64/product-software'.freeze
-  CDK_BOX_BASE_NAME = 'rhel-cdk-kubernetes-7.2-25.x86_64.vagrant'.freeze
-  LATEST_VERSION = 'v. 2.1.0 for x86_64'.freeze
+  CDK_DOWNLOAD_URL = 'https://access.redhat.com/downloads/content/293/ver=2.2/rhel---7/2.2.0/x86_64/product-software'.freeze
+  CDK_BOX_BASE_NAME = 'rhel-cdk-kubernetes-7.2-29.x86_64.vagrant'.freeze
+  LATEST_VERSION = 'v. 2.2.0 for x86_64'.freeze
 
   def initialize(box_dir, provider)
     super(box_dir, provider)

data/features/adb-openshift.feature

@@ -22,7 +22,7 @@ Feature: Command output from various OpenShift related commands in ADB
       config.vm.provider('libvirt') { |v| v.memory = 3072 }
       config.vm.provider('virtualbox') { |v| v.memory = 3072 }
 
-      config.servicemanager.services = 'docker, openshift'
+      config.servicemanager.services = 'openshift'
     end
     """
 
@@ -37,8 +37,7 @@ Feature: Command output from various OpenShift related commands in ADB
     And I successfully run `bundle exec vagrant service-manager status`
     Then stdout from "bundle exec vagrant service-manager status" should contain "openshift - running"
 
-    When I sleep for 10 seconds
-    And I successfully run `bundle exec vagrant service-manager env openshift`
+    When I successfully run `bundle exec vagrant service-manager env openshift`
     Then stdout from "bundle exec vagrant service-manager env openshift" should be evaluable in a shell
     And stdout from "bundle exec vagrant service-manager env openshift" should contain:
     """
@@ -61,14 +60,12 @@ Feature: Command output from various OpenShift related commands in ADB
     DOCKER_REGISTRY=hub.openshift.centos7-adb.<ip>.xip.io
     """
 
-    When I sleep for 10 seconds
-    And I successfully run `bundle exec vagrant service-manager install-cli openshift --cli-version 1.3.0`
+    When I successfully run `bundle exec vagrant service-manager install-cli openshift --cli-version 1.3.0`
     Then the exit status should be 0
     And the binary "oc" of service "openshift" should be installed with version "1.3.0"
     And stdout from "bundle exec vagrant service-manager install-cli openshift --cli-version 1.3.0" should be evaluable in a shell
 
-    When I sleep for 10 seconds
-    And I evaluate and run `bundle exec vagrant service-manager install-cli openshift --cli-version 1.3.0 --path #{ENV['VAGRANT_HOME']}/oc`
+    When I evaluate and run `bundle exec vagrant service-manager install-cli openshift --cli-version 1.3.0 --path #{ENV['VAGRANT_HOME']}/oc`
     Then the exit status should be 0
     And the binary should be installed in path "#{ENV['VAGRANT_HOME']}/oc"
     And stdout after evaluating and running "bundle exec vagrant service-manager install-cli openshift --cli-version 1.3.0 --path #{ENV['VAGRANT_HOME']}/oc" should be evaluable in a shell

data/features/cdk-openshift.feature

@@ -1,7 +1,7 @@
 Feature: Command output from various OpenShift related commands in CDK
   service-manager should return the correct output from commands affecting OpenShift in CDK
 
-  @openshift
+  @todo
   Scenario Outline: Boot and execute commands
     Given box is <box>
     And provider is <provider>
@@ -22,7 +22,7 @@ Feature: Command output from various OpenShift related commands in CDK
       config.vm.provider('libvirt') { |v| v.memory = 3072 }
       config.vm.provider('virtualbox') { |v| v.memory = 3072 }
 
-      config.servicemanager.services = 'docker, openshift'
+      config.servicemanager.services = 'openshift'
     end
     """
 
@@ -32,8 +32,8 @@ Feature: Command output from various OpenShift related commands in CDK
     ==> default: Docker service configured successfully...
     ==> default: OpenShift service configured successfully...
     """
-
-    When I successfully run `bundle exec vagrant service-manager status`
+    
+    And I successfully run `bundle exec vagrant service-manager status`
     Then stdout from "bundle exec vagrant service-manager status" should contain "openshift - running"
 
     When I successfully run `bundle exec vagrant service-manager env openshift`

data/features/docker.feature

@@ -0,0 +1,298 @@
+Feature: Command output from box command
+  service-manager should return the correct output from box commands
+
+  Scenario Outline: Boot and execute box commands
+    Given box is <box>
+    And provider is <provider>
+    And a file named "Vagrantfile" with:
+    """
+    begin
+      require 'vagrant-libvirt'
+    rescue LoadError
+      # NOOP
+    end
+
+    Vagrant.configure('2') do |config|
+      config.vm.box = '<box>'
+      config.vm.box_url = 'file://../../.boxes/<box>-<provider>.box'
+      config.vm.network :private_network, ip: '<ip>'
+      config.vm.synced_folder '.', '/vagrant', disabled: true
+      config.servicemanager.services = 'docker'
+    end
+    """
+
+    When I run `bundle exec vagrant up --provider <provider>`
+    Then the exit status should be 0
+    And stdout from "bundle exec vagrant up --provider <provider>" should contain:
+    """
+    ==> default: Docker service configured successfully...
+    """
+
+    ####################################################################################################################
+    # BOX command
+    ####################################################################################################################
+    When I run `bundle exec vagrant service-manager box`
+    Then the exit status should be 1
+    And stdout from "bundle exec vagrant service-manager box" should contain:
+    """
+    Usage: vagrant service-manager box <sub-command> [options]
+
+    Sub-Command:
+          version    display version and release information about the running VM
+          ip         display routable IP address of the running VM
+
+    Options:
+          --script-readable  display information in a script readable format
+          -h, --help         print this help
+    """
+
+    When I successfully run `bundle exec vagrant service-manager box --help`
+    Then the exit status should be 0
+    And stdout from "bundle exec vagrant service-manager box --help" should contain:
+    """
+    Usage: vagrant service-manager box <sub-command> [options]
+
+    Sub-Command:
+          version    display version and release information about the running VM
+          ip         display routable IP address of the running VM
+
+    Options:
+          --script-readable  display information in a script readable format
+          -h, --help         print this help
+
+    Examples:
+          vagrant service-manager box version
+          vagrant service-manager box version --script-readable
+          vagrant service-manager box ip
+          vagrant service-manager box ip --script-readable
+    """
+
+    When I successfully run `bundle exec vagrant service-manager box ip`
+    Then stdout from "bundle exec vagrant service-manager box ip" should contain "<ip>"
+
+    When I successfully run `bundle exec vagrant service-manager box ip --script-readable`
+    Then stdout from "bundle exec vagrant service-manager box ip --script-readable" should contain "IP=<ip>"
+    And stdout from "bundle exec vagrant service-manager box ip --script-readable" should be script readable
+
+    When I successfully run `bundle exec vagrant service-manager box version`
+    Then stdout from "bundle exec vagrant service-manager box version" should match /(Container Development Kit \(CDK\) \d.\d.?\d?|Atomic Developer Bundle \(ADB\) \d.\d.?\d?)/
+
+    When I successfully run `bundle exec vagrant service-manager box version --script-readable`
+    Then stdout from "bundle exec vagrant service-manager box version --script-readable" should match /(Container Development Kit \(CDK\)|Atomic Developer Bundle \(ADB\))/
+    And stdout from "bundle exec vagrant service-manager box version --script-readable" should match /VARIANT_ID="<box>"/
+    And stdout from "bundle exec vagrant service-manager box version --script-readable" should match /VARIANT_VERSION="\d.\d.?\d?"/
+    And stdout from "bundle exec vagrant service-manager box version --script-readable" should be script readable
+
+    ####################################################################################################################
+    # ENV command
+    ####################################################################################################################
+    When I successfully run `bundle exec vagrant service-manager env --help`
+    Then the exit status should be 0
+    And stdout from "bundle exec vagrant service-manager env --help" should contain:
+    """
+    Usage: vagrant service-manager env [object] [options]
+
+    Objects:
+          docker      display information and environment variables for docker
+          openshift   display information and environment variables for openshift
+          kubernetes  display information and environment variables for kubernetes
+
+    If OBJECT is omitted, display the information for all active services
+
+    Options:
+          --script-readable  display information in a script readable format.
+          -h, --help         print this help
+    """
+
+    When I successfully run `bundle exec vagrant service-manager env`
+    Then stdout from "bundle exec vagrant service-manager env" should be evaluable in a shell
+
+    When I successfully run `bundle exec vagrant service-manager env --script-readable`
+    Then stdout from "bundle exec vagrant service-manager env --script-readable" should be script readable
+
+    When I successfully run `bundle exec vagrant service-manager env docker`
+    Then stdout from "bundle exec vagrant service-manager env docker" should be evaluable in a shell
+    And stdout from "bundle exec vagrant service-manager env docker" should contain "export DOCKER_HOST=tcp://<ip>:2376"
+    And stdout from "bundle exec vagrant service-manager env docker" should match /export DOCKER_CERT_PATH=.*\/.vagrant\/machines\/cdk\/virtualbox\/docker/
+    And stdout from "bundle exec vagrant service-manager env docker" should contain "export DOCKER_TLS_VERIFY=1"
+    And stdout from "bundle exec vagrant service-manager env docker" should match /export DOCKER_API_VERSION=1.2\d/
+    And stdout from "bundle exec vagrant service-manager env docker" should match /# eval "\$\(vagrant service-manager env docker\)"/
+
+    When I successfully run `bundle exec vagrant service-manager env docker --script-readable`
+    Then stdout from "bundle exec vagrant service-manager env docker --script-readable" should be script readable
+
+    When I run `bundle exec vagrant service-manager env openshift`
+    Then the exit status should be 126
+    And stderr from "bundle exec vagrant service-manager env openshift" should contain:
+    """
+    # OpenShift service is not running in the vagrant box.
+    """
+
+    When I successfully run `bundle exec vagrant service-manager env --debug`
+    Then stdout from "bundle exec vagrant service-manager env --debug" should match /DEBUG command: [ service-manager: env ]/
+
+
+    ####################################################################################################################
+    # INSTALL-CLI command
+    ####################################################################################################################
+    When I successfully run `bundle exec vagrant service-manager install-cli --help`
+    Then the exit status should be 0
+    And stdout from "bundle exec vagrant service-manager install-cli --help" should contain:
+    """
+    Install the client binary for the specified service
+
+    Usage: vagrant service-manager install-cli [service] [options]
+
+    Service:
+      A supported service. For example: docker, kubernetes or openshift.
+
+    Options:
+          -h, --help            print this help
+          --cli-version         binary version to install
+          --path                absolute or relative path where to install the binary
+
+    Example:
+          vagrant service-manager install-cli docker
+    """
+
+    When I run `bundle exec vagrant service-manager install-cli`
+    Then the exit status should be 126
+    And stdout from "bundle exec vagrant service-manager install-cli" should match /Service name missing/
+
+    When I run `bundle exec vagrant service-manager install-cli docker --cli-version 111.222.333`
+    Then the exit status should be 126
+
+    When I run `bundle exec vagrant service-manager install-cli docker`
+    Then the exit status should be 0
+    And the binary "docker" should be installed
+    And the stderr should not contain anything
+
+    When I run `bundle exec vagrant service-manager install-cli docker --cli-version 1.12.1`
+    Then the exit status should be 0
+    And the binary "docker" of service "docker" should be installed with version "1.12.1"
+    And the stderr should not contain anything
+
+    When I evaluate and run `bundle exec vagrant service-manager install-cli docker --path #{ENV['VAGRANT_HOME']}/docker`
+    Then the exit status should be 0
+    And the binary should be installed in path "#{ENV['VAGRANT_HOME']}/docker"
+    And the stderr should not contain anything
+
+    When I evaluate and run `bundle exec vagrant service-manager install-cli docker --path #{ENV['VAGRANT_HOME']}/unknown_dir/docker`
+    Then the exit status should be 126
+    And stderr from evaluating and running "bundle exec vagrant service-manager install-cli docker --path #{ENV['VAGRANT_HOME']}/unknown_dir/docker" should match /Directory path #{ENV['VAGRANT_HOME']}/unknown_dir is invalid or doesn't exist/
+
+    When I run `bundle exec vagrant service-manager install-cli docker --path /foo/bar/docker`
+    Then the exit status should be 126
+    And stderr from evaluating and running "bundle exec vagrant service-manager install-cli docker --path /foo/bar/docker" should match /Permission denied @ dir_s_mkdir - /foo/
+
+    ####################################################################################################################
+    # START/STOP/STATUS/RESTART command
+    ####################################################################################################################
+    When I successfully run `bundle exec vagrant service-manager status --help`
+    Then the exit status should be 0
+    And stdout from "bundle exec vagrant service-manager status --help" should contain:
+    """
+    Usage: vagrant service-manager status [service] [options]
+
+    Options:
+          -h, --help         print this help
+
+    If a service is provided, only that service is reported.
+    If no service is provided only supported orchestrators are reported.
+
+    Example:
+          vagrant service-manager status openshift
+    """
+
+    And I successfully run `bundle exec vagrant service-manager stop --help`
+    Then the exit status should be 0
+    And stdout from "bundle exec vagrant service-manager stop --help" should contain:
+    """
+    stops the service
+
+    Usage: vagrant service-manager stop <service> [options]
+
+    Service:
+        A service provided by sccli. For example:
+         docker, kubernetes, openshift etc
+
+    Options:
+          -h, --help         print this help
+
+    Examples:
+      vagrant service-manager stop docker
+    """
+
+    And I successfully run `bundle exec vagrant service-manager start --help`
+    Then the exit status should be 0
+    And stdout from "bundle exec vagrant service-manager start --help" should contain:
+    """
+    starts the service
+
+    Usage: vagrant service-manager start <service> [options]
+
+    Service:
+        A service provided by sccli. For example:
+         docker, kubernetes, openshift etc
+
+    Options:
+          -h, --help         print this help
+
+    Examples:
+      vagrant service-manager start docker
+    """
+
+    And I successfully run `bundle exec vagrant service-manager restart --help`
+    Then the exit status should be 0
+    And stdout from "bundle exec vagrant service-manager restart --help" should contain:
+    """
+    restarts the service
+
+    Usage: vagrant service-manager restart <service> [options]
+
+    Service:
+        A service provided by sccli. For example:
+         docker, kubernetes, openshift etc
+
+    Options:
+          -h, --help         print this help
+
+    Examples:
+      vagrant service-manager restart docker
+    """
+
+    When I successfully run `bundle exec vagrant service-manager status`
+    Then stdout from "bundle exec vagrant service-manager status" should contain "docker - running"
+    Then stdout from "bundle exec vagrant service-manager status" should contain "openshift - stopped"
+    Then stdout from "bundle exec vagrant service-manager status" should contain "kubernetes - stopped"
+
+    When I successfully run `bundle exec vagrant service-manager status docker`
+    Then stdout from "bundle exec vagrant service-manager status" should contain "docker - running"
+
+    When I run `bundle exec vagrant service-manager status abcd`
+    Then the exit status should be 126
+    And stderr from "bundle exec vagrant service-manager status abcd" should contain:
+    """
+    Unknown service 'abcd'.
+    Supported services are docker, openshift, kubernetes etc.
+    """
+
+    When the "docker" service is running
+    And I successfully run `bundle exec vagrant service-manager stop docker`
+    Then the service "docker" should be stopped
+
+    When the "docker" service is not running
+    And I successfully run `bundle exec vagrant service-manager start docker`
+    Then the service "docker" should be running
+
+    When the "docker" service is running
+    And I successfully run `bundle exec vagrant service-manager restart docker`
+    Then the service "docker" should be running
+    And have a new pid for "docker" service
+
+    Examples:
+      | box   | provider   | ip          |
+      | cdk   | virtualbox | 10.10.10.42 |
+      | adb   | virtualbox | 10.10.10.42 |
+      | cdk   | libvirt    | 10.10.10.42 |
+      | adb   | libvirt    | 10.10.10.42 |