Hello guys. We have one plugging which assumes to submit tasks to celery and retrieve their outputs. I have a feedback from one of our developers, that beer garden is dealing only with sync tasks and this makes a problem to integrate this solution with the beer garden. Do we understand the limitation properly? How to solve this?
Anyway, some update from my side. We think to use
result.get(timeout=300)in celery. This turns the call into sync one (http://docs.celeryproject.org/en/latest/getting-started/first-steps-with-celery.html#keeping-results)
It's been a real long time since I came back to gitter. I updated my installation of beer garden with the latest version, (this time in a virtual environment) but it seems the old systems I wrote no longer works. The error I am receiving is "Backend request timed out" when the system starts up.
This is on a CentOS 7.5, on Python 3.7. Thanks!
.tar.gz. You've transferred the
.tar.gzto the correct folder in the compose, exploded the file, and then tried to rescan but to no avail
docker-compose logs -f bartender
I found the issue. Seems I didn't read enough :)
TLDR: I was missing some required fields in the beer.conf
After I ran the docker-compose logs (thanks @loganasherjones ) and saw the error messages, I went back and read the entry for the required fields below in the tutorial. Might want to consider updating the "Configure your plugin" portion on the plugin local guide. For a noob like myself, it can be misleading. I was under the impression all I needed was the PLUGIN_ENTRY.
That all said, I have my first plugin running. Now the real fun begins.