You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While reviewed the configuration changes in #332, we realised that our Ansible playbooks use very different styles for setting the OMERO.web app configuration:
sls-gallery and learning explicitly set the OMERO.web configuration using the primary omero_web_config_set - see
nightshade-webclients.yml uses a combination of omero_web_apps_names, omero_web_apps_packages, omero_web_apps_top_links, omero_web_apps_config_append and omero_web_apps_config_set - see
omero/training-server/playbook.yml copies a .omero file containing a series of omero config set and omero config append commands into the configuration directory - see
The mixture of styles is particularly confusing. Deciding on the preferred style(s) and applying them systematically would certainly reduce maintenance.
A related issue highlighted by the progression #332 is that extreme care should be put in the usage of the _append variables. The configuration files stored under /opt/omero/web/config are loaded as part of the omero-web service lifecycle. Internally omero config append includes some logic avoiding the duplication of a value in a configuration list. However, removing a value from a list e.g. unregistering a web app requires more thoughts
The text was updated successfully, but these errors were encountered:
While reviewed the configuration changes in #332, we realised that our Ansible playbooks use very different styles for setting the OMERO.web app configuration:
sls-gallery
andlearning
explicitly set the OMERO.web configuration using the primaryomero_web_config_set
- seeprod-playbooks/sls-gallery.yml
Lines 81 to 111 in d21c6f7
prod-playbooks/learning.yml
Lines 82 to 118 in d21c6f7
ome-demoserver.yml
converts three Jinja template containing a series ofconfig append
andconfig set
subcommands into configuration filesprod-playbooks/ome-demoserver.yml
Lines 213 to 246 in d21c6f7
nightshade-webclients.yml
uses a combination ofomero_web_apps_names
,omero_web_apps_packages
,omero_web_apps_top_links
,omero_web_apps_config_append
andomero_web_apps_config_set
- seeprod-playbooks/nightshade-webclients.yml
Lines 113 to 169 in d21c6f7
omero/training-server/playbook.yml
copies a.omero
file containing a series ofomero config set
andomero config append
commands into the configuration directory - seeprod-playbooks/omero/training-server/playbook.yml
Lines 182 to 191 in d21c6f7
For comparison, the IDR deployment playbooks use a style most closest to
nightshade-webclients
i.e. the built-inomero_web_apps*
variables supplemented byomero_web_apps_config_append
andomero_web_apps_config_set
-see https://github.com/IDR/deployment/blob/77b759ce21f2a165903aa5cbea7fcb673fcf55a8/ansible/group_vars/omero-hosts.yml#L162-L604The mixture of styles is particularly confusing. Deciding on the preferred style(s) and applying them systematically would certainly reduce maintenance.
A related issue highlighted by the progression #332 is that extreme care should be put in the usage of the
_append
variables. The configuration files stored under/opt/omero/web/config
are loaded as part of theomero-web
service lifecycle. Internallyomero config append
includes some logic avoiding the duplication of a value in a configuration list. However, removing a value from a list e.g. unregistering a web app requires more thoughtsThe text was updated successfully, but these errors were encountered: