Closed sbesson closed 2 years ago
The volumes of prod107
are now ready for redeployment. I would propose to get this merged so that we redeploy it with the provisionin infrastructure decided for the searchengine backend. Improvements and to the app/deployment can then be opened as follow-up PRs. @khaledk2 would this work from your side?
Let's remove all the references to the search engine client deployment as it has been added as a web app to IDR deployment so there is no point in including it.
Should that be included in this PR or should open a new one for that?
All modifications would happen in the idr-searchengine.yml
playbook, is that correct? IF so, I'd propose to get this in and let you open a follow-up PR cleaning the deployment of the initial client?
Some modifications are needed also in searchengine-hosts.yml
Thanks @khaledk2 and fair enough. As these variables are only used in the post-provisioning steps (and specifically during the execution of the idr-02-services.yml playbook, this should still be fine to handle separately. I'll merge this and leave you to open the cleanup PR
Fixes #370
As discussed on the issue, this PR implements option 3 and creates a new VM of similar compute capacity to
omeroreadwrite
and some dedicated storage.To be deployed on
test107