Re: Deleting old AMIs in AWS

On 4/23/24 12:04, Miroslav Suchý wrote: > Dne 23. 04. 24 v 3:31 odp. Dusty Mabe napsal(a): >> If you don't mind give us until next week to finish up loose ends on this. >> We are already >> adding the FedoraGroup=coreos tag to our snapshots/AMIs as we create them >

Re: Deleting old AMIs in AWS

On 4/4/24 05:11, Miroslav Suchý wrote: > Dne 04. 04. 24 v 4:06 dop. Dusty Mabe napsal(a): >> If you don't mind let me try to get the FedoraGroup tag added to our CoreOS >> AMIs first. >> >> I'll try to set up something to get that done this week. > >

Re: Different owner of some Fedora-Cloud-Base images in AWS?

On 2/12/24 05:14, Miroslav Suchý wrote: > I was wondering why I cannot tag some images in AWS and I found that some GA > images in AWS have different owner. > > I.e. all our images has > > Owner account ID 125523088429 > > But e.g. ami-0e4e634d022c1a3f8 in ap-southeast-4 region has owner id

Re: HEADS UP - deletion of Fedora Atomic Hosts AMIs

On 2/7/24 13:39, Miroslav Suchý wrote: > Dne 09. 12. 23 v 9:21 Miroslav Suchý napsal(a): >> As mentioned in previous thread - I plan to delete from AWS all Fedora >> Atomic Hosts and related snapshots. >> >> Atomic Host EOLed at 2019 and we have the images stored elsewhere too. >> >> To protect

Re: AWS Snapshots without FedoraGroup tag

On 11/3/23 03:00, Miroslav Suchý wrote: > 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. >

Re: AWS Snapshots without FedoraGroup tag

On 11/2/23 05:32, Miroslav Suchý wrote: > 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/8p59

Re: Meeting Agenda Item: Introduction Blake Ridgway

On 10/11/23 09:13, Blake Ridgway wrote: > Good day Fedora Infrastructure team, > > I'm Blake Ridgway. My IRC alias is /Zormak/ and my Matrix alias is > /@blakeridgway:fedora.im. /I am reaching out to introduce myself to the > Fedora Infrastructure team and express my enthusiasm for collaborati

Re: Migration from registry.fp.o to quay.io

On 9/5/23 06:56, Jakub Čajka wrote: > I have one concern about quay.io, more of a double check that quay supports > manifest lists for/in image formats that fedora is using. IIRC there have > been some limitations on how manifest lists can be used, created in quay.io. > We are using manifest

Re: Lot of snapshots in AWS Sydney region

On 7/12/23 19:03, Miroslav Suchý wrote: > Dne 13. 07. 23 v 0:26 Dusty Mabe napsal(a): >> If you say it's an issue then hopefully we can give this some priority and >> get to it soon. >> >> Removing the "old ones" isn't that easy to do. Our product

Re: Lot of snapshots in AWS Sydney region

On 7/12/23 16:17, Miroslav Suchý wrote: > Dne 11. 07. 23 v 15:53 Dusty Mabe napsal(a): >> Apologies for not responding sooner. Actually for some reason this is the >> first email I've seen >> in the thread so maybe I need to check my spam filters. Either way, >>

Re: Lot of snapshots in AWS Sydney region

On 7/11/23 04:21, Miroslav Suchý wrote: > Dne 05. 07. 23 v 21:17 Kevin Fenzi napsal(a): >> On Mon, Jul 03, 2023 at 04:02:02PM +0200, Fabian Arrotin wrote: >>> On 03/07/2023 06:39, Miroslav Suchý wrote: I was going through our spending in AWS and I found that we spent a lot in Sydney reg

Re: Freeze break request: moving /mnt/koji/compose/

On 2/22/23 12:51, Kevin Fenzi wrote: > Greetings. > > As some of you may know, our fedora_koji volume is hitting up against > some limits (namely the netapp 100TB per volume limit). If it hits 100TB > used, the netapp folks tell me it will go offline and we will need to do > special things to fr

Re: fedimg

