The instances do not have a predefined root password. During deployment, the SSH public key you specify is automatically set up on the instance.
The easiest way to access an instance is via a public floating IP.
Simply click on the arrow next to your instance and on “Associate floating IP”. Then select a suitable floating IP. If no floating IP is available yet, you can request a new one.
Click on “Access & Security” in the “Compute” section. Then click on the tab “floating IPs” and finally on “Allocate IP to Project”.
The reason for this is probably an overly restrictive security group (see firewall). The default security group is comparable to a SoHo-Router. Outgoing everything is allowed, but incoming is blocked
Click on “Access & Security” in the “Compute” section. Then click on “Create Security Group”. Select a name and a description and then add the desired rules. Of course, the “Default” security group can also be extended by rules if desired
Simply click on the arrow next to your instance and on “Edit Security Groups”.
Currently we use OpenStack in version Ocata, thus the following API versions are supported:
- image (glance): 2.5 (supported: 2.0 – 2.4; deprecated: 1.0, 1.1)
- volume (cinder): 3.27 (supported: 2.0, 3.0; deprecated: 1.0)
- identity (keystone): 3.8
- compute (nova): 2.42 (supported: 2.0, 2.1)
- networking (neutron): 2.0
- alarming (aodh): 2
- metering (ceilometer): 2
- orchestration (heat): 1.0
Most APIs provide version information under the base URL, e.g. enter the following into a web browser for Keystone version information: https://de-nbg6-1.noris.cloud:5000. A list of all URLs is available with “openstack catalog list” or in the GUI under “Project -> Compute -> API Access”