Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 45 Next »

Planned changes

Active changes today

Closed changes

Planned O/S security patches this month

Closed O/S security patches last 30 days

Patch management of Operating System security patches is carried out using an automatic and unattended tool. The tool is scheduled to apply patches to all servers according to the schedule below. The schedule matches the allowed service windows and repeats every month.

First Saturday (at 01:00)

  • preprod-lb02.fut.netic.dk

  • prod001-lb02.fut.netic.dk

Second Saturday (at 01:00)

  • preprod-db01.fut.netic.dk

  • preprod-es01.fut.netic.dk

  • preprod-lb01.fut.netic.dk

  • preprod-mq01.fut.netic.dk

  • preprod-rancher01.fut.netic.dk

  • preprod-vault01.fut.netic.dk

  • prod001-db01.fut.netic.dk

  • prod001-es01.fut.netic.dk

  • prod001-lb01.fut.netic.dk

  • prod001-mq01.fut.netic.dk

  • prod001-vault01.fut.netic.dk

Third Saturday (at 01:00)

  • admin-vault01.fut.netic.dk

  • prod-db01.fut.netic.dk

  • prod-es01.fut.netic.dk

  • gitlab01.fut.netic.dk

  • harbor01.fut.netic.dk

  • keycloak01.fut.netic.dk

  • prod-lb01.fut.netic.dk

  • prod-mq01.fut.netic.dk

  • prod-rancher01.fut.netic.dk

  • splunk01.fut.netic.dk

  • syslog01.fut.netic.dk

  • prod-vault01.fut.netic.dk

Fourth Saturday (at 01:00)

  • keycloak02.fut.netic.dk

  • prod-lb02.fut.netic.dk

In order to assess whether the patches are correctly applied, please refer to the patch management tickets displayed in the column to the right. A ticket is created for every patching run and for every server. The resolution indicates whether the server has been correctly patched. It can be of two values: Patched or Failed.

  • No labels