Re: Freeze Break request: update *.apps.ocp.fedoraproject.org cert
On Wed, Sep 06, 2023 at 06:56:36AM -0400, Stephen Smoogen wrote: > On Wed, 6 Sept 2023 at 06:51, Sandro wrote: > > > On 05-09-2023 21:53, Kevin Fenzi wrote: > > > I already have the cert ready to push into ansible-private, just need > > > +1's to run the proxies playbook and update the cert there. > > > > Not sure if my vote counts, but updating certs seems low risk: > > > > +1 > > > > My vote no longer counts but I agree with Sandro. This is low risk and > darknao and others are available for backup. Thanks everyone. Pushing it out now. kevin signature.asc Description: PGP signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
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 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Freeze Break request: update *.apps.ocp.fedoraproject.org cert
On Wed, 6 Sept 2023 at 06:51, Sandro wrote: > On 05-09-2023 21:53, Kevin Fenzi wrote: > > I already have the cert ready to push into ansible-private, just need > > +1's to run the proxies playbook and update the cert there. > > Not sure if my vote counts, but updating certs seems low risk: > > +1 > My vote no longer counts but I agree with Sandro. This is low risk and darknao and others are available for backup. -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Freeze Break request: update *.apps.ocp.fedoraproject.org cert
On 05-09-2023 21:53, Kevin Fenzi wrote: I already have the cert ready to push into ansible-private, just need +1's to run the proxies playbook and update the cert there. Not sure if my vote counts, but updating certs seems low risk: +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: PDC replacement proposal
On Mon, Sep 04, 2023 at 04:51:22PM +0200, Tomas Hrcka wrote: > Hello all, it took us a few years but we are finally getting rid of the PDC > project. Thanks to the ARC research we identified use cases in our tooling > and proposed solution. > > The essential functionalities currently provided by PDC will be > re-implemented in other applications within our release infrastructure, as > there are no immediate plans for their replacement and are currently > maintained > > This work is anticipated to span several months for completion. However, > before we embark on this endeavor, > > we would like to proactively share our proposed solution with all of you > and gather your valuable feedback. > > Below, we outline our strategy to preserve the core functionality of PDC by > leveraging existing applications within our ecosystem. > > Current uses of PDC: > > Currently, we rely on the Package Database (PDC) for various data > management tasks, including: > > >1. > >Critical Path Package Tracking: Bodhi leverages PDC to track packages on >the critical path. >2. > >Retirement of Packages and Service Level Agreements (SLAs): PDC assists >in managing the retirement of packages and their associated SLAs. Hmm, what SLAs? With the removal of modularity, the idea of SLAs also died. Packages are supported until the release for which they are built goes EOL. So this whole idea and related functionality is not needed. >3. > >Metadata for Nightly Composes: Our Release Engineering and Fedora >Quality Assurance teams rely on PDC for metadata related to nightly >composes. Zbyszek ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Cleaning infra groups on Pagure and GitHub
That sounds like a reasonable way to do it. To determine the activity I was using audit log for organization on GitHub, but it doesn't seem to work very well. In case of Pagure I was just looking at user activity and if there weren't any on infra repos in last year. Michal On 05. 09. 23 17:16, Kevin Fenzi wrote: On Fri, Sep 01, 2023 at 02:59:12PM +0200, Michal Konecny wrote: Hi everyone, I did a cleaning in Fedora infra groups in both Github (fedora-infra organization https://github.com/fedora-infra) and Pagure (fedora-infra group https://pagure.io/group/fedora-infra). I removed the people that were inactive in the last year. I also removed people from infra-sig FAS group (https://accounts.fedoraproject.org/group/infra-sig/) I only left the same members as in fedora-infra pagure group (I didn't add any). I thought that those groups should be synced, but it doesn't seem like they are. Is this correct? If I accidentally removed somebody who should be in those groups, let me know and I will add you back. Thanks for doing the cleanup. I think perhaps we should try and do this more regularly (once a year? twice a year after releases?) and use a more open method. I like the method nb used for clearing out groups a while back: * Identify the potentially inactive people * Open a ticket explaining that we are removing inactive people and @mention all of the people on the list. * If they see it and decide they want to be active again, they can comment in the ticket about that * After a week or whatever we remove everyone who hasn't responded. That gives people a chance to notice and become active again and also prevents any surprize when they are removed. Thoughts? kevin ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue