bwCloud-OS - Recent changes [en]

Guide: Instance Action Menu

Admin — Fri, 29 May 2026 11:54:45 GMT

💽 Storage Management

← Older revision		Revision as of 11:54, 29 May 2026
(One intermediate revision by the same user not shown)
Line 16:		Line 16:

	== 💽 Storage Management ==		== 💽 Storage Management ==
	* '''Attach / Detach Volume:''' Connects or disconnects persistent block storage (Cinder Volumes) to your instance. Volumes are ideal for storing data that must persist even if the instance is deleted or rebuilt.		* '''Attach / Detach Volume:''' Connects or disconnects persistent block storage (Cinder Volumes) to your instance. Volumes are ideal for storing data that must persist even if the instance is deleted or rebuilt. For more details see [[Guide:_Volumes_and_Images#Create_and_Attach_a_Volume\|here]].

	== ⚙️ Administration & Diagnostics ==		== ⚙️ Administration & Diagnostics ==
Line 37:		Line 37:
	* '''Soft Reboot Instance:''' Sends a graceful shutdown signal to the guest operating system, allowing it to close processes safely before rebooting (similar to typing <code>sudo reboot</code>).		* '''Soft Reboot Instance:''' Sends a graceful shutdown signal to the guest operating system, allowing it to close processes safely before rebooting (similar to typing <code>sudo reboot</code>).
	* '''Hard Reboot Instance:''' Forces an immediate restart at the hypervisor level (similar to pressing the physical reset button on a server). Use this only if the instance is unresponsive.		* '''Hard Reboot Instance:''' Forces an immediate restart at the hypervisor level (similar to pressing the physical reset button on a server). Use this only if the instance is unresponsive.
	* '''Shut Off Instance:''' Forcibly powers down the instance (virtual power plug pull). ''Please note that a stopped instance still incurs costs. To avoid incurring further costs, it must be deleted. (Applies only to Gen3; see [[Booking_Units\|Booking Units]].)''		* '''Shut Off Instance:''' Forcibly powers down the instance (virtual power plug pull). ⚠️''Please note that a stopped instance still incurs costs. To avoid incurring further costs, it must be deleted. (Applies only to Gen3; see [[Booking_Units\|Booking Units]].)''
	* '''Rebuild Instance:''' Re-installs the operating system from a selected image. '''Warning:''' All data on the local ephemeral root disk will be permanently destroyed. The instance retains its IP address and ID.		* '''Rebuild Instance:''' Re-installs the operating system from a selected image. '''Warning:''' All data on the local ephemeral root disk will be permanently destroyed. The instance retains its IP address and ID.
	* '''Delete Instance:''' Permanently destroys the instance and all ephemeral data. Attached volumes and Floating IPs will be detached but not deleted.		* '''Delete Instance:''' Permanently destroys the instance and all ephemeral data. Attached volumes and Floating IPs will be detached but not deleted.

	----		----

Instances (VMs)

Admin — Fri, 29 May 2026 11:53:05 GMT

What actions can I perform on a running instance?

← Older revision		Revision as of 11:53, 29 May 2026
(2 intermediate revisions by the same user not shown)
Line 126:		Line 126:
	#* <code>sudo resize2fs</code> (for ext4)		#* <code>sudo resize2fs</code> (for ext4)
	#* <code>sudo xfs_growfs</code> (for XFS)		#* <code>sudo xfs_growfs</code> (for XFS)


			= Managing Running Instances =

			== What actions can I perform on a running instance? ==

			Once your instance is running, you can manage its lifecycle, network, and storage directly from the dashboard.
			For a complete breakdown of all available options in the instance dropdown menu (like Snapshots, Resizing, or Shelving), please refer to our dedicated guide:


			➡️ [[Guide: Instance Action Menu\|Instance Action Menu Guide]]

Guide: Instance Action Menu

Admin — Fri, 29 May 2026 11:46:45 GMT

🌐 Network Configuration

← Older revision		Revision as of 11:46, 29 May 2026
(3 intermediate revisions by the same user not shown)
Line 10:		Line 10:
	== 🌐 Network Configuration ==		== 🌐 Network Configuration ==
	These options manage how your instance communicates internally and externally.		These options manage how your instance communicates internally and externally.
	* '''Associate / Disassociate Floating IP:''' Assigns a public IP address to your instance, making it accessible from the internet (e.g., for SSH or web servers). Use ''Disassociate'' to remove the public IP and free it up for other resources.		* '''Associate / Disassociate Floating IP:''' Assigns a public IP address to your instance, making it accessible from the internet (e.g., for SSH or web servers). Use ''Disassociate'' to remove the public IP and free it up for other resources. See [[Guide:_Routers_and_Floating_IPs\|here]] for more details.
	* '''Attach / Detach Interface:''' Adds or removes a virtual Network Interface Card (NIC). This is useful if your instance needs to connect to multiple separate private networks simultaneously.		* '''Attach / Detach Interface:''' Adds or removes a virtual Network Interface Card (NIC). This is useful if your instance needs to connect to multiple separate private networks simultaneously.
	* '''Edit Security Groups:''' Allows you to attach or detach Security Groups (virtual firewalls). These groups define which incoming (ingress) and outgoing (egress) traffic is permitted for the instance.		* '''Edit Security Groups:''' Allows you to attach or detach Security Groups (virtual firewalls). These groups define which incoming (ingress) and outgoing (egress) traffic is permitted for the instance.
Line 32:		Line 32:
	* '''Shelve / Unshelve Instance:''' Shuts down the instance and moves it off the compute node into image storage. This completely frees up your allocated CPU and RAM quota. ''Unshelving'' restores the instance to a new compute node.		* '''Shelve / Unshelve Instance:''' Shuts down the instance and moves it off the compute node into image storage. This completely frees up your allocated CPU and RAM quota. ''Unshelving'' restores the instance to a new compute node.

	== ⚠️ ~~Critical~~ System Actions ==		== ⚠️ System Actions ==
	These actions severely impact the instance lifecycle and are often marked in red in the dashboard to prevent accidental clicks.		These actions severely impact the instance lifecycle and are often marked in red in the dashboard to prevent accidental clicks.
	* '''Resize Instance:''' Changes the instance's flavor (e.g., upgrading from ''m1.small'' to ''m1.medium''). This requires the instance to be restarted and the resize action to be explicitly confirmed afterwards.		* '''Resize Instance:''' Changes the instance's flavor (e.g., upgrading from ''m1.small'' to ''m1.medium''). This requires the instance to be restarted and the resize action to be explicitly confirmed afterwards.
	* '''Soft Reboot Instance:''' Sends a graceful shutdown signal to the guest operating system, allowing it to close processes safely before rebooting (similar to typing <code>sudo reboot</code>).		* '''Soft Reboot Instance:''' Sends a graceful shutdown signal to the guest operating system, allowing it to close processes safely before rebooting (similar to typing <code>sudo reboot</code>).
	* '''Hard Reboot Instance:''' Forces an immediate restart at the hypervisor level (similar to pressing the physical reset button on a server). Use this only if the instance is unresponsive.		* '''Hard Reboot Instance:''' Forces an immediate restart at the hypervisor level (similar to pressing the physical reset button on a server). Use this only if the instance is unresponsive.
	* '''Shut Off Instance:''' Forcibly powers down the instance (virtual power plug pull).		* '''Shut Off Instance:''' Forcibly powers down the instance (virtual power plug pull). ''Please note that a stopped instance still incurs costs. To avoid incurring further costs, it must be deleted. (Applies only to Gen3; see [[Booking_Units\|Booking Units]].)''
	* '''Rebuild Instance:''' Re-installs the operating system from a selected image. '''Warning:''' All data on the local ephemeral root disk will be permanently destroyed. The instance retains its IP address and ID.		* '''Rebuild Instance:''' Re-installs the operating system from a selected image. '''Warning:''' All data on the local ephemeral root disk will be permanently destroyed. The instance retains its IP address and ID.
	* '''Delete Instance:''' Permanently destroys the instance and all ephemeral data. Attached volumes and Floating IPs will be detached but not deleted.		* '''Delete Instance:''' Permanently destroys the instance and all ephemeral data. Attached volumes and Floating IPs will be detached but not deleted.

	----		----

	~~=== Step-by-Step Example: Associating a Floating IP ===~~

	~~If you need your instance to be reachable from the outside world (e.g., for an SSH connection), you must assign it a Floating IP.~~

	~~# Navigate to '''Compute → Instances'''.~~
	~~# Locate your running instance in the list.~~
	~~# Open the dropdown menu on the right side and select '''Associate Floating IP'''.~~
	~~# A new window will appear:~~
	~~#* '''IP Address:''' Select an available IP from the list. If the list is empty, click the '''+ (Plus)''' button to allocate a new IP from the public pool.~~
	~~#* '''Port to be associated:''' Select the network interface of your instance that should receive the IP (usually, there is only one).~~
	~~# Click '''Associate'''. The Floating IP will now be displayed next to your internal IP in the instance list.~~

Guide: Instance Action Menu

Admin — Fri, 29 May 2026 11:40:09 GMT

Created page with "= Instance Action Menu (Dashboard Guide) = Once an instance is running, you can manage it using the dropdown menu located on the far right of the instance list ('''Compute → Instances'''). This menu provides various options for network, storage, power state, and instance lifecycle management. Below is an explanation of all available actions, grouped by their function. == 💾 Core Action: Snapshots == * '''Create Snapshot:''' This is typically the default button nex..."

New page

= Instance Action Menu (Dashboard Guide) =

Once an instance is running, you can manage it using the dropdown menu located on the far right of the instance list ('''Compute → Instances'''). This menu provides various options for network, storage, power state, and instance lifecycle management.

Below is an explanation of all available actions, grouped by their function.

== 💾 Core Action: Snapshots ==
* '''Create Snapshot:''' This is typically the default button next to the dropdown menu. It creates a complete, point-in-time image of the instance's current disk state. This snapshot can be used as a backup or as a template to launch new instances with the exact same configuration.

== 🌐 Network Configuration ==
These options manage how your instance communicates internally and externally.
* '''Associate / Disassociate Floating IP:''' Assigns a public IP address to your instance, making it accessible from the internet (e.g., for SSH or web servers). Use ''Disassociate'' to remove the public IP and free it up for other resources.
* '''Attach / Detach Interface:''' Adds or removes a virtual Network Interface Card (NIC). This is useful if your instance needs to connect to multiple separate private networks simultaneously.
* '''Edit Security Groups:''' Allows you to attach or detach Security Groups (virtual firewalls). These groups define which incoming (ingress) and outgoing (egress) traffic is permitted for the instance.
* '''Edit Port Security Groups:''' Manages security rules directly on the network port level, offering more granular control than instance-level security groups.

== 💽 Storage Management ==
* '''Attach / Detach Volume:''' Connects or disconnects persistent block storage (Cinder Volumes) to your instance. Volumes are ideal for storing data that must persist even if the instance is deleted or rebuilt.

== ⚙️ Administration & Diagnostics ==
* '''Edit Instance:''' Allows you to change basic metadata, such as the instance's display name.
* '''Update Meta''' Add or edit key-value tags associated with the instance. This can be used for organizational purposes or to trigger specific cloud-init scripts during boot.
* '''Console:''' Opens an interactive, web-based terminal directly in your browser (VNC/SPICE). This is crucial for troubleshooting if you lose SSH access due to network misconfiguration or firewall issues.
* '''View Log:''' Displays the console output and boot logs of the instance. This is the first place to look if an instance fails to boot properly.
* '''Rescue Instance:''' Reboots the instance using a temporary, minimal rescue operating system. Your original root disk is attached as a secondary drive, allowing you to fix broken file systems or recover a lost password.
* '''Lock / Unlock Instance:''' Prevents accidental changes, state modifications, or deletion of the instance by other users within the same project.

== ⏸️ Power States & Resource Management ==
These options allow you to temporarily halt an instance.
* '''Pause / Unpause Instance:''' Freezes the instance. The state is kept in RAM, allowing for an immediate resume. However, it still consumes compute resources on the host.
* '''Suspend / Resume Instance:''' Saves the current RAM state to disk and halts the instance. This frees up hypervisor resources, but resuming takes slightly longer than unpausing.
* '''Shelve / Unshelve Instance:''' Shuts down the instance and moves it off the compute node into image storage. This completely frees up your allocated CPU and RAM quota. ''Unshelving'' restores the instance to a new compute node.

== ⚠️ Critical System Actions ==
These actions severely impact the instance lifecycle and are often marked in red in the dashboard to prevent accidental clicks.
* '''Resize Instance:''' Changes the instance's flavor (e.g., upgrading from ''m1.small'' to ''m1.medium''). This requires the instance to be restarted and the resize action to be explicitly confirmed afterwards.
* '''Soft Reboot Instance:''' Sends a graceful shutdown signal to the guest operating system, allowing it to close processes safely before rebooting (similar to typing <code>sudo reboot</code>).
* '''Hard Reboot Instance:''' Forces an immediate restart at the hypervisor level (similar to pressing the physical reset button on a server). Use this only if the instance is unresponsive.
* '''Shut Off Instance:''' Forcibly powers down the instance (virtual power plug pull).
* '''Rebuild Instance:''' Re-installs the operating system from a selected image. '''Warning:''' All data on the local ephemeral root disk will be permanently destroyed. The instance retains its IP address and ID.
* '''Delete Instance:''' Permanently destroys the instance and all ephemeral data. Attached volumes and Floating IPs will be detached but not deleted.

----

=== Step-by-Step Example: Associating a Floating IP ===

If you need your instance to be reachable from the outside world (e.g., for an SSH connection), you must assign it a Floating IP.

# Navigate to '''Compute → Instances'''.
# Locate your running instance in the list.
# Open the dropdown menu on the right side and select '''Associate Floating IP'''.
# A new window will appear:
#* '''IP Address:''' Select an available IP from the list. If the list is empty, click the '''+ (Plus)''' button to allocate a new IP from the public pool.
#* '''Port to be associated:''' Select the network interface of your instance that should receive the IP (usually, there is only one).
# Click '''Associate'''. The Floating IP will now be displayed next to your internal IP in the instance list.

Guide: Project and Quota

Admin — Fri, 29 May 2026 08:18:17 GMT

List of quota flavors

← Older revision		Revision as of 08:18, 29 May 2026
(5 intermediate revisions by the same user not shown)
Line 47:		Line 47:
	!'''ram_gb'''		!'''ram_gb'''
	!'''volumes'''		!'''volumes'''
			! style="border-right: 3px solid #a2a9b1;" \| BEH/day
	!'''volumes_gb'''		!'''volumes_gb'''
	!'''backups'''		!'''backups'''
Line 62:		Line 63:
	\|0		\|0
	\|0		\|0
			\| style="border-right: 3px solid #a2a9b1;" \|
	\|0		\|0
	\|0		\|0
Line 77:		Line 79:
	\|1		\|1
	\|10		\|10
			\| style="border-right: 3px solid #a2a9b1;" \| 4
	\|100		\|100
	\|30		\|30
Line 92:		Line 95:
	\|2		\|2
	\|10		\|10
			\| style="border-right: 3px solid #a2a9b1;" \| 7
	\|100		\|100
	\|30		\|30
Line 107:		Line 111:
	\|4		\|4
	\|20		\|20
			\| style="border-right: 3px solid #a2a9b1;" \| 14
	\|200		\|200
	\|60		\|60
Line 122:		Line 127:
	\|8		\|8
	\|20		\|20
			\| style="border-right: 3px solid #a2a9b1;" \| 26
	\|200		\|200
	\|60		\|60
Line 137:		Line 143:
	\|16		\|16
	\|40		\|40
			\| style="border-right: 3px solid #a2a9b1;" \| 52
	\|400		\|400
	\|120		\|120
Line 152:		Line 159:
	\|32		\|32
	\|40		\|40
			\| style="border-right: 3px solid #a2a9b1;" \| 100
	\|400		\|400
	\|120		\|120
Line 167:		Line 175:
	\|*		\|*
	\|*		\|*
			\| style="border-right: 3px solid #a2a9b1;" \|
	\|*		\|*
	\|*		\|*
Line 176:		Line 185:
	\|*		\|*
	\|*		\|*
			\|}


			Below is the basic translation for calculating Booking Units (BEH). For full details and the complete calculation basis, please refer to the [https://wiki.bwcloud-os.de/index.php/Booking_Units Booking Units page].

			{\| class="wikitable"
			\|+
			! Resource
			! BEH/Day
			\|-
			\| 1 vCPU
			\| 1
			\|-
			\| 1 GB RAM
			\| 2
			\|-
			\| 10 GB Disk
			\| 1
	\|}		\|}

Cloud Migration Guide

Sia — Thu, 28 May 2026 09:52:34 GMT

← Older revision		Revision as of 09:52, 28 May 2026
(One intermediate revision by the same user not shown)
Line 5:		Line 5:
	{\| class="mw-message-box mw-message-box-warning"		{\| class="mw-message-box mw-message-box-warning"
	\| style="vertical-align:middle;" \| '''⚠️ IMPORTANT SHUTDOWN NOTICE:'''		\| style="vertical-align:middle;" \| '''⚠️ IMPORTANT SHUTDOWN NOTICE:'''
	The Gen2 infrastructure will be permanently shut down on '''September ~~15,~~ 2026'''. All projects and data that have not been migrated by this date will be irrevocably deleted. To use Gen3, you must clarify and apply for your entitlements (which are subject to costs) in a timely manner.		The Gen2 infrastructure will be permanently shut down in '''September 2026''' (refer to the [https://bwcloud-os.de/ '''bwCloud-OS website'''] for the exact date). All projects and data that have not been migrated to Gen3 by this date will be irrevocably deleted. To use Gen3, you must clarify and apply for your entitlements (which are subject to costs) in a timely manner.
	\|}		\|}

Guide: Network Configuration by Region

Sia — Thu, 28 May 2026 09:48:56 GMT

← Older revision		Revision as of 09:48, 28 May 2026
(One intermediate revision by the same user not shown)
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 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.

Cloud Migration Guide

Sia — Thu, 28 May 2026 09:42:04 GMT

← Older revision		Revision as of 09:42, 28 May 2026
Line 5:		Line 5:
	{\| class="mw-message-box mw-message-box-warning"		{\| class="mw-message-box mw-message-box-warning"
	\| style="vertical-align:middle;" \| '''⚠️ IMPORTANT SHUTDOWN NOTICE:'''		\| style="vertical-align:middle;" \| '''⚠️ IMPORTANT SHUTDOWN NOTICE:'''
	The Gen2 infrastructure will be permanently shut down on '''~~August 31~~, 2026'''. All projects and data that have not been migrated by this date will be irrevocably deleted. To use Gen3, you must clarify and apply for your entitlements (which are subject to costs) in a timely manner.		The Gen2 infrastructure will be permanently shut down on '''September 15, 2026'''. All projects and data that have not been migrated by this date will be irrevocably deleted. To use Gen3, you must clarify and apply for your entitlements (which are subject to costs) in a timely manner.
	\|}		\|}

Guide: Load Balancers

Sia — Sun, 24 May 2026 13:06:34 GMT

← Older revision		Revision as of 13:06, 24 May 2026
(One intermediate revision by the same user not shown)
Line 60:		Line 60:
	= Load Balancer Setup and Backend Integration =		= Load Balancer Setup and Backend Integration =

			Install the client (preferably in a Python virtual environment):
			<pre>pip3 install python-octaviaclient</pre>
	== Create the load balancer ==		== Create the load balancer ==
	<pre>		<pre>

	openstack loadbalancer create \		openstack loadbalancer create \
	--name myLB \		--name myLB \