Site/Location: EQIAD, CODFW
Number of systems: 2
Service: dmarc (reporting)
Networking Requirements: external
Processor Requirements: 1
Memory: 2G
Disks: 25G
Other Requirements:
Description
Description
Details
Details
Related Objects
Related Objects
Event Timeline
Comment Actions
Change 363300 had a related patch set uploaded (by Alexandros Kosiaris; owner: Alexandros Kosiaris):
[operations/dns@master] Introduce diadem, dysprosium
Comment Actions
Change 363300 merged by Alexandros Kosiaris:
[operations/dns@master] Introduce diadem, dysprosium
Comment Actions
Change 363313 had a related patch set uploaded (by Alexandros Kosiaris; owner: Alexandros Kosiaris):
[operations/puppet@production] Introduce diadem, dysprosium
Comment Actions
Change 363313 merged by Alexandros Kosiaris:
[operations/puppet@production] Introduce diadem, dysprosium
Comment Actions
VMs diadem and dysprosium are up and running. In site.pp are marked with only including ::standard so they have all the basic stuff a newly installed box has. I am handing them over to @herron and resolving this.
Comment Actions
Change 394624 had a related patch set uploaded (by Dzahn; owner: Dzahn):
[operations/puppet@production] diadem/dysprosium: introduce skeleton role
Comment Actions
Change 394624 merged by Dzahn:
[operations/puppet@production] diadem/dysprosium: introduce skeleton role
Comment Actions
Hey @herron @akosiaris you might be suprised to see a notification on this ticket from 2017 but .. I just found it by digging backwards in history to find out why we have a "role::dmarc" that is not used on anything and pops up on T272559.
So in git log I said about this in 2017 "diadem/dysprosium: introduce skeleton role" :) and those hosts are what was created here.
But then.. what happened? Did diadem and dysprosium ever end up being used?
edit: sorry, I found T86209#3937223. I'll delete this based on those findings. All good.