... | ... | @@ -1556,11 +1556,16 @@ area of the disk to hunt for file signatures. |
|
|
|
|
|
<!-- TODO: how to setup the service from scratch -->
|
|
|
|
|
|
## Upgrades
|
|
|
|
|
|
Bacula is packaged in Debian and automatically upgraded. Major Debian
|
|
|
upgrades involve a [PostgreSQL](howto/postgresql) upgrade, however.
|
|
|
|
|
|
## SLA
|
|
|
|
|
|
<!-- TODO: acceptable level of service for this service -->
|
|
|
|
|
|
## Design
|
|
|
## Design and architecture
|
|
|
|
|
|
<!-- TODO: finalize audit from -->
|
|
|
<!-- https://bluesock.org/~willkg/blog/dev/auditing_projects.html -->
|
... | ... | @@ -1682,16 +1687,25 @@ There is no issue tracker specifically for this project, [File][] or |
|
|
[File]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/new?label_name%5B%5D=Backup
|
|
|
[search]: https://gitlab.torproject.org/tpo/tpa/team/-/issues?label_name%5B%5D=Backup
|
|
|
|
|
|
## Monitoring and testing
|
|
|
## Maintainer
|
|
|
|
|
|
This service is maintained by TPA, mostly by anarcat.
|
|
|
|
|
|
## Monitoring and metrics
|
|
|
|
|
|
<!-- TODO: describe how this service is monitored and how it can be tested -->
|
|
|
<!-- after major changes like IP address changes or upgrades -->
|
|
|
<!-- TODO: describe how this service is monitored -->
|
|
|
|
|
|
## Logs and metrics
|
|
|
## Tests
|
|
|
|
|
|
<!-- TODO: document how to test the service after major changes like IP address changes or upgrades -->
|
|
|
|
|
|
## Logs
|
|
|
|
|
|
<!-- TODO: where are the logs? how long are they kept? any PII? -->
|
|
|
<!-- what about performance metrics? same questions -->
|
|
|
|
|
|
## Backups
|
|
|
|
|
|
## Other documentation
|
|
|
|
|
|
* [upstream manual](https://www.bacula.org/9.4.x-manuals/en/main/index.html) (has formatting problems, the [PDF](https://www.bacula.org/9.4.x-manuals/en/main/main.pdf) looks better)
|
... | ... | @@ -1708,25 +1722,21 @@ TODO: populate Discussion section. |
|
|
<!-- describe the overall project. should include a link to a ticket -->
|
|
|
<!-- that has a launch checklist -->
|
|
|
|
|
|
## Goals
|
|
|
## Security and risk assessment
|
|
|
|
|
|
|
|
|
<!-- include bugs to be fixed -->
|
|
|
## Technical debt and next steps
|
|
|
|
|
|
### Must have
|
|
|
|
|
|
### Nice to have
|
|
|
|
|
|
### Non-Goals
|
|
|
|
|
|
## Approvals required
|
|
|
|
|
|
<!-- for example, legal, "vegas", accounting, current maintainer -->
|
|
|
|
|
|
## Proposed Solution
|
|
|
|
|
|
## Cost
|
|
|
<!-- Link to RFC -->
|
|
|
|
|
|
## Alternatives considered
|
|
|
## Other alternatives
|
|
|
|
|
|
<!-- include benchmarks and procedure if relevant -->
|
|
|
|
... | ... | |