BwUniCluster3.0/Data Migration Guide - Revision history

S Braun: /* Software */

2025-04-22T08:19:35Z

Software

← Older revision		Revision as of 10:19, 22 April 2025
Line 18:		Line 18:
	The operating system on all nodes is Red Hat Enterprise Linux (RHEL) 9.4.		The operating system on all nodes is Red Hat Enterprise Linux (RHEL) 9.4.

	Conda users should note the change to <code>devel/miniforge</code> replacing <code>devel/miniconda</code> (cf. [[Development/~~Python~~ \| ~~Python~~ Documentation]])		Conda users should note the change to <code>devel/miniforge</code> replacing <code>devel/miniconda</code> (cf. [[Development/Conda \| Conda Documentation]])

	== Operations ==		== Operations ==

S Braun: /* Software */

2025-04-22T08:17:27Z

Software

← Older revision		Revision as of 10:17, 22 April 2025
Line 18:		Line 18:
	The operating system on all nodes is Red Hat Enterprise Linux (RHEL) 9.4.		The operating system on all nodes is Red Hat Enterprise Linux (RHEL) 9.4.

	Conda users should note the change to <code>devel/miniforge</code> replacing <code>devel/miniconda</code>.		Conda users should note the change to <code>devel/miniforge</code> replacing <code>devel/miniconda</code> (cf. [[Development/Python \| Python Documentation]])

	== Operations ==		== Operations ==

S Braun: /* Software */

2025-04-22T08:15:18Z

Software

← Older revision		Revision as of 10:15, 22 April 2025
Line 17:		Line 17:
	== Software ==		== Software ==
	The operating system on all nodes is Red Hat Enterprise Linux (RHEL) 9.4.		The operating system on all nodes is Red Hat Enterprise Linux (RHEL) 9.4.


	Conda users should note the change to <code>devel/miniforge</code> replacing <code>devel/miniconda</code>.		Conda users should note the change to <code>devel/miniforge</code> replacing <code>devel/miniconda</code>.

S Braun: /* Software */

2025-04-22T08:15:09Z

Software

← Older revision		Revision as of 10:15, 22 April 2025
Line 17:		Line 17:
	== Software ==		== Software ==
	The operating system on all nodes is Red Hat Enterprise Linux (RHEL) 9.4.		The operating system on all nodes is Red Hat Enterprise Linux (RHEL) 9.4.


			Conda users should note the change to <code>devel/miniforge</code> replacing <code>devel/miniconda</code>.

	== Operations ==		== Operations ==

R Laifer: /* Migration of Workspaces */ Hinweis auf ws_list auf UC2

2025-04-03T12:34:32Z

Migration of Workspaces: Hinweis auf ws_list auf UC2

← Older revision		Revision as of 14:34, 3 April 2025
Line 154:		Line 154:

	If the quota checks are successful, then an appropriate workspace needs to be created and the data transfer can be initiated:<br>		If the quota checks are successful, then an appropriate workspace needs to be created and the data transfer can be initiated:<br>
	1. Create a new workspace with the same name as the old one, e.g. <code>ws_allocate demospace 10</code><br>		1. Create a new workspace with the same name as the old one, e.g. <code>ws_allocate demospace 10</code>. If you do not reemember your old workspace names, go to a login node of bwUniCluster 2.0 and execute the <code>ws_list</code> command.<br>
	2. Transfer the data using the recommended command:<br>		2. Transfer the data using the recommended command:<br>
	<div style="padding-left: 20px;">		<div style="padding-left: 20px;">

S Braun: /* Data Migration */

2025-03-31T06:54:04Z

Data Migration

← Older revision		Revision as of 08:54, 31 March 2025
Line 37:		Line 37:
	= Data Migration =		= Data Migration =

	bwUniCluster 3.0 features a completely new file system, there is no automatic migration of user data! Users have to actively migrate the data to the new file system. During a limited duration of time ('''till July 6, 2025'''), however, the old file system and login nodes remain in operation ~~and~~ is mounted on the new system. It will also be possible to log in to the old bwUniCluster 2.0 login nodes during this period. This leaves enough time to copy any HOME directory and workspace data to be migrated to the new file systems.		bwUniCluster 3.0 features a completely new file system, there is no automatic migration of user data! Users have to actively migrate the data to the new file system. During a limited duration of time ('''till July 6, 2025'''), however, the old file system and login nodes remain in operation. The file system is mounted on the new system. It will also be possible to log in to the old bwUniCluster 2.0 login nodes during this period. This leaves enough time to copy any HOME directory and workspace data to be migrated to the new file systems.
	Please be aware of the new, slightly more stringent quota policies! Before the data can be copied, the new quotas must be checked to see if they are sufficient to accept the old data. If there are any quota issues, users should take a look at their respective data lifecycle management.		Please be aware of the new, slightly more stringent quota policies! Before the data can be copied, the new quotas must be checked to see if they are sufficient to accept the old data. If there are any quota issues, users should take a look at their respective data lifecycle management.

S Braun: /* Data Migration */

2025-03-31T06:53:14Z

Data Migration

