On 12 Jul 2019, at 13:24, Peter Robinson <pbrobinson(a)gmail.com>
wrote:
On Fri, Jul 12, 2019 at 5:50 AM David Woodhouse <dwmw2(a)infradead.org> wrote:
>
>
>> IIRC, what we have right now is a somewhat vague setup where we just
>> have 'local', 'ec2' and 'openstack' columns. The
instructions for
>> "Amazon Web Services" just say "Launch an instance with the AMI
under
>> test". So we could probably stand to tighten that up a bit, and define
>> specific instance type(s) that we want to test/block on.
>
> I think we can define a set of instance types that would cover what it
> makes sense to test. Do we still care about actual PV guests or only
> HVM? I think it makes sense to test guests with Xen netback and blkback
> rather than only ENA and NVMe, but Fedora probably wants to test the
> latter two *anyway*.
>
> Do we want to do this by making sure you have free credits to run the
> appropriate tests directly... or is it better all round for us to just
> do this on nightly builds for ourselves?
>
> The latter brings me to a question that's been bugging me for a while —
> how in $DEITY's name *do* I launch the latest official Fedora AMI
> anyway? I can't find it through the normal GUI launch process and have
> to go to
getfedora.org and click around for a while because I find the
> specific AMI ID for the that region, and then manually enter that to
> launch the instance. Can't we fix that so I can just select 'Fedora 30'
> with a single click? Whose heads do I have to bash together to make
> that work?
So the easiest way to do this is by going to link [1] and select the
cloud image "click to launch" it gives you a list of AWS regions and
takes you direct to the AWS dialogs to run them.
[1]
https://alt.fedoraproject.org/cloud/
David, Peter,
thanks for helping resolve this issue. It seems to me that testing against EC2 Xen
instances should indeed cover what most users need
Lars