we are now in the infrastructure freeze leading up to the Fedora 27 Beta
release. This is a pre-release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 27 Beta when it's available.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2017-09-19 (or later if Beta
slips). Frozen hosts should have no changes made to them without a
sign-off on the change from at least 2 sysadmin-main or rel-eng members,
along with (in most cases) a patch of the exact change to be made to
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,
Good Morning Everyone,
There has been work on fedora-hubs for a while now and there is an objective to
make it live in staging early this year.
However, there is a question about how we want to deploy such application.
So far we have asked that all our application be packaged in RPMs. The main
application may not be in the official Fedora repositories but (for most) we
asked that all of its dependencies are.
For example, pkgdb or pagure aren't in Fedora's repositories themselves, but we
still build them in koji pulling the dependencies from the official repos.
Hubs is the second of our app where this model is almost not workable because it
is written in nodejs where every file is/can be a separate package and semantic
versioning sometime not very well respected.
The other application we have that is in nodejs is the flock registration
application that, iirc, we run in our cloud.
However, hubs is not meant to be run in our cloud.
So how do we want to deploy hub?
Do we allow npm install? Do we want to use container? Should it target
How do we want to handle updates? (especially considering the semantic
versioning aspect mentioned above)
What do people think?
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
I am doing something different this time with this email:
If you would like to stay in the apprentice group, please login at least
once to batcave01.phx2.fedoraproject.org. I'll check at the end of the
month and remove folks who haven't logged in at all in January.
Note that you can always be re-added down the road when you have more time.
If you need assistance logging into batcave01, please do look at:
and ask on irc or email list if you have any problems.
Hello the Team,
I'm looking to join the infrastructure team, you will probably see me on
IRC as Raboliot.
To briefly introduce myself, I'm a French student doing and I'm also
working in an IOT company, I'm studying networks, system administration and
cyber security, but I was originally a developer.
several other languages (C/C++, Java, recently Perl).
I'm eager to learn anything, whether it is in development or systems
I'm new to contributing to an open-source project, so I will be happy if
someone can mentor me and guide me through the apprentice process.
Have a nice day,
The infrastructure team will be having it's weekly meeting tomorrow,
2018-01-18 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.
> This shared document is for the next fedora infrastructure meeting.
> = Preamble =
> The infrastructure team will be having its weekly meeting tomorrow,
> HERE, 2018-01-11 at 18:00 UTC in #fedora-meeting on the freenode network.
> = Introduction =
> 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 (2018-01-18)
> #meetingname infrastructure
> #topic aloha
> #chair smooge relrod nirik dgilmore threebean pingou puiterwijk pbrobinson maxamillion
> = Let new people say hello =
> #topic New folks introductions
> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
> = 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 Lots of reboot been and upcoming for various CVEs - puiterwijk/kevin/smooge/relrod
> #info Many old f25 instances moved to f27, a few more to go - kevin
> #info Many folks traveling to devconf/fosdem/configmgmt-camp next week>
> = 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 /suor 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 Ticket cleanup
> #info none this week.
> = Apprentice office hours =
> #topic Apprentice Open 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 i/nfo 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:
> #info none this week
> = Meeting end stuff =
> #topic Open Floor