Hey Kevin and Petr (and anyone else on the list who is interested),
I've been talking with Ben Cotton about moving the elections
application into Communishift. We had a few back and forth e-mails,
and it became clear that it would be helpful if we had quality
documentation describing how community members can use Communishift.
I think there may need to be a balance between documenting how to use
OpenShift, and linking to already existing resources regarding the use
of OpenShift. Perhaps some simple hello world type examples would be
good to document, but it would probably be best to link to official
OpenShift documentation for details on how to use OpenShift.
On the other hand, there are likely to be some particularities with how
we have deployed/configured Communishift that should be documented.
Since we are hoping to hand off several infrastructure applications to
the community, there may be some common patterns among those apps that
would be good to document as well.
It would also be good to document best practices suggestions for some
common problems our users will need to solve:
* How can they use persistent storage?
* How can they use a database?
* How can they back up the applications, persistent storage, and
We do have a wiki page for Communishift already that we can use as a
starting point, but we probably want to move it to our documentation
project as we extend it.
Let me know if you are interested in participating in this project.
 Communishift is an OpenShift instance hosted by Fedora
Infrastructure for the community to use to host applications for
Fedora. Fedora Infrastructure does not maintain or administrate any
applications in Communishift, but rather administers the OpenShift
Was really impressed when I installed Fedora on an old laptop and
everything just works (Cockpit, FreeIPA, kvm). Wanted to come over and see
if I can give back to the community.
I'm a linux sysadmin and former C# developer. I'd be thrilled to learn
about python, openshift, openstack and ansible. I have an RHCSA and I'm
studying for the RHCE.
Originally from Sweden but living in Brazil so I'm in the GMT -3 timezone.
My IRC handle is joalon, I'll try to make it to the infra meeting this
thursday, as well as the Fridays with Infra event.
Hi Infra team,
I'd like to get some Friday (or another day) with Infra time in the
coming month to get Elections moved to CommuniShift, that way I can
make a few bug fixes that need done in advance of the elections coming
up in December.
He / Him / His
Fedora Program Manager
Attached is a patch for https://pagure.io/fedora-infrastructure/issue/8156
There were lots of places where I didn't know if a certain conditional
makes sense, for example checking for ansible_distribution == RedHat
when we maybe have only Fedora machines and that playbook would never
run on RHEL
I've added a couple of FIXME lines where I though that a closer look
might be required.
nirik suggested trying out board.net for the weekly meeting agenda, so
I created a meeting agenda there:
Feel free to add your own material to the agenda. Here is what it looks
like at the time of this writing:
title: Infrastructure Meeting template
tags: Fedora, Infra, CPE
# Infrastructure Meeting
Send on IRC a day before meeting (#fedora-noc #fedora-admin #fedora-releng #fedora-apps)
REMINDER: There will be a Fedora Infrastructure meeting tomorrow (2019-09-19) at 15:00 UTC in #fedora-meeting-1. Please check the agenda at https://board.net/p/fedora-infra and mail updates to sysadmin-main members.
On the day of the meeting send the following
REMINDER: There will be a Fedora Infrastructure meeting today (2019-09-19) at 15:00 UTC in #fedora-meeting-1. Please check the agenda at https://board.net/p/fedora-infra and mail updates to sysadmin-main members.
The infrastructure team will be having its weekly meeting tomorrow,
2019-09-19 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a document at https://board.net/p/fedora-infra
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.
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 (2019-09-19)
#chair nirik pingou puiterwijk relrod smooge tflink cverna mizdebsk mkonecny abompard bowlofeggs
### 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
#info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted
### 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 We are looking for people to maintain Fedocal and Nuancier - mkonecny
### 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)```
#info Summary of last week: (from relrod )
#topic Monitoring discussion
#info Go over existing out items and fix
#topic Tickets discussion
Go thru each ticket one by one
### Put all topics for discussion under here
#topic Where to put these docs in the future?
#info infinote is going away
#info a new central doc place would be good. can someone set this up?
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.)
### Meeting end stuff
#topic Open Floor
we are now in the infrastructure freeze leading up to the Fedora 31
Beta release. This is a pre release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 31 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 2019-09-17 (or later if
release slips or uses the secondary target). 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 this list.
You are kindly invited to the meeting:
Fedora Infrastructure on 2019-09-19 from 15:00:00 to 16:00:00 UTC
The meeting will be about:
Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before.