trafficcontrol-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dewr...@apache.org
Subject [trafficcontrol] branch master updated: Remove outdated traffic_ops build README and Vagrantfile
Date Thu, 27 Sep 2018 00:15:40 GMT
This is an automated email from the ASF dual-hosted git repository.

dewrich pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficcontrol.git


The following commit(s) were added to refs/heads/master by this push:
     new 052a1af  Remove outdated traffic_ops build README and Vagrantfile
052a1af is described below

commit 052a1af59f35ebd5dafe713661d09d79cdf45794
Author: Rawlin Peters <rawlin_peters@comcast.com>
AuthorDate: Wed Sep 26 15:33:12 2018 -0600

    Remove outdated traffic_ops build README and Vagrantfile
---
 traffic_ops/build/README.md   | 49 ---------------------
 traffic_ops/build/Vagrantfile | 99 -------------------------------------------
 2 files changed, 148 deletions(-)

diff --git a/traffic_ops/build/README.md b/traffic_ops/build/README.md
deleted file mode 100644
index 3715c10..0000000
--- a/traffic_ops/build/README.md
+++ /dev/null
@@ -1,49 +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.
--->
-
-# Create a TO RPM with Dependencies
-
-1. Download repo Traffic Control (or from your favorite repo)
-```
-$ git clone http://github.com/Comcast/traffic_control.git
-```
-2. Bring up Vagrant environment (http://www.vagrantup.com)
-```
-$ cd <repo dir>
-$ cp traffic_control/traffic_ops/build/Vagrantfile ./
-$ vagrant up
-```
-3. ssh into vagrant environment
-```
-$ vagrant ssh
-```
-4. **OPTIONAL** Set environment variables to control build.  All are
-   automatically set to reasonable defaults (in parentheses) and it is
-   recommended to leave them unset.   They can be overridden if necessary:
-   - *BRANCH* (master)
-   - *HOTFIX\_BRANCH* (none)
-   - *WORKSPACE* (top level of local repo tree -- workspace must be a clone of the repository)
-   - *BUILD\_NUMBER* (# of commits in branch + last commit identifier)
-5. Build the RPM
-```
-$ cd /vagrant/traffic_control/traffic_ops/build
-$ ./build_rpm.sh
-```
-Notes:  
-This is known to work with CentOS 6.7 as the Vagrant environment.
diff --git a/traffic_ops/build/Vagrantfile b/traffic_ops/build/Vagrantfile
deleted file mode 100644
index 147d09e..0000000
--- a/traffic_ops/build/Vagrantfile
+++ /dev/null
@@ -1,99 +0,0 @@
-# -*- mode: ruby -*-
-# vi: set ft=ruby :
-#
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-
-# All Vagrant configuration is done below. The "2" in Vagrant.configure
-# configures the configuration version (we support older styles for
-# backwards compatibility). Please don't change it unless you know what
-# you're doing.
-Vagrant.configure(2) do |config|
-  # The most common configuration options are documented and commented below.
-  # For a complete reference, please see the online documentation at
-  # https://docs.vagrantup.com.
-
-  # Every Vagrant development environment requires a box. You can search for
-  # boxes at https://atlas.hashicorp.com/search.
-  config.vm.box = "bento/centos-6.7"
-
-  # Disable automatic box update checking. If you disable this, then
-  # boxes will only be checked for updates when the user runs
-  # `vagrant box outdated`. This is not recommended.
-  # config.vm.box_check_update = false
-
-  # Create a forwarded port mapping which allows access to a specific port
-  # within the machine from a port on the host machine. In the example below,
-  # accessing "localhost:8080" will access port 80 on the guest machine.
-  # config.vm.network "forwarded_port", guest: 80, host: 8080
-
-  # Create a private network, which allows host-only access to the machine
-  # using a specific IP.
-  # config.vm.network "private_network", ip: "192.168.33.10"
-
-  # Create a public network, which generally matched to bridged network.
-  # Bridged networks make the machine appear as another physical device on
-  # your network.
-  # config.vm.network "public_network"
-
-  # Share an additional folder to the guest VM. The first argument is
-  # the path on the host to the actual folder. The second argument is
-  # the path on the guest to mount the folder. And the optional third
-  # argument is a set of non-required options.
-  # config.vm.synced_folder "../data", "/vagrant_data"
-
-  # Provider-specific configuration so you can fine-tune various
-  # backing providers for Vagrant. These expose provider-specific options.
-  # Example for VirtualBox:
-  #
-  # config.vm.provider "virtualbox" do |vb|
-  #   # Display the VirtualBox GUI when booting the machine
-  #   vb.gui = true
-  #
-  #   # Customize the amount of memory on the VM:
-  #   vb.memory = "1024"
-  # end
-  #
-  # View the documentation for the provider you are using for more
-  # information on available options.
-
-  # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
-  # such as FTP and Heroku are also available. See the documentation at
-  # https://docs.vagrantup.com/v2/push/atlas.html for more information.
-  # config.push.define "atlas" do |push|
-  #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
-  # end
-
-  # Enable provisioning with a shell script. Additional provisioners such as
-  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
-  # documentation for more information about their specific syntax and use.
-  # config.vm.provision "shell", inline: <<-SHELL
-  #   sudo apt-get update
-  #   sudo apt-get install -y apache2
-  # SHELL
-  config.vm.provision "shell", inline: <<-SHELL
-	sudo yum install -y epel-release 
-	sudo yum install -y rpm-build openssl-devel
-	sudo yum install -y git hg golang cpan
-	sudo yum install -y mysql-devel mysql-server libpcap-devel libcurl-devel
-	
-	export GOPATH=/home/vagrant/go
-	mkdir -p $GOPATH
-	echo "export GOPATH=$GOPATH" >> /home/vagrant/.bash_profile
-	# just to make sure anything we created in /home/vagrant still owned by vagrant user
-	chown -R vagrant.vagrant /home/vagrant
-	service mysqld start
-  SHELL
-end
-


Mime
View raw message