From Fedora Project Wiki
No edit summary
No edit summary
Line 113: Line 113:
== Contingency Plan ==
== Contingency Plan ==


<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
This is new feature and will not affect anything else.
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.   
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
Line 120: Line 122:
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
-->


== Documentation ==
== Documentation ==

Revision as of 09:34, 28 February 2018

FedoraScientific VagrantBox

Build and Release Vagrant boxes for Fedora Scientific

Summary

Fedora Scientific is currently delivered as ISOs. Shipping vagrant boxes will give potential users a friendlier option to try out Fedora Scientific while keeping their current operating system.

Owner

  • Name: Amit Saha
  • Email: amitsaha.in@gmail.com
  • Release notes owner:

Current status

  • Targeted release: Fedora 29
  • Last updated: 2018-02-28
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Vagrant boxes for Fedora Scientific will allow users to easily run Fedora Scientific in a virtual machine. This can be useful for users who are using another operating system as their host operating system and not have to manually download the ISO, and go through the installation process which can be unfamiliar or unnecessary hassle for users who may be new to Fedora or Linux.


Benefit to Fedora

This will lower the barrier of entry to potential Fedora Scientific and Fedora users.


Scope

  • Proposal owners: This will require creating pungi configuration as well as new kickstarts to be able to build the vagrant boxes for Fedora Scientific.
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: #7324 (a check of an impact with Release Engineering is needed)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

As far as I understand, there will be two vagrant boxes - one for libvirt and the other for VirtualBox drivers. As part of the testing, for each driver, the following should succeed (assuming the user has setup either successfully):

  • The user will be able to do vagrant init <image> followed by vagrant up to create a new VM running Fedora Scientific
  • The user will be able to ssh into the virtual machine using vagrant ssh
  • The user will then be able to perform any of the "usual" tasks that Fedora Scientific aims to provide a platform for


User Experience

This should enable users to have a easier path to trying out Fedora Scientific. Since this does not change any existing behavior or expectations, the only noticeable change should be a positive one.

Dependencies

Not any.

Contingency Plan

This is new feature and will not affect anything else.

  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

-->

Documentation

The Fedora Scientific guide at https://fedora-scientific.readthedocs.io/en/latest/ will be updated.

Release Notes