Add postgresql_clients to requirements

[pwalczysko]

As discussed in #11 (comment), the missing item in the requirements.yml when run on a clean CentOS 7 machine was causing

TASK [ome.postgresql_client : postgres | install client packages] ****************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "No package matching 'postgresql13' found available, installed or updated", "rc": 126, "results": ["No package matching 'postgresql13' found available, installed or updated"]}

With this PR, this error is removed, and the playbook was run to the end successfully.

cc @sbesson

[sbesson]

Looks good. I am still unclear how the first error happened as ome.postgresql_client is a transitive dependency of ome.omero_server (https://github.com/ome/ansible-role-omero-server/blob/f87ded09d57c01d60f456750722f51aa5e6a8c88/meta/main.yml#L30) and I would have expected ansible-galaxy install -r requirements.yml to install the latest published version in the absence of a pinned requirement.

[pwalczysko]

I would have expected ansible-galaxy install -r requirements.yml to install the latest published version in the absence of a pinned requirement.

And so it did. I will have to reconsider, there are quite a few degrees of freedom to test, like ansible version, python version, and also the requirements. Unfortunately, I am having differing results with what seems to me like a repeat (it is quite hard to repeat things exactly, as there are quite a bit of commands and back and forth once you are inside the docker).

[pwalczysko]

@sbesson maybe the way forward to me would be to figure out the way to list the freshly spun up docker with CentOS7 in my ansible hosts.yml file -> this would allow me to treat the docker as a remote machine, and run ansible from my local setup. But unfortunately cannot find the way to do it. Would you have an idea @sbesson please ?

[pwalczysko]

I am having differing results with what seems to me like a repeat (it is quite hard to repeat things exactly, as there are quite a bit of commands and back and forth once you are inside the docker).

I think this was caused by not allocating enough resources to the docker. When I increased this, I can confirm a stable working OMERO server which I can connect to with insight and externally run web and CLI.
As indicated, the ansible version is ansible [core 2.11.12] , dictated by the fact that python 3.6 is installed.
Nevertheless, this was installed by

pip install ansible

in that env.
I still do not understand the port forwarding necessary for OMERO.web, as indicated previously, the OMERO.web which runs inside the docker and was successfully installed by ansible and systemctl reports it is running, is not accessible from my browser on any reasonable url.
I think I will stop here, concluding it all works and write the workflow in ome/omero-guides#232
with simple pip install ansible, remarking on the tested version as 2.11.12 core.

[pwalczysko]

The OMERO.web problem is probably caused by the complete lack of any web config.

(venv3) bash-4.2$ export OMERODIR=/opt/omero/web/OMERO.web      
(venv3) bash-4.2$ omero config get
(venv3) bash-4.2$

Wonder why is that. It seems to me that at least something should be configured ?

[sbesson]

I am a bit lost. Many of the discussions below seem unrelated to the original change which adds a role to the requirements file. Should we merge this and capture anything unsolved as issues @pwalczysko ?

[pwalczysko]

I am a bit lost. Many of the discussions below seem unrelated to the original change which adds a role to the requirements file. Should we merge this and capture anything unsolved as issues @pwalczysko ?

Sorry for the chaos. I am trying to go ahead with the guide mainly.
Yes, please, merge and I will capture the latest unsolved issues as you say, thanks.