vagrant-service-manager 1.0.2 → 1.1.0.beta.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 931ed28213feec845263c099a965a747c85891ae
-  data.tar.gz: bf8447ff4ce1f42b9a0b460db37bff7d561cc468
+  metadata.gz: 4d72420be6d3f4e17f9e649cfe9236ac0b8709ef
+  data.tar.gz: 7f65631baa320c7602742c9fac835183bbe64810
 SHA512:
-  metadata.gz: 072cfd5bf2882444c43eaa9bc869954117d141228d6997d049e618a5aab38640b8322bba26771a68641167399fc9897bb1c2a6559041c36f04bb7da3567885f8
-  data.tar.gz: 23c23b006585fc65760762f49823474bebc637419a2b4aecfdec17cb8db4eb81703749b59aa7e6c3c60e54d0ffcb2ad8567e6dd1df4023f193c1a7f37f6e2d61
+  metadata.gz: b7edeefe39c4841c208b050c3d775302bfe803b03567037466eba8cc9969db1540719f495c5b24e0116e1c19abd5189999ab2937d805ed076b5a404fd1631e0b
+  data.tar.gz: c90cf6b537f209728e1cae6e3a08aaf6c1eb884449064f0e018debacb816e878a698aa9d47998431bb18bb8a38e87588752b569d2b62c95ade5ac69ee4c9b38a

data/.config/cucumber.yml

@@ -0,0 +1,12 @@
+# config/cucumber.yml
+##YAML Template
+---
+default: --profile html
+
+pretty: --format pretty -b
+html: --format progress --format html --out=build/features_report.html -b
+
+help: --tags @help --profile html
+box: --tags @box --profile html
+env: --tags @env --profile html
+openshift: --tags @openshift --profile html

data/.gitignore

@@ -1,4 +1,17 @@
+# Ruby, Bundler
 Gemfile.lock
-.vagrant
 .bundle
+.ruby-version
+.ruby-gemset
+
+# Vagrant
+.vagrant
+
+# Idea
+.idea
+*.iml
+
+# Build and tmp directories
+tmp
+build
 pkg

data/CHANGELOG.md

@@ -1,11 +1,20 @@
 # Changelog
 
 ## Unreleased
+- Updated README to make Installation Instructions clearer @bexelbie
+- Fix #195 Adding Cucumber and Aruba based acceptance tests @hferentschik
+- CHANGELOG fix and README update for OS support for tests @budhrg
+- Fix #188: Name of k8s service not consistent @budhrg
+- Fix #225: service-manager env throws NameError @budhrg
+- Fix #168: Extend --debug flag to show plugin activity @budhrg
+- Don't set private network for unsupported box @budhrg
+- Convert CONTRIBUTING and README docs to AsciiDoc @bexelbie
+- Fix #172: Implement "start/enable" service command @budhrg
 
 ## v1.0.2 May 09, 2016
 - Add --script-readable to env and env docker @bexelbie
 - Fix #178: Add status command and separate status from env @bexelbie
-- Fix#173: Shows if kubernetes services is running in the box @navidshaikh
+- Fix #173: Shows if kubernetes services is running in the box @navidshaikh
 - Fix #169: Adds command for displaying box routable IP address @navidshaikh
 - Fix message for box command on default help @budhrg
 - Fix #184: Make env headers comments for vagrant service-manager env @bexelbie

data/CONTRIBUTING.adoc

