Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removed refresh-token stuff and mentioned offline_token and api_token #635

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Removed refresh-token stuff and mentioned offline_token and api_token #635

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
296d6a1
removed refresh-token stuff and mentioned offline_token
sheldor1510 Oct 22, 2024
7e7071d
forgot run
sheldor1510 Oct 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 3 additions & 11 deletions docs/source/usage/openshift.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,7 +159,7 @@ Using the python-esiclient CLI
Configure Access to the Assisted Installer API
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The python-esiclient CLI commands requires the user to access the Assisted Installer API. In order to do so, the user must `follow the steps in the Assisted Installer API documentation`_ which detail how to create a ``refresh-token`` script and how to export a ``PULL_SECRET`` to your environment.
The python-esiclient CLI commands requires the user to access the Assisted Installer API. In order to do so, the user must `follow the steps in the Assisted Installer API documentation`_ which detail how to export a ``API_TOKEN``, a ``OFFLINE_TOKEN``, and a ``PULL_SECRET`` to your environment.

Create a Cluster Configuration File
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down Expand Up @@ -191,17 +191,9 @@ Orchestrate the Cluster
| Orchestrate Cluster | ``openstack esi openshift orchestrate <path-to-cluster-config-file>`` |
+---------------------+-----------------------------------------------------------------------+

Once the cluster config file is created, run ``refresh-token`` and then ``openstack esi openshift orchestrate`` to start the orchestration of the OpenShift cluster.
Once the cluster config file is created, run ``openstack esi openshift orchestrate`` to start the orchestration of the OpenShift cluster.

Installation will take roughly an hour, and involves constant calls to the Assisted Installer API. However, the token from ``refresh-token`` will expire after 15 minutes. When this happens, the orchestration command will fail. Fortunately, it will do so while providing a command to continue installation:

.. prompt::

* YOU MAY NEED TO REFRESH YOUR OPENSHIFT API TOKEN
Run this command to continue installation:
openstack esi orchestrate openshift --cluster-id the-generated-cluster-id --infra-env-id the-generated-infra-env-id

If you see this message, simply run ``refresh-token`` again and then copy and paste the specified command.
Installation will take roughly an hour, and involves constant calls to the Assisted Installer API. The CLI will output the status of the cluster as it progresses.

Undeploy the Cluster
~~~~~~~~~~~~~~~~~~~~
Expand Down