← Older revision		Revision as of 08:53, 31 March 2025
Line 37:		Line 37:
	= Data Migration =		= Data Migration =

	bwUniCluster 3.0 features a completely new file system, there is no automatic migration of user data! Users have to actively migrate the data to the new file system. During a limited duration of time ('''till July 6, 2025'''), however, the old file system ~~remains~~ in operation and is mounted on the new system. It will also be possible to log in to the old bwUniCluster 2.0 login nodes during this period. This leaves enough time to copy any HOME directory and workspace data to be migrated to the new file systems.		bwUniCluster 3.0 features a completely new file system, there is no automatic migration of user data! Users have to actively migrate the data to the new file system. During a limited duration of time ('''till July 6, 2025'''), however, the old file system and login nodes remain in operation and is mounted on the new system. It will also be possible to log in to the old bwUniCluster 2.0 login nodes during this period. This leaves enough time to copy any HOME directory and workspace data to be migrated to the new file systems.
	Please be aware of the new, slightly more stringent quota policies! Before the data can be copied, the new quotas must be checked to see if they are sufficient to accept the old data. If there are any quota issues, users should take a look at their respective data lifecycle management.		Please be aware of the new, slightly more stringent quota policies! Before the data can be copied, the new quotas must be checked to see if they are sufficient to accept the old data. If there are any quota issues, users should take a look at their respective data lifecycle management.

S Braun: /* Data Migration */

2025-03-31T06:52:53Z

Data Migration

← Older revision		Revision as of 08:52, 31 March 2025
Line 37:		Line 37:
	= Data Migration =		= Data Migration =

	bwUniCluster 3.0 features a completely new file system, there is no automatic migration of user data! Users have to actively migrate the data to the new file system. During a limited duration of time ('''till ~~June~~ 30, 2025'''), however, the old file system remains in operation and is mounted on the new system. It will also be possible to log in to the old bwUniCluster 2.0 login nodes during this period. This leaves enough time to copy any HOME directory and workspace data to be migrated to the new file systems.		bwUniCluster 3.0 features a completely new file system, there is no automatic migration of user data! Users have to actively migrate the data to the new file system. During a limited duration of time ('''till July 6, 2025'''), however, the old file system remains in operation and is mounted on the new system. It will also be possible to log in to the old bwUniCluster 2.0 login nodes during this period. This leaves enough time to copy any HOME directory and workspace data to be migrated to the new file systems.
	Please be aware of the new, slightly more stringent quota policies! Before the data can be copied, the new quotas must be checked to see if they are sufficient to accept the old data. If there are any quota issues, users should take a look at their respective data lifecycle management.		Please be aware of the new, slightly more stringent quota policies! Before the data can be copied, the new quotas must be checked to see if they are sufficient to accept the old data. If there are any quota issues, users should take a look at their respective data lifecycle management.

S Braun: /* Hardware */

2025-03-31T06:50:25Z

Hardware

← Older revision		Revision as of 08:50, 31 March 2025
Line 12:		Line 12:

	== Hardware ==		== Hardware ==
	The new bwUniCluster 3.0 features more than 340 CPU nodes and 28 GPU nodes. Most of the CPU nodes originate from the bwUniCluster 2.0 Extension and are equipped with the well-known Intel Xeon Platinum 8358 processors (Ice Lake) with 64 cores per dual socket node. The new CPU partition consists of 70 AMD EPYC 9454 nodes with 96 cores per dual socket node. The GPU nodes feature A100 and H100 accelerators by NVIDIA. The ~~one~~ AMD ~~GPU~~ node features MI300A ~~APUs~~.<br>		The new bwUniCluster 3.0 features more than 340 CPU nodes and 28 GPU nodes. Most of the CPU nodes originate from the bwUniCluster 2.0 Extension and are equipped with the well-known Intel Xeon Platinum 8358 processors (Ice Lake) with 64 cores per dual socket node. The new CPU partition consists of 70 AMD EPYC 9454 nodes with 96 cores per dual socket node. The GPU nodes feature A100 and H100 accelerators by NVIDIA. The AMD APU node features 4 MI300A accelerators.<br>
	The node interconnect for the new partitions is InfiniBand 2x/4x NDR200, which is expected to provide even better parallel performance. For details please refer to [[BwUniCluster3.0/Hardware_and_Architecture\|Hardware and Architecture]].		The node interconnect for the new partitions is InfiniBand 2x/4x NDR200, which is expected to provide even better parallel performance. For details please refer to [[BwUniCluster3.0/Hardware_and_Architecture\|Hardware and Architecture]].

S Braun: /* Entitlement, Registration and Login */

2025-03-31T06:48:59Z

Entitlement, Registration and Login

← Older revision		Revision as of 08:48, 31 March 2025
Line 9:		Line 9:
	'''The service bwUniCluster 3.0 will be visible in bwIDM from 07.04.2025 8 o'clock.'''<br>		'''The service bwUniCluster 3.0 will be visible in bwIDM from 07.04.2025 8 o'clock.'''<br>
	The new hostname for login via Secure Shell (SSH) is: '''uc3.scc.kit.edu'''<br>		The new hostname for login via Secure Shell (SSH) is: '''uc3.scc.kit.edu'''<br>
	KIT users have to use the <code>ka_</code> prefix in front of their username.		Like all other users, from now on also KIT users have to use the <code>ka_</code> prefix in front of their username.

	== Hardware ==		== Hardware ==