Bootstrap a vagrant 1.1 environment on "dev" folder with reference to vagrant-lxc gem in place

This commit is contained in:
Fabio Rehm 2013-02-25 20:14:10 -03:00
parent 48c03d288d
commit 7f99ff98ec
4 changed files with 156 additions and 2 deletions

5
dev/Gemfile Normal file
View file

@ -0,0 +1,5 @@
# A sample Gemfile
source "https://rubygems.org"
gem 'vagrant', github: 'mitchellh/vagrant'
gem 'vagrant-lxc', path: '../'

38
dev/Gemfile.lock Normal file
View file

@ -0,0 +1,38 @@
GIT
remote: git://github.com/mitchellh/vagrant.git
revision: 803269f7291719715011c5c76d66e20101f7af50
specs:
vagrant (1.1.0.dev)
childprocess (~> 0.3.7)
erubis (~> 2.7.0)
i18n (~> 0.6.0)
json (~> 1.6.6)
log4r (~> 1.1.9)
net-scp (~> 1.0.4)
net-ssh (~> 2.2.2)
PATH
remote: ../
specs:
vagrant-lxc (0.0.1)
GEM
remote: https://rubygems.org/
specs:
childprocess (0.3.8)
ffi (~> 1.0, >= 1.0.11)
erubis (2.7.0)
ffi (1.4.0)
i18n (0.6.2)
json (1.6.8)
log4r (1.1.10)
net-scp (1.0.4)
net-ssh (>= 1.99.1)
net-ssh (2.2.2)
PLATFORMS
ruby
DEPENDENCIES
vagrant!
vagrant-lxc!

111
dev/Vagrantfile vendored Normal file
View file

@ -0,0 +1,111 @@
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
# All Vagrant configuration is done here. The most common configuration
# options are documented and commented below. For a complete reference,
# please see the online documentation at vagrantup.com.
# Every Vagrant virtual environment requires a box to build off of.
config.vm.box = "base"
# The url from where the 'config.vm.box' box will be fetched if it
# doesn't already exist on the user's system.
# config.vm.box_url = "http://domain.com/path/to/above.box"
# 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, 80, 8080
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network :private_network, "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|
# # Don't boot with headless mode
# vb.gui = true
#
# # Use VBoxManage to customize the VM. For example to change memory:
# vb.customize ["modifyvm", :id, "--memory", "1024"]
# end
#
# View the documentation for the provider you're using for more
# information on available options.
# Enable provisioning with Puppet stand alone. Puppet manifests
# are contained in a directory path relative to this Vagrantfile.
# You will need to create the manifests directory and a manifest in
# the file base.pp in the manifests_path directory.
#
# An example Puppet manifest to provision the message of the day:
#
# # group { "puppet":
# # ensure => "present",
# # }
# #
# # File { owner => 0, group => 0, mode => 0644 }
# #
# # file { '/etc/motd':
# # content => "Welcome to your Vagrant-built virtual machine!
# # Managed by Puppet.\n"
# # }
#
# config.vm.provision :puppet do |puppet|
# puppet.manifests_path = "manifests"
# puppet.manifest_file = "base.pp"
# end
# Enable provisioning with chef solo, specifying a cookbooks path, roles
# path, and data_bags path (all relative to this Vagrantfile), and adding
# some recipes and/or roles.
#
# config.vm.provision :chef_solo do |chef|
# chef.cookbooks_path = "../my-recipes/cookbooks"
# chef.roles_path = "../my-recipes/roles"
# chef.data_bags_path = "../my-recipes/data_bags"
# chef.add_recipe "mysql"
# chef.add_role "web"
#
# # You may also specify custom JSON attributes:
# chef.json = { :mysql_password => "foo" }
# end
# Enable provisioning with chef server, specifying the chef server URL,
# and the path to the validation key (relative to this Vagrantfile).
#
# The Opscode Platform uses HTTPS. Substitute your organization for
# ORGNAME in the URL and validation key.
#
# If you have your own Chef Server, use the appropriate URL, which may be
# HTTP instead of HTTPS depending on your configuration. Also change the
# validation key to validation.pem.
#
# config.vm.provision :chef_client do |chef|
# chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
# chef.validation_key_path = "ORGNAME-validator.pem"
# end
#
# If you're using the Opscode platform, your validator client is
# ORGNAME-validator, replacing ORGNAME with your organization name.
#
# If you have your own Chef Server, the default validation client name is
# chef-validator, unless you changed the configuration.
#
# chef.validation_client_name = "ORGNAME-validator"
end

View file

@ -81,7 +81,7 @@ vagrant_ssh "sudo apt-get update && sudo apt-get upgrade -y"
sh 'vagrant reload'
# Install dependencies
vagrant_ssh "sudo apt-get install lxc rinetd libffi-dev libffi-ruby ruby1.9.1-dev htop git -y && sudo gem install bundler --no-ri --no-rdoc"
vagrant_ssh "sudo apt-get install lxc rinetd libffi-dev libffi-ruby ruby1.9.1-dev htop git virtualbox -y && sudo gem install bundler --no-ri --no-rdoc"
# Backup rinetd config
vagrant_ssh "cp /etc/rinetd.conf /vagrant/cache/rinetd.conf"
@ -90,7 +90,7 @@ vagrant_ssh "cp /etc/rinetd.conf /vagrant/cache/rinetd.conf"
vagrant_ssh 'sudo chown vagrant:vagrant /etc/rinetd.conf'
# Bundle!
vagrant_ssh 'cd /vagrant && bundle'
vagrant_ssh 'cd /vagrant && bundle && cd /vagrant/dev && bundle'
# Setup vagrant default ssh key
vagrant_keys_path = '$(cd /vagrant && bundle show vagrant)/keys'