I’ve just make a public repository where I have written some roles to install/configure a Linux desktop account. The prerequisite is ansible and to have an access to the root account for some setup.
If you use zabbix to monitor your infrastructure and applications, you probably have a lot of templates that you affect to different servers. And maybe you have different environements, so you also have two zabbix servers (or more ?).
Well, when you update a zabbix template on the zabbix server of the test environement because the last update have changed the way you need to monitor one app, you will have to update the template in production also.
Easy, you go to templates, search the template, export it (save to My documents or whatever) and after that, you login to the zabbix in production, and load the new version of the template.
- Do you have the history of the template ?
- Are you able to rollback the template ?
We are beginning to use Swarm at work and I wanted to make a complete CI/CD in the Swarm. So I have tried to run my own gitlab-runner in the Swarm (connected to https://gitlab.com).
As for Kubernetes, I have done some code to build a swarm cluster with vagrant too :
Hello, I’beginning to learn Kubernetes and I have used vagrant and ansible to create a complete kubernetes cluster.