move getulum off moly

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.

Trac:
Parent Ticket: #29974 (moved)

added component::internal services/tor sysadmin team owner::hiro parent::29974 priority::medium resolution::fixed severity::normal status::closed type::task labels

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

Trac:
Owner: tpa to hiro
Status: new to assigned

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.

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

Getulum has been decommisioned.

Trac:
Resolution: N/A to fixed
Status: assigned to closed

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 (moved)) 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!

Trac:
Status: closed to reopened
Resolution: fixed to N/A

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

Trac:
Status: reopened to closed
Resolution: N/A to fixed

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

closed

mentioned in issue #29974 (moved)