No edit summary |
No edit summary |
||
| (4 intermediate revisions by 3 users not shown) | |||
| 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: | * 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 == | ||
| Line 60: | Line 61: | ||
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: Vagrant boxes for VirtualBox and libvirt | ** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: Vagrant boxes for VirtualBox and libvirt | ||
* Policies and guidelines: Not | * Policies and guidelines: Not needed | ||
* Trademark approval: Not needed | |||
* Trademark approval: Not | |||
<!-- 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 85: | Line 85: | ||
--> | --> | ||
As far as I understand, there will be two vagrant boxes | 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 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 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 | * The user will then be able to perform any of the "usual" tasks that Fedora Scientific aims to provide a platform for | ||
| Line 97: | Line 97: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
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 | 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. | ||
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)? --> | ||
None. | |||
== Contingency Plan == | == Contingency Plan == | ||
This is new feature and will not affect anything else. In addition, this is not a blocking release. | 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 == | == Documentation == | ||
| Line 122: | Line 120: | ||
--> | --> | ||
[[Category: | [[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 --> | ||
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
- Targeted release: Fedora 29
- Last updated: 2018-03-04
- Tracker bug: #1551321
- Release Notes tracking: #122
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)
- List of deliverables: Vagrant boxes for VirtualBox and libvirt
- 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.