Vagrant
Summary
Provide Vagrant http://www.vagrantup.com/ with the libvirt provider as a default.
Owner
- Name: Josef Stribny
- Email: jstribny@redhat.com
- Release notes owner:
Contributors
- Name: Adam Miller, Alex Drahon, Vít Ondruch, Michael Adam
- Email: maxamillion@fedoraproject.org, adrahon@redhat.com, vondruch@redhat.com, madam@redhat.com
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. See upstream issue for details.
| Package name | Task | Status |
|---|---|---|
| rubygem-hashicorp-checkpoint | Create | 1150152 |
| rubygem-log4r | Create |  ingvar |
| rubygem-rb-inotify | Update to 0.9.5 | 894705 |
| rubygem-listen | Update to 2.7.9 | 853781 |
| rubygem-childprocess | Update to 0.5.3 | 1060098 |
- 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)
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)