vagrant-lxc 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 70fcb094e16f27eac4a4d23327866eae45dd33c3
+  data.tar.gz: e7be5798cbcb853890c5813a7b90aa2e8dacd9ec
+SHA512:
+  metadata.gz: 52f59f16fc4dcb69f76599c365bbf16b7b06664b0a34a0e06cb617f0f68f20b027b1160d7e54e43e312f16dcd84950aa8e09c630c0317473bac93e38e4a2ae71
+  data.tar.gz: d0c8193b364eff7cfe53b952273ffe250c33c2b5a13fb239fe3903eaaa5395e15d5766d40d927f4c215de5789333a27bec645917697dd6217232505e789ebe3c

data/.gitignore

@@ -0,0 +1,29 @@
+*.gem
+*.rbc
+.bundle
+.config
+coverage
+InstalledFiles
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+
+# YARD artifacts
+.yardoc
+_yardoc
+doc/
+
+/tags
+/gems.tags
+
+.vagrant
+/cache
+
+/boxes/**/*.tar.gz
+/boxes/quantal64/rootfs-amd64/
+/boxes/output/
+/development/Vagrantfile

data/.gitmodules

@@ -0,0 +1,3 @@
+[submodule "vendor/vagrant"]
+	path = vendor/vagrant
+	url = git://github.com/mitchellh/vagrant.git

data/.rspec

@@ -0,0 +1,2 @@
+--color
+--format documentation

data/.travis.yml

@@ -0,0 +1,8 @@
+language: ruby
+rvm:
+  - 1.9.3
+  - 2.0.0
+matrix:
+  allow_failures:
+    - rvm: 2.0.0
+script: "bundle exec rake ci"

data/.vimrc

