Re: Welcome to the batcave

Dne 25.9.2015 v 18:47 Kevin Fenzi napsal(a): > I hope everyone enjoys the nice RHEL7, faster, larger, better batcave. Hurray! I especially appreciate the presence of Ansible 1.9, with newer modules (e.g dnf module). -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fe

Re: State of python3 in our infrastructure

Dne 2.12.2015 v 12:14 Pierre-Yves Chibon napsal(a): > So what do you folks think? Copr is already migrated to python3 (in upstream) and I'm getting ready to use python3 on production servers soon. But Copr (frontend and backend) is using Fedora it is no big deal anyway. Well we will migrate front

SPF and email forwarding

Today I sent email to packager-spons...@fedoraproject.org and several email returned back due SPF protection. Can someone either implement this: http://www.openspf.org/Best_Practices/Forwarding or turn those email aliases to mailing list? Mirek Přeposlaná zpráva Předmět: Und

Re: Support levels and RFR adjustments

Dne 22.1.2016 v 22:33 Kevin Fenzi napsal(a): > fedoraproject.org - Anything with this domain is something that has > passed though our RFR process and we support fully. This means we > update status, we alert on them anytime they have issues, we work on > them anytime they are down, etc. > > fedo

Re: SPF and email forwarding

Dne 25.1.2016 v 16:46 Kevin Fenzi napsal(a): > I don't think there's anything we can do here. We can. We can enable SRS: http://www.openspf.org/SRS For postfix there exist: https://github.com/roehling/postsrsd Unfortunately not packaged for Fedora. -- Miroslav Suchy, RHCA Red Hat, Senior Sof

Re: Support levels and RFR adjustments

Dne 25.1.2016 v 18:06 Kevin Fenzi napsal(a): > Sure, but I was hoping to phase out cloud.fp.o in favor of > fedorainfracloud. Hmm. There is a *lot* of people who have .repo file pointing to copr-be.cloud.fedoraproject.org. -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #deve

Re: ansible 2.0 on batcave01

Dne 30.1.2016 v 18:40 Kevin Fenzi napsal(a): > The only other thing related to ansible 2.0 I can think of is that copr > may need to adjust to the new API if it's using that directly, but it > can do that on it's own timeframe. Nope. We are calling ansible python methods directly just on copr-be.

Re: ansible 2.0 on batcave01

Dne 12.2.2016 v 22:29 Kevin Fenzi napsal(a): > But it should migrate sometime... 1.9.x isn't going to be supported all > that much longer, so it should move to the new 2.0 api as soon as it > can. F23 will stay on 1.9.x, isn't it... oh, there is an update filed for F23. I really hope it did not g

Re: COPR builds/services for other distros?

Dne 14.3.2016 v 23:58 Patrick Uiterwijk napsal(a): > I would suggest you to look at our Request For Resource procedure. OK. I created: https://fedorahosted.org/fedora-infrastructure/ticket/5166 > - How well would at least the frontend and package download server work behind > a load balanced/HA

Best practice for 3rd party playbook

Hi, I am in process in writing playbook for retrace.fedoraproject.org ABRT team created: https://github.com/abrt/ansible-role-retrace-server Which we can use. I just wonder what is best practise for using such 3rd party roles? Should I just copy it into our ansible.git? Or should I use ansible-g

Fwd: reuse space on retrace02 for retrace01

FYI Přeposlaná zpráva Předmět: reuse space on retrace02 for retrace01 Datum: Thu, 13 Apr 2017 16:07:37 +0200 Od: Miroslav Suchý Společnost: Red Hat Czech s.r.o. Komu: abrt-devel-l...@redhat.com Hi, for Fedora we have two servers: retrace01.qa.fedoraproject.org retrace02

SOP for retrace

