Upgrade box for EventLogging, the current box we use -vanadium- is to be replaced by a newer, most robust system
Description
Details
Related Objects
- Mentioned In
- rOMWCa70d30146d91: Send server side eventlogging logs to eventlog1001 instead of vanadium
rOPUP3196131da692: Use ensure => present for default varnish::logging
rOPUP672920583694: Use ensure => absent for varnish::logging vanadium
rOPUP31cae723f550: Use eventlog1001 as main eventlogging host instead of vanadium
rOPUP9bfc27307e62: Puppetize eventlog1001
Event Timeline
@ori, do you know the status of this? Nuria says that you know of some box that has been slated for this use? I'm happy to go ahead and do this upgrade, if you will point me in the right direction.
PROBLEM - RAID on vanadium is CRITICAL: CRITICAL: Active: 4, Working: 4, Failed: 2, Spare: 0
Just happened, so this box needs to be replaced pretty quickly. now.
since this is a SPOF for EventLogging, and plenty of people will be sadface if eventlogging dies.
Change 201724 had a related patch set uploaded (by Ottomata):
Use eventlog1001 as main eventlogging host instead of vanadium
Change 201724 merged by Ottomata:
Use eventlog1001 as main eventlogging host instead of vanadium
Change 201734 had a related patch set uploaded (by Ottomata):
Use ensure => absent for varnish::logging vanadium
Change 201735 had a related patch set uploaded (by Ottomata):
Use ensure => present for default varnish::logging
Change 201737 had a related patch set uploaded (by Ottomata):
Send server side eventlogging logs to eventlog1001 instead of vanadium
Change 201737 merged by jenkins-bot:
Send server side eventlogging logs to eventlog1001 instead of vanadium
Things are looking good! eventlog1001 has fully taken over all vanadium duties. I will leave vanadium up for now, and decommission it next week.