Hello everyone, my name is Troy Dawson, I work for Red Hat.
I work on the central stream and emerging rail team.
This talk was originally written by Adam Samalak.
He's not able to be here.
But he told me he would be here in spirit.
He's actually watching right there.
And he told me he had, well, I don't believe him.
But he told me to hack it by laptop.
See what happens.
Anyway, let's get going.
It all starts with Fedora.
What is Fedora?
Fedora is a little blue bot.
Fedora is lots of things.
Fedora is servers, IOT.
Oh, maybe he is in here.
Well, I guess you can do gaming.
People have some gaming machines, yeah, Adam.
But you know what, we're not here to talk about Fedora.
Are we talking about rail?
Fedora, every three years, it's brings in to rail.
In the past, I was on the team that did rail a eight.
And it was all behind closed doors.
And we couldn't talk about it.
And it was very secretive.
And I hated it.
It was terrible.
But that didn't last too long with rail nine.
We put in central stream in the middle.
And now, every three years, it goes from Fedora to central stream,
and going to rail.
But we're not here to talk about rail either.
We're here to talk about central stream.
What is central stream?
It is a Linux OS maintained by rail engineers.
I'm not a rail engineer, but I don't maintain the packages.
The rail packages maintain those packages.
Okay, so I like we are going to talk about Fedora.
What is Fedora?
Fedora has this raw-high branch that keeps up with the latest things.
And the package maintainers keep things up to date there,
and every six months, six months.
Well, I can talk to it.
Every six months, they'd branch to make a Fedora release.
But while that packaging is happening,
there's a little thing called ELM there.
And that is the Fedora packages being built with red hat
or rail flags, tags, macros.
And to test if they build, to test how they work.
And then every three years, we're actually branching from ELM
into central stream, and then that central stream eventually goes into rail.
Now, this is a blow up of what's happening right now.
This is what central stream can and railed can a while ago.
ELM is going along doing its business.
And we started doing bootstrapping and during that bootstrapped phase,
we kept the sources sink between Fedora and ELM,
which is the same source into central stream.
And we kept that going.
Getting our infrastructure set up, getting our build route set up.
And then at some point, we cut that off.
And then we have what we call the pre-release phase.
And that's where the rail maintainers go.
We want this.
We don't want that.
All this flag really needs to be tweaked this way.
And that way.
And then at some point, we're doing another cut.
And we say, we're doing releases.
We're doing rail betas.
And we're here right now.
So, central stream 10 was released in December.
It's a great release.
I recommend it for people who like Linux.
I like it.
Run whatever you want.
But I like this one.
So, we're here.
We do have central stream release.
You might notice that rail does not have a release yet,
but their beta is out.
And while we're still doing it,
we continue to do central stream 9.
That gets developed on central stream and goes to 9.
So, what does this look like?
We'll look at the pipeline a little bit.
We have our three things that we want to look at.
We're going to look at our sources.
The sources are kept in sync between central stream and rail.
The central stream stuff is all visible by the public.
It should be, if it isn't, let us know.
But if it's in sync when something goes into the central stream release,
it gets automatically synced as well.
If it doesn't happen, then might think it's page,
then we make sure it gets synced into rail that does happen occasionally.
But less or less.
Builds are sort of coupled.
Adam made this.
He said he trademarked it.
I don't think it is.
But they're sort of coupled.
Central stream.
Things they built in coaching.
You know, let's go into more detail.
And then we have releases.
We're releases are totally uncoupled.
Central stream does their own thing and rail does stuff.
Oh, yeah.
Adam lives in Europe.
European elevators start with zero.
So we're not going to start with one.
Everything starts with zero.
Yes.
We love JIRA.
We're just going to have one slide on JIRA.
I promise this one slide on JIRA.
Issues at redhat.com.
You just have to do things in bugsillers.
Now go to issues.redhat.com.
It is JIRA.
They're trying to make it better.
That's where you do bugs in issues.
And the most importantly, you can talk with the maintainers of various packages.
Because when you do sources.
When you're working with sources, you first want to merge your quest.
But before they can do a merge your quest, you've got to have a JIRA ticket.
You see, the merge your quest goes through a test before the merge.
Test number one.
Is there a JIRA ticket?
I'm sorry.
But that's the test.
But the merge request goes through.
It gets tested.
It gets merged into the sense of strain.
And then immediately goes over the rail.
Because rail already knows it's been tested and merged.
This is sort of what it looks like.
We're looking at the system D when the system D got updated 256.
This was the merge request.
There's the tests.
Doing the check number one.
Checking the status.
It's checking right there.
There's a rail ticket right there.
And here is JIRA.
It seems not so scary.
It's not that scary.
Yeah.
But this was actually opened by a member of the public.
This was not opened by a rail maintainer.
Public says, hey, I would like system D to be updated.
We were early enough in the 10 development cycle.
They said, yeah, that sounds like a great idea.
And they did it.
And when into there, it went into the Git Hub source repo.
I said GitHub, didn't I?
Yeah.
If I say GitHub, substitute it for GitLab.
We're doing GitLab.
It went through the GitLab repo.
Somebody else said, oh, previous talk was talking about GitLab.
GitLab repo.
And this is what the files look like.
This is a quick overview for those of you.
I've not seen spec file or packages for those familiar with the door.
You will notice that you got your spec file there at the bottom.
Various patches and stuff read me.
But the top you see, I think, called sources.
That is not a directory.
That is not the actual sources.
That is a hash tag that says, hey, this is the hash tag for the sources.
The sources, because sometimes it's a bigger tip.
It's like, look, it's like cast.
And where you went, oh, Adam did this before.
It didn't work.
It worked for him.
We tried.
Adam, Adam, stop.
I'm just going to, no, stop.
There.
No, no, no.
There we go.
Okay, we're fighting over it enough.
There is ways to get those tarballs down.
It's called cent package.
Adam had this really fancy thing.
Anyway, don't worry about it.
You can directly, W get these tarballs.
But it's harder to find.
You have to figure out where the look inside cash is.
You have to find the hash.
If you use a thing called cent package similar to Fed package.
But it's for centros.
It will automatically look those things up.
If you do cent package, sources, cent package, SRPM.
You can get them.
If you really, really want to find them.
Contact me.
Oh, let's, you know.
Anyway, sources are there.
Let's move on to builds.
Again, we said they were sort of coupled.
What does that mean?
Let's look at the build things.
The top thing is centros stream the bottom is real.
This is all public.
You can see it as it's happening.
This is not public.
But sometimes it influences what is happening.
The first thing is a real maintainer.
I'm sorry if you remember the public you cannot start a build.
You might be able to do a merge request and various things.
But the real only maintainers can start a build.
If it passes build, it goes down there and gets build internally.
And they both get a tag.
This is a Koji tag.
It's a wait for Koji and various scripts and stuff to keep track of this.
And they give a tag called gate.
And then they go to the gating things.
And that's where the tests get run on it.
And it's really fun and exciting.
And if you like test, that is fun and exciting.
If they pass the test, they go to candidate.
And at this point, it's sort of a, that's where the maintainer goes,
OK, do I really want this in or do I not want this in?
Is past the tests.
And then they do.
And if they verify it, then it goes to pending.
So let's look at this a little bit.
I'm going to use Firefox here.
And Firefox here has, this was a 16th of January.
It got the 10 gatings and then it passed those gates and made it to candidate.
And then it took several days.
You can't see it here, but I know this particular package.
It's several days.
And then it went into pending.
And we'll talk about that another one just a little bit.
Those of you outside of the rail influence,
didn't look at the rail beta or central string beta,
we'll notice this is an important package.
Why would Firefox be so important?
Because it wasn't there.
I don't get to say what's in rail and what's not in rail,
but Firefox was not in rail.
But there is now.
And it came just in time for this conference.
Just in time for me to make some images that I'll talk about a little bit later.
So Firefox is now in rail and central string.
10.
And it was already in, don't worry about those ones.
Anyway.
So what happens after we build them and tag them,
they go into a release.
So we go into composers.
We go into tips that repose and images,
except, okay, composers have repose and images
in the et cetera and Adam knows that I have two more slides
and we're going to talk about that.
Anyway, they have composers that get tested
and then they release them.
Here's let's talk about that.
We talked about tags.
We already said, getting pending.
Guess what that, pending sign means.
It's signed.
Yes, you guys guessed it.
You are a brilliant bunch.
Compose is not really a tag,
but it is a tag.
But you won't see it in Koji.
It helps us for making our composers.
And I will show you that there.
We have two composers.
The development composes usually goes out every day.
Unless we're running out of storage and then it's every other day.
Because we're running out of storage.
Production goes out every few days.
It gets produced every few days.
But once a week we do run it through testing
and it goes to the central stream release.
So what's in the release?
That's what Adam wanted me to say.
Oh, it was three slides.
Three slides.
In a release we have different repos.
We have baseless, we have upstream.
We have CRB, which is an acronym yet to be determined.
We have lots of add-ons.
These are usually just small little things.
But they're important for those people that want them.
High availability, NFD, I don't know what that is.
RT, resilient storage, sap.
Anyway, lots of little small things.
They're usually just one, too.
But more important, we have images.
There's lots of DVD ISOs, net installs,
small containers, which everybody really likes.
AWS, which people will need.
But you must like in two cows.
Which I love that name.
I grew up around there.
And so, you know, the cute cows.
But there's two of them.
Sorry, I couldn't resist.
Oh, more images.
Oh, and there's more images.
Well, talk about them a bit later.
I'll image a signal.
This is my own plug.
I'm sorry.
I haven't gave it a plug that for me.
Okay.
Yeah.
Tell me more about the testing.
Okay, let's talk about the testing.
He's right.
It's good thing to talk about.
The testing is done by the Centos integration, said.
And we, it's on Jenkins.
Of course, it's on Jenkins.
I like Jenkins.
You know, it's a little popular that serves you.
But many people don't.
In the old days, all the way up through Centos Stream 9,
they've been using the Centos Test Suite.
I can't remember it.
And it's all the way across over there.
So I can't read a deep functional suite.
I just remembered it.
That's a good testing thing.
But it wasn't community-based.
I don't know who wrote it.
But the, the, the Centos Test, it's not, it's not called testing.
But I'm going to call it that.
Integrations.
It's actually right there on the slide.
I should read it better.
The Centos integration, say, wrote, wrote up some new tests
in there in TMT.
They are still working on some, but the art 64 in the,
you can't see it in here.
But another one always works if things work.
And then they don't, if they don't.
There's still working on a couple of other arches.
And anyway, we are, they are doing a great job with that.
And we appreciate the community work that's came down.
This is their page, a sick page.
More importantly, this is where the composed tests are.
And we can, you can see what the composed tests.
And even more importantly, here's their get lab,
re-post and get lab on getting that.
And I wanted to think Carlos, he, he set up,
almost all of this, if not all of this.
And it's done a great job.
And if you wanted to help with testing in the Centos,
you can.
And you can influence each week's composed.
And we really appreciate what happened in there.
Now I talked about Cigs before I talked about Cigs.
So that's sort of backwards.
Let's talk about Cigs.
First off, I'm using the acronym Special Interest Groups.
That's what I say is the Centos Special Interest Groups.
The Centos Project is a rectangle.
It's not a square.
It's also a purple.
But it really, Centos Project has lots of things in it.
The Centos Stream is one little part of it.
But there's a lot of other things that are built in the community.
And those are the Cigs.
The Centos Project has two built systems.
It's just, aren't acronyms.
Yes, acronyms are just lovely, Adam.
But you know very well that next slide,
I'm going to talk to anyway.
Ciscogee in CBS Cogee.
The Centos Stream gets built on the Centos Stream Cogee.
But the Cigs have their own Cogee, which is the community.
Build system Cogee.
You know, the C-S don't get confused with that.
But Cigs, there's a governance on how to,
all about Cigs in Centos,
because Cigs are a very big thing.
They're driven by the Centos Board until they don't need to be governed anymore.
Or, well, governed too much.
They're all independent.
Meaning they can do the membership their own way.
They're releases their own way.
As long as they follow within certain guidelines,
we have documentation for creating retiring.
But you really should start trying to join the Cigs.
You can see which Cigs fit what you want to do,
and then join it.
If there isn't one that doesn't what you want to do,
then go ahead and start your own if you want.
So today, I wanted to talk a little bit.
I'm going to slow down my talking.
This is where Adam stops, sorry Adam.
I wanted to talk about some of the Cigs.
So I have with me Neil, who is part of the HyperScale Cig,
Neil, would you come on up here for a few minutes?
I'm going to ask you pretty much two questions.
And two questions are, why did you and the others start the Cig?
And what does your Cig do?
So, hi, Neil Gompo.
I helped co-found the HyperScale Cig along with a bunch of other people.
Dabana, they're in the corner,
and Michelle's probably somewhere in the corner too.
But yeah, so we created the HyperScale Cig because it became fairly evident
that all of us who are at the time working at different companies,
well, we are still working at different companies, but,
not the point.
Anyway, people working at different companies who are using CENTOS
all wound up doing a bunch of the same things to make CENTOS useful and usable
for their environments.
And all of us were fairly unhappy that we were all doing it redundantly
inside of our environment, rather than bringing it out into the open
and sharing and collaborating so that other people can benefit
and that we're not doing duplicative work all over the place.
So, that's kind of why we started it.
And what the purpose of it is, is really for enabling CENTOS
to be more useful at large scale deployments.
Pretty much all over.
Although it could be used anywhere.
We don't care if you're interested in the stuff that we're doing
and the stuff that we offer, you know,
we're always open for that kind of thing.
Like the big thing we do is make a variant of CENTOS stream
that brings a lot of the nice things from Fedora that
Brett had did not include and make it available for people to use
in a long-term supported fashion.
I heard one of those things was butter offense.
It involves both not just the butter as a file,
but also the kernel.
Yeah, so we provide our own kernel.
We also go, we work our way backwards through
CENTOS stream user space and enable the butter
of a support that was turned off in the base distribution.
So, that means that in addition to providing packages
and content, we also provide images that have
an integrated storage stack all the software
turned back on.
So things like anaconda cockpit and all that stuff
will helpfully be able to use butterflies and be able to do things for you.
And in addition to, you know, images around with
butter offense, we also do things like provide updated
system-d testing on new features,
bringing in all the kinds of enhancements
and features that you would see on Fedora
but also now optimized on a CENTOS space.
Thank you very much, Neil.
We have one other signal,
what you handed to him and he'll
he'll know what to do with it.
We have one other person from another sig.
The other sig is all turned of images sig.
Troy Dawson, would you come up here?
Yes, yes, I will.
Thank you very much.
Let me put on my other hat.
One of the things I do in the CENTOS
stream team is I make the actual images.
And I got frustrated that there is a
tin of Troy, you're talking
before I asked you the questions.
Why did you start your, why did you start
starting to sig?
And what does it do?
Oh, sorry, I got ahead myself.
I was working with the CENTOS stream making the images.
And I'm like these images just come in
10 gig size.
I want this smaller size for my installation
because I keep hitting my internet cap.
And then I asked around the CENTOS community.
And there's other people, like,
hyper scale and I actually have several of the
hyper scale people on our sig.
And we still, yes, we still do.
And we have a few others that are not on the
hyper scale.
So what sort of things do you do?
Well, we make these images up here as you see here.
We make live images.
Those are currently one of the most popular.
We make them for every desktop.
You know, you see, for nine, we got CENTOS
KDE, Matai slash make of whatever you want to pronounce.
We have CTE that we have this CENTOS Max min.
My favorite is min, but also Max.
Min is a text-based live thing, which, you know,
has no desktop, but it's great for low memory.
Something you just want to boot in and do something.
You're talking a little too much.
Say about that.
But Max has all of the desktops.
The other one that is becoming much more popular
is WSL images.
Those are images to run CENTOS stream on Windows.
Anyway, I don't use them much, but other people
have been asking for them.
They were excited for it.
Does it do graphics?
Yes, if you saw my CENTOS,
they do graphics, but the CENTOS stream
doesn't run Firefox, KDE, all sorts of fun things.
Thank you very much.
Okay.
Two cats.
I actually do have a CENTOS stocking cap,
but I didn't want to wear it through the whole thing,
and what a sweater did that.
Anyway, the CENTOS project,
it is a great thing, it is more than just CENTOS stream.
It's got a lot of neat and interesting things.
I would have actually brought up many more things
that it would have been a great thing.
But I figured too was enough.
It is a CENTOS stream,
as an operating system maintained by real engineers.
It's not going to just sort of go away.
As long as there's real,
you're going to get your CENTOS stream maintained for five years.
It's released every three years.
It's supported for five-ish years.
It's five years from the time that realm,
the corresponding realm releases.
So that's a pretty good time.
And thank you.
Do we have any questions?
Yeah, he stole my hat.
But it's just too hot.
Do we have any questions?
Sorry.
We got one over there.
Okay.
Do you see yourself pursuing an alternative career
in STEM that's not a comedy?
No, but I do see myself in a fashion designer.
Except for nobody likes my fashion.
I should be here.
I also have a series question.
I can't talk to you today, so forgive me.
Do you see this sex-powered organization
on model spreading to other districts in the future?
I certainly hope so.
Now, I think CENTOS SIGS was model off of Fedora's SIGS.
But to me, I feel like the CENTOS SIGS have more freedom than the Fedora's SIGS.
Do you think it's the other way around?
But anyway, it's at least corresponding with Fedora.
I don't see it spreading to realm.
I don't know how that would happen.
Yeah, I'm not going to do it.
But I hope it spreads to Susay, open Susay.
I don't know the deviant Ubuntu.
Oh, I'm getting a nod from a Susay.
Oh, Alma.
Alma, Linux, possibly Rocket Linux?
Yeah.
So yes, I do see the SIGS thing spreading.
Because it empowers people.
It allows people to use what they want.
I'm not only the CENTOS SIGS, one of the main teenagers,
or I'm not a package maintainer.
I put it all together.
Whatever that is called, but I'm a user.
I'm really like CENTOS SIGS.
So what are the biggest pain points in this kind of approach in your opinion?
Using the SIGS?
Yeah.
The biggest pain point is CENTOS SIGS.
And that it is tied directly to realm.
And you can talk to Neil about pain points.
But just so you know the alternative image is SIGS.
We don't change things.
We'll put Apple on top of it.
We'll put things on top of it.
But we do not change the base realm because we want people
when they install our alternative images to get the base realm.
Whereas hyperscales, skids, hyperscales.
Yeah, I know.
Yes, words are hard.
But they do changes.
And the fact that the realm packages cannot be changed.
But as you can see, there's some SIGS that want to keep the same
something one to change.
But that is, in my opinion, probably a pain point.
Thank you.
Good.
Oh, that was just people.
There is one.
Thanks.
Oh, there's, I think to one on the other side too.
Hello.
I have to admit, I haven't used SENTOS.
But I would like to have the question about SENTOS.
Not about the SIGS.
If that's okay.
That's fine.
What would be, I mean, convincing for an end user.
This is admin.
Do you use SENTOS stream?
Okay.
SENTOS stream.
Instead of say, all the Linux or Rockie Linux.
And that's a good question.
I almost answered that question before.
As, as a SIS admin.
And this is the last question we're out of time.
At least that's what the science said.
As a SIS admin, I like it because I don't have that every six month jump.
Real has a jump.
Fedora has a jump every six months.
SENTOS stream has a once a week update.
But there's no major jump.
And that's why I like it.
A lot of people just use a for testing.
You know, I'm doing real and testing.
But as an admin, that is why I like it.
If others don't like it, that is fine.
I'm totally fine with whatever people like running.
But it's, it would be stable enough.
Oh, yeah, definitely stable enough.
It's, it's real stable.
There's, there's many tests that gaming tests that we said.
That's a pretty intensive thing.
And my time is up.
Thank you very much.
And thank you.
Thank you.