overview
community.zabbix
overview | community.zabbix | |
---|---|---|
12 | 11 | |
244 | 304 | |
0.4% | 1.7% | |
3.7 | 8.2 | |
12 days ago | about 15 hours ago | |
Python | ||
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
overview
-
The Bullhorn #84 (Ansible Newsletter)
As mentioned in last week's Bullhorn issue, cyberark.pas is subject to removal from version 9 of the Ansible community package due to unresolved Collection Requirements violations. A week has passed since the community-topics issue was filed and other SC members confirmed the violation, so a vote has been started (vote ends on 2022-12-16).
-
The Bullhorn #83 (Ansible Newsletter)
cyberark.pas is subject to removal from version 9 of the Ansible community package due to unresolved Collection Requirements violations. Please see community-topics#168 for more information.
-
The Bullhorn #80 (Ansible Newsletter)
The community steering committee has started a vote on whether we should amend the Ansible community package removal process to consider collections with unresolved Collection Requirements violations unmaintained and thus subject to removal. Please see the PR that amends the policy and the community-topics ticket for more information.
-
The Bullhorn #79 (Ansible Newsletter)
The Ansible Community Steering Committee has approved a change to the Collection Requirements re. SCM and release requirements. Collections were always required to tag releases, but we have clarified what tagging actually means. We have also explicitly stated that "collection artifacts released to Galaxy MUST be built from the sources that are tagged in the collection's git repository as that release." Please see the full change for more information.
-
The Bullhorn #69 (Ansible Newsletter)
We are happy to announce that the ibm.spectrum_virtualize collection has been included in the ansible community package. Thanks to everyone who helped review the collection and thanks to the maintainers for submitting the collection and making it satisfy the Collection requirements!
-
The Bullhorn #62 (Ansible Newsletter)
How? Copy the Review checklist into a discussion and go through it. See the complete example.
-
The Bullhorn #56 (Ansible Newsletter)
We've recently signed off on that process, which you can review here.
-
The Bullhorn #55 (Ansible Newsletter)
Your votes needed! Proposal: merge and adopt the procedures defined in Describe how collections can be removed from the Ansible package. Please vote in this issue (and not in the PR). The vote will close on 2022-04-27.
-
Future of Ansible package
Pros: - Motivation for developers to create new collections which can become a part of Ansible package ("so popular and important in IT world", etc). - Motivation to create content satisfying the collection requirements. - Motivation to maintain included collections to avoid kicking them out from the package "I can't show off with my collection any more..:(" - ...(suggest yours)
-
The Bullhorn #49 (Ansible Newsletter)
We have docs in three places today for contributors: * ansible/ansible in the community folder * ansible/community-docs - more collection focused * ansible-collections/overview - has deeper collection contribution details
community.zabbix
-
Import Hosts from Zabbix Server into AWX Inventory
However, there is a breaking change to https://github.com/ansible-collections/community.zabbix/blob/main/plugins/inventory/zabbix_inventory.py which breaks the ability to import host groups from zabbix. This means you'll have all the hosts into one single group.
-
Changing PSK on multiple hosts.
Use the "official" zabbix collection, there seems no "force psk renewal' present but you could just insert a pre_task to delete it and run the role: https://github.com/ansible-collections/community.zabbix/blob/main/roles/zabbix_agent/tasks/tlspsk_auto_linux.yml
-
Deploy Zabbix Windows Agent with community.zabbix - Wrong Version installed
i'm using community.zabbix for deploying the zabbix_agent2 on Windows Machines.
- How to install zabbix RPM ,copy files & Start Service?
-
The Bullhorn #69 (Ansible Newsletter)
We are happy to welcome several new maintainers in the community.zabbix collection: pyrodie18, BGmot and lzadjsf. Thank you, folks, for your interest and desire to help! Many thanks to D3DeFi, one of the current collection maintainers, for promoting them!
-
Zabbix 4.0.19
As for automation, I'm about to start playing with: Ansible Collection: Community Zabbix So that might prove useful for you too.
-
The Bullhorn #46 (Ansible Newsletter)
for community.zabbix: With the release of Zabbix 6.0 LTS we would love to get some help on blocking issues like with the integration of a new scripts module. Thank you for your attention!
-
The Bullhorn, Issue 40 (Ansible Newsletter)
A lot has been happening in the community.zabbix collection. They've gained two new maintainers, rockaut and ragingpastry, congratulations to both and thank you for your continued great work. The team has recently released version 1.5.1. If you're interested in Zabbix, join the active discussion in #community-zabbix_community:gitter.im via Matrix.
-
Searching for a lightweight log server
The ansible collection is very good (no one wants to setup manually agent and extend checks with user-parameters manually): https://github.com/ansible-collections/community.zabbix (works for all components).
-
Start at specific role
Yes, each role has their own Molecule configuration and tests. So with every change you make in your role, Molecule will test this. (Keep note: It needs to be executed from Jenkins/GitLab CI/Github Actions etc). Once everything is valid, you will merge the code to master|main. See: https://github.com/ansible-collections/community.zabbix/tree/main/molecule These are the roles I maintain, everytime when someone is creating a PR to add new code/functionality, molecule is executed. When Molecule exits correctly (exit code of 0), then to me the role is ok (In a nutshell). And when the role is ok, I will accept/merge the PR.
What are some alternatives?
Ansible - Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.
ansible-collection-k8s - To use in conjunction with Kubernetes and Ansible Operator SDK
docsite - Static HTML and assets for docs.ansible.com
zabbix-mini-IPMI - Disk and CPU temperature monitoring for Linux, FreeBSD and Windows. LLD, trapper.
awx - AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
ansible-meraki - Cisco Meraki Ansible Collection
ansible-lint - Best practices checker for Ansible [Moved to: https://github.com/ansible/ansible-lint]
azure - Development area for Azure Collections
ansible-borgbase - Ansible modules for managing borgbase SSH keys and repositories
community.network - Ansible Community Network Collection
community.kubernetes - Kubernetes Collection for Ansible