< Changes
(→Scope) |
(→Scope) |
||
| Line 42: | Line 42: | ||
* Proposal owners: | * Proposal owners: | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
Initial work has been done in for Vagrant on F20 in [http://copr.fedoraproject.org/coprs/jstribny/vagrant-f20 | Initial work has been done in for Vagrant on F20 in [http://copr.fedoraproject.org/coprs/jstribny/vagrant-f20 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. | ||
<!-- * Other developers: N/A (not a System Wide Change) --><!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- * Other developers: N/A (not a System Wide Change) --><!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
<!-- * Release engineering: N/A (not a System Wide Change) --> <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- * Release engineering: N/A (not a System Wide Change) --> <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | ||
<!-- * Policies and guidelines: N/A (not a System Wide Change) --><!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- * Policies and guidelines: N/A (not a System Wide Change) --><!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | ||
Revision as of 13:00, 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
- Name: Alex Drahon
- Email: adrahon@redhat.com
- Release notes owner:
Contributors
- Name: Adam Miller
- Email: maxamillion@fedoraproject.org
- Packaging Tracker BZ: | 1113808
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
- Proposal owners:
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)