fedora-server
LOGS
<@pboy:fedora.im>
18:00:15
!startmeeting fedora-server
<@meetbot:fedora.im>
18:00:17
Meeting started at 2025-03-05 18:00:15 UTC
<@meetbot:fedora.im>
18:00:17
The Meeting name is 'fedora-server '
<@pboy:fedora.im>
18:00:20
Sorry regarding the missing agenda: I just discovered that I must have hit the wrong button and the email was saved in draft instead of sent. So we have to improvise a bit today.
<@pboy:fedora.im>
18:00:30
!topic Welcome / roll call
<@aggraxis:fedora.im>
18:00:35
!hi
<@zodbot:fedora.im>
18:00:37
Paul Maconi (aggraxis) - he / him / his
<@pboy:fedora.im>
18:00:39
As usual, let's wait a moment for everybody to show up.
<@pboy:fedora.im>
18:00:39
I'll post the agenda in 2-3 minutes.
<@eseyman:fedora.im>
18:00:43
!hello
<@zodbot:fedora.im>
18:00:44
Emmanuel Seyman (eseyman) - he / him / his
<@eseyman:fedora.im>
18:00:55
Hello, fellow kids!
<@pboy:fedora.im>
18:01:32
Welcome Paul, Welcome Emmanuel
<@pboy:fedora.im>
18:04:06
Well, I think we start now and hope, John and Steve will participate soon.
<@pboy:fedora.im>
18:04:21
!topic Agenda
<@pboy:fedora.im>
18:04:31
!info Follow-up actions & announcements
<@pboy:fedora.im>
18:04:39
!info Scheduled server podcast for March 11
<@pboy:fedora.im>
18:04:49
!info Ansible assisted installation and configuration of NFS service
<@pboy:fedora.im>
18:05:00
!info F43 Change proposal: Disabling support of building OpenSSL engines
<@pboy:fedora.im>
18:05:07
!info Open Floor
<@pboy:fedora.im>
18:05:20
Anything to add?
<@pboy:fedora.im>
18:05:48
Obviously not :-)
<@pboy:fedora.im>
18:05:59
!topic 1. Follow-up actions & announcements
<@pboy:fedora.im>
18:06:11
Regarding the action, nothing new. See
<@pboy:fedora.im>
18:06:20
<@pboy:fedora.im>
18:06:35
And no announcement from me.
<@pboy:fedora.im>
18:07:30
I suppose no announcement at the moment.
<@pboy:fedora.im>
18:07:40
!topic 2. Scheduled Server podcast for March 11
<@pboy:fedora.im>
18:07:59
No tracking issue yet
<@pboy:fedora.im>
18:08:36
a) Who will participate
<@pboy:fedora.im>
18:08:36
b) What message do we want to get across?
<@pboy:fedora.im>
18:08:36
The questions are
<@pboy:fedora.im>
18:09:28
The recording and sending tine is not determined yet. Usually it is in the US east evening.
<@eseyman:fedora.im>
18:10:29
While I don't see myself participating, I'm always in favour of the Server SIG being on the Fedora Podcast
<@pboy:fedora.im>
18:10:44
++1
<@pboy:fedora.im>
18:10:54
That was my intention, too.
<@pboy:fedora.im>
18:12:04
My idea is to talk about some results of our server poll, talk a bit about a homelab spin-off and maybe about our issues with getting some Ansible playbooks working.
<@pboy:fedora.im>
18:13:12
Any comment / additional ideas?
<@eseyman:fedora.im>
18:13:48
I suspect the poll should be the main subject
<@pboy:fedora.im>
18:14:30
Yes, indeed. But not to much. We should have something new left for Fedora Magazine.
<@eseyman:fedora.im>
18:14:44
Perhaps add a mention that we are always looking for new people to help us
<@pboy:fedora.im>
18:15:34
Yes. I will talk about that regarding homelab spin-off and Ansible.
<@pboy:fedora.im>
18:16:18
We should make is specific. So anybody can see what exactly should be done.
<@pboy:fedora.im>
18:16:31
At least for the next months or so.
<@pboy:fedora.im>
18:17:56
I assume everything has been said at the moment?
<@pboy:fedora.im>
18:18:23
!topic 3. Ansible assisted installation and configuration of NFS service
<@pboy:fedora.im>
18:18:42
<@pboy:fedora.im>
18:19:31
We are missing John today. Emmanuel Seyman Could you manage to spent some time on this topic?
<@eseyman:fedora.im>
18:20:13
I will try to spend some time on it this week
<@eseyman:fedora.im>
18:20:40
FTR, I have my NPO's annual meeting this saturday and I am quite busy these days
<@pboy:fedora.im>
18:21:27
OK, so I suppose we should re-schedule this topic in 14 days! or better in 3 weeks?
<@eseyman:fedora.im>
18:23:00
Let's try 14
<@eseyman:fedora.im>
18:23:27
Note that I will probably not be at the meeting next week so 14 is actually the bare minimum
<@pboy:fedora.im>
18:23:52
OK., let's re-schedule in 14 days.
<@pboy:fedora.im>
18:24:06
!topic 4. F43 Change proposal: Disabling support of building OpenSSL engines
<@pboy:fedora.im>
18:24:21
<@pboy:fedora.im>
18:24:37
It's not urgent. We just have to be careful that the renewal junkies don't cripple our IPA server with the update. Some are in too much of a hurry and disregard the existing use of Fedora.
<@pboy:fedora.im>
18:25:13
I have already objected to the plan as it currently stands.
<@pboy:fedora.im>
18:26:38
Any comment to the mailing list thread?
<@eseyman:fedora.im>
18:27:23
I have read the whole thing with interest
<@eseyman:fedora.im>
18:28:11
I'm still hoping that bind-dydnb-ldap will work without OpenSSL engines in time for F43
<@pboy:fedora.im>
18:28:55
Yes, but that is unclear according to Alexander.
<@eseyman:fedora.im>
18:29:58
Perhaps I can give him a hand
<@eseyman:fedora.im>
18:30:19
Not that I know anything about Bind's API...
<@pboy:fedora.im>
18:30:35
Yeah, w/o secure DNS IPA doesn't work without adjustments. Upstream is working on that.
<@pboy:fedora.im>
18:31:14
Emmanuel Seyman: As our expert for change proposals: Can you put this on your monitor list?
<@eseyman:fedora.im>
18:31:31
I will
<@pboy:fedora.im>
18:31:40
Thanks.
<@pboy:fedora.im>
18:31:49
Let's switch then
<@pboy:fedora.im>
18:32:01
!topic 5. Open Floor
<@pboy:fedora.im>
18:33:05
A while ago, I found an interesting graphic about the development of the use of, among other things, servers. I hope I can find it quickly.
<@pboy:fedora.im>
18:34:21
Found it.
<@pboy:fedora.im>
18:34:33
<@pboy:fedora.im>
18:34:49
It is from CoreOS discussions.
<@pboy:fedora.im>
18:35:08
We should have a closer look at the countme statistics.
<@aggraxis:fedora.im>
18:37:04
Well, I'm not surprised to see the Cloud image take off like wildfire as people discover it, especially if you're making VMs on a hypervisor that supports cloud-init.
<@aggraxis:fedora.im>
18:38:05
Even for RHEL systems, I cook a VM one time from a pre-fab kickstart, layer in cloud-init and some basic security changes via %post, then seal the image with some nice stuff in the cloud-init blocks in our production Proxmox clusters.
<@aggraxis:fedora.im>
18:38:29
That first VM takes 12 minutes to cook itself once a quarter, but subsequent clones are up within minutes with almost no human intervention.
<@aggraxis:fedora.im>
18:39:13
Fedora Cloud image on Proxmox is even easier than the guide I put together for using the regular server image. Make a VM, ingest disk, set up the hardware and cloud-init bits, convert to template.
<@aggraxis:fedora.im>
18:39:42
Each clone gets its hostname set as the name of the VM. You pre-seed an account and pw and/or ssh key, and you're off to the races in seconds.
<@pboy:fedora.im>
18:40:03
Yes, it is much easier than buying or renting a server.
<@aggraxis:fedora.im>
18:40:44
Well, even consider places like Digital Ocean or other VPS providers. You don't have to do much to the Fedora images out of the box to get going quickly.
<@aggraxis:fedora.im>
18:40:49
It just... works.
<@pboy:fedora.im>
18:41:35
But is cloud computing really cheaper or at least more cost-effective? Based on some cursory research, I doubt it.
<@aggraxis:fedora.im>
18:41:56
The cloud image has less to do with cloud computing and more with a way of provisioning.
<@aggraxis:fedora.im>
18:42:40
It wakes the system up, configures the network ,hostname, credentials, generates new SSH keys, I think some plugin variant of cloud-init can resize a volume if need be, and can even trigger a package update on boot if desired.
<@aggraxis:fedora.im>
18:42:59
It's almost like 'sysprepping' a Windows system.
<@eseyman:fedora.im>
18:43:29
Oh, I'm certain you can, on first boot, grow your image to whatever size the volume is
<@aggraxis:fedora.im>
18:43:49
It is *VERY* nice to work with once you get a handle on what's going on.
<@aggraxis:fedora.im>
18:44:10
Like I said, I demonstrated the capability to my customer, and he let me rebuild our template systems based on it.
<@pboy:fedora.im>
18:44:35
By cloud computing, I mean running the server in longterm production in a cloud system.
<@aggraxis:fedora.im>
18:46:08
We stopped making a distinction between local virtualization or what people started calling 'the cloud'. We either have the local private cloud, a public cloud, or a hybrid implementation between the two. Once we got away from VMware in particular and started using something that played nice with cloud-init, it's all just fluffy cloud. :)
<@pboy:fedora.im>
18:47:54
Yes, cloud init is a relief if you set up and take down servers multiple times a month. But if you only use it once every few months,....
<@pboy:fedora.im>
18:48:30
first boot is very elaborate, indeed.
<@aggraxis:fedora.im>
18:49:16
For us, not so much. Aside from some key "named systems", we start from a common baseline concept and then build through automation. Even stuff we've had going for years.
<@aggraxis:fedora.im>
18:49:43
Either way, I'm thrilled to see that kind of data out there and what folks are doing with Fedora.
<@pboy:fedora.im>
18:50:53
Indeed, yes, that's interesting. We should have a closer look into the Server related data. I hope, Emmanuel and me can do that for our Flock talk (if our CfP gets accepted).
<@pboy:fedora.im>
18:51:43
I think, that's it for today. Or is anything else to discuss?
<@aggraxis:fedora.im>
18:51:58
Just thanks for doing what you guys do :)
<@pboy:fedora.im>
18:52:33
Oh, yes, thanks!
<@pboy:fedora.im>
18:53:12
Well, i'll close now
<@pboy:fedora.im>
18:53:15
3
<@pboy:fedora.im>
18:53:25
2
<@pboy:fedora.im>
18:53:41
1
<@pboy:fedora.im>
18:53:49
!endmeeting