Determine how corto will be deployed to production, document and test deployment.
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Create corto deployment/configuration | operations/puppet | production | +233 -0 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T308467 implementing an incident response workflow automation tool for SRE | |||
Resolved | Eevans | T356790 Corto: Incident responder workflow automation (MVP) | |||
Resolved | BCornwall | T370789 corto: production deployment |
Event Timeline
I'm guessing we want a Ganeti corto1001.eqiad.wmnet with internal-only networking and the typical debian packaging, puppetization, /etc/corto, and systemd service, etc? Happy to handle this stuff if so.
Please excuse the drive-by comment, as a ONFIRE alumni I seem to remember we talked about hosting corto on alert hosts. As a o11y member, the offer is still valid in terms of hosting the package + puppetization, whilst ownership stays with ONFIRE
HTH!
Change #1060516 had a related patch set uploaded (by BCornwall; author: BCornwall):
[operations/puppet@production] Create corto deployment/configuration
brett opened https://gitlab.wikimedia.org/repos/sre/corto/-/merge_requests/24
debian: Expect config /etc/corto/config.yaml
brett merged https://gitlab.wikimedia.org/repos/sre/corto/-/merge_requests/24
debian: Expect config /etc/corto/config.yaml
brett opened https://gitlab.wikimedia.org/repos/sre/corto/-/merge_requests/25
config: Add Google Drive credentials file path
brett merged https://gitlab.wikimedia.org/repos/sre/corto/-/merge_requests/25
config: Add Google Drive credentials file path
Change #1060516 merged by BCornwall:
[operations/puppet@production] Create corto deployment/configuration