Opened 11 months ago

Closed 8 months ago

Last modified 7 months ago

#31785 closed task (fixed)

move getulum off moly

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

Description

as part of an effort to reduce our dependence on an old server (moly), we should move getulum (a non-redundant server) to a different host, probably the FSN* cluster.

Child Tickets

Change History (8)

comment:1 Changed 10 months ago by weasel

talked to hiro. we'll set up a new VM and move the service.

comment:2 Changed 10 months ago by hiro

Owner: changed from tpa to hiro
Status: newassigned

comment:3 Changed 10 months ago by hiro

I have created a new VM gettor-01.
All the system configuration is now in puppet, and all the service configuration is now in ansible (https://gitweb.torproject.org/admin/services/gettor.git/).

Gettor is not using anymore virtualenvs. As all the packages are now installed in the system (and added to puppet).

The website part of gettor is being moved to lektor and the www-rotation.

I will continue moving the service and decommisioning getulum. More soon.

comment:4 Changed 10 months ago by hiro

Gettor has now moved to gettor-01.
We can now start decommissioning getulum.

comment:5 Changed 10 months ago by hiro

Resolution: fixed
Status: assignedclosed

Getulum has been decommisioned.

comment:6 Changed 9 months ago by anarcat

Resolution: fixed
Status: closedreopened

got this through the mail this morning:

On 2019-10-25 09:22:00, root wrote:

Volume group "vgname" not found
Cannot process volume group vgname

i thought it was a mistake i made during the dictyotum decom (#31786) but then I saw this message come up:

On 2019-10-25 18:47:00, root wrote:

Failed to find logical volume "vg0/dictyotum-boot"
Failed to find logical volume "vg0/dictyotum-pg"
Failed to find logical volume "vg0/dictyotum-root"
Failed to find logical volume "vg0/dictyotum-swap"

... so I issued the correct at job.

hiro, is it possible you didn't schedule the right volume to be deleted? it seems getulum is still present on moly...

can we delete it?

thanks!

comment:7 Changed 8 months ago by anarcat

Resolution: fixed
Status: reopenedclosed

those files were removed, so i think this is done.

comment:8 Changed 7 months ago by anarcat

i removed getulum from the spreadsheet, for some reason it was still there, but it's definitely not running on moly anymore.

Note: See TracTickets for help on using tickets.