From FedoraProject

< Changes
Revision as of 20:46, 27 June 2014 by Maxamillion (Talk | contribs)

Jump to: navigation, search




Provide Vagrant with the KVM libvirt plugin.

NOTE: This wiki page still needs some updating. Stay tuned.



Current status

Detailed Description

Vagrant is an automation tool used to manage development environments using virtualization and configuration management tools. It allows developers and teams to work on their projects and test them in an environment similar to production. Historically, Vagrant had a dependency on VirtualBox, but the newer versions have a plugin system allowing it to work with other virtualization technologies, including KVM.

Benefit to Fedora

Vagrant is widely used by development teams and is also used to provide pre-built environments by a lot of open-source projects. It would be a good addition to the Fedora development toolchain. More generally, Vagrant is currently provided as a self-contained Ruby environment in /opt and a properly packaged Vagrant would be better integrated to Linux.


  • Proposal owners:

There's still some work to be done on the vagrant-kvm plugin to make it work seamlessly, eg. with SELinux and Firewalld, but it should be simple enough. Most of the work is about packaging Vagrant and its dependencies as rubygems RPMs and ensuring integration with the Fedora Ruby environment.

  • Other developers: N/A (not a System Wide Change)
  • Release engineering: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)


N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No


N/A (not a System Wide Change)

Release Notes