Guide: Network Configuration by Region - Revision history

Sia at 09:48, 28 May 2026

2026-05-28T09:48:56Z

← Older revision		Revision as of 09:48, 28 May 2026
Line 52:		Line 52:
	This setup allows users to migrate their instances and data from Gen2 to Gen3.		This setup allows users to migrate their instances and data from Gen2 to Gen3.

	* The coexistence period will last until ~~15.~~ September 2026.		* The coexistence period will last until September 2026. Refer to the [https://bwcloud-os.de/ bwCloud-OS website] for the exact date.

	After the transition period:		After the transition period:
Line 107:		Line 107:
	This setup allows users to migrate their instances and data from Gen2 to Gen3.		This setup allows users to migrate their instances and data from Gen2 to Gen3.

	* The coexistence period will last until 31. ~~August 2026~~.		* The coexistence period will last until September 2026. Refer to the [https://bwcloud-os.de/ bwCloud-OS website] for the exact date.
	* During this period, <code>provider_interim_net</code> is used as the flat external network.		* During this period, <code>provider_interim_net</code> is used as the flat external network.

Sia at 09:43, 28 May 2026

2026-05-28T09:43:31Z

← Older revision		Revision as of 09:43, 28 May 2026
Line 52:		Line 52:
	This setup allows users to migrate their instances and data from Gen2 to Gen3.		This setup allows users to migrate their instances and data from Gen2 to Gen3.

	* The coexistence period will last until 31. ~~August~~ 2026.		* The coexistence period will last until 15. September 2026.

	After the transition period:		After the transition period:

Sia: /* Separated Networks */

2026-04-25T15:04:19Z

Separated Networks

← Older revision		Revision as of 15:04, 25 April 2026
Line 34:		Line 34:

	=== Separated Networks ===		=== Separated Networks ===
	If you require a ~~seperated~~ Broadcast Domain you can request one via a '''[https://bw-support.scc.kit.edu/ support ticket]'''.		If you require a separated Broadcast Domain you can request one via a '''[https://bw-support.scc.kit.edu/ support ticket]'''.

	The network will:		The network will:

Sia: /* Seperated Networks */

2026-04-25T15:04:06Z

Seperated Networks

← Older revision		Revision as of 15:04, 25 April 2026
Line 33:		Line 33:
	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.

	=== ~~Seperated~~ Networks ===		=== Separated Networks ===
	If you require a seperated Broadcast Domain you can request one via a '''[https://bw-support.scc.kit.edu/ support ticket]'''.		If you require a seperated Broadcast Domain you can request one via a '''[https://bw-support.scc.kit.edu/ support ticket]'''.

Admin-ulm-1: /* Per Project Networks */

2026-04-20T08:55:01Z

Per Project Networks

← Older revision		Revision as of 08:55, 20 April 2026
Line 148:		Line 148:
	* If a project with multiple VMs wishes to use a separate network instead of relying on the <code>virt-shared</code> network, it is possible to allocate a private network.		* If a project with multiple VMs wishes to use a separate network instead of relying on the <code>virt-shared</code> network, it is possible to allocate a private network.
	* Private networks have the same properties and limitations as the shared <code>virt-shared</code> network, but receive a smaller private IPv4 range and are not shared with other projects.		* Private networks have the same properties and limitations as the shared <code>virt-shared</code> network, but receive a smaller private IPv4 range and are not shared with other projects.
			* Private networks need to be connected the the internal side of a private router with the external side connected to <code>public-link</code>.
	* A VM in a dual-stacked private network will receive a private, NAT-ed IPv4 and a public, global IPv6 address.		* A VM in a dual-stacked private network will receive a private, NAT-ed IPv4 and a public, global IPv6 address.
	** A unique, private IPv4 /26 range can be allocated from the subnet pool <code>tenant-v4-16-26</code>.		** A unique, private IPv4 /26 range can be allocated from the subnet pool <code>tenant-v4-16-26</code>.

Admin-ulm-1: /* Network Renumbering */

2026-04-20T08:50:20Z

Network Renumbering

← Older revision		Revision as of 08:50, 20 April 2026
Line 161:		Line 161:
	** This affects <code>virt-shared</code> and all per project networks.		** This affects <code>virt-shared</code> and all per project networks.
	** IPv6 ranges and addresses will remain unchanged.		** IPv6 ranges and addresses will remain unchanged.
			** private IPv4 ranges and addresses will remain unchanged.

Admin-ulm-1: /* Network Renumbering */

2026-04-20T08:49:52Z

Network Renumbering

← Older revision		Revision as of 08:49, 20 April 2026
Line 160:		Line 160:
	** Afterwards new IPv4 '''Floating IPs''' can be allocated from <code>public-link</code>.		** Afterwards new IPv4 '''Floating IPs''' can be allocated from <code>public-link</code>.
	** This affects <code>virt-shared</code> and all per project networks.		** This affects <code>virt-shared</code> and all per project networks.
	** IPv6 will remain unchanged.		** IPv6 ranges and addresses will remain unchanged.

Admin-ulm-1: /* Network Renumbering */

2026-04-20T08:42:42Z

Network Renumbering

← Older revision		Revision as of 08:42, 20 April 2026
Line 156:		Line 156:
	=== Network Renumbering ===		=== Network Renumbering ===

	* The IPv4 range that Gen3 region Ulm starts with initially is only temporary and will be replaced with an IPv4 range that is currently still in-use in Gen2 region Ulm once Gen2 shuts down.		* The IPv4 range that Gen3 region Ulm starts with initially is only temporary and will be replaced with an IPv4 range that is currently still in-use in Gen2 region Ulm, once Gen2 shuts down.
	** During that IPv4 renumbering all IPv4 '''Floating IPs''' will be removed.		** During that IPv4 renumbering all IPv4 '''Floating IPs''' will be removed.
	** Afterwards new IPv4 '''Floating IPs''' can be allocated from <code>public-link</code>.		** Afterwards new IPv4 '''Floating IPs''' can be allocated from <code>public-link</code>.
	** This affects <code>virt-shared</code> and all per project networks.		** This affects <code>virt-shared</code> and all per project networks.
	** IPv6 will remain unchanged.		** IPv6 will remain unchanged.

Admin-ulm-1: /* Network Renumbering */

2026-04-20T08:42:20Z

Network Renumbering

← Older revision		Revision as of 08:42, 20 April 2026
Line 156:		Line 156:
	=== Network Renumbering ===		=== Network Renumbering ===

	* The IPv4 range that Gen3 region Ulm starts with initially is only temporary and will be replaced with an IPv4 range that is currently still in-use in Gen2 region Ulm.		* The IPv4 range that Gen3 region Ulm starts with initially is only temporary and will be replaced with an IPv4 range that is currently still in-use in Gen2 region Ulm once Gen2 shuts down.
	** During that IPv4 renumbering all IPv4 '''Floating IPs''' will be removed.		** During that IPv4 renumbering all IPv4 '''Floating IPs''' will be removed.
	** Afterwards new IPv4 '''Floating IPs''' can be allocated from <code>public-link</code>.		** Afterwards new IPv4 '''Floating IPs''' can be allocated from <code>public-link</code>.
	** This affects <code>virt-shared</code> and all per project networks.		** This affects <code>virt-shared</code> and all per project networks.
	** IPv6 will remain unchanged.		** IPv6 will remain unchanged.

Admin-ulm-1: /* Ulm */

2026-04-20T08:41:52Z

Ulm

← Older revision		Revision as of 08:41, 20 April 2026
Line 153:		Line 153:
	* Optional '''Floating IPs''' from <code>public-link</code> can be used for IPv4 ingress, just like with the default <code>virt-shared</code> network.		* Optional '''Floating IPs''' from <code>public-link</code> can be used for IPv4 ingress, just like with the default <code>virt-shared</code> network.
	* The only meaningful advantage of a per project network is that is not shared with VMs from other projects.		* The only meaningful advantage of a per project network is that is not shared with VMs from other projects.

			=== Network Renumbering ===

			* The IPv4 range that Gen3 region Ulm starts with initially is only temporary and will be replaced with an IPv4 range that is currently still in-use in Gen2 region Ulm.
			** During that IPv4 renumbering all IPv4 '''Floating IPs''' will be removed.
			** Afterwards new IPv4 '''Floating IPs''' can be allocated from <code>public-link</code>.
			** This affects <code>virt-shared</code> and all per project networks.
			** IPv6 will remain unchanged.