[tor-bugs] #33506 [Metrics/Exit Scanner]: Complete Ansible playbook for exit scanner (check-01) deployment

Tor Bug Tracker & Wiki blackhole at torproject.org
Wed Mar 4 17:59:10 UTC 2020


#33506: Complete Ansible playbook for exit scanner (check-01) deployment
----------------------------------+------------------------
 Reporter:  irl                   |          Owner:  irl
     Type:  task                  |         Status:  closed
 Priority:  Very High             |      Milestone:
Component:  Metrics/Exit Scanner  |        Version:
 Severity:  Normal                |     Resolution:  fixed
 Keywords:                        |  Actual Points:
Parent ID:  #33507                |         Points:
 Reviewer:                        |        Sponsor:
----------------------------------+------------------------
Changes (by irl):

 * status:  accepted => closed
 * resolution:   => fixed


Old description:

> This ticket contains the final tasks that need to be integrated into the
> Ansible playbook for the managed deployment of check-01 (aka the exit
> scanner service):
>
> 1. ~~Run tor service for check to have up to date records~~ done
> 2. ~~Add cron job for check service to reload~~ done
> 3. ~~Integrate DNS zone script into Ansible~~ done
> 4. rm everything, re-deploy, check it still works
> 5. Send service announcement, can consider the new DNS service functional
> at this point (best effort)
> 6. Write up ops doc for deployment and disaster recovery

New description:

 This ticket contains the final tasks that need to be integrated into the
 Ansible playbook for the managed deployment of check-01 (aka the exit
 scanner service):

 1. ~~Run tor service for check to have up to date records~~ done
 2. ~~Add cron job for check service to reload~~ done
 3. ~~Integrate DNS zone script into Ansible~~ done
 4. ~~rm everything, re-deploy, check it still works~~ done

--

Comment:

 Everything will redeploy OK, except for the "make start" step. I think
 this is just something we will live with because this has already dragged
 on too long. It's sufficient that we can quickly recover the service if
 needed.

 Step 5 will happen in #33508 and step 6 in #33510, so removing from the
 scope of this ticket.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33506#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list