<@phsmoura:fedora.im>
19:00:51
!startmeeting Fedora Infrastructure Ops Daily Standup Meeting
<@meetbot:fedora.im>
19:00:52
Meeting started at 2024-07-10 19:00:51 UTC
<@meetbot:fedora.im>
19:00:52
The Meeting name is 'Fedora Infrastructure Ops Daily Standup Meeting'
<@phsmoura:fedora.im>
19:00:56
!meetingname fedora_infrastructure_ops_daily_standup_meeting
<@phsmoura:fedora.im>
19:00:56
!info reminder: speak up if you want to work on a ticket!
<@phsmoura:fedora.im>
19:00:56
!info agenda is at https://board.net/p/fedora-infra-daily
<@phsmoura:fedora.im>
19:00:56
!info meeting is 30 minutes MAX. At the end of 30, its stops
<@phsmoura:fedora.im>
19:00:56
!chair nirik smooge phsmoura
<@meetbot:fedora.im>
19:00:57
The Meeting Name is now fedora_infrastructure_ops_daily_standup_meeting
<@phsmoura:fedora.im>
19:01:00
hello
<@nirik:matrix.scrye.com>
19:01:07
morning
<@phsmoura:fedora.im>
19:04:30
we dont have new issues
<@phsmoura:fedora.im>
19:04:32
!topic Planning, Upcoming work and Open floor
<@nirik:matrix.scrye.com>
19:04:53
cool.
<@nirik:matrix.scrye.com>
19:05:08
!info outage / reboot / updates later today at 21UTC (2 hours or so)
<@nirik:matrix.scrye.com>
19:05:21
!info mass rebuild starts next wed
<@markrosenbaum:fedora.im>
19:05:38
Heyo
<@nirik:matrix.scrye.com>
19:07:28
hey Mark Rosenbaum
<@nirik:matrix.scrye.com>
19:07:40
I don't think I had much else today...
<@phsmoura:fedora.im>
19:07:46
nirik: I started looking at this one
<@phsmoura:fedora.im>
19:07:50
!ticket 11715
<@zodbot:fedora.im>
19:07:51
<@zodbot:fedora.im>
19:07:51
**fedora-infrastructure #11715** (https://pagure.io/fedora-infrastructure/issue/11715):**Move from iptables to firewalld**
<@zodbot:fedora.im>
19:07:51
● **Opened:** 6 months ago by kevin
<@zodbot:fedora.im>
19:07:51
● **Assignee:** phsmoura
<@zodbot:fedora.im>
19:07:51
● **Last Updated:** Never
<@nirik:matrix.scrye.com>
19:08:07
cool. :)
<@nirik:matrix.scrye.com>
19:08:35
lots to investigate there...
<@phsmoura:fedora.im>
19:09:29
any tips how I could test it? Im thinking in creating vagrant VMs and do it locally 1st using those iptables templates
<@nirik:matrix.scrye.com>
19:10:45
sure, testing things in a vm is good. The big thing to try and figure out is how we want to manage things with ansible. We don't want to call firewalld-cmd all the time, ideally we could template it's xml settings or have a ansible module interface to it or something.
<@nirik:matrix.scrye.com>
19:11:04
I've not looked at firewalld in a while, so I am not sure what it's capable of these days.
<@phsmoura:fedora.im>
19:11:47
ok, Ill explore that asible module
<@nirik:matrix.scrye.com>
19:12:15
sounds good.
<@markrosenbaum:fedora.im>
19:13:56
Not sure if it overcomplicates it but if your looking to quickly test out the interactions between a few hosts you could probably use GNS3
<@phsmoura:fedora.im>
19:14:16
GNS3?
<@markrosenbaum:fedora.im>
19:14:33
https://gns3.com/
<@nirik:matrix.scrye.com>
19:15:18
Might be useful at some point, but initial stuff is more 'what can this do and how can we manage it'
<@markrosenbaum:fedora.im>
19:15:40
Got it
<@nirik:matrix.scrye.com>
19:15:57
but interesting thing. thanks for pointing to it.
<@phsmoura:fedora.im>
19:16:41
thanks :) So the rules will be a bit different wejust need to understand how we are going to use it?
<@phsmoura:fedora.im>
19:17:10
those templates can be used as reference?
<@nirik:matrix.scrye.com>
19:17:14
Rules are probibly mostly going to be the same (but we might adjust some), but mostly we need to figure out how to best manage it with ansible.
<@nirik:matrix.scrye.com>
19:17:28
sure, can use the extisting templates as a ref
<@phsmoura:fedora.im>
19:17:50
ok thanks :)
<@phsmoura:fedora.im>
19:18:06
also dont have anything else
<@phsmoura:fedora.im>
19:21:04
ok, lets go back then
<@phsmoura:fedora.im>
19:21:45
thanks nirik and Mark Rosenbaum for joining today
<@phsmoura:fedora.im>
19:21:48
!endmeeting