(https://pagure.io/fesco/issue/1856) |
(add test instructions) |
||
| Line 90: | Line 90: | ||
3. What are the expected results of those actions? | 3. What are the expected results of those actions? | ||
--> | --> | ||
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 | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Revision as of 09:27, 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)
- List of deliverables: N/A (not a System Wide Change)
- 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
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
- Blocks product? product
Documentation
N/A (not a System Wide Change)