This is an automated email from the ASF dual-hosted git repository.
rrm pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficserver.git
The following commit(s) were added to refs/heads/master by this push:
new 44201caa00 Remove Vagrant related files (#11932)
44201caa00 is described below
commit 44201caa00d8041a7a225ab682c19137035c0e8c
Author: Randall Meyer <[email protected]>
AuthorDate: Mon Jan 6 17:00:20 2025 -0800
Remove Vagrant related files (#11932)
The Vagrantfile has not been updated since 2016. The list of supported
OSes do not match current reality.
---
Vagrantfile | 100 -------
contrib/vagrant-setup.sh | 121 --------
doc/.tx/config | 5 -
doc/developer-guide/index.en.rst | 1 -
.../testing-with-vagrant/index.en.rst | 258 ------------------
.../developer-guide/documentation/building.en.po | 69 -----
.../testing-with-vagrant/index.en.po | 303 ---------------------
7 files changed, 857 deletions(-)
diff --git a/Vagrantfile b/Vagrantfile
deleted file mode 100644
index 889c2f8973..0000000000
--- a/Vagrantfile
+++ /dev/null
@@ -1,100 +0,0 @@
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements. See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership. The ASF licenses this file
-# to you 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.
-
-$network = {
- "trusty_64" => "192.168.2.101",
- "trusty_32" => "192.168.2.102",
- "jessie_64" => "192.168.2.103",
- "jessie_32" => "192.168.2.104",
- "centos7_64" => "192.168.2.105",
- "centos6_64" => "192.168.2.106",
- "centos6_32" => "192.168.2.107",
- "omnios" => "192.168.2.108",
- "fedora23_64" => "192.168.2.109",
- "xenial_64" => "192.168.2.110",
- "fedora24_64" => "192.168.2.111",
-}
-
-$vmspec = {
- "trusty_64" => [
- "ubuntu/trusty64"
- ],
- "trusty_32" => [
- "ubuntu/trusty32"
- ],
- "xenial_64" => [
- "ubuntu/xenial64"
- ],
- "jessie_64" => [
- "puppetlabs/debian-8.2-64-nocm"
- ],
- "jessie_32" => [
- "puppetlabs/debian-8.2-32-nocm"
- ],
- "centos7_64" => [
- "puppetlabs/centos-7.2-64-nocm"
- ],
- "centos6_64" => [
- "puppetlabs/centos-6.6-64-nocm"
- ],
- "centos6_32" => [
- "puppetlabs/centos-6.6-32-nocm"
- ],
- "omnios" => [
- "omniti/omnios-r151014"
- ],
- "fedora23_64" => [
- "fedora/23-cloud-base"
- ],
- "fedora24_64" => [
- "fedora/24-cloud-base"
- ],
-}
-
-Vagrant.configure("2") do |config|
-
- # Default all VMs to 1GB and 2 cores
- config.vm.provider :virtualbox do |v|
- v.memory = 1024
- v.cpus = 2
- end
-
- config.ssh.shell = "bash -c 'BASH_ENV=/etc/profile exec bash'"
-
- $vmspec.each do | name, spec |
- config.vm.define name do | config |
- if name == 'omnios'
- # nfs seems to be the only way to make this work for omnios
- # this method fails if hostfs is encrypted
- config.vm.synced_folder ".", "/vagrant", type: "nfs"
- config.ssh.username = "root"
- config.ssh.password = "vagrant"
- else
- config.vm.synced_folder ".", "/vagrant"
- end
- config.vm.box = spec[0]
- config.vm.network :private_network, ip: $network[name]
- config.vm.provision "shell" do |s|
- s.path = "contrib/vagrant-setup.sh"
- s.args = name
- end
- end
- end
-
-end
-
-# -*- mode: ruby -*-
-# vi: set ft=ruby :
diff --git a/contrib/vagrant-setup.sh b/contrib/vagrant-setup.sh
deleted file mode 100644
index 3bb255a144..0000000000
--- a/contrib/vagrant-setup.sh
+++ /dev/null
@@ -1,121 +0,0 @@
-#!/bin/bash
-
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements. See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership. The ASF licenses this file
-# to you 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.
-
-set -e
-set -o pipefail
-
-case ${1} in
-trusty*|jessie*)
- sed -i 's/^mesg n$/tty -s \&\& mesg n/g' /root/.profile
- apt-get update
- apt-get install -y \
- autoconf \
- automake \
- build-essential \
- clang \
- libcap-dev \
- libcurl4-openssl-dev \
- libhwloc-dev \
- liblua5.2-dev \
- libpcre3-dev \
- libssl-dev \
- m4 \
- ncurses-dev \
- git
-;;
-
-centos*)
- yum install -y \
- autoconf \
- automake \
- clang \
- flex \
- gcc \
- gcc-c++ \
- hwloc-devel \
- libcap-devel \
- libcurl-devel d\
- libtool \
- lua-devel \
- m4 \
- ncurses-devel \
- openssl-devel \
- pcre-devel \
- git
-;;
-
-fedora*)
- dnf install -y \
- autoconf \
- automake \
- clang \
- flex \
- gcc \
- gcc-c++ \
- hwloc-devel \
- libcap-devel \
- libcurl-devel \
- libtool \
- lua-devel \
- m4 \
- ncurses-devel \
- openssl-devel \
- pcre-devel \
- git \
- make
-;;
-
-omnios)
- export PATH=/usr/gnu/bin:/usr/bin:/usr/sbin:/sbin:/opt/gcc-4.8.1/bin
- echo "export
PATH=/usr/gnu/bin:/usr/bin:/usr/sbin:/sbin:/opt/gcc-4.8.1/bin" >> /root/.profile
- RC=0
- if [[ ! $(grep http://pkg.omniti.com/omniti-ms/ /var/pkg/pkg5.image) ]];
then
- pkg set-publisher -g http://pkg.omniti.com/omniti-ms/ ms.omniti.com
- fi
- pkg refresh
- pkg install \
- archiver/gnu-tar \
- developer/build/autoconf \
- developer/build/automake \
- developer/build/gnu-make \
- developer/build/libtool \
- developer/gcc48 \
- developer/lexer/flex \
- developer/library/lint \
- developer/linker \
- developer/object-file \
- developer/parser/bison \
- developer/versioning/git \
- library/idnkit \
- library/idnkit/header-idnkit \
- omniti/system/hwloc \
- system/header \
- system/library/math \
- || RC=${?}
- if [[ ${RC} != 0 ]] && [[ ${RC} != 4 ]]; then
- exit 1
- fi
-;;
-
-*)
- echo "no config for ${1}"
- exit 1
-;;
-esac
-
-exit 0
diff --git a/doc/.tx/config b/doc/.tx/config
index f8da647c8f..0934a47f6d 100644
--- a/doc/.tx/config
+++ b/doc/.tx/config
@@ -2112,11 +2112,6 @@ file_filter =
locale/<lang>/LC_MESSAGES/developer-guide/release-process/index.en
source_file = _build/locale/pot/developer-guide/release-process/index.en.pot
source_lang = en
-[apache-traffic-server-6x.developer-guide--testing-with-vagrant--index_en]
-file_filter =
locale/<lang>/LC_MESSAGES/developer-guide/testing-with-vagrant/index.en.po
-source_file =
_build/locale/pot/developer-guide/testing-with-vagrant/index.en.pot
-source_lang = en
-
[apache-traffic-server-6x.developer-guide--troubleshooting-tips--unable-to-load-plugins_en]
file_filter =
locale/<lang>/LC_MESSAGES/developer-guide/troubleshooting-tips/unable-to-load-plugins.en.po
source_file =
_build/locale/pot/developer-guide/troubleshooting-tips/unable-to-load-plugins.en.pot
diff --git a/doc/developer-guide/index.en.rst b/doc/developer-guide/index.en.rst
index c681318025..7a900585ca 100644
--- a/doc/developer-guide/index.en.rst
+++ b/doc/developer-guide/index.en.rst
@@ -41,7 +41,6 @@ duplicate bugs is encouraged, but not required.
introduction/index.en
release-process/index.en
contributing/index.en
- testing-with-vagrant/index.en
debugging/index.en
threads-and-events.en
cache-architecture/index.en
diff --git a/doc/developer-guide/testing-with-vagrant/index.en.rst
b/doc/developer-guide/testing-with-vagrant/index.en.rst
deleted file mode 100644
index 05e2fad73b..0000000000
--- a/doc/developer-guide/testing-with-vagrant/index.en.rst
+++ /dev/null
@@ -1,258 +0,0 @@
-.. Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you 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.
-
-.. include:: ../../common.defs
-
-.. _developer-testing-with-vagrant:
-
-Using Vagrant to Test |TS|
-**************************
-
-The |ATS| project's official repository includes a Vagrantfile, intended to
ease
-the process of creating environments suitable for building and testing |TS|,
-where all the necessary dependencies are installed automatically for a variety
-of operating systems and common distribution releases.
-
-.. epigraph::
-
- Vagrant is a tool for building complete development environments. With an
- easy-to-use workflow and focus on automation, Vagrant lowers development
- environment setup time, increases development/production parity, and makes
- the "works on my machine" excuse a relic of the past.
-
- -- `VagrantUp website <https://www.vagrantup.com/about.html>`_
-
-Vagrant can be used in combination with any of the popular configuration
-management and automation tools, such as `Chef <https://www.chef.io/chef/>`_,
-`Puppet <https://puppetlabs.com/>`_, `Ansible <http://www.ansible.com/home>`_,
-and more. The Vagrantfile included in the |TS| repository happens to make use
-of Puppet.
-
-Installing Vagrant and Dependencies
-===================================
-
-VirtualBox
-----------
-
-The virtualization software `VirtualBox <https://www.virtualbox.org/>`_ is
-required to create and run the virtual machines created by the included project
-Vagrantfile.
-
-VirtualBox can be obtained by free from the official website, and many
-distributions provide their own packages as well. No special configuration of
-the software is required.
-
-Vagrant
--------
-
-A fairly recent version of `Vagrant
<https://www.vagrantup.com/downloads.html>`_
-is necessary to use the included Vagrantfile. While older versions of Vagrant
-could be installed through the Ruby Gems facility, modern versions are only
-provided as distribution specific packages.
-
-NFS Server
-----------
-
-The project Vagrantfile uses the NFS shared folders support of VirtualBox to
-mount the same directory in which the Vagrantfile is located on your host
-machine as a network directory inside the virtual machine. For this to work,
-your host machine must have an NFS server installed and running, and the user
-under which you run the vagrant commands must have sudo permissions to modify
-the NFS exports configuration and restart the NFS service.
-
-The virtual machine created by Vagrant will still function without a working
-NFS server on your host machine, but you will not be able to access the shared
-folder which includes the entire |TS| source tree. You may opt to modify the
-Vagrantfile to use a method other than NFS, as per the `Vagrant documentation
-<https://docs.vagrantup.com/v2/synced-folders/basic_usage.html>`_.
-
-Managing Virtual Machines
-=========================
-
-Listing Available Machines
---------------------------
-
-The included Vagrantfile defines many variations of operating systems,
-releases, and architectures. To see a complete list of the virtual machine
-options available to you, run the command ``vagrant status`` from within the
-same directory as the Vagrantfile. The command may take a few moments to run as
-the configurations defined in the Vagrantfile are evaluated, and calls are made
-to the underlying VirtualBox utilities to check for the existence and
-operational state of each possibility. You should expect to see output along
-the lines of::
-
- $ vagrant status
- Current machine states:
-
- saucy32 not created (virtualbox)
- raring32 not created (virtualbox)
- quantal32 not created (virtualbox)
- precise32 not created (virtualbox)
- trusty32 not created (virtualbox)
- saucy64 not created (virtualbox)
- raring64 not created (virtualbox)
- quantal64 not created (virtualbox)
- precise64 not created (virtualbox)
- trusty64 running (virtualbox)
- freebsd not created (virtualbox)
- omnios not created (virtualbox)
- lucid64 not created (virtualbox)
- fedora18 not created (virtualbox)
- centos63 not created (virtualbox)
- centos59 not created (virtualbox)
- centos64 not created (virtualbox)
- debian7 not created (virtualbox)
- sles11 not created (virtualbox)
- oel63 not created (virtualbox)
-
- This environment represents multiple VMs. The VMs are all listed
- above with their current state. For more information about a specific
- VM, run `vagrant status NAME`.
-
-Creating and Destroying
------------------------
-
-Creation and destruction of virtual machines with Vagrant is very simple. To
-bring a new virtual machine into existence, run the following command from the
-same directory in which the Vagrantfile is located::
-
- vagrant up <name>
-
-Where ``<name>`` should be the specific operating system release you wish to
-use for the virtual machine. For example, to test |TS| in a CentOS 6.4
-environment, you would run::
-
- vagrant up centos64
-
-Running the ``vagrant up`` command for a virtual machine which does not exist
-yet (or has previously been deleted) will create a brand new virtual machine,
-using the appropriate image (called a *basebox* in Vagrant parlance), as well
as
-provision the machine according to any configuration management rules specified
-in the Vagrantfile.
-
-Similarly, you may destroy the virtual machine when you are finished by running
-the command::
-
- vagrant destroy <name>
-
-Or if you wish to only stop the virtual machine temporarily without deleting
it,
-you may run::
-
- vagrant halt <name>
-
-A halted virtual machine is started back up with the same ``vagrant up``
command
-shown earlier. The difference is that Vagrant will recognize the box already
-exists and do nothing more than start the vm process and configure the virtual
-networking interfaces on your host. Any configuration management hooks in the
-Vagrantfile will be skipped.
-
-Logging In
-----------
-
-Logging into a virtual machine created with Vagrant may be accomplished in a
-couple different ways. The easiest is to let Vagrant itself figure out where
the
-machine is and how to properly authenticate you to it::
-
- vagrant ssh <name>
-
-Using that command from within the same directory as the Vagrantfile allows you
-to skip figuring out what virtual network interface has been attached to the
-machine, what local port may be assigned to handle SSH forwarding, and so on.
-As long as the virtual machine was already running, you will be quickly dropped
-into a local shell in the virtual machine as the ``vagrant`` user.
-
-.. important::
-
- Vagrant by default uses a widely-shared private RSA key on newly created
- virtual machines (that are built on public basebox images). The default user
- on these baseboxes is also configured for password-less sudo permissions.
- This is very clearly insecure, but Vagrant is designed for local testing and
- development, not production (or other public) uses, so the project has made
- the philosophical trade-off in favor of ease of use.
-
-Alternatively, you may SSH directly to the virtual machine. Because the virtual
-machines are configured to use only the private virtual network layer provided
-by VirtualBox, you cannot directly. Instead, VirtualBox has created a local
port
-mapping automatically which should be used. There is no fixed, pre-determined
-port mapping that will be universally valid, as Vagrant and VirtualBox may be
-used together to run an arbitrary number of virtual machines simultaneously,
-each provisioned in any order, and defined by any number and variety of
-Vagrantfiles.
-
-The correct way to determine what port Vagrant and VirtualBox have used to map
-to a given virtual machine is to run the following command from within the same
-directory as your Vagrantfile::
-
- vagrant ssh-config <name>
-
-That will output a configuration block, suitable for inclusion in your local
-``~/.ssh/config`` file. Note specifically, in addition to the port, the path to
-the private key you will need to use as your identity when attempting to log
-into the virtual machine.
-
-Shared Host Folders
--------------------
-
-VirtualBox provides a facility for mounting directories from your host machine
-as filesystems inside the virtual machines. The |TS| Vagrantfile makes use of
-this feature to mount its own source tree in a predictable location in the
-virtual environment.
-
-Multiple methods are available for this, including NFS, CIFS, and simulated
-block devices. The |TS| project opts to use NFS for its simplicity, speed,
-support for features such as symlinks, and wide interoperability across the
-various guest operating systems included in the Vagrantfile. Within the
included
-Vagrantfile, you can see the following line::
-
- config.vm.synced_folder ".", "/opt/src/trafficserver.git", :nfs => true
-
-This directs VirtualBox to mount the directory in which the |TS| Vagrantfile
-resides as an NFS mount inside the virtual machine at the path
-``/opt/src/trafficserver.git``. Additional host directories may be mounted in
-the same manner should the need arise.
-
-Forwarding Custom Ports
------------------------
-
-.. TODO::
-
- This is trickier to do than it may seem at first. The easiest method is to
- just rely on the VirtualBox GUI or underlying vboxmanage commands and set
- up custom port mappings by hand. To do it dynamically brings up the problem
- of port conflict resolution, especially with the |TS| Vagrantfile which
- defines so many different virtual machines, any number of which may be run
- simultaneously.
-
-Building |TS| Inside Vagrant
-============================
-
-Producing |TS| builds from within the Vagrant managed virtual machines is
-effectively no different than in any other environment. The same directory in
-which the Vagrantfile exists will be mounted via NFS inside the virtual machine
-at the path ``/opt/src/trafficserver.git``.
-
-.. note::
-
- If you have run ``autoconf`` or ``configure`` from outside the virtual
- machine environment against the same Git working copy as is mounted inside
- the virtual machine, you will encounter failures should you attempt to run
- any of the Make targets inside the VM. Any build related commands should be
- run inside of the virtual machine. Additionally, if you are running more
- than one virtual machine simultaneously, remember that they are each using
- the same NFS export on your host machine.
-
-
diff --git
a/doc/locale/ja/LC_MESSAGES/developer-guide/documentation/building.en.po
b/doc/locale/ja/LC_MESSAGES/developer-guide/documentation/building.en.po
deleted file mode 100644
index a9c6a78c4f..0000000000
--- a/doc/locale/ja/LC_MESSAGES/developer-guide/documentation/building.en.po
+++ /dev/null
@@ -1,69 +0,0 @@
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements. See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership. The ASF licenses this file
-# to you 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.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: Apache Traffic Server 6.2\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2016-01-15 00:13+0900\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <[email protected]>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.2.0\n"
-
-#: ../../../developer-guide/documentation/building.en.rst:23
-msgid "Building the Documentation"
-msgstr ""
-
-#: ../../../developer-guide/documentation/building.en.rst:25
-msgid ""
-"All documentation and related files are located in the source tree under "
-"the ``doc/`` directory. Makefiles are generated automatiically by the main "
-"configure script. For simplicity's sake, it is recommended that "
-"contributors new to the documentation make use of the included Vagrant "
-"configurations, as these will take care of providing all dependencies. "
-"Please refer to the :ref:`developer-testing-with-vagrant` chapter for "
-"complete details on using Vagrant to build and test the |TS| source tree."
-msgstr ""
-
-#: ../../../developer-guide/documentation/building.en.rst:33
-msgid ""
-"With a configured source tree, building the documentation requires only the "
-"invocation ``make html`` from within ``doc/``. For repeated builds while "
-"working on the documentation, it is advisable to clean out the built and "
-"intermediate files each time by running the following instead (again, from "
-"within the ``doc/`` directory of the |TS| source tree)::"
-msgstr ""
-
-#: ../../../developer-guide/documentation/building.en.rst:41
-msgid ""
-"This will ensure that make doesn't inadvertently skip the regeneration of "
-"any targets."
-msgstr ""
-
-#: ../../../developer-guide/documentation/building.en.rst:44
-msgid ""
-"To view the built documentation, you may point any browser to the directory "
-"``doc/docbuild/html/``. If you are building the documentation on your local "
-"machine, you may access the HTML documentation files directly without the "
-"need for a full-fledged web server, as all necessary resources (CSS, "
-"Javascript, and images) are referenced using relative paths and there are "
-"no server-side scripts necessary to render the documentation."
-msgstr ""
diff --git
a/doc/locale/ja/LC_MESSAGES/developer-guide/testing-with-vagrant/index.en.po
b/doc/locale/ja/LC_MESSAGES/developer-guide/testing-with-vagrant/index.en.po
deleted file mode 100644
index d34e16e9ef..0000000000
--- a/doc/locale/ja/LC_MESSAGES/developer-guide/testing-with-vagrant/index.en.po
+++ /dev/null
@@ -1,303 +0,0 @@
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements. See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership. The ASF licenses this file
-# to you 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.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: Apache Traffic Server 6.2\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2016-01-02 21:32+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <[email protected]>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.1.1\n"
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:23
-msgid "Using Vagrant to Test |TS|"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:25
-msgid ""
-"The |ATS| project's official repository includes a Vagrantfile, intended to "
-"ease the process of creating environments suitable for building and testing "
-"|TS|, where all the necessary dependencies are installed automatically for "
-"a variety of operating systems and common distribution releases."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:32
-msgid ""
-"Vagrant is a tool for building complete development environments. With an "
-"easy-to-use workflow and focus on automation, Vagrant lowers development "
-"environment setup time, increases development/production parity, and makes "
-"the \"works on my machine\" excuse a relic of the past."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:43
-msgid "`VagrantUp website <https://www.vagrantup.com/about.html>`_"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:39
-msgid ""
-"Vagrant can be used in combination with any of the popular configuration "
-"management and automation tools, such as `Chef <https://www.chef.io/chef/";
-">`_, `Puppet <https://puppetlabs.com/>`_, `Ansible <http://www.ansible.com/";
-"home>`_, and more. The Vagrantfile included in the |TS| repository happens "
-"to make use of Puppet."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:46
-msgid "Installing Vagrant and Dependencies"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:49
-msgid "VirtualBox"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:51
-msgid ""
-"The virtualization software `VirtualBox <https://www.virtualbox.org/>`_ is "
-"required to create and run the virtual machines created by the included "
-"project Vagrantfile."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:55
-msgid ""
-"VirtualBox can be obtained by free from the official website, and many "
-"distributions provide their own packages as well. No special configuration "
-"of the software is required."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:60
-msgid "Vagrant"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:62
-msgid ""
-"A fairly recent version of `Vagrant <https://www.vagrantup.com/downloads.";
-"html>`_ is necessary to use the included Vagrantfile. While older versions "
-"of Vagrant could be installed through the Ruby Gems facility, modern "
-"versions are only provided as distribution specific packages."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:68
-msgid "NFS Server"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:70
-msgid ""
-"The project Vagrantfile uses the NFS shared folders support of VirtualBox "
-"to mount the same directory in which the Vagrantfile is located on your "
-"host machine as a network directory inside the virtual machine. For this to "
-"work, your host machine must have an NFS server installed and running, and "
-"the user under which you run the vagrant commands must have sudo "
-"permissions to modify the NFS exports configuration and restart the NFS "
-"service."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:77
-msgid ""
-"The virtual machine created by Vagrant will still function without a "
-"working NFS server on your host machine, but you will not be able to access "
-"the shared folder which includes the entire |TS| source tree. You may opt "
-"to modify the Vagrantfile to use a method other than NFS, as per the "
-"`Vagrant documentation <https://docs.vagrantup.com/v2/synced-folders/";
-"basic_usage.html>`_."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:84
-msgid "Managing Virtual Machines"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:87
-msgid "Listing Available Machines"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:89
-msgid ""
-"The included Vagrantfile defines many variations of operating systems, "
-"releases, and architectures. To see a complete list of the virtual machine "
-"options available to you, run the command ``vagrant status`` from within "
-"the same directory as the Vagrantfile. The command may take a few moments "
-"to run as the configurations defined in the Vagrantfile are evaluated, and "
-"calls are made to the underlying VirtualBox utilities to check for the "
-"existence and operational state of each possibility. You should expect to "
-"see output along the lines of::"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:127
-msgid "Creating and Destroying"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:129
-msgid ""
-"Creation and destruction of virtual machines with Vagrant is very simple. "
-"To bring a new virtual machine into existence, run the following command "
-"from the same directory in which the Vagrantfile is located::"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:135
-msgid ""
-"Where ``<name>`` should be the specific operating system release you wish "
-"to use for the virtual machine. For example, to test |TS| in a CentOS 6.4 "
-"environment, you would run::"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:141
-msgid ""
-"Running the ``vagrant up`` command for a virtual machine which does not "
-"exist yet (or has previously been deleted) will create a brand new virtual "
-"machine, using the appropriate image (called a *basebox* in Vagrant "
-"parlance), as well as provision the machine according to any configuration "
-"management rules specified in the Vagrantfile."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:147
-msgid ""
-"Similarly, you may destroy the virtual machine when you are finished by "
-"running the command::"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:152
-msgid ""
-"Or if you wish to only stop the virtual machine temporarily without "
-"deleting it, you may run::"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:157
-msgid ""
-"A halted virtual machine is started back up with the same ``vagrant up`` "
-"command shown earlier. The difference is that Vagrant will recognize the "
-"box already exists and do nothing more than start the vm process and "
-"configure the virtual networking interfaces on your host. Any configuration "
-"management hooks in the Vagrantfile will be skipped."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:164
-msgid "Logging In"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:166
-msgid ""
-"Logging into a virtual machine created with Vagrant may be accomplished in "
-"a couple different ways. The easiest is to let Vagrant itself figure out "
-"where the machine is and how to properly authenticate you to it::"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:172
-msgid ""
-"Using that command from within the same directory as the Vagrantfile allows "
-"you to skip figuring out what virtual network interface has been attached "
-"to the machine, what local port may be assigned to handle SSH forwarding, "
-"and so on. As long as the virtual machine was already running, you will be "
-"quickly dropped into a local shell in the virtual machine as the "
-"``vagrant`` user."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:180
-msgid ""
-"Vagrant by default uses a widely-shared private RSA key on newly created "
-"virtual machines (that are built on public basebox images). The default "
-"user on these baseboxes is also configured for password-less sudo "
-"permissions. This is very clearly insecure, but Vagrant is designed for "
-"local testing and development, not production (or other public) uses, so "
-"the project has made the philosophical trade-off in favor of ease of use."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:187
-msgid ""
-"Alternatively, you may SSH directly to the virtual machine. Because the "
-"virtual machines are configured to use only the private virtual network "
-"layer provided by VirtualBox, you cannot directly. Instead, VirtualBox has "
-"created a local port mapping automatically which should be used. There is "
-"no fixed, pre-determined port mapping that will be universally valid, as "
-"Vagrant and VirtualBox may be used together to run an arbitrary number of "
-"virtual machines simultaneously, each provisioned in any order, and defined "
-"by any number and variety of Vagrantfiles."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:196
-msgid ""
-"The correct way to determine what port Vagrant and VirtualBox have used to "
-"map to a given virtual machine is to run the following command from within "
-"the same directory as your Vagrantfile::"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:202
-msgid ""
-"That will output a configuration block, suitable for inclusion in your "
-"local ``~/.ssh/config`` file. Note specifically, in addition to the port, "
-"the path to the private key you will need to use as your identity when "
-"attempting to log into the virtual machine."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:208
-msgid "Shared Host Folders"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:210
-msgid ""
-"VirtualBox provides a facility for mounting directories from your host "
-"machine as filesystems inside the virtual machines. The |TS| Vagrantfile "
-"makes use of this feature to mount its own source tree in a predictable "
-"location in the virtual environment."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:215
-msgid ""
-"Multiple methods are available for this, including NFS, CIFS, and simulated "
-"block devices. The |TS| project opts to use NFS for its simplicity, speed, "
-"support for features such as symlinks, and wide interoperability across the "
-"various guest operating systems included in the Vagrantfile. Within the "
-"included Vagrantfile, you can see the following line::"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:223
-msgid ""
-"This directs VirtualBox to mount the directory in which the |TS| "
-"Vagrantfile resides as an NFS mount inside the virtual machine at the path "
-"``/opt/src/trafficserver.git``. Additional host directories may be mounted "
-"in the same manner should the need arise."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:229
-msgid "Forwarding Custom Ports"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:241
-msgid "Building |TS| Inside Vagrant"
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:243
-msgid ""
-"Producing |TS| builds from within the Vagrant managed virtual machines is "
-"effectively no different than in any other environment. The same directory "
-"in which the Vagrantfile exists will be mounted via NFS inside the virtual "
-"machine at the path ``/opt/src/trafficserver.git``."
-msgstr ""
-
-#: ../../developer-guide/testing-with-vagrant/index.en.rst:250
-msgid ""
-"If you have run ``autoconf`` or ``configure`` from outside the virtual "
-"machine environment against the same Git working copy as is mounted inside "
-"the virtual machine, you will encounter failures should you attempt to run "
-"any of the Make targets inside the VM. Any build related commands should be "
-"run inside of the virtual machine. Additionally, if you are running more "
-"than one virtual machine simultaneously, remember that they are each using "
-"the same NFS export on your host machine."
-msgstr ""
