Skip to content
This repository

Vagrant VM setup for kitsune

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 manifests
Octocat-spinner-32 README.rst
Octocat-spinner-32 Vagrantfile
README.rst

Introduction

Follow these steps to run a kitsune [1] development environment inside a virtual machine [2]

Installation

Clone the repository:

$ git clone git://github.com/aclark4life/kitsune-vagrant.git
$ cd kitsune-vagrant

Then add a vagrant box [3]:

$ vagrant box add kitsune http://files.vagrantup.com/lucid64.box

Then up the vagrant box:

$ vagrant up

This will take about 15-20 minutes to run on a "modern" machine (author has 2.66Ghz Macbook Pro w/4GB RAM). When it finishes, you should be able to open:

Eventually, you will be able to see kitsune running by opening http://33.33.33.10 in your browser (via mod_wsgi).

Todo

Troubleshooting

Vagrant is taking too long

Sometimes vagrant up will say:

[default] Waiting for VM to boot. This can take a few minutes.

then take much longer. If it takes longer than a few minutes, CTRL-C and re-run vagrant up.

Vagrant says read-only fs

Sometimes vagrant up will quit with the message:

[default] err: Could not send report: Got 1 failure(s) while initializing: change from absent to directory failed: Could not set 'directory on ensure: Read-only file system - /var/lib/puppet/rrd

vagrant destroy and vagrant up again should fix the problem (whatever it is).

Notes

[1] https://github.com/jsocol/kitsune
[2] Requires vagrant and VirtualBox to be installed: http://vagrantup.com, http://www.virtualbox.org/.
[3] You only need to do this once. Afterward you can vagrant destroy and vagrant up as needed.
Something went wrong with that request. Please try again.