Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump ZarrReader to 0.5.2 and omero-server to 5.6.12 #429

Merged
merged 3 commits into from
Aug 15, 2024

Conversation

dominikl
Copy link
Member

See title.

@dominikl
Copy link
Member Author

Deployed on idr-testing. (/cc @sbesson )

Copy link
Member

@sbesson sbesson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deployment changes look good to me. From this morning's IDR meeting, I understand the goal is to have this deployed onto idr-testing alongside the image-region micro-service with the same version of ZarrReader for a new round of testing.

At the code level, this raises the question of whether the micro-service addition will come as a separate PR and be included here. Note that from an deployment perspective, it should be also possible to update prod122 with these changes first and schedule the integration of the micro-service at a later date.

ansible/group_vars/omero-hosts.yml Outdated Show resolved Hide resolved
@sbesson sbesson merged commit 36da6ae into IDR:master Aug 15, 2024
3 checks passed
@sbesson
Copy link
Member

sbesson commented Aug 15, 2024

The following playbooks idr-omero.yml, idr-omero-readonly.yml and idr-omero-web.yml have been successfully executed against prod122 upgrading the server and web environments as required.

Note that as part of this action, the PostgreSQL configuration file was "downgraded" to the state installed by the ome.postgresql:5.4.0 role. @khaledk2 manually added effective_cache_size = 24GB to the configuration file which was the primarily change from the CentOS 7 -> Rocky Linux 9 upgraded. Mid-term, this should be addressed properly by completing the work on #424.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants