infrastructure June 2018

infrastructure@lists.fedoraproject.org

34 participants
36 discussions

Re: Public facing space for Anaconda CI logs
by Kevin Fenzi 25 Jun '18

25 Jun '18

On 06/25/2018 12:33 AM, jkonecny(a)redhat.com wrote: > On Sat, 2018-06-23 at 11:23 -0700, Kevin Fenzi wrote: >> On 06/22/2018 09:38 AM, Martin Kolman wrote: >> >>> Yeah, that looks good: >>> - lack of backup/mirroring should not be a problem (the results are >>> more or less >>> ephemeral anyway & we can easily back them up internally if needed) >>> - upload speed should not be an issue for the PR test logs & we >>> plan to publish daily logs >>> from kickstart test runs, so even if there was a ~hour delay for >>> uploding the logs it should not >>> make much difference for once-a-day run. >>> >>> Using the existing gitanaconda group should be fine as well, >>> thanks. :) >>> >>> BTW, how would you recommend to handle the automated log uploads to >>> this space ? >>> >>> Is there some interface where we can set a SSH public key, so that >>> the test runner >>> can upload the logs there or something similar ? >> >> Other groups (cockpit at least) have created a fas user. I'd suggest >> something with 'bot' in the name like 'anaconda-bot'. Then login and >> set >> it's ssh key and add it to the group. > > We already have bot user with name: installker ok. You should be able to use that as long as you add it to the group. kevin

1 0

Staging outage 2018-06-27 18:00 UTC -> 22:00 UTC
by Stephen John Smoogen 25 Jun '18

25 Jun '18

There will be an outage starting at 2018-06-27 18:00UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2018-06-27 18:00UTC' Reason for outage: We will be updating and rebooting staging servers to new kernels as well as giving them new ip addresses. Affected Services: All staging systems will be down for some period during the outage Contact Information: smooge(a)fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/7048 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. Steps involved: Staging Hosts Move Add entries into dns Rename/reboot virthost04 to virthost02.stg a. Change hostname on host b. Change ips on host c. Edit ansible guests and playbooks d. Reboot Rename/reboot virthost05 to virthost03.stg a. Change ip on host b. Change hostname on host c. Edit ansible guests and playbooks d. Reboot Rename/reboot virthost11 to virthost04.stg a. Change ip on host b. Change hostname on host c. Edit ansible guests and playbooks d. Reboot Rename/reboot virthost20 to virthost05.stg a. Change ip on host b. Change hostname on host c. Edit ansible guests and playbooks d. Reboot -- Stephen J Smoogen.

1 0

Fwd: Red Hat bugzilla upgrade coming -- test now!
by Ralph Bean 25 Jun '18

25 Jun '18

FWIW, there's a change to the way messaging works with BZ5. - Messages are published to a different queue. Someone will need to update bugzilla2fedmsg to pull from the new right place. - The message format changes, but I think it may only be additive. Someone should verify that we don't need any further code changes. -Ralph ----- Forwarded message from Matthew Miller <mattdm(a)fedoraproject.org> ----- Date: Thu, 21 Jun 2018 11:26:48 -0400 From: Matthew Miller <mattdm(a)fedoraproject.org> To: devel-announce(a)lists.fedoraproject.org Subject: Red Hat bugzilla upgrade coming -- test now! User-Agent: Mutt/1.5.21 (2010-09-15) Reply-To: devel(a)lists.fedoraproject.org Red Hat is planning on upgrading Bugzilla to BZ5 in September. There's a test instance running now at http://bugzilla5.redhat.com/ Since Fedora is a major user and stakeholder here, it'd be helpful if we make sure everything works for us. If you find any bugs, report at https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&version=5.0 -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… ----- End forwarded message -----

1 0

Public facing space for Anaconda CI logs
by Martin Kolman 23 Jun '18

23 Jun '18

Hi, I would like to ask if it would be possible to allocate some storage space that would be publically available (eq. fedorapeople.org, or similar) we could use store logs from our CI so that external contributors can access them. Why is this needed ? Our CI runs in internal vm hosts and internal open stack, both if which is not accessbile from the public internet, has no public IP or domain. At the same time we would like the make te test results available, so that for example an external contributor can see the results of tests we run on their pull request. What tests does the Anaconda CI run ? - unit tests & Pylint we run on all pull requests for Anaconda and related projects - periodically run kickstart tests[0], a battery of 130+ integration test, where each test is basically a full kickstart-configured installation run What kind of environment would be needed ? Basically just a simple file/static html storage would be needed, where we can SCP the log files to. The general idea is that tests results would be uploaded to this space whem the respective tests finish & there would a periodic cleanup task that would keep last N logs & remove old logs. What ammount of storage space would be needed for this ? While the unit tests & pylint runs we do on Pull requests don't produce that much data, the kickstart test suite is in a different class. Each of the 130+ tests is a full installation run, which produces a sizeable ammount of data as we gather a substantial ammount of logs from each test (anaconda logs, dnf logs, lvm & storage logs). This data is important to debug all the various issues that can happen in what is essentially a full instrumented installation run. Our measurements have shown that each full kickstart test run (~130 tests) produces ~800 MB of logs. Therefore we would like to request 16 GB of space to be available so that we can store ~10 last tests results from kickstart test, a reasonable number of PR test results & have some room to spare. Would this be possible ? Requesting 16 GB might seem like a lot but I'm afraid we can't reasonably reduce the space requirements for logs from kickstart tests runs without at the same time also making test runs harder to debug. Looking for your feedback & don't be afraid to ask any questions about this proposal. :) Best Wishes Martin Kolman [0] https://github.com/rhinstaller/kickstart-tests

2 3

How often is sshkey sync from FAS to fedorapeople.org
by Zamir SUN 23 Jun '18

23 Jun '18

Hi Infra team, Today at around 11:26 AM UTC+8 I updated my ssh key to FAS. However I cannot ssh into fedorapeople.org use the new key. After I am back with my laptop (around 21:00 UTC+8), I ssh to it and found it is still using my old key. So I temporary added the new one. So my question is, how often is the pubkey updated to fedorapeople.org? Thanks! -- Ziqian SUN (Zamir) GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E Want to know more about Fedora? Visit https://fedoraproject.org/wiki/ Ready to contribute? See https://whatcanidoforfedora.org/

2 2

Meeting Agenda Item: Introduction Mike Oliver
by Mike Oliver 22 Jun '18

22 Jun '18

IRC: mklvr Skills: Development: - Perl - Bash - Some Python System Administration: - Ansible, SaltStack, NGINX, MySQL, RabbitMQ, Containers (Docker and Buildah/Podman), Kubernetes, Jenkins, PHP, Django, StackDriver, RHEL6/7, DNS, SMTP, E-mail Deliverability, Cisco ASAs, OPNSense Interests: - Improving existing skill set - Learning more about Nagios and OpenShift Tickets: - I might be able to resolve #6527 - I'm going to do some research on #6441 and #6442 I hope to see you at the next Fedora Infrastructure meeting. In the meantime I'll checkout the Getting Started page on the wiki.

2 1

[PATCH] twoweek: Stop building F27 Atomic twoweek nightly compose
by Sinny Kumari 21 Jun '18

21 Jun '18

Since F28 release, we no longer do atomic twoweek release based on F27 content. This patch (available in email attachment) is to stop running cron job for building F27 twoweek nightly composes.

3 4

Agenda for 2018-06-21 Infrastructure Meeting 14:00 UTC
by Stephen John Smoogen 20 Jun '18

20 Jun '18

This shared document is for the next fedora infrastructure meeting. = Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2018-06-21 at 14:00 UTC in #fedora-meeting-1 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-06-21) #meetingname infrastructure #topic aloha #chair nirik pingou puiterwijk relrod smooge tflink threebean = 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 bowlofeggs is on PTO for a long time #info tflink is on PTO for a longer time = 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 Oncall #info Relrod is on call from 2018-06-20->2018-06-26 #info Smooge is on call from 2018-06-27->2018-07-05 #info ?? is on call from 2018-07-06->2018-07-12 #topic Ursa-major? https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapr… - threebean #topic Office hours - how did it go? - kevin #topic Flock again - kevin #topic pkgdb retirement - kevin #topic Tickets discussion #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket Go thru each ticket one by one = Apprentice office hours = #topic Apprentice Open office minutes #info A time where apprentices may ask for help or look at problems. 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 = #topic Letsencrypt - relrod (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.) #info = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

Meeting Agenda Item: Introduction Diogo Nunes
by Diogo Nunes 19 Jun '18

19 Jun '18

IRC: dnunes My Skills: -- Software Development: - Python -- Infrastructure: - +7 years of Enterprise Linux usage and administration; - OpenVPN, DHCP, Apache, Satellite, pulp, and some other services - RHCSA/RHCE ( RHEL 6/7 ), Satellite 6 and RHEV 3 Certified: 140-176- 900 What I want to Learn: -- I want to improve mainly my python and everything that I can with Linux; Initial Questions: -- How to get started ? -- Can someone coach me ? Ty for the opportunity. -- Diogo Nunes [ED90 5C78 7E7D CD62 C46D 6108 3EA4 A072 DF2B 8CC3]

2 1

[Fedocal] Reminder meeting : Infra Office Hours
by cverna＠fedoraproject.org 18 Jun '18

18 Jun '18

Dear all, You are kindly invited to the meeting: Infra Office Hours on 2018-06-19 from 18:00:00 to 19:00:00 UTC At fedora-admin(a)irc.freenode.net The meeting will be about: Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features. Source: https://apps.fedoraproject.org/calendar/meeting/9255/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure June 2018