Learn more about these different git repos.
Other Git URLs
For:
https://github.com/redhat-imaging/imagefactory/commit/f51a8da61737b4c664cf22dc17bcb806c601b862
<imcleod> I implemented the patch in that way originally because it allowed us to add the ability to generate box files to koji without any changes to koji itself. The OVA support already had the ability to pass arbitrary config parameters to the Factory OVA plugin. <imcleod> The only downside, as I see it, is that the output files have confusing names. I started on a small koji patch to fix that up.
So we either need that koji patch, or to just "for x in *.ova; do mv $x $(basename $x .ova).box" in run-pungi.
This is nothing we can control, we do not rename or modify the output of koji, run-pungi is only a small part of the releng process. if a patch gets upstream in koji that changes things we will pick up the changes then.
Dennis, is there any chance of an upstream patch getting into production before the release?
This is a security / user experience issue, because vagrant boxes are dangerous to run out of the context of vagrant.
As a workaround for f22, would it be possible to create a symlink on the mirrors with the .box extension, and then we can point users to that from the web site?
Reopening this because the ''need'' is valid, regardless of implementation or timing.
Replying to [comment:2 mattdm]:
Dennis, is there any chance of an upstream patch getting into production before the release? This is a security / user experience issue, because vagrant boxes are dangerous to run out of the context of vagrant.
How is "xxx.ova" dangerous to run out of the context of Vagrant? I haven't tried to open one of the Vagrant boxes in VirtualBox or VMWare Player, but wouldn't the virtualizer protect me?
BTW, I'm not a huge fan of Vagrant - it seems heavily dependent on VirtualBox and its "configuration file" is Ruby code!
Replying to [comment:4 znmeb]:
Particularly, it has well-known accounts and passwords as standard. Vagrant by default sets up host-only networking so this is not a big deal.
Whether or not you are a fan, many people definitely are, and many of those people are the software developers we'd like to entice into using Fedora. Many of them aren't even (yet?...) using Linux on the desktop, instead using a Mac or Windows. Having Virtualbox images therefore helps us spread into a new segment.
However, we also have libvirt (kvm-based) Vagrant as a feature for Fedora 22 https://fedoraproject.org/wiki/Changes/Vagrant, so no one will be tied to Virtualbox.
Metadata Update from @walters: - Issue set to the milestone: Fedora 21 Final
Login to comment on this ticket.