Today
better variable name
removed for loop
testing list format for routers
I've asked upstream for advice how to resolve pillar for another server than the current node @ https://groups.google.com/g/salt-tower/c/XEKg2CEiZrU
added router parameter
Light modifications
The output is really useful to avoid to manually repeat the ports.
Rebased. Fixed pillar handling.
updated for loop syntax
Note: we're deploying a third secret for CARP routers scripts. If we've already that code merged, we'll need to append a line to deploy that state too.
Added router-002
Next: try salt web-001 paas_docker.get_upstreams
Removed cloudhugger
Rebased against current main for Alkane.
This change is interesting and should be rebased.
This configuration is for Pixelfed old versions.
Not sure today if we still want to deploy through Docker, or if we would target Alkane PaaS for Espace Win sites. It's also unknown if it brings value to put back the forum archive.
Currently, zed51.dereckson.be serves a 500 error.
Tried to deploy on DevCentral - it's now an old container still using PHP 7.4.
We can consider the mail server as deployed and create tasks for extra actions in the Mail projects.
@DorianWinty Do we have everything in the configuration or is there some actionnables remaining?
Deployed and working fine.
Dovecot deployed and working well.
[ Resetting assignee of long-assigned tasks. Feel free to reassign when working on this. ]
With Salt, sudo files content are now managed from rOPS.
Not a priority right now, as we use Alkane to trigger website deployments.
See also T1784 to improve UX and URLs.
Software has been renamed to Redpanda Connect:
Checked today, it works fine:
Yesterday
Ah, that's now what we need, nice for the script!
vault_policy.router: Creating... module.router_approle.vault_approle_auth_backend_role.this: Creating... module.router_approle.vault_approle_auth_backend_role.this: Creation complete after 0s [id=auth/approle/role/router] module.router_approle.data.vault_approle_auth_backend_role_id.this: Reading... module.router_approle.data.vault_approle_auth_backend_role_id.this: Read complete after 0s [id=auth/approle/role/router/role-id] module.router_approle.vault_approle_auth_backend_role_secret_id.this: Creating... vault_policy.router: Creation complete after 0s [id=router] module.router_approle.vault_approle_auth_backend_role_secret_id.this: Creation complete after 1s [id=backend=approle::role=router::accessor=...] module.router_approle.vault_kv_secret_v2.this: Creating... module.router_approle.vault_kv_secret_v2.this: Creation complete after 0s [id=ops/data/secrets/network/router/vault]
The file /usr/local/etc/devd/carp.conf :
You can directly use variables in the action to pass interface and state with $subsystem and $type
notify 0 {
match "system" "CARP";
match "subsystem" "[0-9]+@[0-9a-z.]+";
match "type" "(MASTER|BACKUP)";
action "/usr/local/scripts/carp-test.sh";
};Closed as inactive.
Next: configure DNS records
This method works well, Salt automation is welcome.
Solution is satisfactory and stable all summer long.
We can consider we're done and handle the remaining as regular tasks.
Panel Used By
| Dashboard | Default home view | |
| Dashboard | Nasqueron DevCentral | |
| Dashboard | Legacy home view — recent tasks grouped by priorities |