We have/(had?) an effort to replace fedimg in the cloud WG. https://pagure.io/cloud-sig/issue/301 Some people have worked on it off and on but it's stalled. Dusty On 6/7/21 1:38 PM, Kevin Fenzi wrote: > Hey everyone. > > We have a application called fedimg that takes our images and uploads >

[PATCH 2/2] openshift-apps/compose-tracker: switch to Fedora 31

--- .../openshift-apps/compose-tracker/templates/imagestream.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/openshift-apps/compose-tracker/templates/imagestream.yml b/roles/openshift-apps/compose-tracker/templates/imagestream.yml index 9c889c0af..fed50e16f 1006

openshift-apps/compose-tracker: add cverna to app owners, switch to Fedora 31

___ 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

[PATCH 1/2] openshift-apps/compose-tracker: add cverna to app owners

--- playbooks/openshift-apps/compose-tracker.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/playbooks/openshift-apps/compose-tracker.yml b/playbooks/openshift-apps/compose-tracker.yml index 72691f592..bcb6d8a8b 100644 --- a/playbooks/openshift-apps/compose-tracker.yml +++ b/playbooks/ope

Re: [PATCH] openshift-apps/docsbuilding: add dustymabe to owners

On 1/16/20 8:42 AM, Clement Verna wrote: > I have applied and deployed this patch. > > You should be all set now. Thanks All! ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le..

[PATCH] openshift-apps/docsbuilding: add dustymabe to owners

Considering we have CoreOS documentation. I'd like to be able to see the build processes to know when/if they are failing for any reason. --- playbooks/openshift-apps/docsbuilding.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/playbooks/openshift-apps/docsbuilding.yml b/playbooks/openshi

Re: [PATCH] aws-iam-policies: fcos-upload-amis: add ability to DescribeRegions

On 11/30/19 3:21 PM, Kevin Fenzi wrote: > On Wed, Nov 27, 2019 at 09:26:09AM -0500, Dusty Mabe wrote: >> pushed, can you update the policy in AWS? > > Done. > Thanks Kevin! Can we look at getting Mohan the permissions to d

Re: [PATCH] aws-iam-policies: fcos-upload-amis: add ability to DescribeRegions

pushed, can you update the policy in AWS? On 11/27/19 9:22 AM, Mohan Boddu wrote: > LGTM +1 > > On Wed, Nov 27, 2019 at 9:19 AM Dusty Mabe wrote: >> >> Need this since we recently changed to dynamically detect regions >> to upload to. See https://github.com/cor

[PATCH] aws-iam-policies: fcos-upload-amis: add ability to DescribeRegions

Need this since we recently changed to dynamically detect regions to upload to. See https://github.com/coreos/coreos-assembler/commit/ab3cae5 --- files/aws/iam/policies/fcos-upload-amis.json | 1 + 1 file changed, 1 insertion(+) diff --git a/files/aws/iam/policies/fcos-upload-amis.json b/files/a

Re: [PATCH] robosignatory.toml.j2: bump FCOS artifacts signing key to f31

On 11/25/19 9:47 AM, Jonathan Lebon wrote: > From: Jonathan Lebon > > FCOS is now rebased to f31. Bump the signing key accordingly. > > Signed-off-by: Jonathan Lebon > --- > roles/robosignatory/templates/robosignatory.toml.j2 | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff

Re: FBR bodhi-pungi: only run multi-arch SB on f31+

pushed and ran playbook Thanks! On 10/29/19 3:09 PM, Stephen John Smoogen wrote: > +1 .. now I found it. > > On Tue, 29 Oct 2019 at 14:19, Stephen John Smoogen wrote: >> >> I didn't see anything patched on there so I am not sure what to review. >> >> On

[PATCH] bodhi-pungi: only run multi-arch SB on f31+

This is a fixup for d7713e6 where mulit-arch was enabled. --- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index 640

FBR bodhi-pungi: only run multi-arch SB on f31+

[PATCH] bodhi-pungi: only run multi-arch SB on f31+ ___ 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.

Re: [PATCH 1/2] bodhi-pungi: F32 will be the next "branched"

4:13 PM Mohan Boddu wrote: >>> >>> No, with rawhide gating we are using bodhi to push rawhide builds as >>> updates, I think it might call it and cause some issues. >>> >>> On Thu, Oct 24, 2019 at 4:05 PM Dusty Mabe wrote: >>>> >>&

