Re: [Xen-devel] Criteria / validation proposal: drop Xen
by Adam Williamson
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
4 years, 1 month
Re: [atomic-announce] Fedora Atomic 29 EOL date?
by Dusty Mabe
On 8/24/19 6:27 AM, Feilong Wang wrote:
> Hi team,
>
Hi Feilong! I'm adding in Spyros who has worked with us in the past on Atomic Host and Magnum.
> Could you please help me understand when will be the EOL date for Fedora Atomic 29? I understand generally it takes 13 months. But given Fedora Atomic 29 -> Fedora CoreOS 30 is a big jump, is there any special considering for this case?
Fedora 29 Atomic Host will follow the EOL schedule for Fedora 29. It will EOL approximately a month
after Fedora 31 is released. Fedora 31 is scheduled to be released at the end of October, so the EOL
for Fedora 29 will probably be around the end of November.
>
> The background is OpenStack Magnum is using Fedora Atomic as the base operating system to deploy Kubernetes cluster, but because of the big change from FA29 to FCOS 30, we haven't got enough resources on this work. So it would be really helpful if the Fedora Atomic/CorOS community can help me understand the roadmap and plan. Thank you very much.
>
The Fedora CoreOS preview release is out now. We're hoping to bring that to stable ASAP but we've got
some things we'd like to finish before we make that declaration. The best thing that can be done is to
get some experience trying out OpenStack Magnum on Fedora CoreOS so that we can get in fixes now before
we declare stable.
We'd like to work with you more closely to make sure the transition is smooth for the Magnum project. Can
you all share some time/resources to work with us to make sure we smooth out any wrinkles?
Dusty
4 years, 3 months
Fedora 30 cloud image inline_data
by Thomas Meyer
Hi,
As the base image has a lot of small files, did someone test what is the influence of setting ext4 feature inline_data?
Are there other reasons why this feature is not active by default?
And:
Why are there so many duplicate files in the cloud image?
Most of them seem to be from pycache and the filename ends in .opt-1.pyc and an equal file ending in .pyc
Would it be possible to add an extra step after creating the cloud image to hard link all duplicate files or what would speak against that?
With kind regards
Thomas
4 years, 3 months
Re: [Xen-devel] Xen / EC2 release criteria proposal
by Adam Williamson
On Sat, 2019-08-10 at 20:12 +0200, Dridi Boukelmoune wrote:
> Sorry for the top posting, "smart" phone...
>
> What about Qubes OS? Isn't their dom0 using xen, based on Fedora?
>
> Do they use Xen as packaged by Fedora? If not, couldn't they contribute
> whatever they do that Fedora doesn't here?
>
> It might be worth getting in touch with them. They look like a significant
> Xen user, on Fedora.
I have no idea, but those seem like reasonable questions. I'll see if I
can track down a contact point for them. Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
4 years, 4 months
Xen / EC2 release criteria proposal
by Adam Williamson
Hey folks! I'm starting a new thread for this to trim the recipient
list a bit and include devel@ and coreos@.
The Story So Far: there is a Fedora release criterion which requires
Fedora to boot on Xen:
"The release must boot successfully as Xen DomU with releases providing
a functional, supported Xen Dom0 and widely used cloud providers
utilizing Xen."
We (QA group) had a discussion about removing this criterion entirely.
That has now morphed into the idea that we should tweak it to be
focused exclusively on the "widely used cloud providers utilizing
Xen"...by which we mean EC2. At the time this criterion was invented,
all EC2 instance types used Xen; now, some still use Xen, and some use
KVM.
So it seems like this would also be a good opportunity to revisit and
nail down more specifically exactly what our cloud requirements are.
bcotton suggested that we require two sample instance types to be
tested, c5.large (KVM) and t3.large (Xen). (I've also mailed Thomas
Cameron, ex-of Red Hat, now of Amazon, for his opinion, as it seemed
like it might be worthwhile - he's promised to get back to me).
So, for now, let me propose this as a trial balloon: we rewrite the
above criterion to say:
"Release-blocking cloud disk images must be published to Amazon EC2 as
AMIs, and these must boot successfully and meet other relevant release
criteria on c5.large and t3.large instance types."
Notes:
1. The test matrix template has an Openstack column, but we never
actually covered Openstack in the release criteria. I think we should
continue to leave it out of the criteria and also remove the column
from the matrix. In the past we tested Openstack boot in the infra
Openstack, but that has gone away or is going away...that means a) we
can't test on Openstack so easily any more and b) a lot of the reason
to bother testing on Openstack is gone. This is up for debate, but if
we believe it's important to test on Openstack and block on working in
that environment we need to have a reliable way to *do* that.
2. The test matrix template also has a 'Local' column which is for
testing locally with testcloud, but I don't think we need to
specifically require that to work in the criteria. It's more of a
testing convenience thing, so even if no-one tests on EC2 we at least
test that the image boots in testcloud; testcloud isn't an environment
you'd actually use to do anything practical in.
3. I believe this wording is generic enough to cover us if we, e.g.,
want to start blocking on CoreOS images. All we have to do is declare
that some CoreOS image is 'release-blocking', and it's instantly
covered by this requirement.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
4 years, 4 months
