Drop 6.4 support?

[BGmot]

@pyrodie18 @eb4x ?

[pyrodie18]

I could go either way. 6.4 is still supported by Zabbix isn't it? Do we want to do a major release?

[BGmot]

No, it is not supported by Zabbix https://www.zabbix.com/life_cycle_and_release_policy
If we drop it then we have to go major.

[pyrodie18]

6.4 is still on their download page is why I bring it up. Agree that it shouldn't be.

[BGmot]

Talked to Zabbix. 6.4 is no longer supported.

[eb4x]

Not against removal. People can still pin/downgrade their collections to retain support. Are we thinking dropping 6.0 aswell? It's out of "full support" in 8 days.

[BGmot]

I would not remove 6.0 for now. Only one my client decided to switch to 7.0 as of now. I know there is a lot of people still on 6.0.
But I am open for discussion.
@pyrodie18 what are you voting for? -)

[pyrodie18]

If it's not supported then I see no issue with dropping it. Need to double check and see if any of our OS we support have gone EOL (I don't think so but if we're doing a major release might as well check)

[BGmot]

Then we probably need to release a minor. Because we have some fixes for 6.0 too (PSK stuff)

[eb4x]

I've gone on a little side project getting a working windows box in vagrant for testing zabbix-agent on microsoft platforms, and then refactor the zabbix-agent playbooks, which would be nice to get in before any major version. So I would also prefer a minor release.

[BGmot]

That's cool! How do you see vagrant fit here? I'd love to some tests against Windows platform.

[eb4x]

The documentation for molecule recommends creating a directory extensions/molecule/, and stuffing all your molecule in there. So I figured we can create an extensions/vagrant/ and stuff whatever seems practical for testing there. (Then at some point refactor and move the molecule stuff in extensions/ along side it.)

Something like this;

.
├── docs
├── extensions
│   ├── molecule
│   │   ├── default
│   │   │   ├── create.yml
│   │   │   ├── destroy.yml
│   │   │   └── ...
│   │   └── zabbix_server
│   │       ├── molecule.yml
│   │       └── ...
│   └── vagrant
│       ├── ansible-collection-requirements.yml
│       ├── database-mysql.yml
│       ├── database-pgsql.yml
│       ├── vagrant-os-image-fixes.yml
│       └── windoze.yml
├── meta
├── plugins
├── roles
└── Vagrantfile

I'm not sure we can run vagrant/vms with github-actions, but atleast for local dev/testing it'll work fine. I've used it for testing out selinux code, timescale and the dbtlsconnect fix for zabbix_server among other things.

It's available under https://github.com/eb4x/community.zabbix/tree/vagrant It's just one massive Vagrantfile (that I'd split up in the future), and some ansible glue under extensions/vagrant/.

The vagrant boxes of windows currently available at app.vagrantup.com aren't supporting the spec I like to put on qemu vms (q35,uefi,virtio-scsi,etc), so I have to roll my own with packer. Basing most of the work on some old json windows tutorial templates, and later bento. I've got the build working, but not the post-processor for vagrant yet. I'll put the packer code up to my github once it's working.

[BGmot]

by the way Zabbix "fixed" it https://support.zabbix.com/browse/ZBX-26079