Link Search Menu Expand Document

FAQ

The command openstack --help shows the error “Could not load EntryPoint.parse”

In this case some components of the OpenstackClient are outdated. You can use the command below, to get an overview of which components need to be updated:

$ openstack --debug --help

This will show you which components need to be updated, which you can do with the command below. (Replace <PROJECT> with the correct project):

$ pip install python-<PROJECT>client -U

How can I use VRRP?

In order to use VRRP, you will need to add a rule to a security group that’s associated with an actual VM. You can only add this via the OpenStack client! An example of adding VRRP to a security group would be:

$ openstack security group rule create --remote-ip 10.0.0.0/24 --protocol vrrp --ethertype IPv4 --ingress  default

Is it possible to use ED25519 SSH keys?

For now, it’s not possible to use ED25519 SSH keys.

There is a bug in OpenSSL that’s needed for the TLS layer in OpenStack. You can track the progress of this bug in these two tickets:

Why am I charged for Floating IPs I am not using?

We have to charge for reserved Floating IPs, and most often the case is that you did not remove the Floating IP after deleting the VM that used it.

To get an overview of your Floating IPs, you can use the Horizon Dashboard, where you can find the list a ProjectNetworkFloating-IPs.

You can accomplish the same using the OpenStack client:

$ openstack floating ip list
+--------------------------------------+---------------------+------------------+--------------------------------------+--------------------------------------+----------------------------------+
| ID                                   | Floating IP Address | Fixed IP Address | Port                                 | Floating Network                     | Project                          |
+--------------------------------------+---------------------+------------------+--------------------------------------+--------------------------------------+----------------------------------+
| 84eca713-9ac1-42c3-baf6-860ba920a23c | 185.116.245.222     | 192.0.2.7        | a3097883-21cc-49fa-a060-bccc1678ece7 | 54258498-a513-47da-9369-1a644e4be692 | b15cde70d85749689e6568f973bb002  |
+--------------------------------------+---------------------+------------------+--------------------------------------+--------------------------------------+----------------------------------+

How can I change the flavor of a virtual machine (instance resize)?

In the Optimist Stack you change the flavor of an instance – the available RAM and vCPUs – using the following steps:

Resizing via command line

With the name or UUID of the server you wish to resize, resize it using the openstack server resize command.

Specifying the desired new flavor and then the instance name or UUID:

$ openstack server resize --flavor FLAVOR SERVER

Resizing can take some time. During this time, the instance status will show as RESIZE.

When the resize completes, the instance status will be VERIFY_RESIZE. You can now confirm the resize to change the status to ACTIVE:

$ openstack server resize --confirm SERVER

Resizing via the Optimist dashboard

On Optimist Dashboard → Instances navigate to the instance to resize, then choose: Actions → _Resize Flavor:.

The current flavor will be shown, use the “Select a new flavor” dropdown list to choose the new flavor and confirm with “Resize”

Why are the logs of the compute instance in the optimist dashboard empty?

Due to maintenance work or load balancing of the OpenStack, the instance might have been migrated. In this case the log file gets cleared. New messages will be logged to the file as they occur.

Why do I get the error “Conflict (HTTP 409)” when creating a swift container?

Swift uses unique names across the entire OpenStack environment. The error message states that the selected name is already in use.

How-To Mount Cinder Volumes to Instances by UUID

When attaching multiple Cinder Volumes to an instance, it is possible that the mount points will be shuffled on every reboot. Mounting the volumes by UUID ensures the proper volumes are reattached to the correct mount points in the event the instance requires a power cycle.

Change the mountpoint in /etc/fstab to use the UUID after fetching the infos with blkid on eg:

# /boot was on /dev/sda2 during installation
/dev/disk/by-uuid/f6a0d6f3-b66c-bbe3-47ba-d264464cb5a2 /boot ext4    defaults        0       2