infrastructure February 2018

infrastructure@lists.fedoraproject.org

36 participants
38 discussions

Deploying JS-based application (Hubs)
by Pierre-Yves Chibon 10 Feb '18

10 Feb '18

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 openshift? How do we want to handle updates? (especially considering the semantic versioning aspect mentioned above) What do people think? Thanks, Pierre

5 12

congrats to Mikolaj Izdebski
by Kevin Fenzi 09 Feb '18

09 Feb '18

I'm happy to announce that We have approved Mikolaj into the sysadmin-main group. This is the core group of trusted folks that high level access to most things. He's done great work maintaining koschei, helping us with jenkins and java things and koji. Congrats and use your powers for good! kevin

4 3

[PATCH] atomic host life support for f26
by Dusty Mabe 09 Feb '18

09 Feb '18

Sync out the stable ref too, which is just aliased to the updates ref at this point. --- roles/bodhi2/backend/files/new-updates-sync | 3 +++ 1 file changed, 3 insertions(+) diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync index 142a73516..e220d7121 100755 --- a/roles/bodhi2/backend/files/new-updates-sync +++ b/roles/bodhi2/backend/files/new-updates-sync @@ -57,6 +57,9 @@ RELEASES = {'f27': {'topic': 'fedora', 'from': 'f26-updates', 'ostrees': [{'ref': 'fedora/26/x86_64/updates/atomic-host', 'dest': os.path.join(ATOMICDEST, '26')}], + # Hack around for the fact that ostree on f25 doesn't know links + {'ref': 'fedora/26/x86_64/atomic-host', + 'dest': os.path.join(ATOMICDEST, '26')}], 'to': [{'arches': ['x86_64', 'armhfp', 'source'], 'dest': os.path.join(FEDORADEST, '26')}, {'arches': ['aarch64', 'i386', 'ppc64', 'ppc64le'], -- 2.14.3

3 4

Meeting Agenda Item: Introduction Daniel Bruno
by Daniel Bruno 09 Feb '18

09 Feb '18

Hi there, I have contributed with Fedora Project in the last 10 years, most of this time as Ambassador in LATAM, RPM Packages and sometimes I did to contribution here in the Infra group, however in the last 2 years since I moved from Brazil I stayed away from the project, and I would like to come back to contribute :) Currently I work for Amazon Web Services as Systems Engineer in Cape Town (UTC +2), and I would like to contribute with Python (systems or web), CI/CD, Ansible, Linux and monitoring. I am looking forward to attend the next meeting and to start working in the Apprentice group. Cheers, -- Daniel Bruno http://dbruno.org

2 1

Plan for tomorrow's Fedora Infrastructure Meeting 2018-02-08
by Stephen John Smoogen 07 Feb '18

07 Feb '18

= Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2018-02-08 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 = 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-02-08) #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 Mass rebuild began on 2018-02-06 #info Infrastructure hackfest in april: https://fedoraproject.org/wiki/Infrastructure_Hackathon_2018 #info = 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. #topic = 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 #endmeeting -- Stephen J Smoogen.

1 0

Script to check mirrorlist age
by Adrian Reber 07 Feb '18

07 Feb '18

The following patch would add a script to check for the age of the mirrorlist servers. If somebody could add the necessary nagios configuration to let this run against the proxies I would add this script to the repository. The script makes it easy to verify that the mirrorlist containers have up-to-date data: $ ./check_mirrorlist_pkl_age.py 02 3000 5000 WARN: mirrorlist data on proxy02 older than 3000s (3894s) Is this a check that would make sense for the current Nagios setup? We probably need to figure out the right values for warning and critical. Adrian

1 1

January status update for Fedora Infrastructure Apprentices
by Kevin Fenzi 01 Feb '18

01 Feb '18

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 list). 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: https://docs.pagure.org/infra-docs/sysadmin-guide/sops/sshaccess.html and ask on irc or email list if you have any problems. Thanks! kevin

6 15

Plan for tomorrow's Fedora Infrastructure Meeting 2018-02-01
by Stephen John Smoogen 31 Jan '18

31 Jan '18

The infrastructure team will be having its weekly meeting tomorrow, 2018-02-01 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 = 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-02-01) #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 Devconf is over. They had cake. #info The cake is a lie. #info = 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. #topic = 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 #endmeeting -- Stephen J Smoogen.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure February 2018