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

Decouple bmon-infra deploy from infrastructure restart #3

Open
jamesob opened this issue Oct 6, 2022 · 0 comments
Open

Decouple bmon-infra deploy from infrastructure restart #3

jamesob opened this issue Oct 6, 2022 · 0 comments

Comments

@jamesob
Copy link
Collaborator

jamesob commented Oct 6, 2022

Certain bmon-server infrastructure often doesn't need to be restarted during deploys (e.g. db, redis). Specifically in the case of redis, we don't want to routinely restart the container because of the ephemeral nature of redis' storage.

Split out deployment for app containers (e.g. server-task-worker) from the more infra-based containers. This probably amounts to having separate systemd unit files for each "type" of process, perhaps:

  • Infra containers
    • db
    • redis
  • Grafan containers
    • grafana
    • prom
    • alertman
    • loki
  • bmon containers
    • web
    • server-task-worker
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

1 participant