Re: [PATCH] new-updates-sync: sync multiarch silverblue ostree content

Thanks! Fixed the syntax error and pushed! On 10/24/19 5:06 PM, Rick Elrod wrote: > +1 after the syntax fix I mentioned inline. > > -re > > On 2019-10-24 15:56, Dusty Mabe wrote: >> --- >> roles/bodhi2/backend/files/new-updates-sync | 10 ++ >> 1

Re: [PATCH 1/2] bodhi-pungi: F32 will be the next "branched"

On 10/24/19 4:02 PM, Mohan Boddu wrote: > Just wondering, doesn't it affect rawhide composes, since rawhide is still 32? > IIUC the first time this will take any effect is when we start calling bodhi with '32' as the number (i.e. after we have branched and rawhide is now 33). Dusty __

[PATCH] new-updates-sync: sync multiarch silverblue ostree content

--- roles/bodhi2/backend/files/new-updates-sync | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync index d08c89301..9ad7628b8 100755 --- a/roles/bodhi2/backend/files/new-updates-s

FBR new-updates-sync: sync multiarch silverblue ostree content

[PATCH] new-updates-sync: sync multiarch silverblue ostree content ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs

[PATCH 2/2] bodhi-pungi: enable aarch64 and ppc64le for silverblue updates

--- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index 28b524a10..640ddf058 100644 --- a/roles/bodhi2/backend/templates/p

FBR: updates Silverblue in bodhi pungi config

[PATCH 1/2] bodhi-pungi: F32 will be the next "branched" [PATCH 2/2] bodhi-pungi: enable aarch64 and ppc64le for silverblue Now that F31 is a go we need to do a few things. One of them is enabling other architectures, which was done in rawhide and f31. This propagates it into bodhi. _

[PATCH 1/2] bodhi-pungi: F32 will be the next "branched"

Now that f31 is go we can use the final location for ostree repo input. Bump the variable so that it will only look at branched for f32. --- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/bodhi2/backend/templates/pungi

Re: communishift reinstall

On 10/19/19 7:49 PM, Kevin Fenzi wrote: > Greetings communishift group (and infrastructure list). > > I was working on the communishift cluster trying to fix it's failing to > upgrade as well as some cert issues, and managed to munge up the cluster > but good. ;( It's a tribute to the resillanc

Re: CPE Weekly: 2019-10-11

Thanks again for putting this out! The brief updates are really nice! Dusty On 10/11/19 1:57 PM, Aoife Moloney wrote: Hi everyone, Welcome to the CPE team weekly project update mail!

Re: CPE Team Weekly Update

On 9/27/19 9:18 AM, Aoife Moloney wrote: > Hi everyone, > > > I’d like to introduce myself first, my name is Aoife Moloney and I recently > started with the Community Platform Engineering (CPE) team. My role within > this team is going to be a hybrid role of a Product Owner / Project Manager.

Re: [PATCH] openshift/rbac: allow project owners to cancel-builds

On 9/30/19 9:24 AM, Luca BRUNO wrote: > This tweaks project-owners RBAC to allow updating a build, in order > to make `cancel-build` work. > > Ref: https://pagure.io/fedora-infrastructure/issue/8005 > Signed-off-by: Luca BRUNO > --- > roles/openshift/project/templates/role-appowners.yml | 2 ++

Re: Freeze Break Request: update openssl on proxy servers

On 9/17/19 1:46 PM, Kevin Fenzi wrote: > Greetings. > > I'd like to apply: > https://bodhi.fedoraproject.org/updates/FEDORA-2019-d51641f152 > > to our proxy servers and restart httpd on them. > > This is to fix: > > https://pagure.io/fedora-infrastructure/issue/8173 > https://bugzilla.redhat.

Re: State/future of the packages app

On 9/12/19 4:16 PM, Kevin Fenzi wrote: > On 9/12/19 1:12 PM, Adam Williamson wrote: >> On Thu, 2019-09-12 at 02:32 -0400, Neal Gompa wrote: >>> On Thu, Sep 12, 2019 at 2:28 AM Clement Verna >>> wrote: On Wed, 11 Sep 2019 at 15:06, Ankur Sinha wrote: > Hello, > > I wa

