Networks Gen3: Difference between revisions
No edit summary |
No edit summary |
||
| (13 intermediate revisions by 2 users 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 | <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 11: | Line 13: | ||
__TOC__ | __TOC__ | ||
= Networks & IP | = Networks & IP addresses = | ||
== Will my instance receive a public IP? == | == Will my instance receive a public IP? == | ||
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, egress | 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:''' 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'''.''' | ||
[[Guide: Network Configuration by Region|➡️ Guide: Network Configuration by Region]] | |||
[[Guide: | |||
== How long does an IP remain assigned to my instance? == | == How long does an IP remain assigned to my instance? == | ||
| Line 36: | 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. | ||
| Line 43: | Line 45: | ||
➡️ [[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 = | ||
| Line 55: | Line 68: | ||
* 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 60: | Line 74: | ||
'''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? == | ||
Latest revision as of 08:55, 27 March 2026
| In a Nutshell |
|
Networks & IP addresses
Will my instance receive a public IP?
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: If not available by default, IPv4 ingress connectivity can also be provided via a support ticket.
Note: Each region in bwCloud-OS has its own set of networks and IP address ranges.
➡️ Guide: Network Configuration by Region
How long does an IP remain assigned to my instance?
The IP address(es) assigned to your instance remains associated with it for the entire lifetime of the instance — even if you stop (shut down) the instance.
The IP is only released when the instance is deleted (terminated). After termination, the IP is returned to the regional pool and may be reassigned to another instance in the region.
Note: Floating IPs will persist even after an Instance deletion. They can be released manually.
Are Floating IPs also available for instances?
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.
For more information and detailed setup instructions, see the guide below.
➡️ 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.
Domains and FQDNs
Does bwCloud-OS assign FQDNs?
Yes. Every running instance in bwCloud-OS is automatically assigned a fully qualified domain name (FQDN). This allows the instance to be reached via a persistent network identifier. This FQDN is valid for the lifetime of the instance.
Format of an instance FQDN
- The instance name
- The project name
- The zone prefix (
vmfor instances) - The region abbreviation (e.g.,
mafor Mannheim) - The domain suffix:
.bwcloud-os-instance.de.
Example:
If your instance name is instance-name the project is called project-name and it runs in Mannheim (ma), the FQDN will be:
instance-name.project-name.vm.ma.bwcloud-os-instance.de
Can I get a request more DNS records in bwCloud-OS?
Yes.
We manage the top level domain bwcloud-os-instance.de. It is possible to request a DNS record for a floating IP for example.
Can I obtain a custom domain through bwCloud-OS?
No, bwCloud-OS does not provide custom domain registration. However, you can use your own domain — either through your home institution or an external domain provider — to point to your instance.
Some options o achieve this are described below.
How can I point a domain to an instance?
You can point a domain to your instance in two main ways:
🔹 CNAME to the instance FQDN
Since the FQDN is persistent for the lifetime of the instance (even if the instance is stopped and started again), you can safely set a CNAME record like:
myvm.example.org → instance-name.project-name.vm.region.bwcloud-os-instance.de
🔹 Dynamic DNS
Alternatively, you can configure a Dynamic DNS setup where your VM updates its IP in a third party DNS service — especially if you don’t have your own domain, or your use case involves frequently changing IPs or multiple IPs.
Does bwCloud-OS provide TLS/SSL certificates?
No, bwCloud-OS does not provide certificates. However, you can obtain certificates directly from public providers like Let’s Encrypt using tools such as Certbot that you install and run on your instance.