Guide: Network Configuration by Region: Difference between revisions
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
__TOC__ | __TOC__ | ||
== Freiburg == | == Freiburg == | ||
*Information for this region will be provided soon.* | *Information for this region will be provided soon.* | ||
== Karlsruhe == | == Karlsruhe == | ||
*Information for this region will be provided soon.* | *Information for this region will be provided soon.* | ||
== Mannheim == | == Mannheim == | ||
| Line 40: | Line 34: | ||
* IPv4 (egress): Provided via SNAT through the router | * IPv4 (egress): Provided via SNAT through the router | ||
* IPv4 (ingress): Not available by default | * IPv4 (ingress): Not available by default | ||
=== IPv4 Ingress via Floating IPs (<code>provider_default</code>) === | === IPv4 Ingress via Floating IPs (<code>provider_default</code>) === | ||
| Line 50: | Line 42: | ||
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 Network: <code>provider_interim</code> === | === Flat External Network: <code>provider_interim</code> === | ||
| Line 64: | Line 54: | ||
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. | ||
=== Migration from Gen2 to Gen3 === | === Migration from Gen2 to Gen3 === | ||
| Line 86: | Line 74: | ||
* This migration will be performed by administrators; no user action is required. | * This migration will be performed by administrators; no user action is required. | ||
* Projects requiring a flat external network will be assigned <code>provider_default</code>. | * Projects requiring a flat external network will be assigned <code>provider_default</code>. | ||
== Ulm == | == Ulm == | ||
*Information for this region will be provided soon.* | *Information for this region will be provided soon.* | ||
Revision as of 08:47, 17 March 2026
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.
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.
Freiburg
- Information for this region will be provided soon.*
Karlsruhe
- Information for this region will be provided soon.*
Mannheim
Overview
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: routed_default
- All projects have access to the default network
routed_default. - Instances connected to this network receive:
** A public IPv6 address ** A private IPv4 address
This is a routed network using an OpenStack router connected to the external provider network provider_default.
- IPv6: Direct public connectivity
- IPv4 (egress): Provided via SNAT through the router
- IPv4 (ingress): Not available by default
IPv4 Ingress via Floating IPs (provider_default)
- Public IPv4 connectivity can be enabled using Floating IPs.
- Floating IPs are allocated from the external network
provider_default. - They can be assigned to projects upon request via a support ticket.
Once assigned, a Floating IP can be associated with an instance to provide IPv4 ingress connectivity.
Flat External Network: provider_interim
- The network
provider_interimis a flat external network. - It can be assigned to projects via RBAC rules.
Instances connected to this network receive:
- A public IPv4 address
- A public IPv6 address
This enables dual-stack public connectivity (IPv4 and IPv6) without the need for Floating IPs.
Migration from Gen2 to Gen3
The Mannheim region is currently operating two environments in parallel:
- Gen2 (legacy cloud)
- Gen3 (current bwCloud-OS environment)
This setup allows users to migrate their instances and data from Gen2 to Gen3.
Transition plan
- The coexistence period will last until September 2026.
- During this period,
provider_interimis used to support migration scenarios.
After the transition:
- All IP addresses from
provider_interimwill be migrated toprovider_default. - This migration will be performed by administrators; no user action is required.
- Projects requiring a flat external network will be assigned
provider_default.
Ulm
- Information for this region will be provided soon.*