Vagrant 2.2 with QEMU Session

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://fedoraproject.org/wiki/Changes/Vagrant_2.2_with_QEMU_Session

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

== Owner ==
* Name: [[User:pvalena | Pavel Valena]], [[User:vondruch | Vit Ondruch]]
* Email: pvalena@xxxxxxxxxx, vondruch@xxxxxxxxxx
* Release notes owner:

== 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 ==
* Proposal owners:
** Finish packaging Vagrant 2.2. Current changes:
https://src.fedoraproject.org/rpms/vagrant/pull-request/17
** Finish packaging Vagrant-Libvirt plugin. Current changes:
https://src.fedoraproject.org/rpms/vagrant-libvirt/pull-request/3
** Work has been done in a Copr repository:
https://copr.fedorainfracloud.org/coprs/pvalena/vagrant/
* Other developers: N/A (not a System Wide Change)
* Release engineering: [https://pagure.io/releng/issues #8085]
** [[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)
* Trademark approval: N/A (not needed for this Change)

== 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

-- 
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux