>
> I'd like to understand the EC2 strategy a bit more. Is the goal to have a
> populated / up to date AMI (maybe this exists) that a customer could
> launch?
These already exist and are updated regularly [
https://getfedora.org/cloud/download/atomic.html]. There is an open ticket
b/c some of t
On 02/01/2016 10:00 AM, Jonathan Lebon wrote:
The manageiq website handles this sort of branching pretty nicely:
http://manageiq.org/download/
You choose openstack, ovirt, rhev or vsphere, and each heads off
to a nice short quickstart.
Nice, that'd be sweet!
So in our case, we'd have
- Va
> The manageiq website handles this sort of branching pretty nicely:
>
> http://manageiq.org/download/
>
> You choose openstack, ovirt, rhev or vsphere, and each heads off
> to a nice short quickstart.
Nice, that'd be sweet!
So in our case, we'd have
- Vagrant
- QCOW2 with cloud-init
- QCOW2 w
On Sat, Jan 30, 2016 at 5:17 PM, Jason Brooks wrote:
>
>
> - Original Message -
> > From: "Matt Micene"
> > To: "Jonathan Lebon"
> > Cc: "atomic-devel" , "container-tools" <
> container-to...@redhat.com>
> > Sent: Friday, January 29, 2016 12:48:59 PM
> > Subject: Re: [atomic-devel] Land
On Mon, Feb 1, 2016 at 9:41 AM, Aaron Weitekamp wrote:
> On Sat, Jan 30, 2016 at 5:17 PM, Jason Brooks wrote:
>
>>
>>
>> - Original Message -
>> > From: "Matt Micene"
>> > To: "Jonathan Lebon"
>> > Cc: "atomic-devel" , "container-tools" <
>> container-to...@redhat.com>
>> > Sent: Frida
