intent to retire: fedmsg-irc, old fmn, osbs

2023-11-09 Thread Kevin Fenzi
Greetings everyone.

Now that fedora 39 is out the door, I'd like to schedule some
retirements of a few old services:

fedmsg-irc: This is a old fedmsg process that send fedmsg's to IRC.
Currently we have one running in production and one in staging, both on
rhel7 vm's that we would like to retire. They currently gateway the
entire message bus to #fedora-fedmsg (prod) and #fedora-fedmsg-stg
(staging), but due to the volume and IRC throttling they are way behind.
It's often behind by 12-48 hours. Additionally, it sends some matching
messages to the #fedora-releng channel (composes, etc). We plan to
replace that with a matrix bot webhook at some point.

old fmn (old fedora notifications service).
https://apps.fedoraproject.org/notifications-old/
This was replaced with https://notifications.fedoraproject.org/
and we said we would sunset the old one after f39 was out.
If you're missing features with the new one, please make sure they are
tracked at https://github.com/fedora-infra/fmn/issues

osbs (openshift build service). This is 4 openshift 3.11 clusters. (one
each for x86_64 and aarch64 x production and staging). This service
built containers for us, but all the containers we now build are done
via ImageFactory (base, minimal, toolbox) or elsewhere (quay.io, etc).

I'd like to turn these services off next wed (2023-11-15) if there's no
reasons I missed to do so before then. We will keep the data from them
around in case we need to bring them back or get data from them.

Please let us know if there's any uses for these services we aren't
aware of before next wed. 

https://pagure.io/fedora-infrastructure/issue/11504 is a tracking ticket
for the osbs cluster retirement.

Thanks!

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 Snapshots without FedoraGroup tag

2023-11-09 Thread Kevin Fenzi
On Mon, Nov 06, 2023 at 10:22:57PM +0100, Miroslav Suchý wrote:
> 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 take
> 
> snap-0fdf88e3527a6ca6e (fedora-coreos-39.20231101.1.0-x86_64)
> that was created
> 
> Fri Nov 03 2023 04:12:53 GMT+0100
> 
> with description
> Copied for DestinationAmi ami-0e62f1adedc546f4d from SourceAmi
> ami-0b9d8baf52b75e62c for SourceSnapshot snap-033116129e665e380. Task
> created on 1,698,981,171,355.Copied for DestinationAmi ami-0e62f1adedc546f4d
> from SourceAmi ami-0b9d8baf52b75e62c for SourceSnapshot
> snap-033116129e665e380. Task created on 1,698,981,171,355.Copied for
> DestinationAmi ami-0e62f1adedc546f4d from SourceAmi ami-0b9d8baf52b75e62c
> for SourceSnapshot snap-033116129e665e380. Task created on
> 1,698,981,171,355.Copied for DestinationAmi ami-0e62f1adedc546f4d from
> SourceAmi ami-0b9d8baf52b75e62c for SourceSnapshot snap-033116129e665e380.
> Task created on 1,698,981,171,355. as snapshot of vol-
> that does not exists.
> 
> Hmm, 
> fromhttps://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-an-ami-ebs.html
>   :
> 
> During the AMI-creation process, Amazon EC2 creates snapshots of your
> instance's root volume and any other EBS volumes attached to your instance.
> You're charged for the snapshots until you deregister the AMI
> 
> and delete the snapshots. If any volumes attached to the instance are
> encrypted, the new AMI only launches successfully on instances that support
> Amazon EBS encryption
> .

yeah, I am not sure here. I guess we could check fedimg code, and/or ask
any subject matter experts to chime in. 

Well, actually, we should probibly check in on the thing thats cleaning
up the amis? and confirm that it is deleting the snapshots?

I think that is this: 
roles/fedimg/templates/clean-amis.py
in ansible.

and it does delete the snapshot... so, perhaps indeed all these ones
with vol- are some mistake or some other amis?

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