Re: Freeze Break Request: Fix typo in bodhi status variable

On 9/9/19 2:34 PM, Kevin Fenzi wrote: > Greetings. > > We have a variable in: > vars/all/FedoraBranchedBodhi.yaml > > thats used in our bodhi config to set the proper policies. > The template uses 'predeta' and 'postbeta'... but the variable was > updated to 'preBeta', which isn't going to work

Re: Freeze break request: update registry.redhat.io ip

On 9/9/19 2:06 PM, Kevin Fenzi wrote: > diff --git a/roles/hosts/files/os-hosts b/roles/hosts/files/os-hosts > index e9dc0a2..3c283e3 100644 > --- a/roles/hosts/files/os-hosts > +++ b/roles/hosts/files/os-hosts > @@ -1,4 +1,4 @@ > 127.0.0.1 localhost localhost.localdomain localhost4 > localhos

Re: Meeting Agenda 2019-09-05

On 9/4/19 2:00 PM, Stephen John Smoogen wrote: > > ``` > #topic Where to put these docs in the future? > #info infinote is going away and this is my 'private hackmd' > #info a new central doc place would be good. can someone set this up? > ``` More topics to discuss from the CoreOS teams: htt

FBR: hotfix robosignatory to fix ostree signing issue

We hit a bug every release where the directories haven't yet been created for the refs we want to sign [1]. The bug has been fixed in the latest code [2] but hasn't been deployed to prod yet. We'd like to deploy that small patch to prod so we can make sure we never hit this again. Dusty [1] http

Re: Subject: 'Meeting Agenda Item: Introduction T.C. Williams'

On 8/28/19 5:31 PM, T.C. Williams wrote: > Greetings Fedora Infrastructure Team, > > My name is T.C. Williams and my IRC nick is austinpowered. > Nice to meet you T.C.! Dusty ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.or

Re: Fedora 31 Beta freeze now in effect

On 8/27/19 3:38 PM, Kevin Fenzi wrote: > On 8/27/19 11:50 AM, Dusty Mabe wrote: >> >> >> On 8/27/19 2:21 PM, Kevin Fenzi wrote: >>> Greetings. >>> >>> we are now in the infrastructure freeze leading up to the Fedora 31 >>> Beta release. T

Re: Fedora 31 Beta freeze now in effect

On 8/27/19 2:21 PM, Kevin Fenzi wrote: > Greetings. > > we are now in the infrastructure freeze leading up to the Fedora 31 > Beta release. This is a pre release freeze. > > We do this to ensure that our infrastructure is stable and ready to > release the Fedora 31 Beta when it's available. >

Re: A few patches for bodhi pungi compose

On 8/23/19 12:19 PM, Kevin Fenzi wrote: > On 8/23/19 5:07 AM, Dusty Mabe wrote: >> [PATCH 1/3] bodhi-pungi: get rid of < f29 logic >> >> Some cleanup >> >> [PATCH 2/3] bodhi-pungi: branched is now f31 >> >> This fixes a compose issue: >

[PATCH 3/3] bodhi-pungi: add the f32 signing key

--- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 2 ++ 1 file changed, 2 insertions(+) diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index bd8ec6526..688badeee 100644 --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 +

[PATCH 2/3] bodhi-pungi: branched is now f31

Update the location so that our f30 updates composes work again. --- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index 4

A few patches for bodhi pungi compose

[PATCH 1/3] bodhi-pungi: get rid of < f29 logic Some cleanup [PATCH 2/3] bodhi-pungi: branched is now f31 This fixes a compose issue: https://pagure.io/releng/failed-composes/issue/53 [PATCH 3/3] bodhi-pungi: add the f32 signing key Future proofing. _

[PATCH 1/3] bodhi-pungi: get rid of < f29 logic

We are no longer building f28 so we can remove these if statements. --- .../bodhi2/backend/templates/pungi.rpm.conf.j2 | 18 +- 1 file changed, 5 insertions(+), 13 deletions(-) diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rp

Re: Access for dusty to sysadmin-main

On 8/20/19 11:52 AM, Clement Verna wrote: > > > Yes just to make sure there is no misunderstanding I am not trying to blame > anyone too and I am also keen on finding a better ways for these work to move > smoothly without the need for you to bug someone every day and without having > someon

