#8321 Remove Freshmaker from Fedora infrastructure
Closed: Fixed 4 years ago by kevin. Opened 4 years ago by jkaluza.

Hi,

year ago, we have asked fedora-infra to create VMs to deploy initial version of Freshmaker to Fedora infrastructure. The main end goals of Freshmaker in Fedora infra were a) to rebuild container images on CVE issues and b) to rebuild modules when some RPM in a module is updated.

However, the priorities changed for the team maintaining Freshmaker and it also seems there is no real benefit of Freshmaker for modularity in the end.

The currently deployed Freshmaker in Fedora is just dummy instance not doing anything. Freshmaker in Fedora is not used by any user or other service currently.

We therefore decided to drop Freshmaker from Fedora infrastructure completely.

I'm therefore asking fedora-infrastructure to remove everything related to following Freshmaker hosts:

  • freshmaker-frontend01.phx2.fedoraproject.org
  • freshmaker-frontend01.stg.phx2.fedoraproject.org
  • freshmaker-backend01.phx2.fedoraproject.org
  • freshmaker-backend01.stg.phx2.fedoraproject.org

You can basically remove everything returned by grep freshmaker -R ansible.


Metadata Update from @mizdebsk:
- Issue assigned to mizdebsk
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: freshmaker

4 years ago

I've removed everything that I could during freeze.

Some parts will need to be removed once freeze ends:

  • DNS
  • nagios
  • haproxy
  • proxies-reverseproxy
  • proxies-websites
  • epylog
  • ipsilon
  • drop database

Metadata Update from @mizdebsk:
- Issue tagged with: unfreeze

4 years ago

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata