Networks: Difference between revisions

From bwCloud-OS
Jump to navigation Jump to search
← Older edit
VisualWikitext
Admin (talk | contribs)
Bureaucrats, Interface administrators, intern, Suppressors, Administrators, translationadmin, translator
736 edits
 
(41 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{InANutshell| <li>Each bwCloud-OS instance automatically receives a <strong>public IP address</strong>, valid for its entire lifetime (until deletion).</li>
<span id="In-a-Nutshell"></span>
{{InANutshell|  
<li>Each bwCloud-OS instance launched using the standard method is automatically assigned a <strong>public IP address</strong>.</li>
<li>Instances are also assigned a <strong>persistent FQDN</strong> based on their UUID and region.</li>
<li>Instances are also assigned a <strong>persistent FQDN</strong> based on their UUID and region.</li>
<li>Domain hosting is not provided, but you can point your own <strong>domain</strong> to the instance’s  FQDN using a CNAME record.</li>}}
<li>Domain hosting is not provided, but you can point your own <strong>domain</strong> to the instance’s  FQDN using a CNAME record.</li>
}}




Line 8: Line 11:
= Networks & IP-addresses =
= Networks & IP-addresses =


===Will my instance receive a public IP? ===
== Will my instance receive a public IP? ==
<span id="Public-IPs"></span>
Yes. By default, every instance launched using the standard method in bwCloud-OS is automatically assigned a '''publicly accessible IP address'''.


Yes. Every instance that is started in the standard way is dynamically assigned a publicly accessible IP address.
'''Note:''' Each '''region''' in bwCloud-OS has its '''own set of IP address ranges.'''
Each region has (currently) different IP ranges from which public IPs are allocated. The current IP ranges are listed [[Network Overview|here]].


=== How long does an IP remain assigned to my instance? ===
== How long does an IP remain assigned to my instance? ==
<span id="Public-IP-Liftime"></span>


The assigned IP address remains assigned to an instance for its entire lifecycle. This means that the instance can also be stopped without the IP address being reassigned. Only when an instance is deleted ("terminated") is the IP released again after a short period of time and reassigned to another instance in the region.
The public 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.


== Freiburg: Floating IPs ==
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.


For assigning a Floating IP is a configuration as illustrated below (or something similar) required. Here is a summary:
'''📌 Note:''' The rules for assigning public IPs to instances are currently under revision, so persistent public IPs cannot be guaranteed in the future. It is recommended to use [[Networks#FQDN|FQDNs]] instead.


# '''Allocate a Floating IP to the project'''
== Are Floating IPs also available for instances? ==
## ''Network'' -> ''Floating IPs''
<span id="Floating-IPs"></span>
## Allocate IP to Project
### Choose the public network/pool
# '''Virtual network creating'''
## ''Network'' -> ''Networks''
## ''Create Network ''
### add network name
## ''Next'' and the slider ''Subnet'' is presented
### Set ''subnet name''
### set ''Network address'' (e.g. 10.10.1.0/24)
### set ''Gateway IP'' (e.g. 10.10.1.254)
## ''Next'' and the slider ''Subnetz Details'' is presented
### ''DHCP enable'' must be checked
## ''Create''
# '''Virtual router creating'''
## ''Network''-> ''Routers''
## ''create Router''
### set ''Routername''
### set ''Gateway/External Network'' to  ''public''
## Choose ''router'' in the ''view'' -> ''Interfaces'' -> ''Add Interface''
### Set ''Subnet'' to the network from step 2
## ''Submit''
'''Afterward, create a VM as follows:'''
# ''Compute'' -> ''Instances'' -> ''Launch Instance''
## Under Networks choose the virtual netzwork from step 2
## Launch Instance
# In the view of the ''instance'' -> ''Associate Floating IP''
## Set IP Address from step 1
# ''Associate''


= Hostnames and Domains =
Yes, but currently not in all regions.


== Does bwCloud-OS also assign host names? ==
'''📌 Note:''' Floating IPs are planned for all regions after the next major software upgrade in 2026.
Yes, each running instance is assigned a generic hostname (FQDN) so that the VM can be reached via the network using a persistent identifier even if the IP address changes.


This consists of the UUID of an instance, the region in which it is running and the postfix ''.bw-cloud-instance.org''. The generic host name is displayed in the overview of the running instances in the web dashboard. This FQDN is valid for the instance lifetime.
For more information and detailed setup instructions, see the guide below.


Here is an example: Let's say, the UUID of your instance is ''caffee-4242-2323-caffee'' and it is running in the bwCloud-OS region Mannheim. The generic hostname will be:
➡️ [[Guide: Routers and Floating IPs|Routers and Floating IPs Guide]].


<pre>caffee-4242-2323-caffee.ma.bw-cloud-instance.org</pre>
= Domains and FQDNs =


Within an instanc the FQDN can be determined by:
== Does bwCloud-OS also assign FQDNs? ==
<span id="FQDN"></span>


<pre>
Yes. Every running instance in bwCloud-OS is automatically assigned a '''generic hostname (FQDN)'''. This allows the instance to be reached via a '''persistent network identifier''', even if its public IP address changes. This FQDN is valid for the '''lifetime''' of the instance.
<nowiki>#</nowiki> BWC_REGION="ma"


<nowiki>#</nowiki> FQDN="$(cat /var/lib/cloud/data/instance-id).${BWC_REGION}.bw-cloud-instance.org"
==== Format of the instance's FQDN ====
</pre>
 
* The '''UUID''' '''of the instance'''
* The '''region abbreviation''' (e.g., <code>ma</code> for Mannheim)
* The '''domain suffix''': <code>.bw-cloud-instance.org</code>
 
'''Example:'''
 
If your instance UUID is <code>caffee-4242-2323-caffee</code> and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>caffee-4242-2323-caffee.ma.bw-cloud-instance.org</pre>
 
'''Retrieval''': From '''inside the instance,''' the FQDN can be determined by:
 
<pre>REGION="ma"
FQDN="$(cat /var/lib/cloud/data/instance-id).${REGION}.bw-cloud-instance.org"</pre>The FQDN can also be found in the '''[https://portal.bw-cloud.org/ Dashboard]''', on the '''Instances'''  page.


== Can I get a domain via bwCloud-OS? ==
== Can I get a domain via bwCloud-OS? ==
No, we do not offer domain hosting. However, every user is free to enter a CNAME in their home institution or even in any domain that points to the FQDN. Users can also set up DynDNS-like systems outside the cloud, which can be configured to the corresponding IP by their own VMs, similar to the procedure for the home network connection if this is made accessible via a persistent name.
<span id="Domains"></span>
 
No, bwCloud-OS does '''not''' provide custom '''domain hosting'''. However, you can use your '''own domain''' — either through your home institution or an external domain provider — to '''point to your instance'''.  
 
Some options are described below.


== How can I point a domain to an instance? ==
== How can I point a domain to an instance? ==
It should either be done dynamically or via a CNAME record to the FQDN of the VM. The assignment of a UUID to an instance is persistent (permanent), even if the instance is stopped - therefore the CNAME record of a domain can refer to the FQDN.
<span id="Domain-Mapping"></span>
 
You can point a domain to your instance in two main ways:
 
==== 🔹 CNAME to the instance FQDN ====
The instance’s FQDN is based on its UUID and region. Since the UUID is persistent for the instance's lifetime (even if the instance is stopped and started again), you can safely set a CNAME record like:
 
<code>myvm.example.org → uuid.region.bw-cloud-instance.org</code>
 
==== 🔹 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 or multiple IPs.
 
== Can I get a certificate from bwCloud-OS? ==
<span id="Certificates"></span>


== Can I get a certificate via bwCloud-OS? ==
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''', which you install and run on your instance.
No, we do '''not offer certificates'''. However, your instance can obtain certificates from other institutions (e.g.  Let's Encrypt) using the CertBot.

Latest revision as of 18:13, 10 November 2025

In a Nutshell
  • Each bwCloud-OS instance launched using the standard method is automatically assigned a public IP address.
  • Instances are also assigned a persistent FQDN based on their UUID and region.
  • Domain hosting is not provided, but you can point your own domain to the instance’s FQDN using a CNAME record.


Networks & IP-addresses

Will my instance receive a public IP?

Yes. By default, every instance launched using the standard method in bwCloud-OS is automatically assigned a publicly accessible IP address.

Note: Each region in bwCloud-OS has its own set of IP address ranges.

How long does an IP remain assigned to my instance?

The public 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: The rules for assigning public IPs to instances are currently under revision, so persistent public IPs cannot be guaranteed in the future. It is recommended to use FQDNs instead.

Are Floating IPs also available for instances?

Yes, but currently not in all regions.

📌 Note: Floating IPs are planned for all regions after the next major software upgrade in 2026.

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

➡️ Routers and Floating IPs Guide.

Domains and FQDNs

Does bwCloud-OS also assign FQDNs?

Yes. Every running instance in bwCloud-OS is automatically assigned a generic hostname (FQDN). This allows the instance to be reached via a persistent network identifier, even if its public IP address changes. This FQDN is valid for the lifetime of the instance.

Format of the instance's FQDN

  • The UUID of the instance
  • The region abbreviation (e.g., ma for Mannheim)
  • The domain suffix: .bw-cloud-instance.org

Example:

If your instance UUID is caffee-4242-2323-caffee and it runs in Mannheim (ma), the FQDN will be:

caffee-4242-2323-caffee.ma.bw-cloud-instance.org

Retrieval: From inside the instance, the FQDN can be determined by: 

REGION="ma"
FQDN="$(cat /var/lib/cloud/data/instance-id).${REGION}.bw-cloud-instance.org"

The FQDN can also be found in the Dashboard, on the Instances page.

Can I get a domain via bwCloud-OS?

No, bwCloud-OS does not provide custom domain hosting. However, you can use your own domain — either through your home institution or an external domain provider — to point to your instance.

Some options 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

The instance’s FQDN is based on its UUID and region. Since the UUID is persistent for the instance's lifetime (even if the instance is stopped and started again), you can safely set a CNAME record like:

myvm.example.org → uuid.region.bw-cloud-instance.org

🔹 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 or multiple IPs.

Can I get a certificate from bwCloud-OS?

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, which you install and run on your instance.

Retrieved from "https://wiki.bwcloud-os.de/index.php?title=Networks&oldid=1516"