@@ -0,0 +1,110 @@
+[[contributing-to-vagrant-service-manager]]
+== Contributing to vagrant-service-manager
+
+* link:#submitting-issues[Submitting issues]
+* link:#submitting-pull-requests[Submitting pull requests]
+** link:#get-started[Get Started]
+** link:#create-a-topic-branch[Create a topic branch]
+** link:#code[Code]
+** link:#commit[Commit]
+** link:#submit[Submit]
+* link:#merging-pull-requests[Merging pull requests]
+
+The following is a set of guidelines for contributing to the
+vagrant-service-manager plugin.
+
+These are guidelines, please use your best judgment and feel free to
+propose changes to this document.
+
+=== Submitting issues
+
+You can submit issues with respect to the vagrant-service-manager plugin
+https://github.com/projectatomic/vagrant-service-manager/issues/new[here].
+Make sure you include all the relevant details pertaining the issue.
+
+Before submitting a new issue, it is suggested to check the
+https://github.com/projectatomic/vagrant-service-manager/issues[existing
+issues] in order to avoid duplication. The vagrant-service-manager
+plugin works closely with the
+https://github.com/projectatomic/adb-atomic-developer-bundle/issues[Atomic
+Developer Bundle] and the
+https://github.com/projectatomic/adb-utils/issues[adb-utils] RPM. You
+may wish to review the issues in both these repositories as well.
+
+=== Submitting pull requests
+
+==== Get Started
+
+If you are just getting started with Git and GitHub there are a few
+prerequisite steps.
+
+* Make sure you have a https://github.com/signup/free[GitHub account].
+* https://help.github.com/articles/fork-a-repo/[Fork] the
+vagrant-service-manager repository. As discussed in the linked page,
+this also includes:
+** https://help.github.com/articles/set-up-git[Setting up] your local
+git install.
+** Cloning your fork.
+
+==== Create a topic branch
+
+Create a
+http://git-scm.com/book/en/Git-Branching-Branching-Workflows#Topic-Branches[topic
+branch] on which you will work. The convention is to name the branch
+using the issue key you are working on. If there is not already an issue
+covering the work you want to do, create one (see
+link:#submitting-issues[submitting issues]). Assuming for example you
+will be working from the master branch and working on the GitHub issue
+123 : `git checkout -b issue-123 master`
+
+==== Code
+
+Do your work! Refer to the link:README.md#development[development]
+section in the link:README.md[README] to get started.
+
+==== Commit
+
+* Make commits of logical units.
+* Be sure to use the GitHub issue key in the commit message, eg
+`Issue #123 ...`.
+* Make sure you have added the necessary tests for your changes.
+* Make sure you have added appropriate documentation updates.
+* Run _all_ the tests to assure nothing else was accidentally broken.
+
+==== Submit
+
+* Push your changes to the topic branch in your fork of the repository.
+* Initiate a https://help.github.com/articles/using-pull-requests/[pull
+request].
+* All changes need at least 2 ACKs from maintainers before they will be
+merged. If the author of the PR is a maintainer, their submission is
+considered to be the first ACK. Therefore, pull requests from
+maintainers only need one additional ACK. By "2 ACKs" we mean that two
+maintainers must acknowledge that the change is a good one.
+
+=== Merging pull requests
+
+A project maintainer will merge the pull request. He should avoid using
+the GitHub UI for the merge and prefer merges over the the command line
+to avoid merge commits and to keep a linear commit history. Here is an
+example work-flow assuming issue 123 from above:
+
+-------------------------------------------------------------------------
+# Create a local branch for the pull request
+$ git checkout -b issue-123 master
+
+# Pull the changes
+$ git pull <remote of the pull request> issue-123
+
+# If necessary rebase changes on master to ensure we have a fast forward.
+$ git rebase -i master
+
+# If required, update CHANGELOG.md in the unreleased section. Commit!
+
+# Merge changes into master
+$ git checkout master
+$ git merge issue-123
+
+# Push to origin
+$ git push origin master
+-------------------------------------------------------------------------

data/Gemfile

@@ -3,11 +3,16 @@ source 'https://rubygems.org'
 gemspec
 
 group :development do
-  gem 'vagrant', git: 'https://github.com/mitchellh/vagrant.git'
-  # added as the vagrant component wouldn't build without it
-  gem 'json'
+  gem 'vagrant',      git: 'https://github.com/mitchellh/vagrant.git'
   gem 'rake'
-  gem 'bundler', '~> 1.6'
+  gem 'vagrant-libvirt'
+  gem 'fog-libvirt', '0.0.3' # https://github.com/pradels/vagrant-libvirt/issues/568
+  gem 'mechanize'
+  gem 'json'
+  gem 'cucumber', '~> 2.1'
+  gem 'aruba', '~> 0.13'
+  gem 'komenda', '~> 0.1.6'
+  gem 'launchy'
 end
 
 group :plugins do

data/README.adoc

