From Fedora Project Wiki
m
m (Add trackers)
 
(5 intermediate revisions by 2 users not shown)
Line 12: Line 12:
 
* Targeted release: [[Releases/30 | Fedora 30 ]]  
 
* Targeted release: [[Releases/30 | Fedora 30 ]]  
 
* 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}}  
* Tracker bug: <will be assigned by the Wrangler>
+
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1678455 #1678455]
* Release Notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/8085 #8085]
+
* Release Notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/303 #303]
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 32: Line 32:
 
** Work has been done in a Copr repository: https://copr.fedorainfracloud.org/coprs/pvalena/vagrant/
 
** Work has been done in a Copr repository: https://copr.fedorainfracloud.org/coprs/pvalena/vagrant/
 
* Other developers: N/A (not a System Wide Change)
 
* Other developers: N/A (not a System Wide Change)
* Release engineering: [https://pagure.io/releng/issues #8085]
+
* Release engineering: [https://pagure.io/releng/issue/8085 #8085]
 
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change)  
 
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change)  
 
* Policies and guidelines: N/A (not a System Wide Change)  
 
* Policies and guidelines: N/A (not a System Wide Change)  
Line 48: Line 48:
 
* No special hardware is needed.
 
* No special hardware is needed.
 
* Install Vagrant
 
* Install Vagrant
* Run ```vagrant version```
+
* Run `vagrant version`
 
* Use your Vagrantfiles or create new as before
 
* Use your Vagrantfiles or create new as before
 
* If something doesn't work as it should, let us know.
 
* If something doesn't work as it should, let us know.
Line 71: Line 71:
 
https://github.com/hashicorp/vagrant/blob/master/CHANGELOG.md
 
https://github.com/hashicorp/vagrant/blob/master/CHANGELOG.md
  
[[Category:ChangeReadyForWrangler]]
+
[[Category:ChangeAcceptedF30]]
  
 
[[Category:SelfContainedChange]]
 
[[Category:SelfContainedChange]]

Latest revision as of 20:00, 18 February 2019

Vagrant 2.2

Summary

Upgrade to Vagrant 2.2, the latest stable version of Vagrant. Enable QEMU Session by default.

Owner

Current status

Detailed Description

Vagrant 2.2 is new upstream's major release, that includes many features, improvements, and and bug fixes. Using qemu:///session instead of qemu:///system Vagrant will run unprivileged.

Benefit to Fedora

  • Enable QEMU Session by default. With this, there's no need for user to input any password, or be present in some group. Everyone is able to use Vagrant, regardless of group or other ACLs.
  • Add host support for void linux
  • Add support for VirtualBox 6.0
  • Add command for uploading files to guest

Scope

Upgrade/compatibility impact

Because of QEMU Session enabled by defailt, a failure occurs with if Vagrantfile contains: ` test_vm.vm.network :private_network, :ip => "172.16.0.2" ` or similar. Can be solved by setting libvirt.qemu_use_session = false in Vagrantfile.

How To Test

  • No special hardware is needed.
  • Install Vagrant
  • Run vagrant version
  • Use your Vagrantfiles or create new as before
  • If something doesn't work as it should, let us know.

User Experience

New features that come with Vagrant 2.2 will be available. Users will not need to add themseles to any group, or have root ACLs and input a password every time they use Vagrant.

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: 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)
  • Blocks product? N/A (not a System Wide Change)

Documentation

https://www.vagrantup.com/docs/

Release Notes

https://github.com/hashicorp/vagrant/blob/master/CHANGELOG.md