Maintenance Schedule - Revision history

Haars0011: IA migration §10: rewrite as maintenance schedule (6-monthly downtimes); reporting via How to Get Help; TODO for live dates (via update-page on MediaWiki MCP Server)

2026-06-19T07:16:39Z

IA migration §10: rewrite as maintenance schedule (6-monthly downtimes); reporting via How to Get Help; TODO for live dates (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 07:16, 19 June 2026
Line 1:		Line 1:
	~~== Maintenance~~ and ~~Management ==~~		Anunna is taken down for planned maintenance — firmware and software updates — roughly twice a year. Typically one downtime is scheduled in April or May, in a week free of teaching, and another in October, to disrupt usage as little as possible.

	~~The~~ cluster is ~~maintained for firmware and software updates on a six-monthly basis~~. ~~Typically one downtime is~~ scheduled ~~in April/May in~~ a ~~week that is free of education~~, ~~whilst~~ the ~~other is scheduled in October, in order to disrupt usage as little as possible~~.		During a downtime the cluster is unavailable. Jobs are not scheduled to run across a planned downtime, so check the announced dates when planning long jobs.

	~~Any issues should be directed to us through [https://support.wur.nl/ WUR's Support portal]~~		== Announcements ==

	~~Choose Support --> Create a ticket~~ and ~~register this On~~ the ~~HPC (Anunna) service~~.		Planned maintenance is announced in advance — watch the Message of the Day on the [[Portal Overview\|Apps Portal]] and the usual support channels.

	~~Questions~~ or ~~incidents can also be registered via the mail: servicedesk~~.~~it@wur.nl~~		<!-- TODO: confirm where maintenance dates are announced (Apps Portal MOTD, mailing list, Teams) and add the next scheduled downtime, or a link to a live maintenance schedule. -->
	~~And it can be done via the telephone: +31 317 488888~~
	~~Please give your name and phonenumber and tell that your mail/call~~ is ~~about Anunna and give the company you are~~ working ~~for~~.		== Reporting problems ==
	~~When you call the servicedesk, give~~ also ~~your email address.~~
			If something is not working — during or outside maintenance — see [[How to Get Help]].

			== See also ==
			* [[How to Get Help]]
			* [[Cluster Architecture Overview]]

Haars0011: Haars0011 moved page Maintenance and Management to Maintenance Schedule: IA migration §10: rename Maintenance and Management → Maintenance Schedule (leaving redirect) (via move-page on MediaWiki MCP Server)

2026-06-19T07:16:30Z

Haars0011 moved page Maintenance and Management to Maintenance Schedule: IA migration §10: rename Maintenance and Management → Maintenance Schedule (leaving redirect) (via move-page on MediaWiki MCP Server)

← Older revision	Revision as of 07:16, 19 June 2026
(No difference)

Itter003 at 12:57, 13 April 2026

2026-04-13T12:57:07Z

← Older revision		Revision as of 12:57, 13 April 2026
Line 1:		Line 1:
	== Maintenance and Management ==		== Maintenance and Management ==

	The cluster is maintained for firmware and software updates on a six-monthly basis. Typically one downtime is scheduled in May, whilst the other is scheduled in October, in order to disrupt usage as little as possible.		The cluster is maintained for firmware and software updates on a six-monthly basis. Typically one downtime is scheduled in April/May in a week that is free of education, whilst the other is scheduled in October, in order to disrupt usage as little as possible.

	Any issues should be directed to us through [https://support.wur.nl/ WUR's Support portal]		Any issues should be directed to us through [https://support.wur.nl/ WUR's Support portal]

Itter003 at 12:51, 20 February 2026

2026-02-20T12:51:36Z

← Older revision		Revision as of 12:51, 20 February 2026
Line 3:		Line 3:
	The cluster is maintained for firmware and software updates on a six-monthly basis. Typically one downtime is scheduled in May, whilst the other is scheduled in October, in order to disrupt usage as little as possible.		The cluster is maintained for firmware and software updates on a six-monthly basis. Typically one downtime is scheduled in May, whilst the other is scheduled in October, in order to disrupt usage as little as possible.

	Any issues should be directed to ~~the~~ WUR ~~IT Servicedesk:~~		Any issues should be directed to us through [https://support.wur.nl/ WUR's Support portal]

	~~This~~ can be ~~done~~ via the mail: servicedesk.it@wur.nl		Choose Support --> Create a ticket and register this On the HPC (Anunna) service.

			Questions or incidents can also be registered via the mail: servicedesk.it@wur.nl
	And it can be done via the telephone: +31 317 488888		And it can be done via the telephone: +31 317 488888
	Please give your name and phonenumber and tell that your mail/call is about Anunna and give the company you are working for.		Please give your name and phonenumber and tell that your mail/call is about Anunna and give the company you are working for.
	When you call the servicedesk, give also your email address.		When you call the servicedesk, give also your email address.

	~~== Previous Maintenance Windows ==~~

Haars0011 at 07:46, 23 May 2025

2025-05-23T07:46:28Z

← Older revision		Revision as of 07:46, 23 May 2025
Line 11:		Line 11:

	== Previous Maintenance Windows ==		== Previous Maintenance Windows ==

	~~=== Maintenance May 24th 2017 ===~~
	~~This update moved Bright Cluster Manager to version 7.3, and SLURM to 16.08. Downtime was 8am to 8pm.~~

	~~=== Maintenance November 16th 2016 ===~~
	~~This was a firmware update and OS update for the system. Downtime was 8am to 8pm.~~

	~~=== Maintenance May 23rd-29th 2016 ===~~
	This update moved the OS from Scientific Linux 6 to Scientific Linux 7, and updated Bright Cluster manager to version 7.2. A week was taken to reconstruct the entire environment from scratch, thanks to assistance from Clustervision for this expedience.

	~~=== Maintenance March 23rd 2016 ===~~
	There will be mainly firmware maintenance between 8h and 20h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, Anunna will be shut down during this maintenance window. Running jobs will be killed!

	~~=== Maintenance June 17th 2015 ===~~
	There will be mainly firmware maintenance between 8h and 20h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, Anunna will be shut down during this maintenance window. Running jobs will be killed!

	~~=== Maintenance November 26th 2014 ===~~
	There will be mainly firmware maintenance between 8h and 20h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, Anunna will be shut down during this maintenance window. Running jobs will be killed!

	~~=== Maintenance June 11th 2014 ===~~
	There will be mainly firmware maintenance between 8h and 13h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, Anunna will be shut down during this maintenance window. Running jobs will be killed!

Haars0011: /* Maintenance and Management */

2025-05-23T07:41:49Z

Maintenance and Management

← Older revision		Revision as of 07:41, 23 May 2025
Line 1:		Line 1:
	== Maintenance and Management ==		== Maintenance and Management ==

	The cluster is maintained for firmware and software updates on a six-monthly basis. Typically one downtime is scheduled in May, whilst the other is scheduled in ~~November~~, in order to disrupt usage as little as possible.		The cluster is maintained for firmware and software updates on a six-monthly basis. Typically one downtime is scheduled in May, whilst the other is scheduled in October, in order to disrupt usage as little as possible.

	Any issues should be directed to the WUR IT Servicedesk:		Any issues should be directed to the WUR IT Servicedesk:

Vaend001 at 17:43, 19 February 2019

2019-02-19T17:43:25Z

← Older revision		Revision as of 17:43, 19 February 2019
Line 22:		Line 22:

	=== Maintenance March 23rd 2016 ===		=== Maintenance March 23rd 2016 ===
	There will be mainly firmware maintenance between 8h and 20h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, ~~the HPC~~ will be shut down during this maintenance window. Running jobs will be killed!		There will be mainly firmware maintenance between 8h and 20h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, Anunna will be shut down during this maintenance window. Running jobs will be killed!

	=== Maintenance June 17th 2015 ===		=== Maintenance June 17th 2015 ===
	There will be mainly firmware maintenance between 8h and 20h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, ~~the HPC~~ will be shut down during this maintenance window. Running jobs will be killed!		There will be mainly firmware maintenance between 8h and 20h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, Anunna will be shut down during this maintenance window. Running jobs will be killed!

	=== Maintenance November 26th 2014 ===		=== Maintenance November 26th 2014 ===
	There will be mainly firmware maintenance between 8h and 20h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, ~~the HPC~~ will be shut down during this maintenance window. Running jobs will be killed!		There will be mainly firmware maintenance between 8h and 20h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, Anunna will be shut down during this maintenance window. Running jobs will be killed!

	=== Maintenance June 11th 2014 ===		=== Maintenance June 11th 2014 ===
	There will be mainly firmware maintenance between 8h and 13h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, ~~the HPC~~ will be shut down during this maintenance window. Running jobs will be killed!		There will be mainly firmware maintenance between 8h and 13h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, Anunna will be shut down during this maintenance window. Running jobs will be killed!

Vaend001 at 17:42, 19 February 2019

2019-02-19T17:42:17Z

← Older revision		Revision as of 17:42, 19 February 2019
Line 7:		Line 7:
	This can be done via the mail: servicedesk.it@wur.nl		This can be done via the mail: servicedesk.it@wur.nl
	And it can be done via the telephone: +31 317 488888		And it can be done via the telephone: +31 317 488888
	Please give your name and phonenumber and tell that your mail/call is about ~~the HPC for Agrogenomics~~ and give the company you are working for.		Please give your name and phonenumber and tell that your mail/call is about Anunna and give the company you are working for.
	When you call the servicedesk, give also your email address.		When you call the servicedesk, give also your email address.

Dawes001: /* Maintenance May 23rd-29th 2016 */

2017-06-01T11:50:24Z

Maintenance May 23rd-29th 2016

← Older revision		Revision as of 11:50, 1 June 2017
Line 19:		Line 19:

	=== Maintenance May 23rd-29th 2016 ===		=== Maintenance May 23rd-29th 2016 ===
	This update moved the OS from Scientific Linux 6 to Scientific Linux 7, and updated Bright Cluster manager to version 7.2. A week was taken to reconstruct the entire environment from scratch, thanks to assistance from ~~CLustervision~~ for this expedience.		This update moved the OS from Scientific Linux 6 to Scientific Linux 7, and updated Bright Cluster manager to version 7.2. A week was taken to reconstruct the entire environment from scratch, thanks to assistance from Clustervision for this expedience.

	=== Maintenance March 23rd 2016 ===		=== Maintenance March 23rd 2016 ===

Dawes001 at 11:49, 1 June 2017

2017-06-01T11:49:58Z

← Older revision		Revision as of 11:49, 1 June 2017
Line 31:		Line 31:

	=== Maintenance June 11th 2014 ===		=== Maintenance June 11th 2014 ===
	There will be mainly firmware maintenance between 8h and 13h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, the HPC will be shut down during this maintenance window. Running jobs will be killed!

	~~=== Maintenance November 26th 2014 ===~~
	There will be mainly firmware maintenance between 8h and 13h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, the HPC will be shut down during this maintenance window. Running jobs will be killed!		There will be mainly firmware maintenance between 8h and 13h CET . Because network controller and storage controller firmware will be upgrades, all servers need to be rebooted and also will have network hick ups. So to prevent job and/or data corruption, the HPC will be shut down during this maintenance window. Running jobs will be killed!