On Thu, Jan 28, 2016 at 02:35:57PM -0500, Zach Villers wrote:
Here is a draft of a Year In Review post for the Community Ops Blog.
left some things blank (and omitted ALOT - wow - lost of stuff happened
in 2015). I didn't take a stab at the conclusion or 2016 goals section.
JFlory7 had asked Infra if we would submit a YIR post. Kevin and Ralph
(Nirik/Threebean) also had some ideas. I left out ticket and outage
numbers, but can add in something if we want. This is formatted as
Thanks for this Zach! I took it and just added more pieces:
The Infrastructure Team consists of dedicated volunteers and
professionals managing the servers, building the tools and utilities,
and creating new applications to make Fedora development a smoother
process. We're located all over the globe and communicate primarily by
IRC and e-mail.
* Ansible Migration - We believe Ansible is the best new technology
for systems deployment and management. This year, Infrastructure
team moved all remaining Puppet recipes (78 at start of FY2016) in
the infrastructure to Ansible playbooks. The automation provided by
Ansible allows us to quickly fix/rebuild/scale our existing services
and deploy new services.
* RHEL 6 to 7 conversion - As we moved hosts over from puppet to ansible, we
used the opportunity to rebuild all hosts on top of RHEL7 and dealt with all
the yak shaving entailed therein.
* OpenStack migration - We migrated our old Openstack instance to a newer
version and moved out from under the .cloud.fedoraproject.org domain to
.fedorainfracloud.org for HSTS reasons.
* Pagure - Our very own git forge! It just got a facelift last week and we
think it’s pretty cool.
* HyperKitty - HyperKitty is a web front end to the new
Mailman version 3 which allows users to browse topics in a more
familiar, forum-like interface. We will complete development of
this application and deploy for use with Fedora mailing lists.
* Koschei - Koschei is a continuous integration service for
Fedora packages. Koschei is aimed at helping Fedora developers
by detecting problems as soon as they appear in rawhide - it
tries to detect package FTBFS in rawhide by scratch-building
them in Koji.
* Bodhi2 - Pronounced as bo-dee is a buddhist term for the wisdom
by which one attains enlightenment. Bodhi is a modular web-based
system that facilitates the process of publishing package updates
for Fedora. It maintains a single stage of repositories by
* MirrorManager 2 - This started with a FAD at the end of 2014 but was finished
and deployed in 2015. The new MirrorManager 2 is written on top of a modern
framework and has many more people familiar with its code now.
* fedora-packages - This service got a partial rewrite this year, attempting to
resolve some data stability issues.
* mdapi - A new service that provides a JSON api to the contents of yum
repository metadata (a useful service for our other services). "mdapi" means
* Other teams have been doing really cool stuff that ends up making its way in
through the infrastructure team, but we really can't claim credit for it.
Notably, releng has been enhancing their automation and working with us to
stand up supportive services and QA-devel has done crazy awesome work with
taskotron and autoQA. They can talk more about all that.
Some Goals for 2016
We tend to set goals for the next year around April each year, and so we’re not
quite ready to commit to a list, but here are some ideas we’ve been batting
* fedora-hubs is a project that was brainstormed, designed, and prototyped
throughout 2015, and we hope to bring it up to maturity in the coming year.
Read mizmo’s writeups on it for a solid introduction.
* We use nagios and collectd for monitoring our deployments, but we need to
rethink how we’re approaching the whole operation; we’ll likely be revamping
all that next year.
* And.. surely there are other plans lurking around the team that we just
aren’t ready to articulate yet. More to come!
We live in interesting times. New directions in Fedora (the council,
releng.NEXT, etc..) mean there’s no shortage of infrastructure problems to
solve. If you’re interested in helping out, check out our wiki page and join
our infrastructure meetings to follow along.