fedrtc.org -> infrastructure?
by Daniel Pocock
Hi all,
At some point, it would be good to see fedrtc.org migrate to Fedora
infrastructure and use the fedoraproject.org domain
I'd be happy to submit the full request for resources[1] but I just want
to see if there is any initial comment on it. Here is a list of what is
involved:
- it uses a PostgreSQL database schema[2]
- it requires some DNS entries (SRV and NAPTR), examples[3]
- it needs a TLS cert for fedoraproject.org on the host(s) where it runs
- it has static HTTP content and PHP that is currently hosted with all
but one problem[4] on a RHEL7 httpd. Content is in Github[5], it could
be presented as an RPM if necessary.
- all packages are in EPEL7, except:
cajun-json in EPEL6, in testing for EPEL7
resiprocate in Fedora, builds from SRPM on RHEL7
- the SIP proxy is a single daemon, managed by systemctl. All settings
in a single file, /etc/repro/repro.config
- the TURN server process is also a single daemon, managed by systemctl.
All settings in a single file, /etc/reTurn/reTurnServer.config
Just to clarify the scope of this: it is not a full telephony service
like Asterisk, just a SIP proxy and TURN server. There is no persistent
state information (as there would be for voicemail, email service, etc)
and no customized routing.
Ongoing maintenance requirements:
- TLS certificate renewals
- monitoring the ports
- package updates from time to time
It currently runs on a lab machine, I'd be happy to arrange SSH access
to the Fedora Infrastructure team to see exactly what is involved and
verify that it is manageable.
Regards,
Daniel
1. https://fedoraproject.org/wiki/Request_For_Resources
2.
https://github.com/resiprocate/resiprocate/blob/master/repro/create_postg...
3. http://rtcquickstart.org/guide/multi/dns.html
4. https://bugzilla.redhat.com/show_bug.cgi?id=1222649
5. https://github.com/opentelecoms-org/fedrtc-org
7 years, 7 months
July status update for Fedora Infrastructure Apprentices
by Kevin Fenzi
Greetings.
You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
infrastructure list).
Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.
https://fedoraproject.org/wiki/Infrastructure_Apprentice
At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going for
you.
I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help us
make the apprentice program more useful.
0. Whats your fedora account system login?
1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?
2. Has it helped you decide any area you wish to focus on or contribute
to more?
3. Have you looked at or been able to work on any of the fi-apprentice
'easyfix' tickets?
https://fedorahosted.org/fedora-infrastructure/report/14
4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?
5. Is there any help or communication or ideas you have that would help
you do any of the above?
6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?
7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?
8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby
9. What was the last game you played?
Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.
Any folks I do not hear from in the next week will be removed from the
group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).
Thanks, and looking forward to your feedback!
kevin
7 years, 9 months
Freeze break request: fix easyfix [easyfix]
by Kevin Fenzi
So, since the move to sundries as the backend for building various
static sites, easyfix hasn't been updating.
The cause is a misnamed directory in rsyncd.conf.
I tested the fix below in staging and it seemed to work fine there.
I'd like to apply this and run the sundries playbook.
+1s?
kevin
--
diff --git a/roles/rsyncd/files/rsyncd.conf.sundries b/roles/rsyncd/files/rsyncd.conf.sundries
index 1b9dec5..39184de 100644
--- a/roles/rsyncd/files/rsyncd.conf.sundries
+++ b/roles/rsyncd/files/rsyncd.conf.sundries
@@ -40,7 +40,7 @@ hosts allow = 10.5.126.0/255.255.255.0 192.168.0.0/255.255.0.0
[gather-easyfix]
comment = Gather easyfix available in Fedora
-path = /srv/web/gather-easyfix
+path = /srv/web/easyfix
uid = root
gid = root
read only = yes
7 years, 10 months
Jenkins in new cloud - status update
by Mikolaj Izdebski
Overall status: most of things are configured and working. New Jenkins
should be ready for data migration from old instance. I've migrated two
projects for now and they seem to be working.
Deployment details: There are: 1 master and 3 slaves (workers) running
in the new cloud. All instances are of type "m1.small" (1 CPU, 2 GB
RAM, 20 GB disk).
master:
jenkins.fedorainfracloud.org (Fedora 22)
slaves:
jenkins-slave-el6.fedorainfracloud.org (Centos 6.6)
jenkins-slave-el7.fedorainfracloud.org (RHEL 7.1)
jenkins-slave-f22.fedorainfracloud.org (Fedora 22)
Some notes or questions, in random order:
Slaves have public IP assigned. It's not needed by Jenkins itself,
but I think it is required to be able to manage them through ansible.
Master is running official jenkins package from Fedora 22, with
several core plugins also from Fedora. Plugins which were not
available in Fedora are packaged in Copr repo and installed as RPMs
too. Packages in Copr are just wrappers around upstream binaries -
they are not built from source in Copr.
Jenknis runs as unprivileged user, so it can't listen on port 80 - it
listens on port 8080. Old Jenkins was running httpd proxy, which
forwarded incoming requests from port 80 to 8080. New Jenkins
forwards ports using netfilter (aka iptables). Was there any other
reason for running httpd proxy?
Only members of sysadmin-jenkins group have admin access through web
interface. Should sysadmin-main be added there too?
Subversion plugin is currently disabled due to unresolved problem.
Projects using subversion SCM (if any) won't work until this is fixed.
Slaves have the same set of extra packages installed as in the old
cloud. Like in the old Jenkins instance, jenkins user is member of
mock group, which opens possibility for arbitrary code execution on
any of Jenkins hosts (on slaves as root, on master as jenkins user)
for anyone with write access to any project. I'm not saying it's
necessairly a problem, but I wanted to point it out clearly.
Current Jenkins master doesn't have persistent storage, but I would
like to add it when moving to production.
Any questions or comments?
--
Mikolaj Izdebski
Software Engineer, Red Hat
IRC: mizdebsk
7 years, 10 months
Freeze break request: s3sync
by Adrian Reber
This is a try to fix the s3sync on mm-backend01. I have tested the
script and it successfully syncs the content to S3. I have, however, not
tested if the ansible rules work. Please have a look at following patch
and if the ansible rules are correct.
In addition to this patch it is necessary to install the new
mirrormanager2 release (0.4.2) in prod. It has now changes except an
additional subpackage mirrormanager2-client which provides report_mirror
which is run after the sync to S3.
Date: Thu, 30 Jul 2015 13:47:48 +0000
Subject: [PATCH] Fix s3sync and start it via cron.
This changes the s3sync setup at multiple places:
* The s3sync script was using wrong paths which are now corrected
* After the sync report_mirror was started which is now installed
* The necessary report_mirror files are installed
* The s3sync script is now running from cron instead as a service
* Before touching any files fedmsg is queried to see if new files
are available for syncing
* logrotate has been adapted to the new setup
---
roles/s3-mirror/files/s3-mirror.init | 77 --------------------
roles/s3-mirror/files/s3-mirror.logrotate | 3 -
roles/s3-mirror/files/s3sync | 100 +++++++++++++-------------
roles/s3-mirror/tasks/main.yml | 19 ++++-
roles/s3-mirror/templates/report_mirror.conf | 60 +++++++++++++++
5 files changed, 126 insertions(+), 133 deletions(-)
delete mode 100644 roles/s3-mirror/files/s3-mirror.init
create mode 100644 roles/s3-mirror/templates/report_mirror.conf
diff --git a/roles/s3-mirror/files/s3-mirror.init b/roles/s3-mirror/files/s3-mirror.init
deleted file mode 100644
index 59dbb39..0000000
--- a/roles/s3-mirror/files/s3-mirror.init
+++ /dev/null
@@ -1,77 +0,0 @@
-#!/bin/sh
-#
-# s3-mirror - sync content to S3
-#
-# chkconfig: - 99 99
-# description: sync content to S3
-
-# http://fedoraproject.org/wiki/FCNewInit/Initscripts
-### BEGIN INIT INFO
-# Provides:
-# Required-Start: $network $named $remote_fs
-# Required-Stop:
-# Should-Start:
-# Should-Stop:
-# Default-Start:
-# Default-Stop:
-# Short-Description:
-# Description:
-### END INIT INFO
-
-# Source function library.
-. /etc/rc.d/init.d/functions
-
-exec="/usr/local/bin/s3sync"
-prog=${exec##*/}
-
-lockfile=/var/lock/subsys/$prog
-pidfile=/var/run/s3-mirror/pid
-
-start() {
- echo -n $"Starting $prog: "
- mkdir -p /var/run/s3-mirror
- chown -R s3-mirror:s3-mirror /var/run/s3-mirror
- daemon --user s3-mirror --pidfile $pidfile $exec &
- retval=$?
- echo
- [ $retval -eq 0 ] && touch $lockfile
- return $retval
-}
-
-stop() {
- echo -n $"Stopping $prog: "
- killproc -p $pidfile
- retval=$?
- echo
- [ $retval -eq 0 ] && rm -f $lockfile
- return $retval
-}
-
-restart() {
- stop
- start
-}
-
-case "$1" in
- start|stop|restart)
- $1
- ;;
- force-reload)
- restart
- ;;
- status)
- status $prog
- ;;
- try-restart|condrestart)
- if status $prog >/dev/null ; then
- restart
- fi
- ;;
- reload)
- action $"Service ${0##*/} does not support the reload action: " /bin/false
- exit 3
- ;;
- *)
- echo $"Usage: $0 {start|stop|status|restart|try-restart|force-reload}"
- exit 2
-esac
diff --git a/roles/s3-mirror/files/s3-mirror.logrotate b/roles/s3-mirror/files/s3-mirror.logrotate
index 12e66aa..7549028 100644
--- a/roles/s3-mirror/files/s3-mirror.logrotate
+++ b/roles/s3-mirror/files/s3-mirror.logrotate
@@ -9,7 +9,4 @@
compressext .bz2
dateext
copytruncate
- postrotate
- /bin/kill -HUP `cat /var/run/s3-mirror/pid 2>/dev/null` 2>/dev/null || true
- endscript
}
diff --git a/roles/s3-mirror/files/s3sync b/roles/s3-mirror/files/s3sync
index 6d0c552..f8d0413 100755
--- a/roles/s3-mirror/files/s3sync
+++ b/roles/s3-mirror/files/s3sync
@@ -1,16 +1,16 @@
#!/bin/bash
-pidfile=/var/run/s3-mirror/pid
logfile="/var/log/s3-mirror/s3sync.log"
+tree="/srv/pub/"
+s3cmd=/usr/bin/s3cmd
+curdate=`date +%s`
-trap sighup_handler HUP
-trap "rm -f ${pidfile}" QUIT EXIT INT TERM
-
-function sighup_handler()
-{
- exec 1>>${logfile} 2>&1
-}
+if [ ! -d ${tree} ]; then
+ echo "Specified root of the directory tree (${tree}) does not exist. Exiting." | tee ${logfile}
+ exit 1
+fi
+exec 1>>${logfile} 2>&1
function newer()
{
@@ -20,16 +20,6 @@ function newer()
return 1
}
-function repeat()
-{
- while :; do
- $1
- /bin/sleep $((${RANDOM} % 300))
- done
-}
-
-s3cmd=/usr/bin/s3cmd
-
S3CMD_ARGS="sync \
--verbose \
--preserve \
@@ -44,41 +34,51 @@ S3CMD_ARGS="sync \
content="epel"
targets="s3-mirror-us-east-1 s3-mirror-us-west-1 s3-mirror-us-west-2 s3-mirror-eu-west-1 s3-mirror-ap-northeast-1"
+report=0
-function parallel_sync_full()
-{
- report=0
- for c in ${content}; do
- if $(newer /pub/${c}/fullfilelist /var/lib/s3-mirror/${c}-fullfilelist) ; then
- echo "=============================================================="
- echo -n "Starting at "
- date
- time $s3cmd $S3CMD_ARGS \
- --cache-file /var/lib/s3-mirror/${c}.cache \
- --delete-removed \
- --delete-after \
- --add-destination s3://s3-mirror-us-west-1.fedoraproject.org/pub/${c}/ \
- --add-destination s3://s3-mirror-us-west-2.fedoraproject.org/pub/${c}/ \
- --add-destination s3://s3-mirror-eu-west-1.fedoraproject.org/pub/${c}/ \
- --add-destination s3://s3-mirror-ap-northeast-1.fedoraproject.org/pub/${c}/ \
- /pub/${c}/ s3://s3-mirror-us-east-1.fedoraproject.org/pub/${c}/
- report=1
- cp -a /pub/${c}/fullfilelist /var/lib/s3-mirror/${c}-fullfilelist
- fi
- done
+if [ -e /var/run/s3-mirror/lastrun ]; then
+ . /var/run/s3-mirror/lastrun
+else
+ # 48 hours -> 172800 seconds
+ let lastrun=curdate-172800
+fi
+
+let delta=curdate-lastrun
- if [ ${report} -ne 0 ] ; then
- for target in ${targets} ; do
- report_mirror -c /etc/mirrormanager-client/report_mirror_${target}.conf --exclude-from /usr/local/etc/s3-mirror-excludes.txt
- done
- echo -n "Ending at "
+# hardcoded to epel only '-e'
+/usr/local/bin/last-sync -d ${delta} -e
+
+if [ "$?" -ne "0" ]; then
+ # no changes since the last sync
+ # abort
+ exit 0
+fi
+
+for c in ${content}; do
+ if $(newer ${tree}/${c}/fullfilelist /var/lib/s3-mirror/${c}-fullfilelist) ; then
+ echo "=============================================================="
+ echo -n "Starting at "
date
+ time $s3cmd $S3CMD_ARGS \
+ --cache-file /var/lib/s3-mirror/${c}.cache \
+ --delete-removed \
+ --delete-after \
+ --add-destination s3://s3-mirror-us-west-1.fedoraproject.org/pub/${c}/ \
+ --add-destination s3://s3-mirror-us-west-2.fedoraproject.org/pub/${c}/ \
+ --add-destination s3://s3-mirror-eu-west-1.fedoraproject.org/pub/${c}/ \
+ --add-destination s3://s3-mirror-ap-northeast-1.fedoraproject.org/pub/${c}/ \
+ ${tree}/${c}/ s3://s3-mirror-us-east-1.fedoraproject.org/pub/${c}/
+ report=1
+ cp -a ${tree}/${c}/fullfilelist /var/lib/s3-mirror/${c}-fullfilelist
+ echo "lastrun=${curdate}" > /var/run/s3-mirror/lastrun
fi
-}
+done
-# send stdout/stderr to logfile
-sighup_handler
-mkdir -p $(dirname ${pidfile})
-echo "$$" > ${pidfile}
-repeat parallel_sync_full
+if [ ${report} -ne 0 ] ; then
+ for target in ${targets} ; do
+ report_mirror -c /etc/mirrormanager-client/report_mirror_${target}.conf --exclude-from /usr/local/etc/s3-mirror-excludes.txt
+ done
+ echo -n "Ending at "
+ date
+fi
diff --git a/roles/s3-mirror/tasks/main.yml b/roles/s3-mirror/tasks/main.yml
index 7900457..3da4b8d 100644
--- a/roles/s3-mirror/tasks/main.yml
+++ b/roles/s3-mirror/tasks/main.yml
@@ -11,6 +11,16 @@
yum: pkg={{ item }} state=installed
with_items:
- s3cmd
+ - mirrormanager2-client
+
+- name: Create report_mirror config files
+ template: src=report_mirror.conf dest=/etc/mirrormanager-client/report_mirror_{{ item }} owner=s3-mirror group=s3-mirror mode=0400
+ with_items:
+ - s3-mirror-us-east-1
+ - s3-mirror-us-west-1
+ - s3-mirror-us-west-2
+ - s3-mirror-eu-west-1
+ - s3-mirror-ap-northeast-1
- name: Create needed directories
file: path={{item}} owner=s3-mirror group=s3-mirror state=directory mode=0755
@@ -33,12 +43,15 @@
- name: s3-mirror logrotate
copy: src=s3-mirror.logrotate dest=/etc/logrotate.d/s3-mirror owner=s3-mirror group=s3-mirror mode=0644
-- name: s3-mirror init.d
- copy: src=s3-mirror.init dest=/etc/init.d/s3-mirror owner=s3-mirror group=s3-mirror mode=0755
-
- name: s3sync-logs
copy: src=s3sync-logs dest=/usr/local/bin/s3sync-logs owner=s3-mirror group=s3-mirror mode=0755
+- name: s3sync cron
+ cron: name="s3sync" minute="3,18,33,48" user="s3-mirror"
+ job="/usr/local/bin/lock-wrapper s3sync /usr/local/bin/s3sync"
+ cron_file=s3sync
+ when: env != 'staging'
+
- name: s3sync-logs cron
cron: name="s3sync-logs" hour="0" user="root"
job='/usr/local/bin/lock-wrapper s3sync-logs "/bin/sleep $((${RANDOM} \% 300)); /usr/local/bin/s3sync-logs >> /var/log/s3-mirror-logs/s3sync-logs.log 2>&1" | /usr/local/bin/nag-once s3mirror-logs 12h 2>&1'
diff --git a/roles/s3-mirror/templates/report_mirror.conf b/roles/s3-mirror/templates/report_mirror.conf
new file mode 100644
index 0000000..e51e1d9
--- /dev/null
+++ b/roles/s3-mirror/templates/report_mirror.conf
@@ -0,0 +1,60 @@
+[global]
+# if enabled=0, no data is sent to the database
+enabled=1
+# server= is the URL to the MirrorManager XML-RPC interface
+server=https://admin.fedoraproject.org/mirrormanager/xmlrpc
+
+
+[site]
+# if enabled=0, no data about this site is sent to the database
+enabled=1
+# Name and Password fields need to match the Site name and password
+# fields you entered for your Site in the MirrorManager database at
+# https://admin.fedoraproject.org/mirrormanager
+name={{ s3_mirror_report_mirror_site }}
+password={{ s3_mirror_report_mirror_pw }}
+
+[host]
+# if enabled=0, no data about this host is sent to the database
+enabled=1
+# Name field need to match the Host name field you entered for your
+# Host in the MirrorManager database at
+# https://admin.fedoraproject.org/mirrormanager
+name={{ item }}.fedoraproject.org
+# if user_active=0, no data about this category is given to the public
+# This can be used to toggle between serving and not serving data,
+# such enabled during the nighttime (when you have more idle bandwidth
+# available) and disabled during the daytime.
+# By not specifying user_active, the database will not be updated.
+# user_active=1
+
+[stats]
+# Stats are only sent when run with the -s option
+# and when this section is enabled.
+# This feature is not presently implemented
+enabled=0
+apache=/var/log/httpd/access_log
+vsftpd=/var/log/vsftpd.log
+# remember to enable log file and transfer logging in rsyncd.conf
+rsyncd=/var/log/rsyncd.log
+
+
+# Content Categories
+# These sections match the Categories for content tracked by MirrorManager.
+#
+# enabled=1 means information about this category will be sent to the database.
+# enabled=0, no data about this host is sent to the database. If the
+# database already has information for you for this Category, it will
+# remain unchanged. This can be used to update the database after you
+# have manually synced some infrequently-updated content, such as
+# historical releases.
+#
+# path= is the path on your local disk to the top-level directory for this Category
+
+[Fedora Linux]
+enabled=0
+path=/srv/pub/fedora/linux
+
+[Fedora EPEL]
+enabled=1
+path=/srv/pub/epel
--
1.7.2.1
7 years, 10 months
Freeze break request: minor change to host ordering priorities
by Peter Robinson
When building ppc builders which reside on qa.fedoraproject.org we get
the wrong /etc/hosts file because the generic ansible_domain executes
before the more specific due to task host_group option.
In general I believe if we have something explicitly in a host_group
we'd want to prioritise that over a generic sub domain.
Peter
diff --git a/roles/hosts/tasks/main.yml b/roles/hosts/tasks/main.yml
index faeccb9..c74827e 100644
--- a/roles/hosts/tasks/main.yml
+++ b/roles/hosts/tasks/main.yml
@@ -16,9 +16,9 @@
- "{{ inventory_hostname }}-hosts"
- "{{ ansible_fqdn }}-hosts"
- "{{ ansible_hostname }}-hosts"
+ - "{{ host_group }}-hosts"
- "{{ ansible_domain }}-hosts"
- "{{ datacenter }}-hosts"
- - "{{ host_group }}-hosts"
skip: true
tags:
- config
7 years, 10 months
[release] pagure: 0.1.20
by Pierre-Yves Chibon
Hi everyone,
As announce and discussed I just cut a new release of pagure: 0.1.20
Here is its changelog:
* Wed Jul 29 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.20
- Update to 0.1.20
- Include the tags in the JSON representation of a project
- Add the ability to open a pull-request from a git repo not hosted on pagure
- Fix pagination when browsing the list of commits
- Fix the fork button when viewing the Settings of a project
- Adjust the example apache configuration file
- Add a favicon with pagure's logo
- Fix asynchronous commentting on pull-requests
- Start working on some documentation on how to install pagure
- Do no flash messages when a comment is submitted via javascript (ie: async)
- Do not blink the tittle of the page if the page is already on focus
- Retrieve ssh key from FAS and set it up in pagure if none is currently set-up
- Fix anchors for comments on the pull-request pages
- Fix checking the merge status of a PR when user is not logged in
This is currently running fine in stg, I will play a little more with it and if
everything goes fine, push to prod tomorrow.
Please test stg as well and let me know if anything breaks :)
Thanks,
Pierre
7 years, 10 months
[release] MirrorManager2: 0.4.2
by Pierre-Yves Chibon
Good morning everyone,
I just released a new version of MirrorManager2: 0.4.2
Here is its changelog:
* Thu Jul 30 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.4.2-1
- Update to 0.4.2
- Create the -client subpackage containing the report_mirror script and
configuration file (Adrian Reber)
Adrian needed this release for the s3sync setup.
Currently the rpm is only in the Fedora infrastructure-testing repository.
Pierre
7 years, 10 months
Plan for tomorrow's Fedora Infrastructure meeting - 2015-07-30
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2015-07-30 at 18:00 UTC in #fedora-meeting on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
fedora-infrastructure-meeting-next is the document.
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
kevin
--
= Introduction =
This shared document is for the next fedora infrastructure meeting.
We will use it over the week before the meeting to gather status and info and
discussion items and so forth, then use it in the irc meeting to transfer
information to the meetbot logs.
= Meeting start stuff =
#startmeeting Infrastructure (2015-07-30)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson
#topic New folks introductions / Apprentice feedback
#topic GSoC student update - kushal
= Status / information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need to discuss)
(Please use #info <the thing> - your name)
#topic announcements and information
#info old cloud to new cloud migration moving along, hopefully done by friday - kevin/patrick
#info ibiblio05 installed and ready for service - kevin
#info virthost19/20/21/22 installed and ready for service - smooge
#info smooge onsite at phx2
#info bapp02/app01.stg now gone. Down to just 9 hosts in puppet - kevin
#info We are now in Fedora 23 Alpha freeze! - kevin
#info
= Things we should discuss =
We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus or decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use #topic your discussion topic - your username)
#topic TRAC tickets review - p_klos
There are many tickets left alone for months with comments that let thin there are done/inactual.
Examples:
https://fedorahosted.org/fedora-infrastructure/ticket/1684
https://fedorahosted.org/fedora-infrastructure/ticket/1180
https://fedorahosted.org/fedora-infrastructure/ticket/3627
Maybe we should review all open tickets one by one and decide whether we should do something or just close the ticket?
#topic Idea: We could create official Fedoraproject Docker repo - p_klos
I found some Fedora cloud repo on Docker Hub but we don't have any official FedoraProject repo with Docker images. Maybe we could create one and put there Docker-ready images? I.E. Latest, alpha, server minimal, server freeipa, other options available to "click" in anaconda during installation?
= Learn about some application or setup in infrastructure =
(This section, each week we get 1 person to talk about an application or setup
that we have. Just going over what it is, how to contribute, ideas for improvement,
etc. Whoever would like to do this, just add the info in this section. In the
event we don't find someone to teach about something, we skip this section
and just move on to open floor.)
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
#endmeeting
7 years, 10 months