@@ -0,0 +1 @@
+set wildignore+=*/vagrant-1.1/*

data/Gemfile

@@ -0,0 +1,19 @@
+source 'https://rubygems.org'
+
+gemspec
+
+# TODO: Group gems
+
+gem 'rake'
+# TODO: setup rake-notes
+gem 'net-ssh'
+gem 'rspec'
+gem 'rspec-fire', require: 'rspec/fire'
+gem 'rspec-spies', require: false
+gem 'simplecov', require: false
+gem 'guard'
+gem 'guard-rspec'
+gem 'guard-bundler'
+gem 'guard-ctags-bundler'
+gem 'rb-inotify'
+gem 'log4r'

data/Gemfile.lock

@@ -0,0 +1,89 @@
+PATH
+  remote: .
+  specs:
+    vagrant-lxc (0.0.1)
+      childprocess (~> 0.3.7)
+      erubis (~> 2.7.0)
+      i18n (~> 0.6.0)
+      json (>= 1.5.1, < 1.8.0)
+      log4r (~> 1.1.9)
+      net-scp (~> 1.0.4)
+      net-ssh (~> 2.2.2)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    childprocess (0.3.9)
+      ffi (~> 1.0, >= 1.0.11)
+    coderay (1.0.9)
+    diff-lcs (1.2.1)
+    erubis (2.7.0)
+    ffi (1.4.0)
+    guard (1.6.2)
+      listen (>= 0.6.0)
+      lumberjack (>= 1.0.2)
+      pry (>= 0.9.10)
+      terminal-table (>= 1.4.3)
+      thor (>= 0.14.6)
+    guard-bundler (1.0.0)
+      bundler (~> 1.0)
+      guard (~> 1.1)
+    guard-ctags-bundler (0.1.6)
+      guard (>= 1.1)
+    guard-rspec (2.5.0)
+      guard (>= 1.1)
+      rspec (~> 2.11)
+    i18n (0.6.4)
+    json (1.7.7)
+    listen (0.7.3)
+    log4r (1.1.10)
+    lumberjack (1.0.2)
+    method_source (0.8.1)
+    multi_json (1.6.1)
+    net-scp (1.0.4)
+      net-ssh (>= 1.99.1)
+    net-ssh (2.2.2)
+    pry (0.9.12)
+      coderay (~> 1.0.5)
+      method_source (~> 0.8)
+      slop (~> 3.4)
+    rake (10.0.3)
+    rb-inotify (0.9.0)
+      ffi (>= 0.5.0)
+    rspec (2.13.0)
+      rspec-core (~> 2.13.0)
+      rspec-expectations (~> 2.13.0)
+      rspec-mocks (~> 2.13.0)
+    rspec-core (2.13.0)
+    rspec-expectations (2.13.0)
+      diff-lcs (>= 1.1.3, < 2.0)
+    rspec-fire (1.1.3)
+      rspec (~> 2.11)
+    rspec-mocks (2.13.0)
+    rspec-spies (2.1.3)
+      rspec (~> 2.0)
+    simplecov (0.7.1)
+      multi_json (~> 1.0)
+      simplecov-html (~> 0.7.1)
+    simplecov-html (0.7.1)
+    slop (3.4.3)
+    terminal-table (1.4.5)
+    thor (0.17.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  guard
+  guard-bundler
+  guard-ctags-bundler
+  guard-rspec
+  log4r
+  net-ssh
+  rake
+  rb-inotify
+  rspec
+  rspec-fire
+  rspec-spies
+  simplecov
+  vagrant-lxc!

data/Guardfile

@@ -0,0 +1,34 @@
+# A sample Guardfile
+# More info at https://github.com/guard/guard#readme
+
+guard 'bundler' do
+  watch('Gemfile')
+  watch(/^.+\.gemspec/)
+end
+
+guard 'ctags-bundler', :src_path => ["lib"] do
+  watch(/^(lib|spec\/support)\/.*\.rb$/)
+  watch('Gemfile.lock')
+end
+
+guard 'rspec' do
+  watch(%r{^spec/.+_spec\.rb$})
+  watch(%r{^lib/vagrant-lxc/(.+)\.rb$}) { |m| "spec/unit/#{m[1]}_spec.rb" }
+  watch('spec/unit_helper.rb')          { "spec/unit" }
+  watch('spec/spec_helper.rb')          { "spec/" }
+
+  # Rails example
+  watch(%r{^app/(.+)\.rb$})                           { |m| "spec/#{m[1]}_spec.rb" }
+  watch(%r{^app/(.*)(\.erb|\.haml)$})                 { |m| "spec/#{m[1]}#{m[2]}_spec.rb" }
+  watch(%r{^app/controllers/(.+)_(controller)\.rb$})  { |m| ["spec/routing/#{m[1]}_routing_spec.rb", "spec/#{m[2]}s/#{m[1]}_#{m[2]}_spec.rb", "spec/acceptance/#{m[1]}_spec.rb"] }
+  watch(%r{^spec/support/(.+)\.rb$})                  { "spec" }
+  watch('config/routes.rb')                           { "spec/routing" }
+  watch('app/controllers/application_controller.rb')  { "spec/controllers" }
+
+  # Capybara features specs
+  watch(%r{^app/views/(.+)/.*\.(erb|haml)$})          { |m| "spec/features/#{m[1]}_spec.rb" }
+
+  # Turnip features and steps
+  watch(%r{^spec/acceptance/(.+)\.feature$})
+  watch(%r{^spec/acceptance/steps/(.+)_steps\.rb$})   { |m| Dir[File.join("**/#{m[1]}.feature")][0] || 'spec/acceptance' }
+end

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2013 Fábio Rehm
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,209 @@
+# vagrant-lxc
+
+[![Build Status](https://travis-ci.org/fgrehm/vagrant-lxc.png?branch=master)](https://travis-ci.org/fgrehm/vagrant-lxc)
+
+Highly experimental, soon to come, Linux Containers support for the unreleased
+Vagrant 1.1.
+
+Please refer to the [closed issues](https://github.com/fgrehm/vagrant-lxc/issues?labels=&milestone=&page=1&state=closed)
+to find out whats currently supported.
+
+
+## WARNING
+
+Please keep in mind that although I'm already using this on my laptop, this is
+"almost alpha" software and things might go wrong.
+
+
+## Dependencies
+
+LXC, `bsdtar` and `fping` packages and a Kernel [higher than 3.5.0-17.28](#im-unable-to-restart-containers),
+which on Ubuntu 12.10 means:
+
+```
+sudo apt-get update && sudo apt-get dist-upgrade
+sudo apt-get install lxc bsdtar fping
+```
+
+
+## What is currently supported?
+
+* Vagrant's `up`, `halt`, `reload`, `destroy`, and `ssh` commands
+* Shared folders
+* Provisioners
+* Setting container's host name
+* Host-only / private networking
+
+
+## Current limitations
+
+* Ruby >= 1.9.3 only, patches for 1.8.7 are welcome
+* Port forwarding does not work [yet](https://github.com/fgrehm/vagrant-lxc/issues/4)
+* A hell lot of `sudo`s
+* Only a [single ubuntu box supported](boxes), I'm still [figuring out what should go
+  on the .box file](https://github.com/fgrehm/vagrant-lxc/issues/4)
+* "[works on  my machine](https://github.com/fgrehm/vagrant-lxc/issues/20)" (TM)
+* + bunch of other [core features](https://github.com/fgrehm/vagrant-lxc/issues?labels=core&milestone=&page=1&state=open)
+  and some known [bugs](https://github.com/fgrehm/vagrant-lxc/issues?labels=bug&page=1&state=open)
+
+
+## Usage
+
+For now you'll need to install the gem from sources:
+
+```
+git clone git://github.com/fgrehm/vagrant-lxc.git --recurse
+cd vagrant-lxc
+bundle install
+bundle exec rake install
+```
+
+Since Vagrant 1.1 has not been released yet and to avoid messing up with you
+current Vagrant installation, I've vendored Vagrant's sources from the master
+and made it available from [`vagrant-lxc`](bin/vagrant-lxc). So after installing
+`vagrant-lxc`, create a `Vagrantfile` like the one below and run
+`vagrant-lxc up --provider=lxc`:
+
+```ruby
+Vagrant.configure("2") do |config|
+  config.vm.box     = "lxc-quantal64"
+  config.vm.box_url = 'http://dl.dropbox.com/u/13510779/lxc-quantal64-2013-03-10.box'
+
+  # Share an additional folder to the guest Container. 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 "/tmp", "/host_tmp"
+
+  config.vm.provider :lxc do |lxc|
+    # Same as 'customize ["modifyvm", :id, "--memory", "1024"]' for VirtualBox
+    lxc.start_opts << 'lxc.cgroup.memory.limit_in_bytes=400M'
+    # Limits swap size
+    lxc.start_opts << 'lxc.cgroup.memory.memsw.limit_in_bytes=500M'
+  end
+
+  # ... your puppet / chef / shell provisioner configs here ...
+end
+```
+
+If you don't trust me and believe that it will mess up with your current Vagrant
+installation and / or are afraid that something might go wrong with your machine,
+fire up the [same Vagrant VirtualBox machine I'm using for development](#using-virtualbox-and-vagrant-10-for-development)
+to try things out and do the same as above. That might also get you up and running
+if you are working on a mac or windows host ;)
+
+
+## Development
+
+If  want to develop from your physical machine, just sing that same old song:
+
+```
+git clone git://github.com/fgrehm/vagrant-lxc.git --recurse
+cd vagrant-lxc
+bundle install
+bundle exec rake # to run all specs
+```
+
+To build the provided quantal64 box:
+
+```
+bundle exec rake boxes:quantal64:build
+vagrant-lxc box add quantal64 boxes/output/lxc-quantal64.box
+```
+
+
+### Using `vagrant-lxc` to develop itself
+
+Yes! The gem has been [bootstrapped](http://en.wikipedia.org/wiki/Bootstrapping_(compilers)
+and since you can boot a container from within another, after cloning the
+project you can run the commands below from the host machine to get a container
+ready for development:
+
+```sh
+bundle install
+cd development
+cp Vagrantfile.1.1 Vagrantfile
+# Required in order to allow nested containers to be started
+sudo apt-get install apparmor-utils
+sudo aa-complain /usr/bin/lxc-start
+bundle exec vagrant-lxc up lxc --provider=lxc
+bundle exec vagrant-lxc ssh lxc
+```
+
+That should result in a container ready to be `bundle exec vagrant-lxc ssh`ed.
+Once you've SSH into the guest container, you'll be already on the project's root.
+Keep in mind that you'll probably need to run `sudo aa-complain /usr/bin/lxc-start`
+on the host whenever you want to hack on it, otherwise you won't be able to
+start nested containers there to try things out.
+
+
+### Using VirtualBox and Vagrant 1.0 for development
+
+```
+cd development
+cp Vagrantfile.1.0 Vagrantfile
+vagrant up
+vagrant reload
+vagrant ssh
+```
+
+### Using VirtualBox and Vagrant 1.1 for development
+
+```
+cd development
+cp Vagrantfile.1.1 Vagrantfile
+bundle exec vagrant-lxc up vbox
+bundle exec vagrant-lxc reload vbox
+bundle exec vagrant-lxc ssh vbox
+```
+
+
+## Protips
+
+If you want to find out more about what's going on under the hood on vagrant,
+prepend `VAGRANT_LOG=debug` to your `vagrant-lxc` commands. For `lxc-start`s
+debugging set `LXC_START_LOG_FILE`:
+
+```
+LXC_START_LOG_FILE=/tmp/lxc-start.log VAGRANT_LOG=debug vagrant-lxc up
+```
+
+This will output A LOT of information on your terminal and some useful information
+about `lxc-start` to `/tmp/lxc-start.log`.
+
+
+## Help!
+
+### I've accidentaly ran `vagrant-lxc` on a Vagrant 1.0 project and I can't use it anymore
+
+That happened to me before so here's how to recover:
+
+```
+rm -rf .vagrant
+mv .vagrant.v1* .vagrant
+```
+
+### I'm unable to restart containers!
+
+It happened to me quite a few times in the past and it seems that it is related
+to a bug on linux kernel, so make sure you are using a bug-free kernel
+(>= 3.5.0-17.28). More information can be found on:
+
+* https://bugzilla.kernel.org/show_bug.cgi?id=47181
+* https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1021471
+* https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065434
+
+Sometimes the dev boxes I'm using are not able to `lxc-start` containers
+anymore. Most of the times it was an issue with the arguments [I provided](https://github.com/fgrehm/vagrant-lxc/blob/master/example/Vagrantfile#L14-L18)
+to it (or a *buggy* kernel). If you run into that, rollback your changes
+and try to `vagrant reload` the dev box. If it still doesn't work,
+please file a bug at the [issue tracker](https://github.com/fgrehm/vagrant-lxc/issues).
+
+
+## Contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request

data/Rakefile

@@ -0,0 +1,5 @@
+Dir['./tasks/**/*.rake'].each { |f| load f }
+
+require 'bundler/gem_tasks'
+
+task :ci => ['spec:unit']