Fixed CI builds for RabbitMQ

[lpottier]

This PR adds RMQ tests to GitHub CI.

• Added missing components (libevent and openssl) so our CI can handle RabbitMQ builds of AMS.
• Test the AMSlib infrastructure to send messages to a RabbitMQ server
• Test the AMS python side to read/consume messages

[ggeorgakoudis]

How come the tests pass without changing the containers?

[lpottier]

I did not change the containers, I just updated the Dockerfile. I built them locally on my side to make sure it works. As AMS code did not change, and the containers did not change, everything is green.

[ggeorgakoudis]

Can you add the tests in this PR? This change is dependent on the tests you want to add. What we should see is that the containerized tests fail, and (hopefully) succeed when the I build/upload the new containers and re-run the workflows.

[lpottier]

Hum good point, the tests are in another PR. I will merge both PRs.

[ggeorgakoudis]

Are you adding also a gitlab test?

[lpottier]

Are you adding also a gitlab test?

Yes I would like to, I have to check how to do that.

[ggeorgakoudis]

Are you adding also a gitlab test?

Yes I would like to, I have to check how to do that.

Check the script ci-build-test.sh under scripts/gitlab. Gitlab CI invokes this script. You can add a function to call, where you run the rmq tests.

[koparasy]

@lpottier what is the status of this. I can see that AMSlib cannot establish a connection with the server. Are we missing container changes?

[lpottier]

@koparasy No the containers are good now. I am working on it but the debugging has proven to be difficult (I cannot easily ssh into the GitHub runner). The Python tools using Pika are able to connect to the RabbitMQ container from the GitHub runner but the AMSlib fails to connect to RabbitMQ. This only happen in the GitHub runner, it works everywhere else (using the same container on LC machine etc).

I think its due to something when we connect to the service in the AMSlib specifically when the RabbitMQ service we connect to has no TLS enabled (so SSL is not needed). I am trying a few things to confirm that.