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

Images in Fedorainfracloud.org are not in playbook

) but it 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

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

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

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

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

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

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

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

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

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

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

Re: VDO

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

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:

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

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

. 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/backend/files

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

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

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.

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-old

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

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

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

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: 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 >>

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 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

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 quick re

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

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

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

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: 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". *

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.

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: -

datacenter=aws

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: sysadmin-memb

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

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

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

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

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: 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. --

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

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

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: 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

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 >

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: 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.

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: 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: 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

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

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

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:

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

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

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

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

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: 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

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

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

AWS Instances without tag FedoraGroup=*

According our SOP https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/aws-access/#_role_and_user_policies Users MUST tag resources with their FedoraGroup tag within one day, or the resource may be removed. I created a small script and queried all resources in all regions for

Re: AWS Instances without tag FedoraGroup=*

Dne 06. 09. 23 v 1:05 Kevin Fenzi napsal(a): * fedora-packages-ng (test) (i-0f15e4c4b9a49be4a) I don't think this one is needed anymore. Right. Not needed. Terminated. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys

Re: AWS Instances without tag FedoraGroup=*

Hi Andrei, You have in AWS under Fedora's account in us-east-2 region instance i-030bd89ccd0a66013. At least this instance has your ssh key. Otherwise we have no infromation about this instance. If you are still using this instance, please add the tags:

Re: AWS Instances without tag FedoraGroup=*

Hi Simon, You have in AWS under Fedora's account in ap-northeast-1 region instance i-0399e6de6e283c229. At least this instance has your ssh key. Otherwise we have no infromation about this instance. If you are still using this instance, please add the tags:

Re: AWS Instances without tag FedoraGroup=*

Dne 08. 09. 23 v 18:11 Kevin Fenzi napsal(a): Should I mail testing farm folks about this? Or would you like to? I will ping TestingFarm people in morning. But I will welcome if you can write Centos guys. I do not know who is the right contact. -- Miroslav Suchy, RHCA Red Hat, Manager,

Re: AWS Instances without tag FedoraGroup=*

Dne 11. 09. 23 v 6:45 Fabian Arrotin napsal(a): AFAIK the ec2 instances in the .centos.org domain are all tagged though, so do you have a list of ec2 instances/volumes that are really from centos and not tagged properly ? In a previous mail I saw something like "centos stream builders"

Re: AWS Instances without tag FedoraGroup=*

Dne 08. 09. 23 v 18:11 Kevin Fenzi napsal(a): I have no idea what to do with the rest. E.g., vol-ef097386 from eu-west-1. Not attached to anything. No tags. No reference in ansible.git. No information.The only thing that comes to my mind is: make a snapshot, tag the snapshot with

Re: AWS - strange error: volume in use, but is not attached

Dne 13. 09. 23 v 20:39 Kevin Fenzi napsal(a): https://ap-southeast-1.console.aws.amazon.com/ec2/home?region=ap-southeast-1#VolumeDetails:volumeId=vol-495d4a40 i.e. vol-495d4a40 in ap-southeast-1 cannot be deleted, because is "in-use". And I can only "detach" or "force detach", but there is no

Re: AWS Instances without tag FedoraGroup=*

Dne 11. 09. 23 v 6:45 Fabian Arrotin napsal(a): I can probably help for that  AFAIK the ec2 instances in the .centos.org domain are all tagged though, so do you have a list of ec2 instances/volumes that are really from centos and not tagged properly ? In a previous mail I saw something like

Re: AWS Instances without tag FedoraGroup=*

