bwCloud-OS - Recent changes [en]

Blocked and Allowed Ports

Sia — Mon, 13 Apr 2026 18:29:00 GMT

← Older revision		Revision as of 18:29, 13 April 2026
Line 22:		Line 22:
	== Region Mannheim ==		== Region Mannheim ==

	The ~~bwcloud~~ networks are accessible from the outside on '''all ports'''.		The bwCloud-OS networks are accessible from the outside on '''all ports'''.

	The following ports are blocked outbound (for all networks):		The following ports are blocked outbound (for all networks):

Booking Units

Admin — Fri, 10 Apr 2026 11:13:59 GMT

Reference values for BEH calculation in bwCloud-OS

← Older revision		Revision as of 11:13, 10 April 2026
Line 60:		Line 60:

	* '''vCPU''': One virtual CPU allocated for one day constitutes one reference unit of compute consumption:		* '''vCPU''': One virtual CPU allocated for one day constitutes one reference unit of compute consumption:
	** 1 vCPU ~~eqals~~ 1 BEH/day		** 1 vCPU equals 1 BEH/day

	* '''RAM''': One gigabyte (GB) of allocated main memory for one day constitutes two reference unit of memory consumption:		* '''RAM''': One gigabyte (GB) of allocated main memory for one day constitutes two reference unit of memory consumption:

Blocked and Allowed Ports

Admin — Thu, 02 Apr 2026 10:51:17 GMT

Region Mannheim

@@ Line 18: / Line 18: @@
 |-
 |-
 == Region Mannheim ==
-In the "well-known" ports range (i.e., ports below 1024), the following ports are open in server networks:
+The bwcloud networks are accessible from the outside on '''all ports'''.
-{| class="wikitable"
+The following ports are blocked outbound (for all networks):
 {| class="wikitable"
-! Transport !! Port !! Protocol !! Description !! Blocking
+! Transport !! Port !! Description
 |-
-| TCP || 9075 || nx-os || Cisco Nexus || inbound
+| UDP, TCP || 128 || Reserved / GSS X License
 |-
-| UDP || 11211 || memcached || Memcached || inbound
+| TCP || 129-139 || NetBIOS / RPC
 |-
-| TCP || 27017 || MongoDB || MongoDB || inbound
+| UDP, TCP || 445 || SMB / Microsoft-DS
 |-
-| UDP || 32100 || IoT || IoT || outbound
+| UDP || 11211 || Memcached
 |-
-| UDP || 32414 || open-SSDP || Plex Media Servers || inbound
+| UDP || 32100 || IoT
 |}

Blocked and Allowed Ports

Admin-ulm-1 — Tue, 31 Mar 2026 12:36:02 GMT

Region Ulm

@@ Line 10: / Line 10: @@
 It may also happen that seemingly outbound connections from the instance to certain services do not work. This occurs whenever the external server providing the service tries to establish a return connection to the instance, which is often difficult for the user to verify.
 == Region Mannheim ==
@@ Line 95: / Line 103: @@
 | UDP, TCP || 111 || RPC Portmapper || Portmapper Security || inbound/outbound
 |}
 {| class="wikitable"
 |-
 |}

Table: Images Gen3

Admin — Tue, 31 Mar 2026 08:49:54 GMT

← Older revision		Revision as of 08:49, 31 March 2026
Line 4:		Line 4:
	! style="background-color: #232e58; color: white; padding: 12px; text-align: left; font-weight: bold; border: 1px solid #1a2340;" \| Last Updated		! style="background-color: #232e58; color: white; padding: 12px; text-align: left; font-weight: bold; border: 1px solid #1a2340;" \| Last Updated
	! style="background-color: #232e58; color: white; padding: 12px; text-align: left; font-weight: bold; border: 1px solid #1a2340;" \| Min. Disk (GB)		! style="background-color: #232e58; color: white; padding: 12px; text-align: left; font-weight: bold; border: 1px solid #1a2340;" \| Min. Disk (GB)
	~~! style="background-color: #232e58; color: white; padding: 12px; text-align: left; font-weight: bold; border: 1px solid #1a2340;" \| Min. RAM (MB)~~
	\|-		\|-
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| AlmaLinux 10		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| AlmaLinux 10
Line 10:		Line 9:
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" \| 20.03.2026		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" \| 20.03.2026
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 10		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 10
	~~\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 256~~
	\|-		\|-
	\| style="padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| CentOS Stream 10		\| style="padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| CentOS Stream 10
