Project

General

Profile

Actions

tickets #111677

closed

Decommissioning of unused machines

Added by lrupp almost 2 years ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Servers hosted in NBG
Target version:
-
Start date:
2022-05-27
Due date:
% Done:

100%

Estimated time:

Description

Just out of interest, what should happen with the existing, but not used machines:
[x] fedora-accounts.infra.opensuse.org (last login from hellcp in at Dec 2 - kept up-to date from other people since than)
[x] fedora-freeipa.infra.opensuse.org (last login from hellcp in May 6 - kept up-to date from other people since than)
[x] identification.infra.opensuse.org (last login from hellcp in Dec 2 - kept up-to date from other people since than)
[ ] new-forum.infra.opensuse.org (last login from others than the people keeping the machine up-to date not detectable) - will keep it, see comment 6

If there is no general objection, the following will happen:
[x] machines will be powered down at the end of June 2022
[x] removed from monitoring
[x] removed from backup
[ ] delete the pillar/id/ files of these machines, but keep the actual salt code (roles etc.)
[ ] machine images (incl. data) will be removed at the end of Dec 2022

Actions #1

Updated by pjessen almost 2 years ago

  • Private changed from Yes to No

lrupp wrote:

  • new-forum.infra.opensuse.org (last login from others than the people keeping the machine up-to date not detectable)

I can tell I was last logged in a little more than a year ago. I'm guessing this machine was for the planned move to the new vBulletin. Which is on hold until we get the authentication sorted out. I have no idea when that might be.

Actions #2

Updated by lrupp almost 2 years ago

  • Assignee set to hellcp
Actions #3

Updated by lrupp almost 2 years ago

Sasi, any comment from your side?
IMHO most of the machines were requested by you (if I remember correctly)?

Actions #4

Updated by lrupp almost 2 years ago

  • Status changed from New to Feedback
Actions #5

Updated by hellcp almost 2 years ago

They can go, none of them have anything of value on them after the decision to use the current horrible login system was reached, so I don't see a reason to keep them around

Actions #6

Updated by cboltz almost 2 years ago

IMHO new-forum should stay - in the hope that someone finds time to fix the login ;-)

Actions #7

Updated by lrupp almost 2 years ago

  • Description updated (diff)

Machines decommissioned:

  • removed from monitoring
  • checked backup: nothing in there
  • checked Galera-Cluster & PostgreSQL: no databases found
  • ran last update
  • machines shutdown

How do we/should we handle:

  • Salt certificate: should we delete the key (to avoid that the salt-master is waiting for the offline machines on each global run)?
  • Git repo: should we keep the configurations of the machines in the repository (including needed adjustments in the future, if there are changes affecting our CI)?
Actions #8

Updated by cboltz almost 2 years ago

lrupp wrote:

How do we/should we handle:

  • Salt certificate: should we delete the key (to avoid that the salt-master is waiting for the offline machines on each global run)?

Yes, please salt-key -d them.

  • Git repo: should we keep the configurations of the machines in the repository (including needed adjustments in the future, if there are changes affecting our CI)?

Usually I'd say delete the pillar/id/ files of these machines, but keep the actual salt code (roles etc.). However, our CI scripts check for unused roles, which makes this question more interesting[tm].

@hellcp: what's your opinion on this?

Actions #9

Updated by lrupp over 1 year ago

  • Description updated (diff)
Actions #10

Updated by lrupp over 1 year ago

  • Description updated (diff)
Actions #11

Updated by lrupp over 1 year ago

  • Description updated (diff)
Actions #12

Updated by lrupp over 1 year ago

  • Tracker changed from communication to tickets
Actions #13

Updated by crameleon about 1 year ago

IMHO new-forum should stay

Is this statement still valid, now that discourse01.i.o.o runs forums.o.o?

On new-forum.i.o.o I only find some PHP/VB5 "stuff".

Actions #14

Updated by crameleon about 1 year ago

  • Status changed from Feedback to In Progress
  • Assignee changed from hellcp to crameleon
  • % Done changed from 0 to 50
  • fedora-accounts.infra.opensuse.org
  • fedora-freeipa.infra.opensuse.org

These machines were not powered on and no Salt keys could be found. I disabled the VM definitions and deleted the disks.

  • identification.infra.opensuse.org

This machine was still running and connected with Salt. I shut it down and will proceed with the deletions if there are no complaints within a week.

Actions #15

Updated by crameleon about 1 year ago

  • Category set to Servers hosted in NBG
Actions #16

Updated by crameleon about 1 year ago

@cboltz, @hellcp - can fedora-sso.i.o.o go away as well? The description states it is (was?) a testing machine.

Actions #17

Updated by crameleon 11 months ago

  • Status changed from In Progress to Feedback

Removed fedora-sso.i.o.o as there has not been any feedback and the machine seems to be stuck in a GRUB rescue shell since a long time without anyone complaining.

Leaves the question about new-forum.i.o.o. @cboltz

Actions #18

Updated by crameleon 11 months ago

Seems the forums application on new-forum.i.o.o is broken anyways - nginx points to /run/php-fpm/forums.sock, but there is only /run/php-fpm/forums. The last nginx access log entries are from a week ago, some web scraping bot. I shut it down now and if nobody complains within a few days I'll remove it.

Actions #19

Updated by luc14n0 11 months ago

crameleon wrote:

IMHO new-forum should stay

Is this statement still valid, now that discourse01.i.o.o runs forums.o.o?

On new-forum.i.o.o I only find some PHP/VB5 "stuff".

Yeah, I don't think we're going back to VBulletin anymore, right?!

Actions #20

Updated by pjessen 11 months ago

  • Subject changed from Decomission of unused machines to Decommissioning of unused machines

crameleon wrote:

Seems the forums application on new-forum.i.o.o is broken anyways - nginx points to /run/php-fpm/forums.sock, but there is only /run/php-fpm/forums. The last nginx access log entries are from a week ago, some web scraping bot. I shut it down now and if nobody complains within a few days I'll remove it.

Confirm new-forum.i.o.o can be removed - it was used for testing a fix of the vBulletin database, but we have since migrated off vBulletin.

Actions #21

Updated by crameleon 11 months ago

  • Status changed from Feedback to In Progress
  • % Done changed from 50 to 60

Great, thank you for confirming, @luc14n0 and @pjessen.

Actions #22

Updated by crameleon 11 months ago

  • % Done changed from 60 to 80
Actions #23

Updated by crameleon 9 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100

All listed machines have now been taken care of.

Actions

Also available in: Atom PDF