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

System setup for Zabbix side not docker friendly #51

Open
minsis opened this issue Aug 6, 2021 · 3 comments
Open

System setup for Zabbix side not docker friendly #51

minsis opened this issue Aug 6, 2021 · 3 comments

Comments

@minsis
Copy link

minsis commented Aug 6, 2021

Zabbix supports docker containers in production. With this pack the setup for docker containers when needing to install packages, etc isn't friendly to without the need for custom builds.

@minsis
Copy link
Author

minsis commented Aug 6, 2021

After poking around it seems the only reason this package needs st2client is to hook into internal systems that st2client uses to make its own calls to whatever client is configured. I feel like this is a kind of hacky way of doing it as the st2client was meant to be a standalone app and not an python API library. Things could change inside of st2client that would break this package.

@namachieli
Copy link
Collaborator

Definitely a good call out. How would you suggest changing it? PRs are always appreciated!

@minsis
Copy link
Author

minsis commented Aug 18, 2021

@namachieli

  • Since the Zabbix containers don't even have python installed you can't even default to doing things the hard way with urllib2 or something.

  • Zabbix suggests that you create your own custom container that includes python. I don't really like this idea because it puts the maintenance off on to me and I'm lazy. But this is a legit method if you're wanting to use the python script

  • When using docker-compose Zabbix does mount a local volume so that you can store your own modules, scripts, etc without the need to copy it into the container.

  • Currently when I have a few minutes out of my day, I work on a shell script that I'm trying to make which uses curl commands to hit the st2 API. Curl is included in the containers during build and isn't removed. This could end up being removed by them later down the road I dont know, but for now its the only thing I can think of.

  • I'm also exploring the option to maybe mount a virtualenv as a volume into the container. This could be a okay solution I'm not entirely sure.

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

No branches or pull requests

2 participants