How can I connect to the bwCloud via CLI/ OpenStack client?[faq_access_1]

The following describes how to connect using the python-openstackclient.

There are two ways to do that:

You should now see all your servers.

CLI

⇈ Top

How can I create an application credential?[faq_access_2]

Application credential/ token allow to gain and controll access to the Project. Therefore, respective privileges as members of the project are required.

Token create:

  1. Indenty -> Application Credentials
  2. Create Application Credentials
  3. Fill out the opened form. E. g.:
    Name: token_test_login
    Secret: ********************
    Expiration Date: 12/31/2023
  4. Create Application Credentials
  5. Download openrc file
  6. Save file. E. g. as my_token.sh
  7. Save the secret protected.
  8. In my_token.sh replace the line export OS_APPLICATION_CREDENTIAL_SECRET=******************** by
    echo "Passphrase: "
    read  -sr os_credential_secret_input
    export OS_APPLICATION_CREDENTIAL_SECRET="$os_credential_secret_input"

Test

Source your credential file my_token.sh. source my_token.sh

Run the following command. You should see your credential ID.

curl \
  -s \
  -H "Content-Type: application/json" \
  -d '{ "auth": { "identity": { "methods": ["application_credential"], "application_credential": { "id": "'${OS_APPLICATION_CREDENTIAL_ID}'", "secret": "'${OS_APPLICATION_CREDENTIAL_SECRET}'" }}}}' \
  "${OS_AUTH_URL}/auth/tokens" \
| jq .token.application_credential

If the curl command is not available, install the corresponding package with your package manager.

Token, Login, CLI

⇈ Top

Can I change the lost SSH key of my instance?[faq_access_3]

No. If you have 'lost' your SSH key to access an instance, you and Support cannot replace or exchange it.

Only if you have set the access to the instance via password in the virtual console in the dashboard active, you and only you can continue to access the machine.

Login, SSH

⇈ Top

I no longer have access to my instance, what can I do? [faq_access_4]

Can you rule out that it is not a network problem? If so, please take a look at the following instructions. The procedure described in it is possible via Dashboard and CLI.

Unfortunately, the solution is a bit messy and cumbersome.

Proceed as follows:

  1. Stop the instance foo1_vm with the ID vm-uuid.
  2. Create a backup/image foo1_img of the instance.
  3. From the image foo1_img, create the data carrier foo1_vol.
  4. Create a new instance foo2_vm.
  5. Attach the volume foo1_vol to the instance foo2_vm and mount the filesystem the instance foo1_vm.

With the volume foo1_vol at hand, you have countless options:

Login, CLI

⇈ Top

Privacy statement   |   Impressum   |   Site built with Simple Responsive Template   |   Modified:19.4.2024during the afternoon byJCS