Line 16:		Line 14:
	\| style="padding: 10px; border: 1px solid #ddd;" \| 20.03.2026		\| style="padding: 10px; border: 1px solid #ddd;" \| 20.03.2026
	\| style="padding: 10px; border: 1px solid #ddd; text-align: center;" \| 10		\| style="padding: 10px; border: 1px solid #ddd; text-align: center;" \| 10
	~~\| style="padding: 10px; border: 1px solid #ddd; text-align: center;" \| 256~~
	\|-		\|-
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| Debian 13		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| Debian 13
Line 22:		Line 19:
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" \| 19.03.2026		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" \| 19.03.2026
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 3		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 3
	~~\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 256~~
	\|-		\|-
	\| style="padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| Fedora 43		\| style="padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| Fedora 43
Line 28:		Line 24:
	\| style="padding: 10px; border: 1px solid #ddd;" \| 20.03.2026		\| style="padding: 10px; border: 1px solid #ddd;" \| 20.03.2026
	\| style="padding: 10px; border: 1px solid #ddd; text-align: center;" \| 5		\| style="padding: 10px; border: 1px solid #ddd; text-align: center;" \| 5
	~~\| style="padding: 10px; border: 1px solid #ddd; text-align: center;" \| 256~~
	\|-		\|-
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| openSUSE Leap 16.0		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| openSUSE Leap 16.0
Line 34:		Line 29:
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" \| 20.03.2026		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" \| 20.03.2026
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 3		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 3
	~~\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 256~~
	\|-		\|-
	\| style="padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| Rocky 10		\| style="padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| Rocky 10
Line 40:		Line 34:
	\| style="padding: 10px; border: 1px solid #ddd;" \| 20.03.2026		\| style="padding: 10px; border: 1px solid #ddd;" \| 20.03.2026
	\| style="padding: 10px; border: 1px solid #ddd; text-align: center;" \| 10		\| style="padding: 10px; border: 1px solid #ddd; text-align: center;" \| 10
	~~\| style="padding: 10px; border: 1px solid #ddd; text-align: center;" \| 256~~
	\|-		\|-
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| Ubuntu 24.04		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| Ubuntu 24.04
Line 46:		Line 39:
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" \| 20.03.2026		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" \| 20.03.2026
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 5		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 5
	~~\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 256~~
	\|}		\|}

Networks Gen3

Sia — Fri, 27 Mar 2026 08:55:06 GMT

