Programmatic Access and Automation: Difference between revisions
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
=== Steps to Create an Application Credential === | === Steps to Create an Application Credential === | ||
# '''Log in''' to the | # '''Log in''' to the '''[https://bw-cloud.org/q/d Dashboard]''' and select the correct '''region'''. | ||
# Go to '''Identity → Application Credentials''' and Click '''+ Create Application Credential'''. | # Go to '''Identity → Application Credentials''' and Click '''+ Create Application Credential'''. | ||
# In the form that opens, fill out: | # In the form that opens, fill out: | ||
| Line 22: | Line 22: | ||
#* '''Expiration''' – set an (optional) expiration date. | #* '''Expiration''' – set an (optional) expiration date. | ||
# At the bottom of the form, Click '''Create Application Credential'''. | # At the bottom of the form, Click '''Create Application Credential'''. | ||
# Download the ''' | # Download the '''openrc file''' and save it, e.g., as <code>my_token.sh</code>. | ||
''Protect your secret — store it securely and do not share it.'' <br> | ''Protect your secret — store it securely and do not share it.'' <br> | ||
| Line 54: | Line 54: | ||
= OpenStack Client = | = OpenStack Client = | ||
== How can I connect to the bwCloud-OS | == How can I connect to the bwCloud-OS using the OpenStack CLI? == | ||
To manage your resources from the command line, you can use the '''Python OpenStack Client (<code>openstack</code> CLI tool)'''. | |||
There are two supported authentication methods: | |||
=== Method 1: Using Application Credentials (Token-based – Recommended) === | |||
This is the preferred method, especially for scripting and automation. | |||
# '''Log in''' to the '''[https://bw-cloud.org/q/d Dashboard]''' . | |||
# Log in to the | # '''Create an Application Credential''' (see [[Automation and Tools#Application-Credential|this guide]] for instructions). | ||
# Create | # '''Download and save''' the generated file, e.g. as <code>my_creds.sh</code>. | ||
=== Method 2: Using Username and Password (Login-based) === | |||
Use this method only if you cannot use tokens. | |||
# '''Log in''' to the '''[https://bw-cloud.org/q/d Dashboard]'''. | |||
# Log in to the | # In the top-right corner, click '''"OpenStack RC File"'''. | ||
# In the | # '''Download and save''' the file, e.g. as <code>my_creds.sh</code>. | ||
<pre> | === Test === | ||
Run the following commands in a terminal:<pre> | |||
# source ./my_creds.sh | # source ./my_creds.sh | ||
# openstack server list | # openstack server list | ||
</pre> | </pre> | ||
This will show a list of your current virtual machines. | |||
= Auto-Deployment = | = Auto-Deployment = | ||
Revision as of 17:05, 19 October 2025
| In a Nutshell |
|
Application Credentials
How can I create an application credential?
Application Credentials (also called tokens) allow access to your OpenStack project in an automated or script-based way — without requiring a password. To create one, you must have the necessary member privileges in the target project.
Steps to Create an Application Credential
- Log in to the Dashboard and select the correct region.
- Go to Identity → Application Credentials and Click + Create Application Credential.
- In the form that opens, fill out:
- Name – a meaningful name for the credential.
- Secret – choose a secure secret (password-like).
- Expiration – set an (optional) expiration date.
- At the bottom of the form, Click Create Application Credential.
- Download the openrc file and save it, e.g., as
my_token.sh.
Protect your secret — store it securely and do not share it.
Optional: Ask for the Secret at Runtime
For added security, you can modify your my_token.sh file so that the secret is not stored in plain text. Replace the line:
export OS_APPLICATION_CREDENTIAL_SECRET=********************
with:
echo "Passphrase: " read -sr os_credential_secret_input export OS_APPLICATION_CREDENTIAL_SECRET="$os_credential_secret_input"
This way, you'll be prompted for the secret each time you use the credential file.
Test Your Application Credential
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 curl or jq are not installed, you can install them using your system’s package manager (e.g., apt, dnf, brew, etc.).
OpenStack Client
How can I connect to the bwCloud-OS using the OpenStack CLI?
To manage your resources from the command line, you can use the Python OpenStack Client (openstack CLI tool).
There are two supported authentication methods:
Method 1: Using Application Credentials (Token-based – Recommended)
This is the preferred method, especially for scripting and automation.
- Log in to the Dashboard .
- Create an Application Credential (see this guide for instructions).
- Download and save the generated file, e.g. as
my_creds.sh.
Method 2: Using Username and Password (Login-based)
Use this method only if you cannot use tokens.
- Log in to the Dashboard.
- In the top-right corner, click "OpenStack RC File".
- Download and save the file, e.g. as
my_creds.sh.
Test
Run the following commands in a terminal:
# source ./my_creds.sh # openstack server list
This will show a list of your current virtual machines.
Auto-Deployment
Proven methods for the (semi-)automated generation of services are listed below.
| Method | Usage |
|---|---|
| Terraform | This tool can be used to create an instance or a defined infrastructure. |
| Ansible | Create roles or tasks for all customizations that you make in an instance. |
Does bwCloud-OS provide templates for the automated deployment of OpenStack instances?
Yes. You can use this Ansible-template or an easier start.