Hi, I created new SOP for retrace server (see attachemnt). I tried to git-push it, but got: $ git push Counting objects: 6, done. Delta compression using up to 8 threads. Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 2.02 KiB | 0 bytes/s, done. Total 6 (delta 3), reused 0 (d

Re: SOP for retrace

Dne 17.5.2017 v 15:14 Jeremy Cline napsal(a): > Hi, > > We've moved our documentation to Pagure[0] and turned it into a sphinx > project. The readme provides guidance on how to contribute, but if you > run into any trouble just let me know!> > [0] https://pagure.io/infra-docs/ OK I created PR. Bu

Re: retrace / faf issues

Dne 26.6.2017 v 18:50 Kevin Fenzi napsal(a): > Greetings. > > I've seen some various retrace/faf issues of late, so I thought I would > collect them into an email and see if you all could take a look and > solve them. :) Thank you for bringing it up. > - retrace02.qa.fedoraproject.org has a 100

Re: retrace / faf issues

Dne 27.6.2017 v 16:17 Kevin Fenzi napsal(a): >>> - retrace01.qa.fedoraproject.org is almost constantly alerting on swap >>> being full. Not sure what to do about this, but perhaps we could add >>> more swap or somehow limit it to use only memory for normal jobs? >> Few months ago I set postgresql t

Higher quota for Copr

Hi, Copr is using up to 29 x86 VMs and 10 ppc VMs from Fedora Cloud for builders. We are hitting the limits quite often. So I would like to ask if I can assign another 10 x86 VMs to Copr? I can do it myself, I am just asking in advance if anyone is against it. I checked the hypervisors and there i

Re: Higher quota for Copr

Dne 1.11.2017 v 16:37 Kevin Fenzi napsal(a): > On 11/01/2017 05:32 AM, Miroslav Suchý wrote: >> Hi, >> Copr is using up to 29 x86 VMs and 10 ppc VMs from Fedora Cloud for builders. >> We are hitting the limits quite often. So I would like to ask if I can >> assign anoth

Images in Fedorainfracloud.org are not in playbook

should be done for common images (i.e., Fedora-Cloud-Base-27-1.6.x86_64.qcow2) Miroslav Suchý ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: How to get invite for joining Fi-apprentice group?

Dne 21.11.2017 v 06:43 Marut Pandya napsal(a): > How do i join fi-apprentice group? > My login name is- pandyamarut > please send me invite. You should attend Fedora Infra meeting: https://fedoraproject.org/wiki/Infrastructure/Meetings introduce yourself, tell everyone what you would like to d

Re: OpenStack endpoints in fed-cloud09

Dne 11.12.2017 v 11:46 Patrick Uiterwijk napsal(a): > Due to known security issues, the current Fedora Cloud's API is not > available from the public internet. 1) then it should be changed in the playbook. 2) so how can I communicate with API from the fedora cloud itself? I am focused on Ansible

Copr storage

We are running out of disk space in Copr. It will probably run out during Christmas so I am going to act before the weekend. Right now we have 4GB volume for production and 4GB for dev machine (just because we can, but we never used that). My plan is to shrink dev volume to 150 GB. And allocate

Re: Copr storage

Dne 19.12.2017 v 16:41 Miroslav Suchý napsal(a): > I plan to do that tomorrow. Done. However after the testing I end up with copr-be-dev-data volume in Detaching state (it is in this state for more than 20 hours). I hope that it will eventually time-out during Christmass. But if anyone kn

VDO

After I seen the talk about VDO: https://www.youtube.com/watch?v=7CGr5LEAfRY I went ahead and tried it. I tried it on small (12GB) sample of Copr data and I saved 20-30% data. I then deployed it on production server retrace.fedoraproject.org and saved there 15% out of 2TB. Several notes: The RP

Re: VDO

Dne 16.2.2018 v 14:56 Dusty Mabe napsal(a): > Once we get it into Fedora this would be a great blog post for the magazine. > What do you think? Yes. Sure. Miroslav ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe

Re: VDO

Dne 16.2.2018 v 20:59 Paul W. Frields napsal(a): > Would love to have a feature on this. Refer here for the process, if > you haven't done an article before: > > https://fedoramagazine.org/writing-an-article-for-the-fedora-magazine/ I am able to log into FM dashboard, but I do not see there an o

Re: VDO

Dne 23.2.2018 v 10:57 Clement Verna napsal(a): > Miroslav, > > Can you access https://fedoramagazine.org/wp-admin/edit.php ? From > there, you should have a "Add new" button that will let you create a > new post. I get: Sorry, you are not allowed to access this page. Miroslav

Re: VDO

channels. :(( My username is: msuchy Miroslav > On 23 February 2018 at 11:17, Miroslav Suchý wrote: >> Dne 23.2.2018 v 10:57 Clement Verna napsal(a): >>> Miroslav, >>> >>> Can you access https://fedoramagazine.org/wp-admin/edit.php ? From >>> there, you s

Re: Libravatar shutting down on 2018-09-01

Dne 5.4.2018 v 04:16 Neal Gompa napsal(a): > The main problem, of course, is finding someone who wants to run it... Even if you find someone (not as big problem), that guy basically cannot do anything else. So basically strike out something from our TODO list as CANNOT FIX. @Justin thank you for

new openstack instance?

Hi, what is the status of the new openstack instance? The old one is becoming pain with every new day. Miroslav ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedorapr

Fwd: mirror failures

Can someone comment on this? I am not really sure if there are some issues on mirrors (not likely) or if this is some issue with Fedora Cloud when network is overloaded (more likely). Miroslav Přeposlaná zpráva Předmět: mirror failures Datum: Mon, 9 Apr 2018 09:38:04 +0200 Od:

Re: Moving meeting time?

Dne 18.4.2018 v 23:31 Kevin Fenzi napsal(a): > What would everyone think of moving the meeting to 16UTC? > Or is there a better time for anyone? +1 I cannot attend at 18UTC, but 16UTC is much better for me. Miroslav signature.asc Description: OpenPGP digital signature _

patch review: storage check for retrace.f.o

I want to set up monitoring of free space on /srv of retrace.fedoraproject.org. It is huge volume therefore normal check_disk_/srv does not have sense. I created new check, but it is my first time working with nrpe. I would welcome if someone can review it, before I push it. Patch is in the attac

Storage at copr-be

FYI - We are running out of space on copr-be.cloud.fedoraproject.org: /dev/vdc1 6.4T 6.4T 75G 99% /var/lib/copr/public_html This is where repositories are stored. We likely run out of space till Monday. Therefore I will add some space to this volume from openstack - I plan to add 500 G

Re: Storage at copr-be

Dne 12.10.2018 v 22:11 Kevin Fenzi napsal(a): > How much do we have left on that device? At the end I added 1TB. Now we have: /dev/vdc1 7.5T 6.2T 1.3T 83% /var/lib/copr/public_html I attached the graph showing the history (sorry for the gap in 2015,2016). But the end of the story is tha

Fwd: Undelivered Mail Returned to Sender -- m...@petetravis.com

not found. Name service error for name=petetravis.com type=A: Host not found --- Begin Message --- commit 4d57437c163d156b79dd212c6587ca03a78c077a Author: Miroslav Suchý Date: Wed Oct 17 11:04:08 2018 +0200 copr: generate index for subdirs of /archive/spacewalk/ roles/copr/bac

Re: Storage at copr-be

Dne 18.10.2018 v 21:08 Kevin Fenzi napsal(a): > Purging old eol data should slow that? Any idea how much? du tells me that: fedora-21-* 82 GB fedora-22-* 132 GB fedora-23-* 241 GB fedora-24-* 343 GB fedora-25-* 438 GB fedora-26-* 775 GB epel-5-* 9.7 GB and I have some more time to check: epel-6

Re: Storage at copr-be

Dne 22.10.2018 v 18:18 Miroslav Suchý napsal(a): > Dne 18.10.2018 v 21:08 Kevin Fenzi napsal(a): >> Purging old eol data should slow that? Any idea how much? > > du tells me that: > > fedora-21-* 82 GB > fedora-22-* 132 GB > fedora-23-* 241 GB > fedora-24-* 343 GB

Re: Statistics. Stats for installled or downloaded packages

Dne 05. 11. 18 v 16:21 Stephen John Smoogen napsal(a): > Currently there is no way to know what > packages are being installed/downloaded the most. Some times ago, I led student bachelor thesis and he added rpm support for Debian's PopCon [1], which is opt-in system to report package usage. Alas,

Re: Statistics. Stats for installled or downloaded packages

Dne 12. 11. 18 v 15:41 Miroslav Suchý napsal(a): > Some times ago, I led student bachelor thesis and he added rpm support for > Debian's PopCon [1], which is opt-in system > to report package usage. Ahh, forgot to add link to the port: https://github.com/xsuchy/popcon-for-fedora

Re: attention brno folks: testing wanted

Dne 14. 11. 18 v 2:20 Kevin Fenzi napsal(a): > So, if you had slow pagure connections in the past, can you: > > * do some initial tests: > > time git clone https://pagure.io/pagure.git Tested from Brno RH office. real0m10,942s user0m7,328s sys 0m1,965s > time curl https://pagure.i

Re: cloud retirement

Dne 27. 02. 19 v 23:00 Peter Robinson napsal(a): >> Hey everyone. >> >> As you know, we currently have a RHOSP5 ancient cloud. After a bunch of >> work last year, we got a RHOSP13 cloud up and mostly working, but it was >> a ton of work. After hearing from the Fedora Council and our various >> mana

Re: What are we going to do about sigul?

Dne 21. 03. 19 v 13:57 Neal Gompa napsal(a): > Forgive me, but what does sigul do that signd cannot? I'm unaware of > any material differences between the two. When I started Copr I considered both Sigul and OBS signd. I spent several hours with Mirek Trmač - original author of Sigul and we talke

Re: What are we going to do about sigul?

Dne 25. 03. 19 v 14:49 Patrick Uiterwijk napsal(a): > Additionally, I would not call it dead since I took it over, given > that I've been adding new features to it over time. > There's not a huge set of new features people have been asking for, so > I've only been adding what I do hear about or nee

Pavel Raiskup is a new member of Copr team

Hi, it is my pleasure to announce that Pavel Raiskup (praiskup) joined the Copr team. Pavel has been contributing to Copr for long time in his free time. He has been maintaining Red Hat internal Copr instance for long time. Now, he is joining Copr team as his full time job. Pavel replaced Michal

Re: pastebin plans

Dne 28. 05. 19 v 9:00 Till Maas napsal(a): > - make fpaste work with paste.centos.org +1 I use fpaste a lot. So please keep the functionality of fpaste. But I do not care to which service it will communicate. -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys

Re: 2020 Datacenter Move: Request for comments

Dne 27. 09. 19 v 23:55 Kevin Fenzi napsal(a): * Populate the new datacenter with new hardware to replace old hardware that either wouldn’t survive the shipping or is due to be refreshed In past, I was in touch with people working in datacenters and they moved several companies from one datacent

Re: 2020 Datacenter Move: Request for comments

Dne 01. 10. 19 v 9:53 Peter Robinson napsal(a): Warrantee generally doesn't cover moves but the DC shipping company should have insurance to cover breakages they cause as mistakes happen. It is hard to claim something if the package does not have any visible damage. And I guess you will not put

Re: [PATCH] postgresql_server / db-koji01: Adjust a bunch more for performance.

Dne 11. 10. 19 v 17:28 Kevin Fenzi napsal(a): config and drop the vm back to 32gb memory, but it seems kind of crazy that more memory would cause more slowness. ;( Can this be caused by swappiness? More memory, the same swappiness ratio, it can cause more IO. I would try to lower swappiness.

Re: The packages app has a short runway

Dne 25. 10. 19 v 20:44 Randy Barlow napsal(a): There appears to be work starting on a brand new implementation: https://github.com/xsuchy/fedora-packages-ng This version looks like it'll be Python 3 compatible, though it is quite new. We can keep it in mind, thanks for sharing! Yes. Give me f

OpenStack images cleanup

In Openstack we have long list of images, which can be deleted. Or likely deleted. These are clearly old, and I will wipe it away on Monday unless somebody say otherwise: Fedora-Cloud-Base-28-1.1.ppc64 Fedora-Cloud-Base-28-1.1.ppc64le Fedora-Cloud-Base-28-1.1.x86_64 Fedora-Cloud-Base-Rawhide-2

Re: The packages app has a short runway

Dne 21. 11. 19 v 23:54 Kevin Fenzi napsal(a): > I hope we can run it in openshift? Yes. No problem with that. -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys signature.asc Description: OpenPGP digital signature

Re: OpenStack images cleanup

-swift_store 138G 107G 25G 82% /srv/node/device1 Miroslav Dne 20. 11. 19 v 9:20 Miroslav Suchý napsal(a): > In Openstack we have long list of images, which can be deleted. Or likely > deleted. > > These are clearly old, and I will wipe it away on Monday unless somebody say > otherwi

status.fedoraproject.org

Hi. For long time, I plan to do something about https://status.fedoraproject.org/ I think that manual updates of this page does not reflect the capabilities of these century. My question is: do we want to go SasS way? I found https://www.statusdashboard.com/pricing which would cost us $99 pe

Re: status.fedoraproject.org

Dne 28. 11. 19 v 1:29 Kevin Fenzi napsal(a): > I am missing what capabilities you are wanting it to > have? * current page shows "Everything is OK" even when some service does not work. I would at least expect some orange text "There seems to be some problems, not acknowledged by admins yet". * I

Re: status.fedoraproject.org

Dne 30. 11. 19 v 21:31 Kevin Fenzi napsal(a): > can't we just point them to the nagios > page? That is great idea. And to have there link to outage calendar as well. > But how do you map those? > Some examples: > > * If a mirrorlist alerts as down that does not mean the service is down > to

Re: status.fedoraproject.org

Dne 03. 12. 19 v 11:34 Miroslav Suchý napsal(a): >> can't we just point them to the nagios >> page? > That is great idea. And to have there link to outage calendar as well. I sent a PR and you can see it live now at: https://status.fedoraproject.org/ Thanks Mikolai for qui

loading of vars/all/

Hi, we have in various PB: - include_vars: dir=/srv/web/infra/ansible/vars/all/ ignore_files=README - import_tasks: "{{ tasks_path }}/yumrepos.yml" In commits: * 5999880b9 add tag, without a tag this load is skipped when using -t config * ae2e32a3c include all/vars only once I moved the li

datacenter=aws

e does not modify fedora*.repo It is probably needed for centos and other, but I needed just this. Miroslav Přeposlaná zpráva Předmět: [ansible] do not modify fedora*.repo when deploying in AWS Datum: Fri, 14 Feb 2020 13:27:04 + (UTC) Od: Miroslav Suchý Komu: sys

Re: When adding hosts to ansible please first update DNS

Dne 17. 02. 20 v 21:50 Stephen John Smoogen napsal(a): > Because ip addresses can change, and we do not have time to fix it in > multiple places, That was me. We will be adding 9 machines. One by one. So my intention was to go with IP and then after we are done (one week) flip it to dns. But OK

new task for creating swap file

I created new task for creating swap file and mount it. https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/tasks/swap.yml 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: - datacente

Re: The packages app has a short runway

Dne 28. 03. 20 v 1:09 Kevin Fenzi napsal(a): > Hey, any news on this? I guess the problem is as always time. > > How far along is it? Could we run a demo/dev version in communishift? Yes. Time :( I have this as huge debt. I will try to prepare something. But still I have "just" the page which sh

Demo of new Fedora Packages

It took longer than expected, but I have something to show. Finally! Live demo: http://35.170.54.152/ Some tabs may not work now because the server are being migrated. Search database is snapshot from May and may not contain all packages. Main changes: * Python3 ! * usage of PatternFly * removed

Re: Demo of new Fedora Packages

Dne 10. 06. 20 v 10:33 Michal Konecny napsal(a): > * Home link in bottom of the page throws 404 > (http://35.170.54.152/url_for('coprs_ns.coprs_show')) > * Input / in search field throws 500 > * Input ? in search field throws 500 > * I tried * as input and I got over 900 results, but I only saw fi

Re: Demo of new Fedora Packages

Dne 16. 06. 20 v 0:40 Kevin Fenzi napsal(a): > So, can this run as a openshift app? Yes. As soon as it will be back. > I assume it uses madpi for things? MDAPI, PDC. -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys signature.asc Description: OpenPGP dig

Re: What is our technical debt?

Dne 25. 06. 20 v 21:27 Pierre-Yves Chibon napsal(a): > What else would we want in there? Automate branching. Or to be more general - automate new release. The whole process include way too many manual steps. Allow people to create groups in FAS without the need to create infra issue. -- Mirosl

Re: What is our technical debt?

Dne 30. 06. 20 v 9:44 Pierre-Yves Chibon napsal(a): > What are you talking about here? The Fedora release process? The > mass-branching > in dist-git? This. And creating new gpg keys, new mock configs, new tags in Koji, add release to retrace.f.o, Copr, ... I have a dream where you just bump up

Re: packages app

Dne 16. 07. 20 v 21:56 Brendan Early napsal(a): > and would time out if an external service took too long to respond. Only if you wanted to list builds, bugs the overview page is more or less static (i.e. it is rendered just from local DB). Fedora-packages-static does not list them at all. Th

s390x for EPEL

What is using Koji to build EPEL builds for s390x. We want to enable s390x in Copr. It is without problem for Fedora, but we cannot do that for EPEL, because there is no CentOS for s390x. Do we have entitlements for RHEL I can use? Or we have some local repo? Something completely different? --

Re: s390x for EPEL

Dne 27. 07. 20 v 16:50 Stephen John Smoogen napsal(a): > Can you use CleFOS for s390x? This? https://hub.docker.com/_/clefos/ I will try to rather use RHEL directly. I will see if I can get the entitlements. -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys _

Re: packages app

Dne 28. 07. 20 v 1:18 Brendan Early napsal(a): > How are you getting the data in ng?! From a clean state on my computer, The code remained unchanged. The most time the code spend quering PDC. Here: https://github.com/xsuchy/fedora-packages-ng/blob/master/fedoracommunity/search/index.py#L212 >

Re: s390x for EPEL

Dne 27. 07. 20 v 21:46 Kevin Fenzi napsal(a): > Can you explain how you plan to do Fedora s390x builds? Emulation? Yes, emulation. -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys signature.asc Description: OpenPGP digital signature ___

Buildsystem indentification

FYI Mock 2.5 has been just released and contains https://github.com/rpm-software-management/mock/pull/608 which set different user agent for DNF when DNF is used by Mock. This may allow you to differ Mock from users when creating statistics about downloads from repo. -- Miroslav Suchy, RHCA Red

Heads-up: New dist-git release

FYI: There is new dist-git release: https://github.com/release-engineering/dist-git/wiki/Release-1.16 Clime built it and submitted to Bodhi. From the release notes: * Added support for fedora-messaging. Fedmsg is still possible, but it is listed as soft requirement (Suggest). * spec twe

Re: DKIM & fedora lists

Dne 03. 11. 20 v 18:13 Dominique Martinet napsal(a): > So I was wondering how do people deal with that? We have been dealing with that in Copr too (some people reported that they did not get emails). In our case, it seems that emails sent to RH (this is what we can test) get correctly to those o

Re: Fedora packages site down

Dne 18. 11. 20 v 2:11 Kevin Fenzi napsal(a): > We are close to replacing this app with a new setup... > > see the 'packages app' thread in this very list. ;) Did we come to conclusion which app (out of these two) we are going to deploy? If that will be the fedora-packages-ng I will be happy to

Re: Fedora packages site down

Dne 24. 11. 20 v 22:53 Kevin Fenzi napsal(a): > Miroslav: what do you think? I am not personally attached to any solution. Whatever has wider consensus work for me. -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys ___

Re: ssh git access to src.fedoraproject.org feedback

Dne 03. 03. 21 v 22:53 Kevin Fenzi napsal(a): * All users in the 'packager' group have accounts on pkgs01.iad2 * All these users have a 'wrapper' on their ssh key that runs the pagure wrapper that checks who they are, etc. Cons: * only packagers have accounts for ssh, so non packagers just get p

Postgresql server in aws.f.o

Hi. In Copr we use postgresql on copr-frontend. I decide that it is time to split it off to separate server. I am going to create new machine in AWS and deploy postgresql there. I have several open questions: * is there interest in having it as general sql server in AWS datacenter for some oth

Re: Postgresql server in aws.f.o

Dne 15. 03. 21 v 17:05 Stephen John Smoogen napsal(a):   * I would love to run the server on RHEL 8. That should be completely fine according to https://www.redhat.com/en/blog/extending-no-cost-red-hat-enterprise-linux-open-source-organizations

Re: Postgresql server in aws.f.o

Dne 15. 03. 21 v 17:28 Kevin Fenzi napsal(a): On Mon, Mar 15, 2021 at 05:20:02PM +0100, Miroslav Suchý wrote: Dne 15. 03. 21 v 17:05 Stephen John Smoogen napsal(a):   * I would love to run the server on RHEL 8. That should be completely fine according to https://www.redhat.com/en

Where to report accounts.fedoraproject.org issues

I used the new accounts.fedoraproject.org for the first time today (btw it is neat). But I immediately spot first issue. I struggle to find where to report it. It is more application issue and not operational, so I hesitate to report it as fedora-infra issue. Where I can report it? Can someone

Re: status.fp.org concept

Dne 03. 05. 21 v 17:18 Stephen John Smoogen napsal(a): The reason we are changing is because of that list. Too many people expect us to know instantly that something is broken, something like https://uptimerobot.com/ that rocky linux uses. They also expect us to be 2

Re: status.fp.org concept

Dne 19. 05. 21 v 10:05 Ryan Lerch napsal(a): What is this link? I didn't see it on the old status when i was re-implementing status https://web.archive.org/web/20210414105928/https://status.fedoraproject.org/ Oh, it already disappeared during datacenter migration. This: https://web.archive.o

Re: status.fp.org concept

Dne 19. 05. 21 v 20:45 Kevin Fenzi napsal(a): You mean the link to nagios? Or ? Yes. The link to older outages is not needed with new design. I'm a bit worried linking to nagios there will confuse people... Why? When something does not work (for me) then I go to status.f.o, then to Nagios

RHEL8 for Copr builders

With the sunset of CentOS8 we want to allow builds on top real RHEL in Copr. Now that the RH Developer program is known, what are the option? Do we already use it somewhere? Or I will be the first to use it? :) I need it accessible from AWS so the repos we use in Koji are likely out of the quest

Re: planet

Dne 01. 03. 22 v 22:28 Kevin Fenzi napsal(a): So, I can think of a number of options and would love everyone who has thoughts on it to chime in: Thank you for kicking this off. 2. Switch to pluto and use account system 'website' fields of contributors. We could likely shove it in openshift and

Re: on rpms

Dne 23. 05. 22 v 20:57 Kevin Fenzi napsal(a): However, now a days we have a number of new apps that are deployed in openshift and aren't using rpms, but pip or s2i or other things. Regarding pip applications - we have pyp2rpm and pyp2spec which can convert to rpm easily. And we have  https://

Re: Software Bill of Materials for Fedora

Dne 11. 07. 22 v 4:53 Jason Shepherd napsal(a): Red Hat Product Security are building an application called Component Registry to meet the requirements set out in the recent Executive Order 14028 [1], "Improving the Nation's Cybersecurity". The executive order requires that software producers

Re: repos.fedorapeople.org

Dne 29. 12. 22 v 10:41 Casper napsal(a): Hi, COPR is awesome and provides online repositories, with a perfect integration in dnf. How about to close"https://repos.fedorapeople.org/"; ? It seems very old... Icon Name Last modifi

Re: repos.fedorapeople.org

Dne 09. 01. 23 v 7:12 Thorsten Leemhuis napsal(a): I tried a few (three? four?) years ago and there were iirc three showstoppers back then. I'm sure I wrote them down somewhere, but I can't find it right now. 🙁 But I think I remember one: It iirc (and afaik back then) was not possible to build p

Re: repos.fedorapeople.org

Dne 09. 01. 23 v 7:38 Thorsten Leemhuis napsal(a): That made me remember the biggest showstopper: I regularly push the results of one build to two different repositories (which ones depends on the phase of the kernel devel cycle and if Fedora is shipping the latest stable series). To explain: c

Re: repos.fedorapeople.org

Dne 09. 01. 23 v 13:12 Thorsten Leemhuis napsal(a): Either I'm missing something or your explanation is missing one important detail: can I rename a project once I tested the newly built packages so that users of my repos get the latest packages with the next "dnf update" without doing anything?

Re: repos.fedorapeople.org

Dne 09. 01. 23 v 13:33 Thorsten Leemhuis napsal(a): 1) Create project "kernel-vanilla-mainline" in Copr 2) Create project "kernel-vanilla-mainline-wo-mergew" in Copr and in settings set:  * external repositories: copr://user/kernel-vanilla-mainline  * Runtime dependencies: copr://user/kernel

AWS gp2 -> gp3

tl;dr I want to change **all** storage types in AWS from gp2 to gp3 next week. The recent Change proposal   https://fedoraproject.org/wiki/Changes/CloudEC2gp3 brought to my attention that gp3 is actually faster and cheaper than gp2. The comparision is as follows: gp2:  * $0.10 per GB-month

Re: AWS gp2 -> gp3

Dne 01. 04. 23 v 10:45 Miroslav Suchý napsal(a): gp2:  * $0.10 per GB-month gp3: I forgot to add price for gp3: $0.08 / GB-month Miroslav ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to

Re: AWS gp2 -> gp3

Dne 01. 04. 23 v 20:27 Kevin Fenzi napsal(a): Should we stop uploading 'standard' and 'gp2'? I mean, is there any reason anyone would want to use one of those? I find it just confusing that there's multiple types for each image. If we can, I'd say we should just do gp3? standard is magnetic vol

Re: AWS gp2 -> gp3

Dne 03. 04. 23 v 19:37 Kevin Fenzi napsal(a): fedimg is the thing that uploads the official cloud images, so if it does gp3, then the fedora images are gp3. :) The volume types are passed on command line.. but if not, then it is read from the config... that I modified. OMG I screwed that! And

Re: AWS gp2 -> gp3

Dne 04. 04. 23 v 23:50 Kevin Fenzi napsal(a): I'm still unsure if that means we only do gp3 or what is the list of ones we do after this change? Depends on your use case. For Copr we use gp3 for all volumes but - copr-dist-git (5TB) and copr-be data volume where we store dnf repositories (3*12

Re: AWS gp2 -> gp3

Dne 05. 04. 23 v 19:24 Kevin Fenzi napsal(a): Currenly we upload 'standard' and 'gp2'. I failed to find what "standard" means. Likely one of the magnetic ones, but don't know which one. Should we do 'standard' and 'gp3'? or 'sc1' and 'gp3'? Yes. I guess thats really for the cloud sig to d

Re: AWS gp2 -> gp3

Dne 04. 04. 23 v 23:47 Kevin Fenzi napsal(a): I changed all Copr volumes to gp3 already. After the Fedora release and after the freeze I will migrate all remaining volumes. Sure, agreed. I have started migrating the volumes. Miroslav ___ infrastruct

<    1   2   3   >