On Fri, Mar 6, 2015 at 3:18 PM, Joe Brockmeier <[email protected]> wrote:
> On 03/06/2015 01:46 PM, David Gay wrote: > > > > If we want the vagrant images to be listed on the prerelease page, the > web team needs some text to put with them, like we do for the other images. > I pinged a few vagrant-connected folks in IRC, but it seems they're not > around. Assuming we *do* want these images listed, can someone with > knowledge of them produce some sort of text to send to the web team? > > Vagrant Images > > Fedora Cloud edition is also available as a Vagrant Box in formats > suitable for libvirt or VirtualBox. If you're using Vagrant on Mac OS X > or Windows, you'll probably want the VirtualBox image. If you're using > the Fedora Vagrant package, you'll want the libvirt image. > > If you're working with general cloud development, choose the Cloud > image. If you're doing Docker development, choose the Atomic image. > > Some mods.. thoughts? Vagrant Images Fedora Cloud edition is also available as Vagrant Boxes in formats suitable for libvirt/KVM or VirtualBox. If you're using Vagrant on Mac OS X or Windows, you'll probably want the VirtualBox image. If you're using the Fedora Vagrant package, you'll want the libvirt/KVM image. If you are doing general cloud development or developing new containers, the Cloud image is probably the right choice. If you want to run containers, either to run a service or to develop on top of, the Atomic image is more suitable. Langdon > > -- > Joe Brockmeier | Principal Cloud & Storage Analyst > [email protected] | http://community.redhat.com/ > Twitter: @jzb | http://dissociatedpress.net/ > > > _______________________________________________ > cloud mailing list > [email protected] > https://admin.fedoraproject.org/mailman/listinfo/cloud > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > >
_______________________________________________ cloud mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
