So, I sent an email a while back about this to get people thinking, but
I didn't get too much feedback from my questions, so this time I am
going to actually outline a proposal for people to look at. ;)
Currently users expect pretty much any public service we have is fully
supported. This means things like updating status when it's down,
working anytime something is down to fix it as quickly as we can.
New applications/services currently all pass through the (somewhat
long) RFR process which we setup to make sure we could support the
service moving forward.
This is great and all, but some services just aren't as sustainable, or
don't really fit into our RFR process very well. Also, our RFR process
makes us pretty slow to bring a new service online properly.
In order to have support levels, we need a way to communicate that to
our users easily and the only/best way I can think of to do that easily
is via domain name. If we try and have a table or something it could
get pretty confusing for people. Tying it to domain names would make it
fedoraproject.org - Anything with this domain is something that has
passed though our RFR process and we support fully. This means we
update status, we alert on them anytime they have issues, we work on
them anytime they are down, etc.
fedorainfracloud.org - This comes with a lesser level of support,
simply because our cloud doesn't have any kind of HA setup, so
it will be down when doing maint or when there's problems. Services in
this domain may be down when there is scheduled cloud maint. We
monitor, but don't page off hours, we may work on issues only during
business hours, etc. Services here may not have passed through our RFR
process (perhaps we should have a parallel cloud process)
stg.fedoraproject.org - These can be down anytime and we monitor on
them, but may not work on them off hours, etc.
someother domain that sounds fedora related (fedorarelated.org?
fedoralinks.org? ?) - These are things that are fedora related, but not
fully controlled by fedora infrastructure. Things like the fedora
bootstrap site or the porting python3 in fedora site, or possibly cloud
instances that aren't managed by us. These we don't monitor or have
status on, and direct people to contact the managers directly.
Any other types of sites / domains people can think of?
Any general thoughts on the idea?
1. Your IRC handle : gkadam
2. Skills you have : Basic knowledge about - Linux Administration,Nagios-Core, Python and Bash Scripting
3. Skills you want to learn : System Administration skills,Networking,Configuration Management with Ansible, Programming
4. What you wanna learn, any initial questions you have : I want to learn System Administration skills and also would like to document systems in fedora infra if required. I would like to learn how fedora-infra works internally.What else do i need to contribute in #fedora-infra?
There's a Bugzilla outage scheduled for 00:00 2016-03-29 UTC.
If everything goes to plan, bugzilla should start transmitting
messages about changes to bug tickets shortly after this outage is
complete. We have a mediator service running and ready that should
receive those and rebroadcast them to our fedmsg bus.
Please keep party streamers and confetti on standby.
The infrastructure team will be having it's weekly meeting tomorrow,
2016-03-31 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-03-31)
#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 Bugzilla messages are now live on our fedmsg bus! - threebean
#info Fedora 24 Alpha was released tuesday (2016-03-29) - everyone
#info New calendar for modularity effort - kevin
#info Feedback in ask now goes in ask questions with meta tag - kevin
#info Lots of small ansible changes pushed out after freeze - kevin
#info db-koji01 still under heavy load for some reason - 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 badges-backend cron jobs - aikidouke
#topic fedmsg from bugzilla brainstorming session - kevin / threebean
= 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.)
2016-03-31 - RFR - patrick
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
we are now in the infrastructure freeze leading up to the Fedora 24
Alpha release. This is a pre-release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 24 Alpha 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:
git clone https://infrastructure.fedoraproject.org/infra/ansible.git
scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2016-03-22 (or later if
Alpha 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 this list.
As an ask.fp.o moderator, I occasionally received emails from its
feedback link, and I believe other moderators should experience the
same. It seems like the emails are mostly asking questions, especially
on login issues. However, I do not know the answers, and even if I
know, there is no way to reply the questioner since the email came
from nobody(a)fp.o ... In my mind, it is better to change the feedback
link to something that directs the user to mailing list or IRC, so
that it is more likely to be answered. Any idea?