Re: [Xen-devel] Criteria / validation proposal: drop Xen
On Thu, 2019-07-11 at 14:19 -0700, Adam Williamson wrote: > Yeah, that's where I was going to go next (there has already been a > thread about this this morning). If what we care about is that Fedora > boots on EC2, that's what we should have in the criteria, and what we > should test. While trying hard to avoid a "haha he would say that" response, I do genuinely believe that's a reasonable canary and could cover most of the use cases that various users even outside EC2 would care about. > 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? smime.p7s Description: S/MIME cryptographic signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: [Xen-devel] Criteria / validation proposal: drop Xen
On Mon, 2019-07-08 at 09:11 -0700, Adam Williamson wrote: > It's worth noting that at least part of the justification for the > criterion in the first place was that Amazon was using Xen for EC2, but > that is no longer the case, most if not all EC2 instance types no > longer use Xen. I don't know where you got that particular piece of information. It isn't correct. Most EC2 instance types still use Xen. The vast majority of EC2 instances, by volume, are Xen. smime.p7s Description: S/MIME cryptographic signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Re: Heads up: impending IPv6 Test Day
On Thu, 2011-06-02 at 16:48 +0100, Daniel P. Berrange wrote: > Anything with an fe80:: prefix is a link local address, which > is only unique within the scope of a single LAN segment. Thus > if you want to send traffic to such addresses, you need to specify > the NIC to send the traffic out from. The vast majority of apps > using sockets have no way to let you do this. [dwmw2@i7 activesyncd]$ ssh fe80::21d:7dff:fe04:dbe2%eth0 Last login: Tue Jun 21 12:40:41 2011 from i7.infradead.org [dwmw2@twosheds ~]$ wget fails though: [dwmw2@i7 activesyncd]$ wget 'http://[fe80::21d:7dff:fe04:dbe2%eth0]/' http://[fe80::21d:7dff:fe04:dbe2%eth0]/: Invalid IPv6 numeric address. And curl is just broken for numeric IPv6 addresses completely: [dwmw2@i7 activesyncd]$ curl http://[2001:8b0:10b:1:21d:7dff:fe04:dbe2]/ curl: (3) [globbing] error: bad range specification after pos 9 I think you get a little further if you put the addresses in /etc/hosts. -- dwmw2 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Grrr... modprobe.conf
On Mon, 2010-09-20 at 11:56 +0200, Michał Piotrowski wrote: > 2010/9/20 Bryn M. Reeves : > > On 09/20/2010 06:43 AM, Ralph Loader wrote: > >> > >>> After all these years, something from the fedora repos > >>> (the only ones I have active in my F14 partition) is still > >>> creating an (empty) /etc/modprobe.conf file. > >> > >> Looks like it's a minor security hole too: > > > > Not sure I'd call that minor considering what you can do via entries in > > that file. > > You can blacklist the firewall modules - it can be critical :) Why on earth would that be critical? The firewall is just a band-aid. If it does anything useful, your system was broken (or infected) already. Seriously, if there is *any* case where the lack of firewall would be 'critical', please file a bug for that. There are *much* more interesting things that someone could do with arbitrary write access to /etc/modprobe.conf -- dwmw2 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
