From Fedora Project Wiki
(updates)
No edit summary
 
(20 intermediate revisions by 3 users not shown)
Line 1: Line 1:


= Change Proposal Name <!-- The name of your change proposal --> =
= FedoraScientific VagrantBox <!-- The name of your change proposal --> =


Build and Release Vagrant boxes for Fedora Scientific
Build and Release Vagrant boxes for Fedora Scientific
Line 26: Line 26:


== Current status ==
== Current status ==
* Targeted release: [[Releases/28 | Fedora 28 ]]  
* Targeted release: [[Releases/29 | Fedora 29 ]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 36: Line 36:
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=1551321 #1551321]
* Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/122 #122]


== Detailed Description ==
== 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.
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.




Line 47: Line 47:


This will lower the barrier of entry to potential Fedora Scientific and Fedora users.
This will lower the barrier of entry to potential Fedora Scientific and Fedora users.
 
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->


== Scope ==
== 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) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Proposal owners: This will require creating pungi configuration as well as new kickstarts to be able to build the vagrant boxes for Fedora Scientific.
<!-- 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: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
* Other developers: This will need creating the pungi configuration, kickstarts and then to test them and push them.
 
* Release engineering: [https://pagure.io/releng/issue/7324 #7324] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: Vagrant boxes for VirtualBox and libvirt
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
 
* 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. -->


* Trademark approval: N/A (not needed for this Change)
* Policies and guidelines: Not needed
* Trademark approval: Not needed
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->


Line 72: Line 68:
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
This is a new deliverable for Fedora Scientific, so upgrades are not relevant.
N/A (not a System Wide Change)


== How To Test ==
== How To Test ==
Line 90: Line 85:
-->
-->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
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):
N/A (not a System Wide Change)
 
* 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 ==
== User Experience ==
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
 
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 ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
None.
N/A (not a System Wide Change)


== 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. In addition, this is not a blocking release. However, any changes made to pungi configuration will need to be reverted. The kickstart files may stay as they should not affect other spins or Fedora Scientific.
* 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. -->
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* 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 -->


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
The Fedora Scientific guide at https://fedora-scientific.readthedocs.io/en/latest/ will be updated.
N/A (not a System Wide Change)


== Release Notes ==
== Release Notes ==
Line 127: Line 120:
-->
-->


[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF29]]
<!-- 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 -->
Line 134: Line 127:


<!-- Select proper category, default is Self Contained Change -->
<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
[[Category:SystemWideChange]]
<!-- [[Category:SystemWideChange]] -->

Latest revision as of 19:45, 4 March 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

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: This will need creating the pungi configuration, kickstarts and then to test them and push them.
  • Release engineering: #7324 (a check of an impact with Release Engineering is needed)
  • Policies and guidelines: Not needed
  • Trademark approval: Not needed

Upgrade/compatibility impact

This is a new deliverable for Fedora Scientific, so upgrades are not relevant.

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

None.

Contingency Plan

This is new feature and will not affect anything else. In addition, this is not a blocking release. However, any changes made to pungi configuration will need to be reverted. The kickstart files may stay as they should not affect other spins or Fedora Scientific.

Documentation

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

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/FedoraScientific_VagrantBox&oldid=512106"