Loading howto/ldap.md +63 −1 Original line number Diff line number Diff line Loading @@ -288,10 +288,24 @@ same changes are performed in the git repositoy. It is preferable, however, to [build and upload](howto/build_and_upload_debs) `userdir-ldap` as a Debian package instead. # Reference ## Pager playbook <!-- information about common errors from the monitoring system and --> <!-- how to deal with them. this should be easy to follow: think of --> <!-- your future self, in a stressful situation, tired and hungry. --> ## Disaster recovery <!-- what to do if all goes to hell. e.g. restore from backups? --> <!-- rebuild from scratch? not necessarily those procedures (e.g. see --> <!-- "Installation" below but some pointers. --> # Reference ## Installation <!-- how to setup the service from scratch --> ## SLA <!-- this describes an acceptable level of service for this service --> ## Design Loading @@ -305,3 +319,51 @@ DNS zone files are also managed (at least partly) in LDAP. This is automated through cron jobs, but if you're in a hurry, the zones get generated by `ud-generate` on `alberti` (as `sshdist`?) and replicate (?) on `nevii` with `ud-replicate` (as `root`?). ## Issues <!-- such projects are never over. add a pointer to well-known issues --> <!-- and show how to report problems. usually a link to the bugtracker --> There is no issue tracker specifically for this project, [File][] or [search][] for issues in the [team issue tracker][search]. [File]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/new [search]: https://gitlab.torproject.org/tpo/tpa/team/-/issues ## Monitoring and testing <!-- describe how this service is monitored and how it can be tested --> <!-- after major changes like IP address changes or upgrades --> ## Logs and metrics <!-- where are the logs? how long are they kept? any PII? --> <!-- what about performance metrics? same questions --> # Discussion ## Overview <!-- describe the overall project. should include a link to a ticket --> <!-- that has a launch checklist --> ## Goals <!-- include bugs to be fixed --> ### Must have ### Nice to have ### Non-Goals ## Approvals required <!-- for example, legal, "vegas", accounting, current maintainer --> ## Proposed Solution ## Cost ## Alternatives considered <!-- include benchmarks and procedure if relevant --> Loading
howto/ldap.md +63 −1 Original line number Diff line number Diff line Loading @@ -288,10 +288,24 @@ same changes are performed in the git repositoy. It is preferable, however, to [build and upload](howto/build_and_upload_debs) `userdir-ldap` as a Debian package instead. # Reference ## Pager playbook <!-- information about common errors from the monitoring system and --> <!-- how to deal with them. this should be easy to follow: think of --> <!-- your future self, in a stressful situation, tired and hungry. --> ## Disaster recovery <!-- what to do if all goes to hell. e.g. restore from backups? --> <!-- rebuild from scratch? not necessarily those procedures (e.g. see --> <!-- "Installation" below but some pointers. --> # Reference ## Installation <!-- how to setup the service from scratch --> ## SLA <!-- this describes an acceptable level of service for this service --> ## Design Loading @@ -305,3 +319,51 @@ DNS zone files are also managed (at least partly) in LDAP. This is automated through cron jobs, but if you're in a hurry, the zones get generated by `ud-generate` on `alberti` (as `sshdist`?) and replicate (?) on `nevii` with `ud-replicate` (as `root`?). ## Issues <!-- such projects are never over. add a pointer to well-known issues --> <!-- and show how to report problems. usually a link to the bugtracker --> There is no issue tracker specifically for this project, [File][] or [search][] for issues in the [team issue tracker][search]. [File]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/new [search]: https://gitlab.torproject.org/tpo/tpa/team/-/issues ## Monitoring and testing <!-- describe how this service is monitored and how it can be tested --> <!-- after major changes like IP address changes or upgrades --> ## Logs and metrics <!-- where are the logs? how long are they kept? any PII? --> <!-- what about performance metrics? same questions --> # Discussion ## Overview <!-- describe the overall project. should include a link to a ticket --> <!-- that has a launch checklist --> ## Goals <!-- include bugs to be fixed --> ### Must have ### Nice to have ### Non-Goals ## Approvals required <!-- for example, legal, "vegas", accounting, current maintainer --> ## Proposed Solution ## Cost ## Alternatives considered <!-- include benchmarks and procedure if relevant -->