I have cleanup a lot. I notified Testing farm, they will tag their resource soon. BTW if you are in CC, then you likely own one of the resources in AWS. Please add tag FedoraGroup=* to it. Otherwise it may be deleted. The remaining stuff is: Region: ca-central-1 Instances: (name, id,

AWS - strange error: volume in use, but is not attached

When cleaning the old volumes I find strange error This volume: https://ap-southeast-1.console.aws.amazon.com/ec2/home?region=ap-southeast-1#VolumeDetails:volumeId=vol-495d4a40 i.e. vol-495d4a40 in ap-southeast-1 cannot be deleted, because is "in-use". And I can only "detach" or "force

Re: AWS Instances without tag FedoraGroup=*

Dne 07. 09. 23 v 20:49 Kevin Fenzi napsal(a): Nice! I think dkirwan should know about Discourse-test and mobrien should know about mobrien-test, and I think the rest are centos ones? Hmm, not everything: Region: ca-central-1 Instances: (name, id, owner) Volumes - [id (attached to instance,

AWS discontinue IAM...

From https://us-east-1.console.aws.amazon.com/iamv2/home?region=us-east-2#/home Attention: Extended Deadline for Updating Your Access Permissions - December 11, 2023 AWS has discontinued use of old IAM permissions for Billing, Cost Management, and Accounts consoles. If you do not take action,

AWS Snapshots without FedoraGroup tag

We have (almost) all instances and volumes properly tagged. Now let check Snapshots. OMG - there are A LOT of them. The list has 97k lines! Because of the size I will not attach it and instead provide link to download it: https://k00.fr/8p59mvcw If you help me to identify something, I can

Re: AWS usage per group

Dne 31. 10. 23 v 12:30 Frank Ch. Eigler napsal(a): Hi - http://debuginfod1.aws.centos.org/ uses io1 type volume. This is suboptimal as io2 is better. But from monitoring the machine does not utilize the IOPS and the price for this volume is ten times more than gp3 which would provide

Re: AWS Snapshots without FedoraGroup tag

Dne 03. 11. 23 v 2:06 Dusty Mabe napsal(a): We'll clean up the ones we do not need soon. I'm sorry it is taking longer than we thought it would to get garbage collection implemented. Thank you. * Fedora-Cloud-Base-29-20190729.0.x86_64-hvm-us-east-1-standard-0 - is this snapshots used to

Re: AWS Snapshots without FedoraGroup tag

Dne 03. 11. 23 v 16:15 Dusty Mabe napsal(a): Does that mean we should set ours to FedoraGroup=coreos ? Yes. The values are not defined. I use the values to group the resources together. If you want you can even use two labels: coreos-dev, coreos-ci. Or just coreos. It is up to you. --

AWS usage per group

Here comes October edition of resources running in AWS. It snapshot of resources running today's morning. Some TestingFarm resources are not included because they still do not tag properly all resources. Few notes: http://debuginfod1.aws.centos.org/ uses io1 type volume. This is suboptimal

Re: AWS Snapshots without FedoraGroup tag

Dne 06. 11. 23 v 20:45 Kevin Fenzi napsal(a): Can we get what volume they are snapshots of? Perhaps the volume name would help us figure things out? Most of the 6GiB volumes like snap-098326d474a07f706 is snapshot of vol- which does not exist (this snapshot is from 2018) Even if I

Resource usage in AWS per group

Now when we have all instances and volumes tagged. I can say who is using what resources. Below you will find the aggregated overview of resources we are using in AWS. If you will not mind, I plan to send this overview every month. My intention is to be able to see the overview of long-term

Re: AWS Instances without tag FedoraGroup=*

 = Current status We have almost everything tagged with FedoraGroup. There are some small leftovers (see bottom of this email). If no one stop me (or tag it) I will delete them by end of next week. There may appear some new volumes without propper tags. Because Kubernetese cluster does not

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  

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 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:

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 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

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:

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

AWS volume cleanup

When I have been working in the AWS console I noticed we have lots of volumes that are: not described, not owned and not attached. Sometimes even combination of all of these. And some of such volumes have been created in 2020. Here is screenshot of suspicious volumes: https://k00.fr/1cn48fze

Re: AWS volume cleanup

Dne 24. 04. 23 v 18:51 Kevin Fenzi napsal(a): Did you only look at us-east-1? There might be more in other regions? (although less I suspect). Yeah, we have lots of volumes in Ohio. Yes, I am checking other regions. FYI I started manually with the biggest volumes. And I pause between them.

awscli2 and Fedora sso

Has anyone use awscli2? How did you configure it to use Fedora SSO? I played with it, but with not luck. BTW awcli2 is now in package review process and is available at https://copr.fedorainfracloud.org/coprs/g/fedora-review/fedora-review-2189420-awscli2/build/5851296/ Miroslav

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 ___

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

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

<    1   2   3   >