Changes/Vagrant

From FedoraProject

< Changes(Difference between revisions)
Jump to: navigation, search
(Change announced on 2013-07-17)
(Add tracker bug)
 
(2 intermediate revisions by one user not shown)
Line 22: Line 22:
 
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: <will be assigned by the Wrangler>
+
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=998503 #998503]
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 101: Line 101:
 
-->
 
-->
  
[[Category:ChangeAnnounced]]
+
[[Category:ChangeAcceptedF20]]
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Latest revision as of 12:38, 20 August 2013

Contents

[edit] Vagrant

[edit] Summary

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

[edit] Owner

[edit] Current status

[edit] 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.

[edit] 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.

[edit] Scope

  • 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)

[edit] Upgrade/compatibility impact

N/A (not a System Wide Change)

[edit] How To Test

N/A (not a System Wide Change)

[edit] User Experience

N/A (not a System Wide Change)

[edit] Dependencies

N/A (not a System Wide Change)

[edit] 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

[edit] Documentation

N/A (not a System Wide Change)

[edit] Release Notes