infrastructure February 2020

infrastructure@lists.fedoraproject.org

31 participants
36 discussions

Freeze Break Request: update wildcard cert to new one
by Stephen John Smoogen 27 Feb '20

27 Feb '20

This patch should make the changes to the appropriate files so that various playbooks will use the newer certificate wildcard-2020 -- Stephen J Smoogen.

3 2

Questions about possible ODCS migration to Openshift.
by Jan Kaluza 27 Feb '20

27 Feb '20

Hi, I'm considering migration of ODCS (https://odcs.fedoraproject.org/api/1/composes/) to Openshift in order to make it more scalable and also to make it closer to internal ODCS deployment which I would like to also move to Openshift in the future. I have some questions related to this: 1) ODCS needs /mnt/koji mounted in read-only mode. Based on my information, it should be possible to mount /mnt/koji in read-only mode in Openshift. Do you foresee any issues with this? 2) ODCS needs /srv/odcs NFS storage ("fedora_odcs") mounted in read-write mode. Is it possible and safe to mount this storage in Openshift in read-write? 3) If I understand it correctly, I will have to use official Fedora Openshift (it means *no* comunnishift) even for my initial tests, because communishift does not allow me to mount these volumes. Is it possible to ask for new Fedora Openshift project for this use-case? 4) Do you foresee any issues I might be missing? Regards, Jan Kaluza

3 4

State of FMN (FedMSG Notifications) and Replacement
by Clement Verna 26 Feb '20

26 Feb '20