Re: Access for dusty to sysadmin-main

On 8/20/19 10:33 AM, Stephen John Smoogen wrote: > > That 5 minute session isn't a 5 minute session to us. For us it is > usually 40-60 minutes of context swapping from what we were doing to > fixing your 5 minute thing to try to get back to the other thing to > going back to you.. but after som

Re: Access for dusty to sysadmin-main

On 8/20/19 10:18 AM, Clement Verna wrote: > On Tue, 20 Aug 2019 at 15:30, Dusty Mabe wrote: >> >> >> >> On 8/19/19 6:09 PM, Kevin Fenzi wrote: >>> >>> Well, this I think is related to our "agile transformation" (or if you >>> pr

Re: Access for dusty to sysadmin-main

On 8/19/19 6:09 PM, Kevin Fenzi wrote: > > Well, this I think is related to our "agile transformation" (or if you > prefer "reorganizing how we work"). Right now, you find it hard to get > stuff done because everyone is busy on other things, so you have to nag > us to get stuff done which makes

Re: Access for dusty to sysadmin-main

On 8/16/19 5:04 PM, Stephen John Smoogen wrote: > On Fri, 16 Aug 2019 at 16:40, Dusty Mabe wrote: >> >> I suspect this request might fall short, but I figure I'll start a dialog. >> > ... >> >> I'd like to help if possible, but I understand if my r

Access for dusty to sysadmin-main

I suspect this request might fall short, but I figure I'll start a dialog. With Fedora CoreOS needing some different services set up and more and more requests getting opened every day on the infra issue tracker, it would be nice if I could gain some more access within Fedora Infra to be able to h

Re: Bot Account for Bodhi Karma

On 8/15/19 2:49 PM, Pierre-Yves Chibon wrote: > On Thu, Aug 15, 2019 at 08:41:53AM -0400, Dusty Mabe wrote: >> >> >> On 8/15/19 5:16 AM, Tim Flink wrote: >>> After the Flock talk from the Facebook folks, they approached QA about >>> the idea of submitti

Re: Bot Account for Bodhi Karma

On 8/15/19 5:16 AM, Tim Flink wrote: > After the Flock talk from the Facebook folks, they approached QA about > the idea of submitting karma and/or test results from their internal > testing as a bot account. > > Is this something that is possible? I know that we have done bot > accounts at vari

Re: A Friday with Infra

On 8/8/19 6:29 AM, Michal Konecny wrote: > Good Morning Everyone, > > As you may remember from [1] the CPE team has started categorizing its > applications into the following categories: > > 1. We maintain it, we run it > 2. We don’t maintain it, we run it > 3. We don’t maintain it, we don’

Re: Sunset of infinote (Gobby) service

On 8/2/19 6:37 AM, Clement Verna wrote: > On Thu, 1 Aug 2019 at 19:46, Justin W. Flory wrote: >> >> On 8/1/19 3:34 AM, Clement Verna wrote: >>> Dear all, >>> >>> The Fedora Infrastructure is planning to retire the infinote [0] >>> service. This service allows text collaboration using the Gobby >

Re: Congrats to our new sysadmin-mainers

On 8/5/19 3:25 PM, Kevin Fenzi wrote: > I'm happy to announce that We have approved several folks into the > sysadmin-main group: > > mohanboddu 'Mohan Boddu' > cverna 'Clement Verna' > bowlofeggs 'Randy Barlow' > > This is the core group of trusted folks that high level access to most > everyt

Re: How to consume fedora-messaging?

On 6/10/19 12:06 PM, Adam Williamson wrote: > On Mon, 2019-06-10 at 09:24 +0900, Tristan Cacqueray wrote: >> On Mon, Jun 10, 2019 at 01:24 Igor Gnatenko wrote: >>> Hello, >>> >>> I have been trying to write some script which would listen on >>> generation of new repository / successful build is t

Re: [Fedocal] Reminder meeting : Fedora Infrastructure

I've added a topic to the Gobby for tomorrow's meeting: ``` #topic options for release artifact signing for Fedora CoreOS - dustymabe We are exploring options for signing our release artifacts for Fedora CoreOS. We have an open ticket where we have defined various options and narrowed down the o

RFC: Deploying coreos-koji-tagger in Fedora Openshift

This is a request for comments on deploying the coreos-koji-tagger service in Fedora OpenShift. The details for the request and what the service are in in the RFR ticket [1]. If it's sufficient to have the conversation there, I'd prefer that. https://pagure.io/fedora-infrastructure/issue/7870

Re: [PATCH] robosignatory: add aarch64 and ppc64le signing for silverblue

On 5/7/19 5:48 PM, Kevin Fenzi wrote: > On 5/7/19 11:24 AM, Dusty Mabe wrote: >> --- >> roles/robosignatory/files/robosignatory.production.py | 8 >> 1 file changed, 8 insertions(+) >> >> diff --git a/roles/robosignatory/files/robosignatory.production.p

[PATCH] robosignatory: add aarch64 and ppc64le signing for silverblue

--- roles/robosignatory/files/robosignatory.production.py | 8 1 file changed, 8 insertions(+) diff --git a/roles/robosignatory/files/robosignatory.production.py b/roles/robosignatory/files/robosignatory.production.py index a15b1e448..daeb9b876 100644 --- a/roles/robosignatory/files/rob

Re: Deprecating Autocloud

On 5/2/19 12:53 PM, Adam Williamson wrote: > On Thu, 2019-05-02 at 10:15 -0400, Dusty Mabe wrote: >> >> On 5/2/19 12:08 AM, Neal Gompa wrote: >>> On Wed, May 1, 2019 at 10:48 PM Dusty Mabe wrote: >>>> We plan to have testing at various stages of the CoreOS

Re: Deprecating Autocloud

On 5/2/19 12:08 AM, Neal Gompa wrote: > On Wed, May 1, 2019 at 10:48 PM Dusty Mabe wrote: >> We plan to have testing at various stages of the CoreOS build and delivery >> pipeline. We definitely plan to have FCOS taken care of using the existing >> kola testing utilit

Re: Deprecating Autocloud

On 5/1/19 10:20 PM, Adam Williamson wrote: > On Mon, 2019-04-29 at 18:57 +0530, Sinny Kumari wrote: >> On Mon, Apr 29, 2019 at 4:47 PM Kamil Paral wrote: >> >>> On Mon, Apr 29, 2019 at 11:39 AM Sinny Kumari wrote: >>> On Wed, Apr 24, 2019 at 12:19 AM Kevin Fenzi wrote: > Or

Re: PATCH: Setup for coreos-pool and coreos-release tags

On 5/1/19 1:24 PM, Mohan Boddu wrote: > CoreOS needs coreos-pool and coreos-release tags to build backported builds > and tag the builds that go into the release. > > More info: https://pagure.io/releng/issue/8294 > > Please review the following patch and let me know if it needs any changes.

Re: Deployment of plume in Fedora Infrastructure

On 4/22/19 4:19 AM, Sayan Chowdhury wrote: > Hi all, > > Over the last few months, I was working on integrating Fedora as a > sub-system to plume. This is to migrate from fedimg to plume, and > finally deprecating plume. > > The work on plume has been completed and over the next few days, I > p

Re: Deprecating Autocloud

On 4/29/19 9:27 AM, Sinny Kumari wrote: > > > On Mon, Apr 29, 2019 at 4:47 PM Kamil Paral > wrote: > > On Mon, Apr 29, 2019 at 11:39 AM Sinny Kumari > wrote: > > > > On Wed, Apr 24, 2019 at 12:19 AM Kevin Fenzi

Re: FBR: update python-tag2distrepo on bodhi-backend02

bump - can we get some votes on this? I would vote but my vote doesn't count :) On 4/16/19 5:10 PM, Mikolaj Izdebski wrote: > Problem: tag2distrepo fails to generate dist-repo for CoreOS > continuous builds [1] bacause CoreOS tags contain unsigned packages > and tag2distrepo can't handle them. >

Re: FBR: upgrade oz on builders

On 3/14/19 9:58 AM, Stephen John Smoogen wrote: > On Thu, 14 Mar 2019 at 09:55, Peter Robinson wrote: >> >> To deal with the cloud image issue I was originally going to resolve >> it slightly differently, I've not dealt with it in oz. the current >> "Fedora version" that pungi specifies (F-22) n

Re: [PATCH] Adjust bodhi pungi config to build AH only for <= F29

On 2/18/19 2:18 PM, Dusty Mabe wrote: > > On 2/18/19 12:29 PM, Sinny Kumari wrote: >> Updated patch with keeping repos list on separate lines and removed comma. > > LGTM > pushed and playbook ran ___ infrastructure mailing l

Re: [PATCH] Adjust bodhi pungi config to build AH only for <= F29

On 2/18/19 12:29 PM, Sinny Kumari wrote: > Updated patch with keeping repos list on separate lines and removed comma. LGTM ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lis

Re: [PATCH] Adjust bodhi pungi config to build AH only for <= F29

Mostly LGTM.. A few comments inline. On 2/18/19 11:40 AM, Sinny Kumari wrote: > We recently announced [1] that with upcoming FCOS, last major release of > Fedora Atomic Host is Fedora 29. This patch (avilable in email attachment) > contains changes in bodhi pungi config to build Fedora Atomic r

Re: Re-enable updates-testing ostree for Silverblue

On 1/8/19 4:25 PM, Kevin Fenzi wrote: > Looks fine to me. +1 Thanks Kevin > > If you can get it in before tonights push that would be great. > pushed and playbook ran! Dusty ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org

Re-enable updates-testing ostree for Silverblue

Now that pungi has been updated on the bodhi backend machines (https://pagure.io/fedora-infrastructure/issue/7484) I can re-enable updates-testing for silverblue. Also added some removal of code specific to f27. - bodhi-pungi: re-enable testing ostree for silverblue - bodhi-pungi: simplify now tha

[PATCH 2/2] bodhi-pungi: simplify now that f27 is EOL

Removes conditional logic that considers f27. --- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 23 ++- 1 file changed, 6 insertions(+), 17 deletions(-) diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index

[PATCH 1/2] bodhi-pungi: re-enable testing ostree for silverblue

This re-enables updates-testing composes for silverblue that were stopped in df5009d because of https://pagure.io/pungi/issue/1092 --- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 2 -- 1 file changed, 2 deletions(-) diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bod

Re: [PATCH] Add CDN testing cloudfront redirect for atomic repo

On 1/3/19 10:40 AM, Sinny Kumari wrote: > Hi, > > Currently, we are using two different cloudfront distributions to CDN content > for > /atomic/repo/objects/ and /atomic/repo/deltas/ . With the current setup we see > an issue https://github.com/ostreedev/ostree/issues/1541 . To overcome this >

[PATCH] bodhi-pungi: don't run silverblue compose for testing

This is a temporary hack to workaround https://pagure.io/pungi/issue/1092. Note this also just re-uses the f27 logic, which is no longer needed. --- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/bodhi2/backend/templat

Re: [PATCH] bodhi-pungi: pass in ostree_oskey to fedora-lorax-templates

On 12/1/18 2:43 PM, Stephen John Smoogen wrote: > patch looks good. should apply ok. Merged and playbook ran. Thanks smooge ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@l

[PATCH] bodhi-pungi: pass in ostree_oskey to fedora-lorax-templates

This is needed because of a recent change to parameterize the key. https://pagure.io/fedora-lorax-templates/pull-request/30 --- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 1 + 1 file changed, 1 insertion(+) diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/back

Re: [PATCH] Silverblue manifest is now fedora-silverblue.yaml

On 11/30/18 11:29 AM, Mohan Boddu wrote: > LGTM +1 > pushed and playbook ran. thanks mohan ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Co

[PATCH] Silverblue manifest is now fedora-silverblue.yaml

--- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index 3f2608099..baed32f3f 100644 --- a/roles/bodhi2/backend/templates/pungi

ostree: silverblue manifest is now fedora-silverblue.yaml

Corresponding configs change is in: https://pagure.io/workstation-ostree-config/pull-request/115# This will require the bodhi machines to have the hotfixed pungi rpm with this fix: https://pagure.io/pungi/pull-request/1088 This was already hotfixed on the composer machines. Dusty ___

Re: [PATCH] Pull OSTree repo from compose/atomic/repo during AH ISO creation

On 11/12/18 10:26 AM, Mohan Boddu wrote: > +1 LGTM > > On Mon, Nov 12, 2018 at 9:50 AM Dusty Mabe <mailto:du...@dustymabe.com>> wrote: > > > > On 11/12/18 9:48 AM, Sinny Kumari wrote: > > We recently noticed inconstancy in OSTree v

Re: [PATCH] Pull OSTree repo from compose/atomic/repo during AH ISO creation

On 11/12/18 9:48 AM, Sinny Kumari wrote: > We recently noticed inconstancy in OSTree version for ppc64le ISO in compose > https://kojipkgs.fedoraproject.org/compose/updates/Fedora-29-updates-20181112.0/compose/ > . > OSTree version for ppc64le ISO was 29.2018.0 while expected was > 29.20181

Re: [FBR] Include updates-testing repo during bodhi u-t run

On 10/30/2018 04:26 PM, Kevin Fenzi wrote: > On 10/30/18 1:05 PM, Dusty Mabe wrote: >> >> >> On 10/30/18 1:47 PM, Kevin Fenzi wrote: >>> On 10/30/18 8:26 AM, Dusty Mabe wrote: >>>> >>>> >>>> On 10/29/18 2:43 PM, Kevin Fenzi wrote:

Re: [FBR] Include updates-testing repo during bodhi u-t run

On 10/30/18 1:47 PM, Kevin Fenzi wrote: > On 10/30/18 8:26 AM, Dusty Mabe wrote: >> >> >> On 10/29/18 2:43 PM, Kevin Fenzi wrote: >>> Just FYI, we should completely redo these configs using the release >>> variables, but that doesn't have to be toda

Re: [FBR] Include updates-testing repo during bodhi u-t run

On 10/30/18 11:26 AM, Dusty Mabe wrote: > > > On 10/29/18 2:43 PM, Kevin Fenzi wrote: >> Just FYI, we should completely redo these configs using the release >> variables, but that doesn't have to be today. ;) >> >> I assume the check for f30 and using bran

Re: [FBR] Include updates-testing repo during bodhi u-t run

On 10/29/18 2:43 PM, Kevin Fenzi wrote: > Just FYI, we should completely redo these configs using the release > variables, but that doesn't have to be today. ;) > > I assume the check for f30 and using branched is only going to get used > once we branch off f30 right (since this config doesn't c

Re: [PATCH] new-updates-sync: no longer sync stable refs for ostrees

pushed. can one of you run the playbook? Dusty On 10/29/2018 02:57 PM, Mohan Boddu wrote: > LGTM +1 > > On Mon, Oct 29, 2018 at 2:44 PM Kevin Fenzi > wrote: > > Sure. +1 > > kevin > > ___ > infrastructure mai

[PATCH] new-updates-sync: no longer sync stable refs for ostrees

Now that we are releasing f29, no longer sync the stable refs. The atomic host stable ref will be controlled by two week releases. The silverblue stable ref will be aliased to the updates ref. --- roles/bodhi2/backend/files/new-updates-sync | 7 --- 1 file changed, 7 deletions(-) diff --git a

FBR: [PATCH] new-updates-sync: no longer sync stable refs for ostrees

Can I get some votes to no longer sync stable ostree refs using new-updates-sync? Dusty ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of

Re: [FBR] Include updates-testing repo during bodhi u-t run

On 10/29/2018 11:57 AM, Sinny Kumari wrote: > > > On Mon, Oct 29, 2018 at 9:25 PM Dusty Mabe <mailto:du...@dustymabe.com>> wrote: > > > > On 10/29/2018 11:16 AM, Sinny Kumari wrote: > > > > > > With RC 1.2 being Gold, doe

Re: [FBR] Include updates-testing repo during bodhi u-t run

On 10/29/2018 11:16 AM, Sinny Kumari wrote: > > > On Fri, Oct 26, 2018 at 7:07 PM Dusty Mabe <mailto:du...@dustymabe.com>> wrote: > > > > On 10/25/2018 01:25 PM, Sinny Kumari wrote: > > Hi, > > > > Here is a patch (avai

  1   2   3   >