Opened 19 months ago

Last modified 22 hours ago

#24956 needs_review defect

put labs.tp.o on hiatus?

Reported by: arma Owned by: anarcat
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: hiro, anarcat, mikeperry Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

labs.tp.o no longer has a valid ssl cert.

weasel is the only one who noticed.

it looks like it is hosted on rackspace, so, not on actual tp.o systems.

should we shut it down? close it for now? archive it somewhere?

Child Tickets

Change History (8)

comment:1 Changed 19 months ago by arma

Owner: changed from alison to mikeperry
Status: newassigned

assigning to mikeperry, since he was the last known labs person, and maybe he knows where it is hosted currently and what the story is there.

(weasel was going to remove the dns record for it, now that the ssl cert is expired. that is a fine start, but i worry that if we do that, we are even more likely to just let the host run, alone and forgotten, forever.)

comment:2 Changed 19 months ago by arma

Cc: hiro added

cc'ing hiro in case she knows anything too

comment:3 Changed 19 months ago by mikeperry

Ok. In order to use the auto-renewed Let's Encrypt cert, we need to point the labs.torproject.org DNS to be a CNAME for live-torlabs.pantheonsite.io.

(Separately, we should also decide if we want Tor Labs to be a thing -- it needs a community manager to interface with volunteer projects to showcase them on there. I don't really have the cycles for that).

comment:4 Changed 2 months ago by arma

Cc: anarcat added

Looks like labs.torproject.org doesn't ping. And the IP address doesn't reverse-resolve to anything.

Does that mean we closed down the machine?

Or does it mean we lost track of it and somebody is still paying for a machine that isn't on anymore? :)

cc'ing Anarcat so he can follow along.

comment:5 Changed 2 months ago by arma

Component: Community/OutreachInternal Services/Tor Sysadmin Team

comment:6 Changed 8 weeks ago by gaba

Cc: mikeperry added
Owner: mikeperry deleted

comment:7 Changed 4 days ago by anarcat

Owner: set to anarcat

comment:8 Changed 4 days ago by anarcat

Status: assignedneeds_review

i'm not sure what that thing is or was, but it's nowhere on my radar here.

going through the retire-a-host procedure exercise shows me the following:

  1. the service is not in nagios
  2. it's not a VM we manage
  3. N/A
  4. N/A
  5. it's not in LDAP or sudoers
  6. it's got a record in the DNS
  7. it's not in Puppet
  8. ditto
  9. it's not in tor-passwords

So, from my perspective, that box doesn't exist at all, apart from DNS. So if there are no objections here in the coming two week, I'll remove this entry from DNS on or after September 3rd 2019 (2019-09-03).

Then we can consider this service retired, whatever it was. :)

Last edited 22 hours ago by anarcat (previous) (diff)
Note: See TracTickets for help on using tickets.