← Older revision		Revision as of 08:55, 27 March 2026
(One intermediate revision by the same user not shown)
Line 20:		Line 20:
	By default, every VM receives a '''public IPv6 address'''. Depending on the assigned or chosen network, it also receives either a '''public IPv4 address''' or a '''private IPv4 address'''. In the latter case, '''IPv4 egress connectivity''' is provided via '''SNAT'''.		By default, every VM receives a '''public IPv6 address'''. Depending on the assigned or chosen network, it also receives either a '''public IPv4 address''' or a '''private IPv4 address'''. In the latter case, '''IPv4 egress connectivity''' is provided via '''SNAT'''.

	'''Note:''' In not available by default, '''IPv4 ingress connectivity''' can also be provided via a [https://bw-support.scc.kit.edu/ support ticket].		'''Note:''' If not available by default, '''IPv4 ingress connectivity''' can also be provided via a [https://bw-support.scc.kit.edu/ support ticket].

	'''Note:''' Each '''[[Registration#Regions\|region]]''' in bwCloud-OS has its own set of networks and IP address ranges'''.'''		'''Note:''' Each '''[[Registration#Regions\|region]]''' in bwCloud-OS has its own set of networks and IP address ranges'''.'''
Line 38:		Line 38:
	<span id="Floating-IPs"></span>		<span id="Floating-IPs"></span>

	Yes.		Yes.

	'''Floating IPs''' provide a mechanism to perform 1:1 NAT between a public IPv4 address and a private IPv4 address of an instance enabling ingress IPv4 connectivity.		'''Floating IPs''' provide a mechanism to perform 1:1 NAT between a public IPv4 address and a private IPv4 address of an instance enabling ingress IPv4 connectivity.

Guide: Network Configuration by Region

Sia — Thu, 26 Mar 2026 06:56:11 GMT

← Older revision		Revision as of 06:56, 26 March 2026
Line 84:		Line 84:
	* They can be assigned to projects upon request via a '''[https://bw-support.scc.kit.edu/ support ticket]'''.		* They can be assigned to projects upon request via a '''[https://bw-support.scc.kit.edu/ support ticket]'''.

	Once assigned, a Floating IP can be associated with an instance to provide '''IPv4 ingress connectivity'''.		Once assigned to a project, a Floating IP can be associated with an instance to provide '''IPv4 ingress connectivity'''.

	=== Flat External Networks ===		=== Flat External Networks ===

Networks Gen3

Sia — Tue, 24 Mar 2026 16:53:12 GMT

← Older revision		Revision as of 16:53, 24 March 2026
Line 73:		Line 73:
	'''Example:'''		'''Example:'''

	If your instance name is <code>instance-name</code> the project is called <code>project-name</code> and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>instance-name.project-name.vm.ma.bwcloud-os-instance.de</pre>The FQDN can also be found in the '''[https://portal.ul.bwcos.de/ Dashboard]''', under '''Instances''' -> '''Instance Name''' -> '''Interfaces''' -> '''Name'''.		If your instance name is <code>instance-name</code> the project is called <code>project-name</code> and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>instance-name.project-name.vm.ma.bwcloud-os-instance.de</pre>

			<!--The FQDN can also be found in the '''[https://portal.ul.bwcos.de/ Dashboard]''', under '''Instances''' -> '''Instance Name''' -> '''Interfaces''' -> '''Name'''.
			-->

	== Can I get a request more DNS records in bwCloud-OS? ==		== Can I get a request more DNS records in bwCloud-OS? ==

Key User: Migration Guide

Admin — Mon, 23 Mar 2026 12:50:32 GMT

Networks

← Older revision		Revision as of 12:50, 23 March 2026
(One intermediate revision by the same user not shown)
Line 26:		Line 26:
	=== Networks ===		=== Networks ===

	The new ~~bwCloud-OS Gen3 environment~~ includes ~~significant changes to the~~ network ~~architecture~~. ~~These region~~-specific ~~changes are described~~ in the following ~~Guide~~.		The new infrastructure includes not only new networks but also new network-related features such as load balancers. You can find an overview [[Networks_Gen3\|here]].

			Network-specific differences between regions and details about the individual networks can be found in the following guide.


	➡️ [[Guide:_Network_Configuration_by_Region\|Guide: Network Configuration by Region]]		➡️ [[Guide:_Network_Configuration_by_Region\|Guide: Network Configuration by Region]]

Guide: SSH

Sia — Sat, 21 Mar 2026 17:28:52 GMT

← Older revision		Revision as of 17:28, 21 March 2026
(One intermediate revision by the same user not shown)
Line 260:		Line 260:

	⚠️ '''Note:''' When you connect via Remote-SSH for the first time, VS Code automatically installs a small server component on your VM (typically under <code>~/.vscode-server</code>). Depending on your workload, this background service may consume noticeable resources — especially memory (RAM), which may even cause the VM to become unresponsive if its flavor is too small.		⚠️ '''Note:''' When you connect via Remote-SSH for the first time, VS Code automatically installs a small server component on your VM (typically under <code>~/.vscode-server</code>). Depending on your workload, this background service may consume noticeable resources — especially memory (RAM), which may even cause the VM to become unresponsive if its flavor is too small.

			⚠️ '''Note:''' In some rare cases, installing the server component on the remote host (step 3 below) fails, this is usually due to some (experimental) settings of the extension Remote-SSH. For example, for openSUSE 16 disabling "Use Exec Sever" in the settings of remote-SSH can solve the issue.

	=== Setting Up VS Code and Remote-SSH ===		=== Setting Up VS Code and Remote-SSH ===

Table: Images Gen3

Sia — Fri, 20 Mar 2026 18:53:28 GMT

← Older revision		Revision as of 18:53, 20 March 2026
(One intermediate revision by the same user not shown)
Line 31:		Line 31:
	\|-		\|-
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| openSUSE Leap 16.0		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" \| openSUSE Leap 16.0
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" \| <code style="background-color: #e8f1fa; padding: 2px 6px; border-radius: 3px; color: #07307d; font-weight: 500;">~~opensuse~~</code>		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" \| <code style="background-color: #e8f1fa; padding: 2px 6px; border-radius: 3px; color: #07307d; font-weight: 500;">sles</code>
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" \| 20.03.2026		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" \| 20.03.2026
	\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 3		\| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" \| 3

Table: Images Gen3

Admin — Fri, 20 Mar 2026 09:54:37 GMT

Created page with "{| class="wikitable sortable" style="border-collapse: collapse; width: 100%; margin: 1em 0; font-family: sans-serif;" ! style="background-color: #232e58; color: white; padding: 12px; text-align: left; font-weight: bold; border: 1px solid #1a2340;" | Image Name ! style="background-color: #232e58; color: white; padding: 12px; text-align: left; font-weight: bold; border: 1px solid #1a2340;" | Default SSH Username ! style="background-color: #232e58; color: white; padding: 12..."

New page

{| class="wikitable sortable" style="border-collapse: collapse; width: 100%; margin: 1em 0; font-family: sans-serif;"
! style="background-color: #232e58; color: white; padding: 12px; text-align: left; font-weight: bold; border: 1px solid #1a2340;" | Image Name
! style="background-color: #232e58; color: white; padding: 12px; text-align: left; font-weight: bold; border: 1px solid #1a2340;" | Default SSH Username
! style="background-color: #232e58; color: white; padding: 12px; text-align: left; font-weight: bold; border: 1px solid #1a2340;" | Last Updated
! style="background-color: #232e58; color: white; padding: 12px; text-align: left; font-weight: bold; border: 1px solid #1a2340;" | Min. Disk (GB)
! style="background-color: #232e58; color: white; padding: 12px; text-align: left; font-weight: bold; border: 1px solid #1a2340;" | Min. RAM (MB)
|-
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" | AlmaLinux 10
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" | <code style="background-color: #e8f1fa; padding: 2px 6px; border-radius: 3px; color: #07307d; font-weight: 500;">almalinux</code>
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" | 20.03.2026
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" | 10
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" | 256
|-
| style="padding: 10px; border: 1px solid #ddd; font-weight: 500;" | CentOS Stream 10
| style="padding: 10px; border: 1px solid #ddd;" | <code style="background-color: #e8f1fa; padding: 2px 6px; border-radius: 3px; color: #07307d; font-weight: 500;">cloud-user</code>
| style="padding: 10px; border: 1px solid #ddd;" | 20.03.2026
| style="padding: 10px; border: 1px solid #ddd; text-align: center;" | 10
| style="padding: 10px; border: 1px solid #ddd; text-align: center;" | 256
|-
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" | Debian 13
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" | <code style="background-color: #e8f1fa; padding: 2px 6px; border-radius: 3px; color: #07307d; font-weight: 500;">debian</code>
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" | 19.03.2026
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" | 3
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" | 256
|-
| style="padding: 10px; border: 1px solid #ddd; font-weight: 500;" | Fedora 43
| style="padding: 10px; border: 1px solid #ddd;" | <code style="background-color: #e8f1fa; padding: 2px 6px; border-radius: 3px; color: #07307d; font-weight: 500;">fedora</code>
| style="padding: 10px; border: 1px solid #ddd;" | 20.03.2026
| style="padding: 10px; border: 1px solid #ddd; text-align: center;" | 5
| style="padding: 10px; border: 1px solid #ddd; text-align: center;" | 256
|-
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" | openSUSE Leap 16.0
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" | <code style="background-color: #e8f1fa; padding: 2px 6px; border-radius: 3px; color: #07307d; font-weight: 500;">opensuse</code>
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" | 20.03.2026
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" | 3
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" | 256
|-
| style="padding: 10px; border: 1px solid #ddd; font-weight: 500;" | Rocky 10
| style="padding: 10px; border: 1px solid #ddd;" | <code style="background-color: #e8f1fa; padding: 2px 6px; border-radius: 3px; color: #07307d; font-weight: 500;">rocky</code>
| style="padding: 10px; border: 1px solid #ddd;" | 20.03.2026
| style="padding: 10px; border: 1px solid #ddd; text-align: center;" | 10
| style="padding: 10px; border: 1px solid #ddd; text-align: center;" | 256
|-
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; font-weight: 500;" | Ubuntu 24.04
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" | <code style="background-color: #e8f1fa; padding: 2px 6px; border-radius: 3px; color: #07307d; font-weight: 500;">ubuntu</code>
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd;" | 20.03.2026
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" | 5
| style="background-color: #f8f9fa; padding: 10px; border: 1px solid #ddd; text-align: center;" | 256
|}

Networks Gen3

Admin — Thu, 19 Mar 2026 15:24:48 GMT

← Older revision		Revision as of 15:24, 19 March 2026
Line 67:		Line 67:
	* The '''instance name'''		* The '''instance name'''
	* The '''project name'''		* The '''project name'''
			* The '''zone prefix''' (<code>vm</code> for instances)
	* The '''region abbreviation''' (e.g., <code>ma</code> for Mannheim)		* The '''region abbreviation''' (e.g., <code>ma</code> for Mannheim)
	* The '''domain suffix''': <code>.bwcloud-os-instance.de.</code>		* The '''domain suffix''': <code>.bwcloud-os-instance.de.</code>
Line 72:		Line 73:
	'''Example:'''		'''Example:'''

	If your instance name is <code>instance-name</code> the project is called <code>project-name</code> and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>instance-name.project-name.ma.bwcloud-os-instance.de</pre>The FQDN can also be found in the '''[https://portal.ul.bwcos.de/ Dashboard]''', under '''Instances''' -> '''Instance Name''' -> '''Interfaces''' -> '''Name'''.		If your instance name is <code>instance-name</code> the project is called <code>project-name</code> and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>instance-name.project-name.vm.ma.bwcloud-os-instance.de</pre>The FQDN can also be found in the '''[https://portal.ul.bwcos.de/ Dashboard]''', under '''Instances''' -> '''Instance Name''' -> '''Interfaces''' -> '''Name'''.

	== Can I get a request more DNS records in bwCloud-OS? ==		== Can I get a request more DNS records in bwCloud-OS? ==

Key User: Migration Guide

Admin — Thu, 19 Mar 2026 14:37:34 GMT

Networks

← Older revision		Revision as of 14:37, 19 March 2026
(5 intermediate revisions by the same user not shown)
Line 18:		Line 18:
	This guide explains how to migrate your resources from the old bwCloud-OS Gen2 environment to bwCloud-OS Gen3. Because the two environments are completely separated, there is no automatic migration path. You will need to manually export your resources from the old cloud, download them locally, and upload them to the new cloud. Please note that network settings and Security Groups cannot be copied and must be reconfigured manually in the new environment.		This guide explains how to migrate your resources from the old bwCloud-OS Gen2 environment to bwCloud-OS Gen3. Because the two environments are completely separated, there is no automatic migration path. You will need to manually export your resources from the old cloud, download them locally, and upload them to the new cloud. Please note that network settings and Security Groups cannot be copied and must be reconfigured manually in the new environment.

	~~'''~~Login~~:'''~~		=== Dashboard Login ===
	* ~~Old bwCloud-OS Gen2:~~ https://portal.bw-cloud.org/
	* New bwCloud-OS ~~Gen3:~~ [https://portal.ul.bwcos.de/auth/login/?next=/ ~~https~~://portal.ul.bwcos.de/]		* [https://portal.bw-cloud.org/ Old bwCloud-OS Gen2]
			* [https://portal.ul.bwcos.de/auth/login/?next=/%20https://portal.ul.bwcos.de/ New bwCloud-OS Gen3]


			=== Networks ===

			The new bwCloud-OS Gen3 environment includes significant changes to the network architecture. These region-specific changes are described in the following Guide.

			➡️ [[Guide:_Network_Configuration_by_Region\|Guide: Network Configuration by Region]]

	= Transferring =		= Transferring =

Key User: Migration Guide

Sia — Tue, 17 Mar 2026 20:30:07 GMT

← Older revision		Revision as of 20:30, 17 March 2026
Line 20:		Line 20:
	'''Login:'''		'''Login:'''
	* Old bwCloud-OS Gen2: https://portal.bw-cloud.org/		* Old bwCloud-OS Gen2: https://portal.bw-cloud.org/
	* New bwCloud-OS Gen3: ....		* New bwCloud-OS Gen3: [https://portal.ul.bwcos.de/auth/login/?next=/ https://portal.ul.bwcos.de/]

	= Transferring =		= Transferring =

Guide: Network Configuration by Region

Qw7402 — Tue, 17 Mar 2026 19:04:45 GMT

← Older revision		Revision as of 19:04, 17 March 2026
Line 41:		Line 41:
	* receive a separate public IPv6 Subnet		* receive a separate public IPv6 Subnet
	* have a separated Broadcast Domain only accessible by authorized projects		* have a separated Broadcast Domain only accessible by authorized projects
	* always use up at least one IPv4 used for the virtual Router		* always use up at least one public IPv4 used for the virtual Router

	=== Migration from Gen2 to Gen3 ===		=== Migration from Gen2 to Gen3 ===

Guide: Network Configuration by Region

Sia — Tue, 17 Mar 2026 18:20:29 GMT

← Older revision		Revision as of 18:20, 17 March 2026
(2 intermediate revisions by the same user not shown)
Line 63:		Line 63:
	== Mannheim ==		== Mannheim ==

	The Mannheim region provides a '''default routed network''', as well as additional networks that can be assigned to projects upon request. Both IPv6 and IPv4 connectivity options are available, depending on the selected network.		The Mannheim region provides a '''default routed network''', as well as '''additional networks''' that can be assigned to projects '''upon request'''. Both IPv6 and IPv4 connectivity options are available, depending on the selected network.

	=== Default Network ===		=== Default Network ===
Line 72:		Line 72:
	** A '''private IPv4 address'''		** A '''private IPv4 address'''

	This is a '''routed network''' using an OpenStack router connected to an external provider network.		This is a '''routed network''' using an OpenStack router connected to an external provider network:

	* IPv6: Direct public connectivity		* '''IPv6''': Direct public connectivity
	* IPv4 (egress): Provided via '''SNAT''' through the router		* '''IPv4 (egress)''': Provided via '''SNAT''' through the router
	* IPv4 (ingress): Not available by default (see [[Guide: Network Configuration by Region#IPv4 Ingress via Floating IPs\|'''IPv4 Ingress via Floating IPs''']])		* IPv4 (ingress): Not available by default (see [[Guide: Network Configuration by Region#IPv4 Ingress via Floating IPs\|'''IPv4 Ingress via Floating IPs''']])
	📌 '''Note:''' This network extends the legacy IPv6-only network in the Mannheim region, which did not provide IPv4 connectivity. ''Before requesting an IPv4 address via a support ticket, please ensure that the combined connectivity is not already sufficient for your use case.''		📌 '''Note:''' This network extends the legacy IPv6-only network in the Mannheim region, which did not provide IPv4 connectivity. ''Before requesting an IPv4 address via a support ticket, please ensure that the combined connectivity is not already sufficient for your use case.''
Line 84:		Line 84:
	* They can be assigned to projects upon request via a '''[https://bw-support.scc.kit.edu/ support ticket]'''.		* They can be assigned to projects upon request via a '''[https://bw-support.scc.kit.edu/ support ticket]'''.

	Once assigned, a Floating IP can be associated with an instance to provide IPv4 ingress connectivity.		Once assigned, a Floating IP can be associated with an instance to provide '''IPv4 ingress connectivity'''.

	=== Flat External Networks ===		=== Flat External Networks ===
Line 93:		Line 93:
	Instances connected directly to this type of network receive:		Instances connected directly to this type of network receive:

	* A public IPv4 address		* A '''public IPv4 address'''
	* A public IPv6 address		* A '''public IPv6 address'''

	This enables dual-stack public connectivity (IPv4 and IPv6) without the need for Floating IPs.		This enables dual-stack public connectivity (IPv4 and IPv6) without the need for Floating IPs.
Line 112:		Line 112:
	After the transition period:		After the transition period:

	* All IP addresses from <code>provider_interim_net</code> will be migrated to <code>provider_default_net</code>. This migration will be performed by administrators; no user action is required.		* All dual-stack IP addresses from <code>provider_interim_net</code> will be migrated to <code>provider_default_net</code>. This migration will be performed by administrators; no user action is required.
	* Projects requiring a flat external network will be assigned <code>provider_default_net</code>.		* Projects requiring a flat external network will be assigned <code>provider_default_net</code>.

			📌 '''Note:''' We do not recommend allocating Floating IPs from the <code>provider_interim_net</code>, because they will be lost after the transition period. Instead, request and associate them from <code>provider_default_net</code>.


	== Ulm ==		== Ulm ==

	Information for this region will be provided soon.		Information for this region will be provided soon.

Guide: Network Configuration by Region

Qw7402 — Tue, 17 Mar 2026 17:51:26 GMT

@@ Line 11: / Line 11: @@
 == Karlsruhe ==
-*Information for this region will be provided soon.*
+The Karlsruhe region provides a '''default routed network''', as well as additional networks that can be assigned to projects upon request.
 == Mannheim ==

Guide: Network Configuration by Region

Sia — Tue, 17 Mar 2026 16:03:25 GMT

← Older revision		Revision as of 16:03, 17 March 2026
Line 1:		Line 1:

	This guide provides details of the ~~networking setup~~ in each '''[[Registration#Regions\|bwCloud-OS region]]'''. It describes which networks are available by default, which can be requested, and how IPv4 and IPv6 connectivity is provided.		This guide provides details of the VM networks in each '''[[Registration#Regions\|bwCloud-OS region]]'''. It describes which networks are available by default, which can be requested, and how IPv4 and IPv6 connectivity is provided.

	While core networking concepts are consistent across regions, available networks, IP address ranges, and access methods may differ. Please refer to the section for your specific region.		While core networking concepts are consistent across regions, available networks, IP address ranges, and access methods may differ. Please refer to the section for your specific region.

Networks Gen3

Sia — Tue, 17 Mar 2026 15:52:52 GMT

← Older revision		Revision as of 15:52, 17 March 2026
(3 intermediate revisions by the same user not shown)
Line 4:		Line 4:
	<li> <strong>Floating IPs</strong>, which persist independent of instances, are also available.		<li> <strong>Floating IPs</strong>, which persist independent of instances, are also available.
	</li>		</li>
	<li>Instances are ~~also~~ assigned a <strong>persistent FQDN</strong> based on their name, project and region.</li>		<li> <strong>Load Balancers</strong> are available and allow traffic to be distributed across multiple backend instances via a single public address.
			</li>
			<li>Instances are assigned a <strong>persistent FQDN</strong> based on their name, project and region.</li>
	<li>Domain hosting is not provided, but you can point your own <strong>domain</strong> to the FQDN of the instance using a CNAME record.</li>		<li>Domain hosting is not provided, but you can point your own <strong>domain</strong> to the FQDN of the instance using a CNAME record.</li>
	}}		}}
Line 37:		Line 39:

	Yes.		Yes.

	'''Floating IPs''' provide a mechanism to perform 1:1 NAT between a public IPv4 address and a private IPv4 address of an instance enabling ingress IPv4 connectivity.		'''Floating IPs''' provide a mechanism to perform 1:1 NAT between a public IPv4 address and a private IPv4 address of an instance enabling ingress IPv4 connectivity.

Line 43:		Line 44:

	➡️ [[Guide: Routers and Floating IPs\|Routers and Floating IPs Guide]]		➡️ [[Guide: Routers and Floating IPs\|Routers and Floating IPs Guide]]
			== Are Load Balancers available in bwCloud-OS? ==
			<span id="Load-Balancers"></span>

			Yes.
			bwCloud-OS provides '''Load Balancers''' based on '''OpenStack Octavia'''. They allow you to distribute traffic across multiple backend instances and expose services via a single public endpoint.

			A typical setup involves creating a private network, deploying backend VMs, and configuring a load balancer with a listener, pool, and members. A [[Networks Gen3#Floating-IPs\|Floating IP]] can then be assigned to make the service publicly accessible.

			For more information and detailed setup instructions, see the guide below.

			➡️ [[Guide: Load Balancers]]

	= Domains and FQDNs =		= Domains and FQDNs =

Guide: Network Configuration by Region

Sia — Tue, 17 Mar 2026 15:13:08 GMT

@@ Line 1: / Line 1: @@
-This guide provides an overview of the networking setup in each bwCloud-OS region. It describes which networks are available by default, which can be requested, and how IPv4 and IPv6 connectivity is provided.
+This guide provides details of the networking setup in each '''[[Registration#Regions|bwCloud-OS region]]'''. It describes which networks are available by default, which can be requested, and how IPv4 and IPv6 connectivity is provided.
 While core networking concepts are consistent across regions, available networks, IP address ranges, and access methods may differ. Please refer to the section for your specific region.
@@ Line 11: / Line 11: @@
 == Karlsruhe ==
+*Information for this region will be provided soon.*
 == Mannheim ==
@@ Line 83: / Line 29: @@
 * IPv4 (egress): Provided via '''SNAT''' through the router
 * IPv4 (ingress): Not available by default (see [[Guide: Network Configuration by Region#IPv4 Ingress via Floating IPs|'''IPv4 Ingress via Floating IPs''']])
 === IPv4 Ingress via Floating IPs ===
@@ Line 91: / Line 38: @@
 Once assigned, a Floating IP can be associated with an instance to provide IPv4 ingress connectivity.
-=== Flat External Network ===
+=== Flat External Networks ===
 * There are also flat external networks available, such as <code>provider_interim_net</code> .
@@ Line 117: / Line 64: @@
 After the transition period:
-* All IP addresses from <code>provider_interim_net</code> will be migrated to <code>provider_default_net</code>.
+* All IP addresses from <code>provider_interim_net</code> will be migrated to <code>provider_default_net</code>. This migration will be performed by administrators; no user action is required.
 * Projects requiring a flat external network will be assigned <code>provider_default_net</code>.