Here is a draft of a Year In Review post for the Community Ops Blog. I 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 markdown.
Introduction ------------ 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.
Top 3 Highlights ---------- * 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. * HyperKitty Deployment - 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. * Bodhi 2 - 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 adding/updating/removing packages. * MirrorManager 2 - * Koschei launch - 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. * RHEL 6 to 7 conversion -
Top Goal(s) for 2016 -------------------- 1. 1. 1.
Conclusion ----------
Links ----- * https://bodhi.fedoraproject.org/ * https://apps.fedoraproject.org/koschei * https://apps.fedoraproject.org/
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. I 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 markdown.
Thanks for this Zach! I took it and just added more pieces:
Introduction ------------
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.
Infrastructure Highlights -------------------------
* 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. https://infrastructure.fedoraproject.org/cgit/ansible.git/
* 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.
Development Highlights ----------------------
* Pagure - Our very own git forge! It just got a facelift last week and we think it’s pretty cool. https://pagure.io https://pagure.io/pagure https://fedoramagazine.org/pagure-diy-git-project-hosting/
* 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. https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... https://gitlab.com/mailman/hyperkitty http://aurelien.bompard.org/post/2015/05/21/Mailman-3-is-out
* 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. https://apps.fedoraproject.org/koschei https://github.com/msimacek/koschei
* 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 adding/updating/removing packages. https://bodhi.fedoraproject.org/ https://github.com/fedora-infra/bodhi
* 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. https://admin.fedoraproject.org/mirrormanager https://github.com/fedora-infra/mirrormanager2
* fedora-packages - This service got a partial rewrite this year, attempting to resolve some data stability issues. https://apps.fedoraproject.org/packages https://github.com/fedora-infra/fedora-packages http://threebean.org/blog/history-of-fedora-packages/
* 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 "metadata api". https://apps.fedoraproject.org/mdapi https://pagure.io/mdapi
* 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 around:
* 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. http://blog.linuxgrrl.com/2015/07/01/fedora-hubs-update/
* 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!
Conclusion ----------
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.
On Mon, 1 Feb 2016 15:33:42 -0500 Ralph Bean rbean@redhat.com wrote:
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. I 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 markdown.
Thanks for this Zach! I took it and just added more pieces:
Thanks to both of you. ;)
Perhaps we should also try and go over this in the meeting thursday and then send it off after that? Would give people a chance to look it over and specific time to read on and comment on it.
Introduction
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.
Infrastructure Highlights
- 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. https://infrastructure.fedoraproject.org/cgit/ansible.git/
Additionally, we worked with Ansible upstream to test the new Ansible 2.0 and have just recently moved our control host to 2.0.
- 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.
The last RHEL6 instances (aside from some few that need to stay like jenkins RHEL6 builder) should go away next year.
- 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.
Development Highlights
- Pagure - Our very own git forge! It just got a facelift last week
and we think it’s pretty cool. https://pagure.io https://pagure.io/pagure https://fedoramagazine.org/pagure-diy-git-project-hosting/
- 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. https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... https://gitlab.com/mailman/hyperkitty http://aurelien.bompard.org/post/2015/05/21/Mailman-3-is-out
Might reword this a little. Hyperkitty is the archiver/web interface. There's also the base mailman3 and postorius (the admin interface).
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. https://apps.fedoraproject.org/koschei https://github.com/msimacek/koschei
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 adding/updating/removing packages. https://bodhi.fedoraproject.org/ https://github.com/fedora-infra/bodhi
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. https://admin.fedoraproject.org/mirrormanager https://github.com/fedora-infra/mirrormanager2
- fedora-packages - This service got a partial rewrite this year,
attempting to resolve some data stability issues. https://apps.fedoraproject.org/packages https://github.com/fedora-infra/fedora-packages http://threebean.org/blog/history-of-fedora-packages/
- 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 "metadata api". https://apps.fedoraproject.org/mdapi https://pagure.io/mdapi
- 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 around:
- 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. http://blog.linuxgrrl.com/2015/07/01/fedora-hubs-update/
- 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!
I might have a few more if we can wait for thursday. ;)
kevin
Hello - tried to add in everyone's edits. I also created a Gobby doc titled "Infra 2015 YIR" and added to Gobby - Infra Meeting Next as a topic.
On Mon, Feb 1, 2016 at 5:29 PM Kevin Fenzi kevin@scrye.com wrote:
On Mon, 1 Feb 2016 15:33:42 -0500 Ralph Bean rbean@redhat.com wrote:
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. I 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 markdown.
Thanks for this Zach! I took it and just added more pieces:
Thanks to both of you. ;)
Perhaps we should also try and go over this in the meeting thursday and then send it off after that? Would give people a chance to look it over and specific time to read on and comment on it.
Introduction
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.
Infrastructure Highlights
- 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. https://infrastructure.fedoraproject.org/cgit/ansible.git/
Additionally, we worked with Ansible upstream to test the new Ansible 2.0 and have just recently moved our control host to 2.0.
- 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.
The last RHEL6 instances (aside from some few that need to stay like jenkins RHEL6 builder) should go away next year.
- 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.
Development Highlights
- Pagure - Our very own git forge! It just got a facelift last week
and we think it’s pretty cool. https://pagure.io https://pagure.io/pagure https://fedoramagazine.org/pagure-diy-git-project-hosting/
- 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.
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
https://gitlab.com/mailman/hyperkitty http://aurelien.bompard.org/post/2015/05/21/Mailman-3-is-out
Might reword this a little. Hyperkitty is the archiver/web interface. There's also the base mailman3 and postorius (the admin interface).
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. https://apps.fedoraproject.org/koschei https://github.com/msimacek/koschei
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 adding/updating/removing packages. https://bodhi.fedoraproject.org/ https://github.com/fedora-infra/bodhi
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. https://admin.fedoraproject.org/mirrormanager https://github.com/fedora-infra/mirrormanager2
- fedora-packages - This service got a partial rewrite this year,
attempting to resolve some data stability issues. https://apps.fedoraproject.org/packages https://github.com/fedora-infra/fedora-packages http://threebean.org/blog/history-of-fedora-packages/
- 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 "metadata api". https://apps.fedoraproject.org/mdapi https://pagure.io/mdapi
- 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 around:
- 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. http://blog.linuxgrrl.com/2015/07/01/fedora-hubs-update/
- 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!
I might have a few more if we can wait for thursday. ;)
kevin _______________________________________________ infrastructure mailing list infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraprojec...
On Mon, Feb 01, 2016 at 03:28:36PM -0700, Kevin Fenzi wrote:
On Mon, 1 Feb 2016 15:33:42 -0500 Ralph Bean rbean@redhat.com wrote:
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. I 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 markdown.
Thanks for this Zach! I took it and just added more pieces:
Thanks to both of you. ;)
Perhaps we should also try and go over this in the meeting thursday and then send it off after that? Would give people a chance to look it over and specific time to read on and comment on it.
Global +1 for me, text looks good :)
- 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. https://admin.fedoraproject.org/mirrormanager https://github.com/fedora-infra/mirrormanager2
I just wonder a little about this one MM2 isn't quite an user-facing app, so while it might be interesting to mention it, I don't know if it is that interesting to bring it forward here for our readers.
Pierre
infrastructure@lists.fedoraproject.org