@@ -0,0 +1,269 @@
+[[vagrant-service-manager]]
+== vagrant-service-manager
+
+* link:#objective[Objective]
+* link:#installation[Installation]
+** link:#installing-from-a-rubygems[Installing from a RubyGems]
+** link:#installing-from-rpm[Installing from RPM]
+* link:#usage[Usage]
+** link:#example-execution-of-the-plugin[Example execution of the plugin]
+** link:#available-commands[Available commands]
+** link:#exit-codes[Exit codes]
+** link:#ip-address-detection[IP address detection]
+* link:#development[Development]
+** link:#setup[Setup]
+** link:#acceptance-tests[Acceptance tests]
+* link:#getting-involved[Getting involved]
+
+== Objective The vagrant-service-manager plugin is designed to enable
+easier access to the features and services provided by the
+https://github.com/projectatomic/adb-atomic-developer-bundle[Atomic
+Developer Bundle (ADB)]. It provides setup information, including
+environment variables and certificates, required to access services
+provided by the ADB and is a must have for most ADB users.
+
+This plugin makes it easier to use the ADB with host-based tools such as
+Eclipse and the docker and kubernetes CLI commands. Details on how to
+use ADB with this plugin can be found in the
+https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/docs/using.rst[ADB
+Documentation].
+
+== Installation
+
+The plugin is distributed as both a Ruby Gem and via RPM using the
+Fedora COPR system.
+
+=== Installing from a RubyGems
+
+The vagrant-service-manager
+https://rubygems.org/gems/vagrant-service-manager[gem] is available on
+https://rubygems.org[RubyGems] and can be installed via the standard
+Vagrant plugin installation method:
+
+------------------------------------------------
+$ vagrant plugin install vagrant-service-manager
+------------------------------------------------
+
+=== Installing from RPM
+
+The
+https://copr.fedorainfracloud.org/coprs/nshaikh/vagrant-service-manager/builds/[Copr
+build] is accessible via the standard COPR access/install method:
+
+----------------------------------------------------------------------------------
+$ dnf copr enable nshaikh/vagrant-service-manager
+$ dnf --enablerepo=nshaikh-vagrant-service-manager install vagrant-service-manager
+----------------------------------------------------------------------------------
+
+== Usage
+
+=== Example execution of the plugin
+
+1.  Install vagrant-service-manager plugin:
++
+----------------------------------------------
+vagrant plugin install vagrant-service-manager
+----------------------------------------------
+2.  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].
+3.  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
+Documentation].
++
+*Note:* When the vagrant-service-manager plugin is loaded and a box is
+started using the VirtualBox provider, the user needs to add a routable
+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:
++
+----------------------------------------------------------------------------
+$ vagrant service-manager env docker
+# Set the following environment variables to enable access to the
+# docker daemon running inside of the vagrant virtual machine:
+export DOCKER_HOST=tcp://172.28.128.4:2376
+export DOCKER_CERT_PATH=/foo/bar/.vagrant/machines/default/virtualbox/docker
+export DOCKER_TLS_VERIFY=1
+export DOCKER_API_VERSION=1.21
+# run following command to configure your shell:
+# eval "$(vagrant service-manager env docker)"
+----------------------------------------------------------------------------
++
+*Note:* The required TLS certificates are copied to the host machine at
+the time of `vagrant up` itself. Every run of
+`vagrant service-manager env docker` checks for the validity of the
+certificates on the host machine by matching the certificates inside the
+box. If the certificates on the host machine are invalid, this command
+will also re-download the certificates onto the host machine.
+
+=== Available commands
+
+The following section lists the available commands for the plugin and
+their explanation:
+
+1.  `vagrant service-manager env [service] [--script-readable]`
++
+Displays connection information for all active services in the box in a
+manner that can be evaluated in a shell. If a `service` is specified,
+only the information for that service is displayed. When
+`--script-readable` is specified the output is in `key=value` format.
+The supported services are: Docker; OpenShift.
+
+1.  `vagrant service-manager box [command]`
++
+Displays box related information like release version, IP etc.
+
+1.  `vagrant service-manager box version [--script-readable]`
++
+Displays the version and release information of the running VM. When
+`--script-readable` is specified the output is in `key=value` format.
+
+1.  `vagrant service-manager box ip`
++
+Displays the routable IP address of the running VM.
+
+1.  `vagrant service-manager status [service]`
++
+Lists services and their running state. If a `service` is specified only
+the status of that service is displayed. If no service is provided then
+only supported orchestrators are reported.
+
+1.  `vagrant service-manager [operation] [service]`
++
+where `operation` could be:
+
+  * `restart` : Restart the given service in the box.
+  * `start`   : Start the given service in the box.
+  * `stop`    : Stop the given service in the box.
++
+and `service` could be `docker`, `openshift`, `kubernetes` etc.
+
+1.  `vagrant service-manager [command] [--help | -h]`
++
+Displays the possible commands, options and other relevant information
+for the vagrant-service-manager plugin. If a `command` is specified,
+only the help relevant to that command is displayed.
+
+[[debug-flag]]
+==== Debug Flag
+
+Append `--debug` flag to enable debug mode.
+
+_Note_: Debug output from `vagrant-service-manager` is prepended with
+the following string:
+
+`DEBUG command: [ service-manager: <command name / log message> ]`
+
+=== Exit codes
+
+The following table lists the plugin's exit codes and their meaning:
+
+[cols=",",options="header",]
+|=======================================================================
+|Exit Code Number |Meaning
+|`0` |No error
+
+|`1` |Catch all for general errors / Wrong sub-command or option given
+
+|`3` |Vagrant box is not running and should be running for this command
+to succeed
+
+|`126` |A service inside the box is not running / Command invoked cannot
+execute
+|=======================================================================
+
+=== IP address detection
+
+There is no standardized way of detecting Vagrant box IP addresses. This
+code uses the last IPv4 address available from the set of configured
+addresses that are _up_. i.e. if eth0, eth1, and eth2 are all up and
+have IPv4 addresses, the address on eth2 is used.
+
+== Development
+
+=== Setup
+
+After cloning the repository, install the http://bundler.io/[Bundler]
+gem:
+
+---------------------
+$ gem install bundler
+---------------------
+
+Then setup your project dependencies:
+
+----------------
+$ bundle install
+----------------
+
+The build is driven via rake. All build related tash should be executed
+in the Bundler environment, e.g. `bundle exec rake clean`. You can get a
+list of available Rake tasks via:
+
+---------------------
+$ bundle exec rake -T
+---------------------
+
+=== Acceptance tests
+
+The source also contains a set of https://cucumber.io/[Cucumber]
+acceptance tests. They can be run via:
+
+---------------------------
+$ bundle exec rake features
+---------------------------
+
+_NOTE_: Only Linux OS is supported at present.
+
+The tests assume that the ADB and CDK box files are available under
+_build/boxes/adb-<provider>.box_ resp
+_build/boxes/cdk-<provider>.box_. You can either copy the box files
+manually or use the _get_adb_ resp. _get_cdk_ Rake tasks.
+
+Per default only the scenarios for ADB in combination with the
+VirtualBox provider are run. However, you can also run against CDK
+and/or use the Libvirt provider using the environment variables _BOX_
+resp _PROVIDER_:
+
+-----------------------------------------------------
+# Run tests against CDK using Libvirt
+$ bundle exec rake features BOX=cdk PROVIDER=libvirt
+
+# Run against ADB and CDK (boxes are comma seperated)
+$ bundle exec rake features BOX=cdk,adb
+-----------------------------------------------------
+
+You can also run a single feature specifying the explicit feature file
+to use:
+
+-----------------------------------------------------------------------
+$ bundle exec rake features FEATURE=features/<feature-filename>.feature
+-----------------------------------------------------------------------
+
+After test execution the Cucumber test reports can be found under
+_build/features_report.html_. They can also be opened via
+
+---------------------------------------
+$ bundle exec rake features:open_report
+---------------------------------------
+
+== Getting involved
+
+We welcome your input. You can submit issues or pull requests with
+respect to the vagrant-service-manager plugin. Refer to the
+https://github.com/projectatomic/vagrant-service-manager/blob/master/CONTRIBUTING.md[contributing
+guidelines] for detailed information on how to contribute to this
+plugin.
+
+You can contact us on:
+
+* IRC: #atomic and #nulecule on freenode
+* Mailing List: container-tools@redhat.com

