 Well, my name is Peter Boy, as you may see. And just about myself and my relation to Fedora Server, I'm a scientist at the University of Bremen and graduated in sociology, far away from server. But as a minor, I had applied mathematics, which was an academic home for computer science those time. Well, and once the time we managed with our institute to apply for a so-called accident center, it's a special funding in Germany. The effect was, we got a lot of money. And we got a lot of independence from our central university IT, but the obligation to do it of our own. And because I had that do the qualification, our colleagues think, OK, it's a job for you. As a side job, of course, we need everyone to research. Fortunately, I got some compensation in teaching, but I had a lot of money and a nice side job. It was, well, we started with AIX, it's the IBM version. But soon the interboxes got more powerful and we started with Linux. And I had to check which Linux distribution. OK, it's somehow Reddit looked for me with all these advantages. I knew from IBM it's a good interface, a good support, everything like that. So I decided for Reddit. Unfortunately, short after we did that, Reddit dropped the academic license program. So we had, despite a lot of money, but not so much. Fortunately, we got scientific Linux and we used it, we used the combination of scientific Linux and Fedora server, the classical case of usage, scientific Linux for the stable version, and Fedora to get the latest software. Sometimes ago, scientific Linux died as well. And I had the option in the center of Fedora and I decided for Fedora and put everything to Fedora server edition, it was in that time. So I had a small bunch of 20, about 20 servers boxes in Fedora server edition and some virtual machines on top. Well, it's my special experience. We had no any problem with Fedora. Everything works fine, just one case. We upgraded the release and a colleague of mine saw a strange message, something as long. But he was saying, OK, it worked forever. Don't worry, be happy. But afterwards, you were not happy, it's something to do. So I think we at Fedora server should build in some quirks. So it means keep watching and not to be sure everything works fine. Well, that's my personal experience with Fedora. And I started then, end of 2020, when Matthew started to reboot the server working group. And I had this strange idea to spend our internal Fedora documentation to Fedora instead to build our own website and started with documentation. Well, and somehow I ended up as a coordinator for all the business we have. No issues? OK. So what is it? Oh, sorry, I have the wrong glasses, I can't. Well, probably first of all, some remarks about the current state of Fedora server addition and some information what's going on. And at the end, what we are planning to do for the next time. Well, the first thing is the working group. We had a reboot in 2020. And currently, we have officially 70 members, according to the working group relations for Fesco. We have two weekly meetings. And we have it constantly about the last two years. So I think the reboot went fine. Well, we have nine members who in the two and a half years have regularly contributed and discussed, specifically contributed some work. And two members who are sometimes discussing. Well, and six members who constantly do nothing over the last one and a half years. And it's probably not no problem, but anyhow we have just to see how to handle these cases, I think. And we have the big advantage that we are a mixture of old hands, so to speak, members who were a part of the working group from the beginning. And a lot of newbies, so as me, who try to catch up and to carry it forward. At the end, I think the reboot was a success. And we have now a quite active server working group. But the other thing is the addition. We update our technical specifications, which we are shifting from the previous base server role as a UDF-based server role to ends of a specifically supported services. There are services which should be relevant. So it currently is not. But maybe we have to introduce some of them as blocking or some kind of blocking services. Well, we discussed our goals. We discussed the issue if our goals are too old now, over, comes like something, but we stayed with them. So we are still stick with the technology which supports various options, not just one, which does not just one option, specifically hyped in the discussion. And we are stick with a server which can easily be adapted to different needs, different needs, different structures, different contexts. So we will stay to be a multi-purpose server. And that means we will stay at the near future with package based distributions, installations, I think. Nevertheless, of course, we are looking for what the development is. And we are looking for new or nearly new use cases. So we may adopt server or some distribution really as to new use cases, some things. I have to log on. And I think it's not so bad with our goals. If we look at the development process over the last year, we have a constantly grow of updates. The graph is the number of DNF updates per month. It may be a better figure to indicate the usage of server as a near download number. So we have been constant growth. I think we are on the right path, so to speak. Yes, we have a growing demand. And if you look at the numbers which Matthew presented yesterday, was it? Yes. With the Fedora server, we have still a good amount of users in relation to other editions and relation to other parts of the Fedora distribution. So I think at the moment, over the time being, we can do what we are doing. Well, what's going on? A constant task is docs improvement. And if you look at the commit numbers, it was the last year, yes. Compared to other editions, we are not that bad. What is it? We have the second most. No, the third most. OK. Commitments and updates of our documentation. And I think we are a good way to improve that further. But of course, if someone of you would like to write some documentation, everyone is welcome. And we have a lot of things to do. We have no lack of tasks to do. We have a long list here, as you see. But the main task for the next future is to bring up or to get up our unsupported support project because it's the main issue of our product demand. And yes, what is it? Product requirement document, yes. And it is the main section in our tentative specification. But unfortunately, we didn't get around it in the last year. And we have to review our installation media. I think the last time the installation media were reviewed is probably eight years or so ago. There were some minor changes, but after eight years, maybe it's a good idea to review the issue. There is actually no problem. I think nobody is complaining about it. But nevertheless, there are some strange issues on it which may be deleted. And there are some new ideas which you should include into it. I know server admins are strange people, including me. When someone comes near to a server, it just don't touch. Don't do anything as long as it works. And that's the way we didn't touch the installation media until now. But sometimes you have to touch. But we are dependent on our own hands to make this work, I would say, because I try hard. I had a lot of hard times to produce our new virtual machine images. And that piece called, what is it? Image factory. It was not so easy to get set up and running. And I think this installation media is much more complicated. Well, then we have some upcoming projects. The first is Fedora Server, the virtualized environment. Until now, we were too much confused. And so Fedora on hard hardware, and probably virtual machines on our own hard, Fedora-based hardware. But nowadays, there are not nowadays. Since some years, there are a lot of providers which offer not only cloud and cloud system, but also offers virtual private servers or dedicated private servers, how you will name it. And at the moment, we don't have anything to offer for those. But I got a lot of questions about how to install Fedora Server on one of these offerings. So the idea is to produce adjusted installed images, depending of the provider's own system, and to create documentation, how to do it. Anyway, I made an initial post on the mailing list. And I got a lot of response and questions and a demand to make it as fast as possible. So I think there is a field where we can gain new users, I hope so. And the other thing is server on single board computers. It's a well-discussed item in the last years. Well, we had a lot of inhibitions. What should we do with such a do-it-yourself thing in Fedora Server for production, meant for production? But we started to discuss the item and to find options to find ways how to use it in a meaningful way. So we started to discuss criteria, how to select one of the single board computers, and some simple things as a solid case. So nothing is good. Oh, it's me, no. Fire extinguished. Well, we tried to determine some selection criteria, and we tried to determine some useful applications. And we find maybe applications with a need of 24-7 operation and are less power-consumptive. So it's maybe a way to offer these services in an economical, useful way. Like backup software, backup server, or server monitor, or cluster monitor software, or cockpit gateway, such things like that, which don't need much computer power, but need to have uninterrupted operation. So it may be a useful, maybe, you have maybe a useful use case for these kind of combination. Our valuable Fedora server, such a do-it-yourself device. And the long term, we are looking to set up an economical energy efficient home server, which offers a lot of services and compensating, or can use to compensate software limitations of commercial NAS or network-attached storage with their web interface, which limits you not to be able to use a lot of fake copyabilities, which operating system of the network-attached storage provides, but you can't access it because of the web interface, and you can't override it because the web interface overrides you, overrides you as soon as you start the box again. So that's, so in short, the plannings we have discussed in our server working group. Yeah, that's it. Thank you. OK, we have a moderator, good. Just one question. I used to run Fedora server on my email machine and when I have all my stuff. And I had the problem that every six months I had to, not every, but there's a point in which the distribution goes and end of life. And it was a little, it was hard to be reinstalling in a remote environment. And eventually went and installed CentOS. But my question is, do you guys have a path of upgrading and avoiding these types of problems? Just as an example, when you upgrade OpenLDAP, the thing will not start until you do the checks of the database and all that stuff. So do you have a path for upgrade? Yeah, it's a standard, usually it's a standard upgrade path using the DNF system upgrade option. And if you wait two or three weeks, I think we have a documentation how to set up an email server on Fedora server. So it may help you to set it up in a way it doesn't interfere with update operations. I can speak to that one a bit too, Peter. I'm Adam Williamson, the Fedora QA team lead. I used to do the same thing, running a mail server. And I ran into a lot of the same issues, probably you ran into. So there tend to be just things when you upgrade a mail server where a server thing has bumped to a new version and you need to change the config files so it won't run properly as something is getting denied by SE Linux that always happened. There is a potential path there, which is that so for free IPA and Postgres, we actually have tests. Those are blocking for server. So we have release blocking tests for it. And we actually have automation, the tests that you can deploy a free IPA server and upgrade it to the next version and it will keep working as one. So in theory, if we make the new mail goal release blocking, if we decided that was an important enough requirement, we could then also do the same for that. I only have the resources to devote to doing this work for things that are release blocking. I can't really do it for all the roles that aren't release blocking. But that would probably be the best way to improve that experience because, yeah, I do know all the things you're talking about and it is painful. Thanks. You mentioned you did Ansible adjustments. What did you have to do on the other side for Ansible? I mean, what did it involve? I'm just a coordinator. We started with a model project, so to speak, to install right fly in a way that we can do it without an RPM using Ansible to install it, to install the system D infrastructure and to maintain it. And well, the guy who was working on that project was a problem. He had to delay it for some time. But he has two issues, obviously, to get Wildfly up and running with certificates. There's the current Wildfly version, which causes some troubles. And he has problems to select from the many Ansible scripts to support Wildfly, to support the one he needs. So if you could give us some advice, some support, it's very helpful, I think. But I'm not the person who does the work at the moment. That's the case we have. And if you look at the Fedora issue, it's in Pagu or Pagu, however it is pronounced. I think it's up to the speaking inside. We have an issue for that. It is 64, I think it was 60. Oh, I had it here. It is, yes, it's issue number 60, so just in case. I'll admit to not having kept up with the discussions around the Fedora server working group, but can you help me understand the difference between the work that's being done by the Fedora IoT folks and the single board ARM computer work that the server group wishes to do? I wish I could be a little louder. I couldn't understand. Oh, sorry. I heard myself through the speakers. Can you help me understand the difference between the server working groups, single board ARM computer thoughts, and the work done by something like Fedora IoT? Well, we are cooperating with the ARM, SIG, of course. And maybe our use case is different from IoT, sorry. We want to assist or replace a network-attached storage world, whereas IoT aims to a different goal. I can't describe it exactly, I must say. The only thing I decided for me, it's different. And the same is true with our virtual environment project. We are not aiming at the cloud, not aiming at cloud services, but aiming at virtual service, which I run independently from any administration service on your hardware instead of mine. So I think it's different. It's a different use case. And if someone has some time to spend, please join our working group. We are friendly, very busy, and good work people. And we need sense. If you look at our project, thanks.