Networks Gen3 - Revision history

Sia at 08:55, 27 March 2026

2026-03-27T08:55:06Z

← Older revision		Revision as of 08:55, 27 March 2026
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.

Sia at 08:54, 27 March 2026

2026-03-27T08:54:25Z

← Older revision		Revision as of 08:54, 27 March 2026
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'''.'''

Sia at 16:53, 24 March 2026

2026-03-24T16:53:12Z

← 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? ==

Admin at 15:24, 19 March 2026

2026-03-19T15:24:48Z

← 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? ==

Sia at 15:52, 17 March 2026

2026-03-17T15:52:52Z

← Older revision		Revision as of 15:52, 17 March 2026
Line 44:		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? ==		== Are Load Balancers available in bwCloud-OS? ==
	<span id="Load-Balancers"></span>		<span id="Load-Balancers"></span>

Sia at 15:51, 17 March 2026

2026-03-17T15:51:34Z

← Older revision		Revision as of 15:51, 17 March 2026
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 46:		Line 47:

	== Are Load Balancers available in bwCloud-OS? ==		== Are Load Balancers available in bwCloud-OS? ==
			<span id="Load-Balancers"></span>

	Yes.		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.		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.

Sia at 15:44, 17 March 2026

2026-03-17T15:44:21Z

← Older revision		Revision as of 15:44, 17 March 2026
Line 50:		Line 50:
	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.		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 Floating IP can then be assigned to make the service publicly accessible.		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.		For more information and detailed setup instructions, see the guide below.

Sia at 15:41, 17 March 2026

2026-03-17T15:41:24Z

← Older revision		Revision as of 15:41, 17 March 2026
Line 43:		Line 43:

	➡️ [[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? ==
			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 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 =

Sia at 08:36, 17 March 2026

2026-03-17T08:36:48Z

← Older revision		Revision as of 08:36, 17 March 2026
Line 22:		Line 22:
	'''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'''.'''

	[[Guide: ~~Networks Regional Details~~\|➡️ Guide: ~~Networks Regional Details~~]]		[[Guide: Network Configuration by Region\|➡️ Guide: Network Configuration by Region]]

	== How long does an IP remain assigned to my instance? ==		== How long does an IP remain assigned to my instance? ==

Sia at 08:12, 17 March 2026

2026-03-17T08:12:41Z

← Older revision		Revision as of 08:12, 17 March 2026
Line 22:		Line 22:
	'''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'''.'''

	[[Guide: Networks Regional Details\|➡️ ~~A detailed guide to public IPv4 allocation in regions~~]]		[[Guide: Networks Regional Details\|➡️ Guide: Networks Regional Details]]

	== How long does an IP remain assigned to my instance? ==		== How long does an IP remain assigned to my instance? ==