Hi all, FMN (https://apps.fedoraproject.org/notifications) is currently one of the main blocking point for dropping fedmsg in favour of fedora-messaging. FMN is quite important to the community and the composition of Fedora because it gives emails and notifications on commits, composes, builds and updates via email and other tools. However, the code base is written in Python 2.7 and not maintained anymore. Currently the service has to run on a Fedora 28 system to continue running. This causes multiple problems and concerns, and needs to be addressed before the datacenter move in June. In order to start putting together a specification for a replacement, we should try to look at the minimum requirements for a notification system. For example the current system supports sending notifications to IRC, emails and SSE (Server Sent Event), Can we live without SSE ? Can we live without IRC ? Do we need it to monitor everything it does currently or just a subset of items that the community has found useful. Let's use this thread to brainstorm ideas on what we need. Thanks all

6 6

Opening a bit more openshift apps
by Michael Scherer 26 Feb '20

26 Feb '20

Hi, I have been asked to look at the build of the docsbuilding openshift app. However, I am not a appowners and do not have access to anything. My understanding is that either you are listed in appowners, and you can control the app, or you are not, and you can do nothing. I would propose that we revise that policy, and let (as a opt-in since I guess opt-out would be too radical) application be a bit more open. Since I tend to think that patch are clearer to express my intent than my words, a patch that would be a first draft of what I would like to see being implemented is attached. I am still reading openshift docs on ressources, to see if I missed and/or opened too much. -- Michael Scherer

2 1

[AAA] automation repository
by Leonardo Rossetti 26 Feb '20

26 Feb '20

I noticed that we have ansible automation in some of our repositories: * Securias: https://github.com/fedora-infra/securitas/tree/master/devel/ansible * Local dev env using vagrant for fasjson being landed: https://github.com/fedora-infra/fasjson/pull/5 Do you think it makes sense to have a dedicated repository for this "installation/automation" work? This "automation" repository could have: * ansible code to deploy freeipa, fasjson, securitas and any other related component (to provision it in bare servers, local vm or even kubernetes) * Vagrantfile for local dev env * terraform code for infra provisioning I would like to know your thoughts on this. Regards, -- Leonardo Rossetti Senior Software Engineer, Red Hat <https://www.redhat.com> lrossett(a)redhat.com M: +55-11-99703-0621 <https://www.redhat.com>

1 0

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 26 Feb '20

26 Feb '20

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2020-02-27 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before. Source: https://apps.fedoraproject.org/calendar/meeting/9675/

1 0

new task for creating swap file
by Miroslav Suchý 25 Feb '20

25 Feb '20

I created new task for creating swap file and mount it. https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/tasks/swap.y… It is handy in AWS where flavors does not have swap disk. You can use it like: tasks: - import_tasks: "{{ tasks_path }}/swap.yml" when: - datacenter == 'aws' - swap_file_size_mb is defined It uses two variables (values are just example): swap_file_size_mb: 2048 swap_file_path: /swap -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys

2 1

[minutes] [2020-02-24] Badges Outreachy internship planning
by Justin W. Flory 24 Feb '20

24 Feb '20

Hi folks, Today, Fedora Badges folks met to continue planning for a Summer 2020 Outreachy intern. Next action items are to submit the proposal to the Outreachy portal and to schedule the call with badgr-server upstream to discuss our needs and intent to collaborate. You can find the notes from the call in the Google Doc, or summarized below: https://docs.google.com/document/d/1R3VndOLYl9A47s_swC03Tci5LpCb8Via9wghDY3… ## Communishift/Kubernetes * Initial focus on containerization; how and where we deploy it (Kubernetes / Communishift / OpenShift) comes after * Kubernetes/containers might be more sustainable * Maybe easier to use CommuniShift? * #agreed - First step would be to create container image, put on communishift, and THEN move to others when possible ## Mentors * Sayan: django, python * Misc: communishift * Justin: Python, containers, issue triage * Xavier ## Things to discuss with Badgr folks * How to containerize badgr-server (see https://github.com/concentricsky/badgr-server/pull/110, https://github.com/concentricsky/badgr-server/pull/212) * When will this be updated to python 3? (see https://github.com/concentricsky/badgr-server/pull/218) * Can we find someone from within Fedora to help contribute to make this happen? (only one person dedicated to work on badgr currently) * What are some “easyfix” tasks we could put up on GitHub before March 1st, when Outreachy applicants first see list of projects? * Documentation needs? * Is there a concise link with instructions for "Add a test badge (using Fedora design assets) to local badgr-server" * Needs review for our use case: https://support.badgr.com/portal/kb/articles/creating-badges-as-an-issuer-i… * Will it be the same for self serve? ## Authentication * Need OAuth authentication for Python Django apps * How we add FAS logins for badgr-server ## SUBMISSION DEADLINE: Feb. 25, 2020 at 4pm UTC * Sayan is submitting proposal & mentorship * Misc is also going to fill in the mentorship part -- Cheers, Justin W. Flory (he/him) justinwflory.com TZ=America/New_York

1 0

CPE Weekly: 2020-02-21
by Aoife Moloney 21 Feb '20

21 Feb '20

--- title: CPE Weekly status email tags: CPE Weekly, email --- # CPE Weekly: 2020-02-21 Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. ## Fedora Updates ### Data Centre Move * The F32 Schedule Key has been updated to include data centre move implications: https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html * The F32 Infrastructure has also been updated to include them too: https://fedorapeople.org/groups/schedule/f-32/f-32-infrastructure-tasks.html * If you have an instance in the fedora private openstack cloud that, please remove it, or lose it! This instance will be turned off on 2020-02-27. You have been warned! :) ### AAA Replacement * I forgot **all** the links last week - my bad! So here is the corrected AAA project work - the team are using a kanban board in GitHub, not Jira for their work and their blog post to the Fedora Community Blog is linked. * The team made great progress in sprint 3, completing over 10 tickets! Check out their kanban board here: https://github.com/orgs/fedora-infra/projects/6 * The blog post can also be viewed here: https://communityblog.fedoraproject.org/aaa-fas-replacement-project-update/ * The team meet on Jitsi Monday-Thursday @ 0915-0945 UTC to talk about tickets they are working on (and to see each other :) ) and if you wish to join, the link is here: https://meet.jit.si/FedoraInfraAAAStandups * They also update the #fedora-aaa channel on IRC with updates and chat regularly about the project here too so feel free to join, contribute or just observe! ### CI/CD * The team has managed to get its monitor-gating script deployed and running on openshift in staging and it has already identified an issue with the packager workflow there (in this case in waiverdb, a ticket has been opened upstream to investigate it). * The team wrote a document listing all the ideas they investigated/thought about for dropping changelog and release fields from spec file * The team made a decision on the recommended approach that will be submitted to the devel list for further consideration and inputs. ### Sustaining Team * The ongoings of these ongoings, are ongoing :) * Infra and Releng tickets are reviewed daily (Mon-Fri) in #fedora-admin at 1900UTC. * * Packit integration in the-new-hotness https://github.com/packit-service/packit/issues/689 * * Jms-messaging-plugin reviews https://github.com/jenkinsci/jms-messaging-plugin/pull/169 https://github.com/jenkinsci/jms-messaging-plugin/pull/168 https://github.com/jenkinsci/jms-messaging-plugin/pull/162 * * Compose-tracker now track the time a compose takes, more info here https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… ## Docs ### Misc Updates ### Git Forge Requirements * Thank you for your engagement on our Git Forge requirements emails. We have received (a lot of) content from (a lot of) sources both internally and externally. * A decision around the Git Forge is still some time away yet, as this decision impacts so many, but we will keep you up to date on where we are in the process on a weekly basis via this email blast. * Right now we are compiling requirements we have received into a complete set to be able to move to a technical comparison of services between Pagure vs GitHub vs GitLab. * We expect to have the requirements set done by March 11th and will make the requirements available to view as soon as they are all accounted for. * If our dates change, good or bad, we will keep you updated and thank you for your patience and understanding as always! ## CentOS Updates ### CentOS * Tycho module has been unblocked which was needed for jmc * Data is being moved for CentOS Infra and trying a new solution for backups https://github.com/CentOS/ansible-role-centos-backup/commit/e32fb06b74c506c… * VDO was deployed for storage duplication and compression * CentOS CI is stable overall with an updated fedora image and python-tox fix, which is allowing the AAA/Securitas team move forward with integrating CentOS account auth in this project too. ### CentOS Stream * The packit team are trying out the dev/staging instances of git.centos.org * We have been receiving regular updates over the last two days As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great weekend! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

How to do ..., let try to share our knowledge
by Clement Verna 20 Feb '20

20 Feb '20

Hi all, In an effort to try to spread knowledge on how to do things in the Fedora Infrastructure, let's try to use a How To git repo [0]. The goal is to add there files with the description on How to complete a certain task. For example I have added a file for How to delete a virtual instance [1]. If we try to use this repo when we process tickets, I think it has the potential to become a good knowledge base that would be useful for all of us. Why not add that information in the SOP ? The SOP[2] are usually dedicated to one system or one application, in order to complete a task you might have to execute steps on different services and/or applications. Also it is, I believe easier to search for something like "How to create a new mailing list" rather than having to know that we are using mailman for mailing list and then search for the mailing list SOP. Let me know what you think about trying this ? [0] - https://pagure.io/Fedora-Infra/howtos [1] - https://pagure.io/Fedora-Infra/howtos/blob/master/f/destroy_a_virt_instance… [2] - https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/index.html

5 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure February 2020