Good Morning Everyone,
Our infrastructure is mostly a python store, meaning almost all our apps are
written in python and most using wsgi.
However in python we are using a number of framework:
* flask for most
* pyramid for some of the biggest (bodhi, FAS3)
* Django (askbot, Hyperkitty)
* TurboGears2 (fedora-packages)
* aiohttp (python3, async app: mdapi)
While this makes sometime things difficult, these are fairly standard framework
and most of our developers are able to help on all.
However, as I see us starting to look at JS for some of our apps (fedora-hubs,
wartaa...), I wonder if we could start the discussion early about the different
framework and eventually see if we can unify around one.
This would also allow those of us not familiar with any JS framework to look at
the recommended one instead of picking one up semi-randomly.
So has anyone experience with one or more JS framework? Do you have one that
would you recommend? Why?
Thanks for your inputs,
Next week I'll be going offline for 3 weeks (two of them being really off
the grid, I'm going to the European equivalent of the Burning Man
festival...), so I'd like to check with you what errors I've seen our
production Mailman3 instance do these last weeks.
I think that the main issue I haven't fixed yet is the fact that sometimes,
for an unknown reason (yet), the archiving process dies, and email isn't
archived anymore. The posts are still relayed to the subscribers, but the
email are not archived. This can be detected by two ways:
* there is no running process called "/usr/bin/python3.4
/usr/libexec/mailman3/runner --runner=archive:0:1 -C /etc/mailman.cfg" (see
the "runner" option on the command line)
* the "/var/spool/mailman3/archive/" directory starts filling up with
files. It's usually empty.
The best way to fix this is currently to restart the mailman process with
"systemctl restart mailman3". Then the unarchived emails in the backlog
will be processed, the speed is variable but it's around 1 or 2 per second.
The other problems that I've been pinged about recently are really
specific, it's either configuration problems or bugs that I've fixed now.
When it's about emails being rejected, it's usually a good idea to start
looking at the list's header filters (in Postorius).
If you have any questions, feel free to ask me. I'm leaving for the desert
on June 30th, I'll start being mildly reacheable on July 13th, and will be
back on Monday 18th.
The infrastructure team will be having it's weekly meeting tomorrow,
2016-06-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.
= 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 (2016-06-30)
#chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson
#topic New folks introductions / Apprentice feedback
= 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 kevin/nirik out tomorrow (2016-07-01) - kevin
#info lots of ansible playbook cleanups this week - kevin
#info zodbot and ursabot are now using limnoria instead of supybot-gribble - kevin
#info Next monday (july 4th) is a holiday in the US - kevin
#info Next tuesday/wed (july 5th/6th) is a holiday other places - kevin
= 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 datagrepper privacy - ticket 5381 - kevin
#topic pagure for hosted status - ticket 5144 - kevin
= Apprentice office hours =
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
= 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
i just noticed that, after login in FAS, there is a button "I am a human"
for CSRF check.
It's all good, but clicking button makes POST request to (
admin.fedoraproject.org/accounts/login?_csrf_token=<token>) which returns
302 Found and redirects to a same url (GET request) , which returns 403
It seems that navigation "knows" that i am logged in, but content part do
See attached screenshot and log for more info, since it's early morning
and i do not provide a good explanation.
I will be out:
2016-07-01 (this coming friday)
2016-07-07 (the following thursday)
2016-07-08 (the following friday).
I'll be around in case of emergency, but will try and avoid email and
I'd like to introduce myself. My name is Luiz Simeone, from Sumaré, Brazil.
I have 12 years experience with Linux (RHEL, Fedora, CentOS and SuSE) and
UNIX (AIX) servers, IBM Power virtualization, VMWare, SAN and storage
I would like to contribute to Fedora project with my server management
experience, bash and ksh scripting skills, and my free time (a lot of free
time - I was fired a month ago from my last job). I want to learn more
about virtualization and cloud and develop my python scripting skills.
My nickname at IRC channels are lesimeone. Feel free to contact me anytime
here or at IRC.
Thanks and I really hope to help you guys!
Now that we have approved FESCo Docker Image Guidlines and
we're really close to having the Docker Layered Image Build System in
place (everything works, just a couple items to get in Ansible and
more testing before going to PROD), it's time to cross off final items
for bringing Docker Layered Images to Fedora. One of the these items
is to create a Bugzilla Component for Docker items much in the same
way that we have components for RPMs. I'm sure there will be something
needed for pkgdb but I don't know what specifically. I know that pkgdb
does already have support for the docker namespace (as does fedpkg) so
I'm hoping that the amount of work needed isn't too bad.
I'm unsure of exactly what all needs to be done and I hope that I
haven't confused the issue because I might not be up on the Bugzilla
vocabulary. I'm mostly looking for advisement on what the next steps
should be, what all needs to be done and where I can help in making
those things happen.
 - https://fedorahosted.org/fesco/ticket/1573