Utilize QBO Kubernetes Engine (QKE) and QBO Container Engine (QCE) to efficiently create, deploy, and oversee resources in QBO Cloud. With QBO, experience high-performance computing while retaining cloud flexibility, granting direct access to GPUs, CPUs, and Disk resources. Execute cluster and instance operations swiftly, surpassing the speed of conventional cloud providers. Harness the capabilities of QCE and QKE effortlessly through the web interface, CLI, or QBO AsyncAPI, providing seamless accessibility to manage resources with utmost convenience.
Configuration
QBO can authenticate access to the API using a web interface or a CLI interface. The web interface uses oauth2 Google authentication and the CLI uses either a temporary universally unique token (oauth2 authentication) or a service account. Both methods as described below
Note that when you login to the Web console @ https://console.cloud.qbo.io the web console is already configured and there is no further configuration needed for authentication. See Configuration priority for more info.
If you are using a Linux, Mac or Windows shell outside QBO’s web console you can authenticate in two ways:
Web Token
This token is generated upon successful authentication with your Google account
It can be retrieved by logging in to the web console @ https://console.cloud.qbo.io and getting user’s CLI local configuration
qbo get user -l | jq .cli[]? |
{ |
Get
qbo_uid
web token from the output above and then export the environment variable:QBO_UUID
.
Note thatQBO_UID
is a temporary token and will expire with the web session expires.
export QBO_UID=33820cc1-d513-4fa8-88ac-1adb008c3864 |
Service Account
QBO service accounts use Elliptical curve cryptography (ECC) P-521 for encryption. A public key in json compact format
qbo_uid
is shared as well as an auxiliary tokenqbo_aux
for authentication.
Before we can obtain and configure a service account a temporary web token is needed as described in Temporary web token to retrieve the service account.
Verify you can authenticate to the qbo API with the web token by getting qbo API version
qbo version | jq .version[]? |
{ |
Download the CLI by cloning the repo @ https://git.eadem.com/alex/qbo-ce.git.
QBO CLI runs inside a container and can be used in Linux, Mac and Windows OSes.
git clone https://github.com/alexeadem/qbo-ce.git |
Add alias to run by typing
qbo
. ./alias |
Get the user’s configuration and pipe the output to the file
cli.json
under$HOME/.qbo/
qbo get user -c [email protected] | jq .users[]?.cli.conf > ~/.qbo/cli.json |
cli.json
is the file containing the service account used by the CLI to authenticate by the API.
ee priorities
cat ~/.qbo/cli.json |
{ |
Unset the temporary web token to start using the service account.
unset QBO_UID |
Verify the service account by getting the user’s local configuration.
qbo get user -l | jq .cli[]? |
{ |
You should now be able to use the service account to authenticate to the qbo API
qbo version | jq .version[]? |
{ |