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

Server side calls missing in multiple roles? #2426

Open
ddevz opened this issue Oct 1, 2023 · 1 comment
Open

Server side calls missing in multiple roles? #2426

ddevz opened this issue Oct 1, 2023 · 1 comment

Comments

@ddevz
Copy link

ddevz commented Oct 1, 2023

I'm reading the code, trying to understand how one would migrate to debops, and how that would be configured. I don't see where the roles call the servers. For example, etckeeper does not seem to create the remote repo on a server? zabbix-agent does not seem to create the entry for the new host on the zabbix server? (even though there is a "Install secret key" task (which might imply that all clients use the same secret key?). I also see roles libvirtd and libvirtd_qemu , but don't see how you specify in the inventory that it should create the virtual machines through.

Maybe I'm misunderstanding what debops objectives are.

@Alphix
Copy link
Contributor

Alphix commented Oct 11, 2023

@ddevz: it varies from role to role.

I don't use etckeeper, but from a quick browse through the role tasks and defaults, it seems to default to using a local repo only, you can set remote repos in etckeeper__push_remote but you'd need to create the repo yourself first since there is no DebOps role for handling git repos (and you might have the repo on GitHub, an internal server, etc).

Other roles, like nullmailer do (optionally) setup things like an LDAP account (via the ldap role) for access to the SMTP server. Many roles (e.g. icinga and roundcube) automatically setup a web server via the nginx role, etc.

So largely it comes down to if the "servers" for a given role have a corresponding DebOps role which can be both discovered and configured automatically via the Ansible inventory.

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