Fixed number of service workers as 4

[Nobuto Murata]

2024.1/edge: 2024.1 2024-05-19 (506)

It looks like the worker number is hardcoded as 4 in most of the places. And we know that 4 is not sufficient to handle production workload sometimes.

e.g. keystone (processes=1 threads=1)

https://opendev.org/openstack/sunbeam-charms/src/commit/0cca8980ef529bf1fcb61b746c762dd33d52635f/charms/keystone-k8s/src/templates/wsgi-keystone.conf.j2#L4

    WSGIDaemonProcess keystone-public processes=4 threads=1 user=keystone group=keystone display-name=%{GROUP} python-path=/usr/lib/python3/site-packages

[Guillaume Boutry (gboutry)]

Hello, Sunbeam does not mean to scale by tuning worker process of individual workers in a pod. Each pod is a building block, and the way to scale sunbeam is to increase the number of units (pod) for each application.

Workers is not meant to be exposed via configuration options or any other mean.

[Nobuto Murata (nobuto)]

Doesn't it have too much overhead just to bump the number of workers then? let's say if we want to bump it to 16, then we need 4 containers on top of the same host.