Namespace: communishift-avant Project Administrators: manky201
The current resource limits ( 1 vCPU, 1GB request/ 2GB limit, 4 pods ) are insufficient for the requirements of the service.
We need to run the following components: - 2× Celery workers (asynchronous task processing) - Flask-RESTX server (API service) - Postgres (database) - Valkey (Redis-compatible cache) - Fedmsg (messaging bus listener)
This requires a minimum of 6 pods for a basic deployment. - The current limit of 4 does not allow all the components to be deployed. - Postgres and celery workers would require more than the current memory limits to start for migrations to run on start.
To support this workload reliably, we request an increase of ResourceQuota to: - Pods: 6 required - CPU: 2 vCPUs - Memory: 1.5 GB request / 3 GB limit
Thank You
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: communishift, low-gain, low-trouble, ops
@dkirwan Could you look into this?
He is on PTO this week.
This just needs adjustments in inventory/group_vars/all for the communishift-avant: entry to set things.
I'd like to take this as a new infra contributor. This is a good excuse to go find all the communishift components. I'm starting to look into it now. And no worries if someone else gets there first.
https://pagure.io/fedora-infra/ansible/pull-request/2837
Thanks @mwinters !
merged, and playbook run. Let us know if you hit any problems.
Metadata Update from @kevin: - Issue assigned to mwinters - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
He is on PTO this week. This just needs adjustments in inventory/group_vars/all for the communishift-avant: entry to set things.
I didn't know it is that easy. But at least it was a good work for somebody new :-)