Instances (VMs): Difference between revisions
Jump to navigation
Jump to search
| Line 31: | Line 31: | ||
It is also possible to create an instance automatically. Details can be found [[Automatisierung & Tools#Instanz mit Ansible einrichten|here]]. | It is also possible to create an instance automatically. Details can be found [[Automatisierung & Tools#Instanz mit Ansible einrichten|here]]. | ||
= Quota | = Quota and resources = | ||
Various resources are available in bwCloud-OS. If you need more quota, you can request it. You can find more information [[here|here]]. | |||
{{:BwCloud-OS Bereitgestellete-Flavors}} | {{:BwCloud-OS Bereitgestellete-Flavors}} | ||
== | == Resize an Instance after Additional Quota Has Been Granted == | ||
If your project has been allocated more quota (vCPU/RAM/instances), you can upgrade an existing VM to a larger '''hardware flavor'''. This will restart the VM and change the flavor (vCPU/RAM). | |||
''' | '''Important:''' | ||
* | * Data on '''attached volumes''' (Cinder) will remain unchanged. | ||
* | * Back up important data before performing the resize. | ||
=== | === Prerequisites === | ||
* | * Sufficient quota in the selected region. | ||
* | * Appropriate larger flavor available (see [[BwCloud-OS Bereitgestellete-Flavors|Hardware Flavors]]). | ||
* | * Schedule a maintenance window (short restart / brief downtime). | ||
=== | === Step-by-Step (Dashboard) === | ||
# | # Log in to the [https://dashboard.bw-cloud.org bwCloud-OS Dashboard] and select the desired '''region''' in the top left. | ||
# | # Navigate to Project → Compute → Instances. | ||
# | # Open the dropdown menu for the desired instance and select '''''Resize Instance'''''. | ||
# | # Select a larger '''flavor''' (e.g., from <code>m1.small</code> to <code>m1.medium</code>) and confirm with ''Resize''. | ||
# | # Wait until the status shows '''VERIFY_RESIZE''' and the VM is reachable again. | ||
=== | === After Resizing: Verify & Confirm === | ||
# | # Check that the resources match: | ||
## RAM/CPU: <code>free -h</code>, <code>nproc</code> | ## RAM/CPU: <code>free -h</code>, <code>nproc</code> | ||
## | ## Disk layout: <code>lsblk</code>, <code>df -h</code> | ||
# | # If everything is working: select '''''Confirm Resize''''' in the instance dropdown. | ||
# | # If problems occur: select '''''Revert Resize''''' (restores the previous flavor). | ||
=== Notes === | |||
=== | * Attached data volumes must be resized separately via ''Volumes → Extend Volume'' and then extended within the guest system (e.g., <code>sudo resize2fs</code> or <code>sudo xfs_growfs</code>). | ||
* | * The VM will be restarted during the resize; the IP address remains unchanged. | ||
* | |||
Revision as of 12:03, 22 September 2025
Quickstart: Store SSH key pair
Launching an Instance
Create an Instance (GUI)
- Click Instances in the left menu. On the new page, select the Launch Instance button. A dialog will open, guiding you through the process step by step.
- First, give the instance a meaningful name (e.g.,
myVM01). Click Next at the bottom. - Select a source / Image for the instance (e.g., Debian X). Add the selection using the ↑ symbol; the chosen image will appear under Allocated. To discard a selection, click the ↓ symbol in the row.
- In the next step, select a Flavor. If the current quota is too low, a yellow warning icon will appear.
- Next, choose the Network. In most cases, the default settings are sufficient; no changes are required.
- For the Security Group, no adjustments are usually necessary. Changes can be made later if needed.
- Select the public SSH Key to be integrated into the instance. This step is mandatory; without a registered SSH key, access to the running instance is not possible.
- Click Launch Instance. The instance will start.
- After the instance has successfully started, the IP address will be displayed in the overview. The instance can be accessed at this address.
SSH Access
- Once started, you can log in via SSH:
ssh -i /path/to/key <username>@<ip-address>
- The corresponding SSH usernames are listed in this reference list.
Configure an Instance with Ansible
It is also possible to create an instance automatically. Details can be found here.
Quota and resources
Various resources are available in bwCloud-OS. If you need more quota, you can request it. You can find more information here.
BwCloud-OS Bereitgestellete-Flavors
Resize an Instance after Additional Quota Has Been Granted
If your project has been allocated more quota (vCPU/RAM/instances), you can upgrade an existing VM to a larger hardware flavor. This will restart the VM and change the flavor (vCPU/RAM).
Important:
- Data on attached volumes (Cinder) will remain unchanged.
- Back up important data before performing the resize.
Prerequisites
- Sufficient quota in the selected region.
- Appropriate larger flavor available (see Hardware Flavors).
- Schedule a maintenance window (short restart / brief downtime).
Step-by-Step (Dashboard)
- Log in to the bwCloud-OS Dashboard and select the desired region in the top left.
- Navigate to Project → Compute → Instances.
- Open the dropdown menu for the desired instance and select Resize Instance.
- Select a larger flavor (e.g., from
m1.smalltom1.medium) and confirm with Resize. - Wait until the status shows VERIFY_RESIZE and the VM is reachable again.
After Resizing: Verify & Confirm
- Check that the resources match:
- RAM/CPU:
free -h,nproc - Disk layout:
lsblk,df -h
- RAM/CPU:
- If everything is working: select Confirm Resize in the instance dropdown.
- If problems occur: select Revert Resize (restores the previous flavor).
Notes
- Attached data volumes must be resized separately via Volumes → Extend Volume and then extended within the guest system (e.g.,
sudo resize2fsorsudo xfs_growfs). - The VM will be restarted during the resize; the IP address remains unchanged.