<html><body><div style="font-family: Arial; font-size: 12pt; color: #000000"><div>Hi Matthew,<br></div><div><br></div><div>The rubygems issues look like they can be solved with Mo's help. The policykit stuff is more tricky, mainly because I have no idea how it works, so I really need help here. Here are the problems I'm currently facing:<br></div><div>1. I'm working on a minimal install to make sure I pull the right dependencies (including qemu etc.), but I need an auth agent for polkit, should I have a dependency on pkexec?<br></div><div>2. Every time the vagrant command is invoked, the user needs to connect to qemu:///system, may have to change virtual networks (destroy/create), change some NFS shares and firewall rules. What's the best way to manage all that, should I provide a custom policy (how do I create it?), maybe as an option? Should I create a vagrant group with some privileges? Or give them to the wheel group? Will it create security issues on the system?<br></div><div><br></div><div>Maybe solving point 1 is enough to have a working vagrant-kvm environment, but the issues in 2 hinder the usability of Vagrant (because you have to authenticate during the command execution) and makes vagrant-kvm not as fluid as with VirtualBox. My goal has been from the beginning to provide the full Vagrant experience using KVM, so I hope we can solve that.<br></div><div><br></div><div>Alex<br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Matthew Miller" <mattdm@fedoraproject.org><br><b>To: </b>"Fedora Cloud SIG" <cloud@lists.fedoraproject.org><br><b>Sent: </b>Monday, 23 September, 2013 2:29:23 PM<br><b>Subject: </b>Re: Vagrant in Fedora<br><div><br></div>On Mon, Sep 23, 2013 at 08:37:33AM -0400, Alexandre Drahon wrote:<br>> nothing engineering related), I wrote the vagrant-kvm plugin on my spare<br>> time to make it work on my Fedora laptop, though there's now a (much more<br>> qualified) second maintainer who is also providing support for Ubuntu<br>> through a PPA. Matthew asked me if I wanted to work on packaging Vagrant<br>> and the KVM plugin for Fedora 20, and I foolishly accepted ;)<br><div><br></div>Hi Alex. Thanks so much for letting me trick you into doing this. :)<br><div><br></div>> 1. I have a vagrant RPM that installs and works as expected, there's some<br>> minimal patching involved which has to do with the fact that Vagrant<br>> expect to be running in it's own Ruby 1.9.3 environment in /opt<br><div><br></div>Excellent!<br><div><br></div>> 2. There was also some patching involved to make the plugin system work,<br>> although I haven't tested plugins extensively (some stuff breaks like<br>> rubygems loading path) and providing common plugins as RPMs looks like the<br>> better way in Fedora.<br><div><br></div>Are there some in particular we should be looking at? Maybe we can get other<br>people to chip in there once the base package is in.<br><div><br></div>> 3. I had to build my own rubygems-childprocess (current Fedora package is<br>> very old) and rubygems-log4r (not provided in Fedora) RPMs, but I don't<br>> know how I should submit them (package review ticket?). There's a existing<br>> ticket for log4r https://bugzilla.redhat.com/show_bug.cgi?id=905240 , I<br>> added it as a dependency to the Vagrant ticket.<br><div><br></div>It looks like Mo Morsi is an approved committer for that package <br>https://admin.fedoraproject.org/pkgdb/acls/name/rubygem-childprocess<br>and could maybe add you as a co-maintainer too. Mo just responded to this<br>thread in another post so that seems like a good possibility. :)<br><div><br></div><br>> 4. I've packaged vagrant-kvm as a RPM and it installs, but I'm running<br>> into serious issues with Policykit. I don't think I'll be able to solve<br>> that without help, I'm not even sure what's the right way to do it.<br><div><br></div>I used to know all about policykit but it has changed a lot in newer<br>versions. I know who to ask, though, for anything beyond what I can help<br>with -- Miloslav Trmač (mitr) is the current RH maintainer. What's the<br>issue?<br><div><br></div><br>> Looks pretty good, right? <br><div><br></div>Absolutely!<br><div><br></div><br>-- <br>Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm@fedoraproject.org><br>_______________________________________________<br>cloud mailing list<br>cloud@lists.fedoraproject.org<br>https://admin.fedoraproject.org/mailman/listinfo/cloud<br>Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct<br></div><div><br></div></div></body></html>