On-ramps to CLI and API
Problem/Opportunity Statement
From the values and goals of Exosphere:
- Empower people to use Exosphere along with other tools to manage the same resources, with minimal cost of switching
- i.e. make it easy to move away from Exosphere to other tools and come back at will
Some advanced cloud use cases will require the use of the OpenStack command-line client (CLI) or the underlying OpenStack APIs.
Getting started with these tools requires:
- Guidance to install the OpenStack command-line client(s)
- Credentials to connect to OpenStack, containing either a password credential or an application credential
- For the CLI, these should be in openrc (bash variable) or clouds.yaml format
- On Jetstream2, obtaining these credentials requires use of Horizon, sending an Exosphere user to an interface that they may otherwise not need
We can make this better.
What would success / a fix look like?
While logged into a project in Exosphere, you get:
- A button that provides usable OpenRC/clouds.yaml file (containing an application credential, see comment below)
- Links to guidance for setting up the command-line client
While "logged into" a provider you should be able to view/export OpenRC files (perhaps strip the password) for a given provider. See also #135 (closed).
Edited by Julian Pistorius