data/Rakefile

@@ -1 +1,112 @@
-require "bundler/gem_tasks"
+require 'bundler/gem_tasks'
+require 'rake/clean'
+require 'cucumber/rake/task'
+require 'mechanize'
+require 'fileutils'
+require 'yaml'
+require 'launchy'
+
+CDK_DOWNLOAD_URL='https://access.redhat.com/downloads/content/293/ver=2/rhel---7/2.0.0/x86_64/product-software'
+CDK_BOX_BASE_NAME='rhel-cdk-kubernetes-7.2-23.x86_64.vagrant'
+
+CDK_DOWNLOAD_URL_NIGHTLY='http://cdk-builds.usersys.redhat.com/builds/nightly/latest-build'
+
+ADB_DOWNLOAD_URL='http://cloud.centos.org/centos/7/atomic/images'
+ADB_BOX_BASE_NAME='AtomicDeveloperBundle-2.1.0-CentOS7'
+
+CLOBBER.include('pkg')
+CLEAN.include('build')
+
+task :init do
+  FileUtils.mkdir_p 'build'
+  puts ENV['FOO']
+end
+
+# Cucumber acceptance test tasks
+Cucumber::Rake::Task.new(:features)
+task :features => :init
+
+namespace :features do
+  desc 'Opens the HTML Cucumber test report'
+  task :open_report do
+    Launchy.open('./build/features_report.html')
+  end
+end
+
+desc 'Download latest publicly released / latest nightly build of CDK Vagrant box using the specified provider (default \'virtualbox\', \'false\')'
+task :get_cdk, [:provider, :nightly] do |t, args|
+  provider = args[:provider].nil? ? 'virtualbox' : args[:provider]
+  use_nightly = args[:nightly].nil? ? false : !!(args[:nightly] =~ /true/)
+  agent = Mechanize.new
+  agent.follow_meta_refresh = true
+
+  if use_nightly
+    agent.ignore_bad_chunking = true
+    agent.get(CDK_DOWNLOAD_URL_NIGHTLY) do |page|
+      page.links.each do |link|
+        if link.href.match(/.*#{Regexp.quote(provider)}.box$/)
+          download_dir = File.join(File.dirname(__FILE__), 'build', 'boxes')
+          unless File.directory?(download_dir)
+            FileUtils.mkdir_p(download_dir)
+          end
+          agent.pluggable_parser.default = Mechanize::Download
+          puts "Downloading #{CDK_DOWNLOAD_URL_NIGHTLY}/#{link.href}"
+          agent.get(link.href).save(File.join(download_dir, "cdk-#{provider}.box"))
+        end
+      end
+    end
+  else
+    agent.get(CDK_DOWNLOAD_URL) do |page|
+
+      # Submit first form which is the redirect to login page form
+      login_page = page.forms.first.submit
+
+      # Submit the login form
+      after_login = login_page.form_with(:name => 'login_form') do |f|
+        username_field = f.field_with(:id => 'username')
+        username_field.value = 'service-manager@mailinator.com'
+        password_field = f.field_with(:id => 'password')
+        password_field.value = 'service-manager'
+      end.click_button
+
+      # There is one more redirect after successful login
+      download_page = after_login.forms.first.submit
+
+      download_page.links.each do |link|
+        if link.href =~ /#{Regexp.quote(CDK_BOX_BASE_NAME)}-#{Regexp.quote(provider)}.box/
+          download_dir = File.join(File.dirname(__FILE__), 'build', 'boxes')
+          unless File.directory?(download_dir)
+            FileUtils.mkdir_p(download_dir)
+          end
+          agent.pluggable_parser.default = Mechanize::Download
+          puts "Downloading #{link.href}"
+          agent.get(link.href).save(File.join(download_dir, "cdk-#{provider}.box"))
+        end
+      end
+    end
+  end
+end
+task :get_cdk => :init
+
+desc 'Download ADB Vagrant box using the specified provider (default \'virtualbox\')'
+task :get_adb, [:provider] do |t, args|
+  provider = args[:provider].nil? ? 'virtualbox' : args[:provider]
+  agent = Mechanize.new
+  agent.follow_meta_refresh = true
+  agent.get(ADB_DOWNLOAD_URL) do |page|
+    page.links.each do |link|
+      if match = link.href.match(/#{Regexp.quote(ADB_BOX_BASE_NAME)}-(.*).box/)
+        if  match.captures[0].downcase == provider
+          download_dir = File.join(File.dirname(__FILE__), 'build', 'boxes')
+          unless File.directory?(download_dir)
+            FileUtils.mkdir_p(download_dir)
+          end
+          agent.pluggable_parser.default = Mechanize::Download
+          puts "Downloading #{ADB_DOWNLOAD_URL}/#{link.href}"
+          agent.get(link.href).save(File.join(download_dir, "adb-#{provider}.box"))
+        end
+      end
+    end
+  end
+end
+task :get_adb => :init

data/features/box-command.feature

@@ -0,0 +1,45 @@
+Feature: Command output from box command
+  service-manager should return the correct output from box commands
+
+  @box
+  Scenario Outline: Boot and execute box commands
+    Given box is <box>
+    And provider is <provider>
+    And a file named "Vagrantfile" with:
+    """
+    require 'vagrant-libvirt'
+
+    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 successfully run `bundle exec vagrant up --provider <provider>`
+    And 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 ip`
+    Then stdout from "bundle exec vagrant service-manager box ip" should contain "<ip>"
+
+    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 |

data/features/debug-flag.feature

@@ -0,0 +1,30 @@
+Feature: Command output from --debug flag
+  service-manager should print the debug logs along with native logs
+
+  @status
+  Scenario Outline: Boot and execute simple env command with debug logs
+    Given box is <box>
+    And provider is <provider>
+    And a file named "Vagrantfile" with:
+    """
+    require 'vagrant-libvirt'
+
+    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 successfully run `bundle exec vagrant up --provider <provider>`
+    And 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 ]/
+
+    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 |