F22 System Wide Change: Vagrant Box for Fedora Atomic and Fedora Cloud

Jaroslav Reznik jreznik at redhat.com
Wed Jan 21 13:30:19 UTC 2015

= Proposed System Wide Change: Vagrant Box for Fedora Atomic and Fedora Cloud 

Change owner(s): Joe Brockmeier <jzb at fedoraproject.org>, Ian McLeod 
<imcleod at redhat.com>, Langdon White <langdon at fedoraproject.org>

To produce Vagrant boxes based on the Fedora Atomic Host and Fedora Cloud 
flavors so that users can easily work with Fedora in the Vagrant environment. 

== Detailed Description ==
Vagrant is a tool for building and distributing development environments. 
Vagrant boxes can easily be used on a number of local virtualization platforms 
such as VirtualBox, VMware, via AWS or OpenStack, or with other platforms. 
Vagrant is used on Linux, Mac OS X, and Microsoft Windows and would present 
Fedora with an opportunity to reach a larger developer audience than it 
currently does.

Many developers prefer to work with Vagrant [1] for their development work, 
using Vagrant to lower their development setup time, increase productivity, 
and avoid having to specifically install an OS each time they wish to use it 
for development.

A number of people have produced unofficial Vagrant boxes, but the Fedora 
project does not currently produce an "official" Vagrant box for consumption. We 
would like to close the gap here and offer Vagrant users easy-to-consume Fedora 
22 Atomic and Cloud flavored Vagrant boxes. 

== Scope ==
* Proposal owners:
** Provide a kickstart file and additional definition for the Vagrant Boxes.
** Provide scripts and patches for Koji to generate Vagrant Boxes.
** Encourage testing of the new Vagrant Boxes by the rest of the Cloud Working 

* Other developers:
** Encourage other Fedora developers to make use of the Fedora Vagrant Boxes 
for their own development work.
** Ensure that Vagrant is packaged for Fedora 22.

* Release engineering:
** Would need to work with owners of this proposal to add needed features to 
Koji, and add Vagrant Boxes to list of output formats required for release.

* Policies and Guidelines:
** No known impact.

== Contingency Plan ==
If feature is incomplete by Fedora 22 beta, it would be pulled from the 
release. No contingency necessary for fallback as this does not exist in 
Fedora 21.

* Contingency deadline: Beta
* Blocks release? No
* Blocks product? No 

[1] https://www.vagrantup.com/
devel-announce mailing list
devel-announce at lists.fedoraproject.org

More information about the devel mailing list