From Fedora Project Wiki
Line 19: Line 19:


== Current status ==
== Current status ==
* Targeted release: [[Releases/21 | Fedora 21 ]]
* Targeted release: [[Releases/22 | Fedora 22 ]]
* Last updated: 2013-07-10
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Bugzilla states meaning as usual:
Bugzilla states meaning as usual:
Line 29: Line 28:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=998503 #998503]
* Tracker bug:


== Detailed Description ==
== Detailed Description ==

Revision as of 13:01, 30 September 2014

Vagrant

Summary

Provide Vagrant http://www.vagrantup.com/ with the KVM libvirt plugin.

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

Owner

Contributors

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 libvirt. The plan is to package Vagrant with the support for libvirt (coming as vagrant-libvirt plugin) replacing VirtualBox as a default provider.

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. Also providing a functional Vagrant package with libvirt provider as a default will help Fedora users to leverage libvirt instead of VirtualBox which is not part of Fedora.

Scope

Initial work has been done in for Vagrant on F20 in a Copr repository. Patches and quick fixes should be cleaned up or revisited. Also we need to depend on newer version of libvirt through rubygem-fog. Some commits for that are already in upstream repositories for vagrant-libvirt and fog.

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)

Dependencies

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

Documentation

N/A (not a System Wide Change)

Release Notes