The current 2.0rc2 requires to start up the full decision engine framework, which will read in the glideinwms.libsonnet config. The configure_gwms_frontend.py then is run and reads the contents of the glideinwms.libsonnet
from the de-client interface, after which the full decision engine again has to be restarted.
In discussions with Bruno, he agrees it is better to have the config script read from the glideinwms.libsonnet
file out of band.
Also technically glideinwms.libsonnet belongs to the resource_request channel and thus is really
properly attached to the resource_request channel as a config file and not to the top level framework.
The current 2.0rc2 requires to start up the full decision engine framework, which will read in the glideinwms.libsonnet config. The configure_gwms_frontend.py then is run and reads the contents of the glideinwms.libsonnet from the de-client interface, after which the full decision engine again has to be restarted.
In discussions with Bruno, he agrees it is better to have the config script read from the glideinwms.libsonnet file out of band.
Also technically glideinwms.libsonnet belongs to the resource_request channel and thus is really properly attached to the resource_request channel as a config file and not to the top level framework.