On Thu, 2019-07-11 at 14:19 -0700, Adam Williamson wrote:
> On Thu, 2019-07-11 at 21:43 +0100, Peter Robinson wrote:
> > > 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.
> >
> > Correct, it's only specific types of new hypervisors that use kvm
> > based, plus new HW like aarch64.
> >
> > That being said I don't believe testing we can boot on xen is actually
> > useful these days for the AWS use case, it's likely different enough
> > that the testing isn't useful, we'd be much better testing that cloud
> > images actually work on AWS than testing if it boots on xen.
>
> 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.
>
> 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.
OK, so, to move forward with this (and looping in cloud list): does
someone want to propose a set (ideally small - 2 would be great, one
Xen and one non-Xen, if we can cover most common usages that way!) of
EC2 instance types we should test on? With that, we could tweak the
criteria a bit to specify those instance types, tweak the Cloud
validation page a bit, and then drop the Xen criterion and test case.
Thanks everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2019-07-31 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/
On 7/15/19 10:33 PM, Feilong Wang wrote:
> Hello, could anybody please take a look at this issue? Thanks.
Hi Feilong,
>
> On Thu, Jul 11, 2019 at 9:43 AM Feilong Wang <hustemb(a)gmail.com <mailto:hustemb@gmail.com>> wrote:
>
> Hi team,
>
> Now I'm testing upgrade for Fedora Atomic 29 image, but when I run command "atomic host deploy <commitID>" I got below error. Could you please help me understand how to fix this? Thank you in advance.
>
> /[root@test-fc29 log]# atomic host status
> /usr/lib/python3.7/site-packages/Atomic/util.py:469: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
> return yaml_load(conf_file)
> State: idle
> AutomaticUpdates: disabled
> Deployments:
> * ostree://fedora-atomic:fedora/29/x86_64/atomic-host
> Version: 29.20190528.0 (2019-05-28T00:23:56Z)
> Commit: cb50ac29d58f4e7e8dcfc3c2dd4156c6acd17038577437e4744edee7b7c02eda
> GPGSignature: Valid signature by 5A03B4DD8254ECA02FDA1637A20AA56B429476B4
> [root@test-fc29 log]# atomic host deploy cb50ac29d58f4e7e8dcfc3c2dd4156c6acd17038577437e4744edee7b7c02eda
> /usr/lib/python3.7/site-packages/Atomic/util.py:469: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
> return yaml_load(conf_file)
> Validating checksum 'cb50ac29d58f4e7e8dcfc3c2dd4156c6acd17038577437e4744edee7b7c02eda'
> error: While fetching mirrorlist 'https://ostree.fedoraproject.org/mirrorlist': While fetching https://ostree.fedoraproject.org/mirrorlist: [6] Couldn't resolve host name
That's odd. It seems to work for me.
Are you still having trouble? Can you tell me what is in the files in your /etc/ostree/remotes.d/ directory?
Dusty
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2019-07-24 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2019-07-17 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2019-07-10 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2019-07-03 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/