Can I allocate more resources (such as RAM memory) to a running instance?[faq_instances_1]

Yes, for a running instance more main memory or even more vCPUs can be allocated at any time. Prerequisite for this is that enough quota is available.

Instance, RAM, vCPU, flavor, quota, increase

⇈ Top

How can I allocate more resources (for example RAM memory) to a running instance?[faq_instances_2]

Note: For this purpose the instance is stopped for a short time!

flavor, change, quota, RAM, vCPU, resize, enlarge

⇈ Top

Can I remove / take away resources (such as RAM memory) from a running instance?[faq_instances_3]

Yes, resources can also be taken away from a running instance - it can be "shrunk". The process is similar to the process for enlarging an instance (see ↑ question above), except that this time a correspondingly smaller flavor is selected.

Please note: We do not recommend this operation! It cannot be guaranteed that your instance will work properly after having shrunken it.

Flavor, change, quota, RAM, vCPU, resize, shrink

⇈ Top

If I reduce an instance, will my attached memory (hard disk) also be reduced?[faq_instances_4]

No, attached storage is not reduced. Only the parameters main memory (RAM) and available vCPUs can be increased or decreased during operation.

flavor, change, quota, RAM, vCPU, resize, attached storage, storage, hard disk, shrink

⇈ Top

So what do I have to do if I want to reduce both my instance and attached memory?[faq_instances_5]

To reduce the instance, simply follow the answer to the question above.
In order to reduce the attached memory, a new disk with the desired size must first be created. This must be attached to the instance. Then copy the data from the old (large) disk to the new (smaller) one. Afterwards the old (large) hard disk can be deleted.

hard disk, storage, attached storage, attached memory, reduce

⇈ Top

What do I have to do to get more quota?[faq_instances_6]

Our general rule applies: whoever comes first will also get first ("first come first serve"). To get more quota, proceed as follows:

  1. Write us a Ticket under https://bw-cloud.org/q/t.
    In the ticket you tell us the following points:

    a) You would like to have more quota
    b) Whereof you need more (more RAM? more vCPUs? ...)
    c) Your OpenStack identifier, ideally the User-ID d) How long you need to do this approximately
    e) What you need it for

    The points a) to c) are obligatory, the following points are optional.

  2. based on your requirements we will check if we are (still) able to enlarge/change your quota settings accordingly
  3. as soon as the settings have been changed you will receive feedback via the ticket system

PLEASE NOTE: Specific allocation rules apply for certain user locations. You can find the current regulations under Quota & Ressourcen.

Quota, Increase, Magnify, More resources,

⇈ Top

The offered flavors are too small for me, can I define my own flavors?[faq_instances_7]

No, the definition and configuration of individual flavors is not possible.

Flavor, individual, configure

⇈ Top

The offered flavors are too small for me, can I at least get bigger flavors?[faq_instances_8]

No, we cannot offer larger flavors at present for technical reasons.

Flavor, bigger machines, more RAM, memory, vCPUS

⇈ Top

Where do I find the Linux username with which I have to log into the instance via SSH for the first time?[faq_instances_9]

On our page Current and available images in the bwCloud SCOPE we have listed all images we currently offer. To these Images we offer some meta information on the website. In the line Standard SSH Username you will find the username that you have to use to log in to the instance via SSH for the first time.

image, instance, start, login, SSH, first login, user name, standard username, user,

⇈ Top

My Debian instance takes forever to reboot when the network is active[faq_instances_10]

This problem seems to only occur with Debian based instances and has to do with the configuration of the network interface for IPv6. We were able to develop a workaround that should fix this problem. The process looks like the following:

  1. Edit the file 50-cloud-init.cfg in the directory /etc/network/interfaces.d
  2. Comment out the block for configuring eth0 for IPv6 via DHCP

$ vi /etc/network/interfaces.d/50-cloud-init.cfg

# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
    dns-nameservers 134.155.96.51 134.155.96.52 2001:7c0:600:60::869b:6033 2001:7c0:600:60::869b:6034

auto eth0
iface eth0 inet dhcp
    mtu 1500

# control-alias eth0
#iface eth0 inet6 dhcp
#    post-up route add -A inet6 default gw 2001:7c0:600:6c::1 || true
#    pre-down route del -A inet6 default gw 2001:7c0:600:6c::1 || true

Hint:

Image, Instance, Reboot, Hangs, Network, Debian, IPv6, DHCP

⇈ Top

Privacy statement   |   Impressum   |   Site built with Simple Responsive Template   |   Modified: 19.2.2020 before midday by JCS