Skip to content

CSCfi/rahti-user-guide

Repository files navigation

Rahti user guide

The user guide for the Rahti OpenShift systems.

Editing the documentation

The guide is written using the Markdown markup language. MkDocs is used to generate static documentation pages out of the Markdown files.

Markdown can be edited using any text editor, but you will need to install MkDocs if you wish to preview your changes while editing your documentation. You can find installation instructions in the MkDocs documentation.

Before building the site from the markdown sources, you will need to set some environment variables:

Variable Description
BILLING_ENABLED Whether the system has usage based billing.
GITLAB_LOGIN_SUPPORT Whether the system supports GitLab logins.
LDAP_LOGIN_SUPPORT Whether the system supports LDAP logins.
OPENSHIFT_VERSION What version of OpenShift is in use.
OSO_REGISTRY_URL The URL of the OpenShift registry web UI.
OSO_WEB_UI_URL The URL of the OpenShift web UI.
SUI_INTEGRATION_DONE Whether it is possible to apply for access via SUI.
SYSTEM_NAME The name of the OpenShift system.
SHOW_AGREEMENTS Whether to show agreements like the ToU and the SLA.

When these are set in the environment, you can create a config file for mkdocs:

./make_config.sh

Afther doing this, you can start a preview web server from the command line while in the root of the project directory:

mkdocs serve

This will start a web server on your computer listening on port 8000. Point your web server to localhost:8000 to get a preview of the documentation.

The configuration for MkDocs is in the mkdocs.yml file in the root of this repository. The name of the documentation site, the structure of the documentation pages and the theme to use for the site are described in this document.

The documentation files themselves are under the docs directory.

Using the included Dockerfile

You can also create a Docker container to host the docs. First build an image from the included Dockerfile, making sure to set all the necessary environment variables. For example:

sudo docker build -t rahti-user-guide \
  --build-arg BILLING_ENABLED=True \
  --build-arg SYSTEM_NAME=Rahti \
  --build-arg OSO_WEB_UI_URL=https://rahti.csc.fi:8443 \
  --build-arg OSO_REGISTRY_URL=https://registry-console.rahti.csc.fi \
  --build-arg LDAP_LOGIN_SUPPORT=True \
  --build-arg GITLAB_LOGIN_SUPPORT=0 \
  --build-arg SUI_INTEGRATION_DONE=True \
  --build-arg OPENSHIFT_VERSION=3.11 \
  --build-arg SHOW_AGREEMENTS=True .

Then run the container:

sudo docker run --rm -it -p 80:8000 --name rahti-user-guide rahti-user-guide

Hosting on OpenShift

The Dockerfile is also made to be compatible with OpenShift, so it should work with the source-to-image mechanism when using oc new-app. First create a new project to host the user guide:

oc new-project rahti-user-guide

Then run oc new-app to create the user guide deployment:

oc new-app \
  --build-env BILLING_ENABLED=True \
  --build-env SYSTEM_NAME=Rahti \
  --build-env OSO_WEB_UI_URL=https://rahti.csc.fi:8443 \
  --build-env OSO_REGISTRY_URL=https://registry-console.rahti.csc.fi \
  --build-env LDAP_LOGIN_SUPPORT=True \
  --build-env GITLAB_LOGIN_SUPPORT=0 \
  --build-env SUI_INTEGRATION_DONE=True \
  --build-env OPENSHIFT_VERSION=3.11 \
  --build-env SHOW_AGREEMENTS=True .
  https://github.com/CSCfi/rahti-user-guide.git#master

In the command above, the #master at the end specifies the branch to use. If you have a feature branch that you would like to test on OpenShift, you can specify a branch different from master.

About

The user guide for the Rahti OpenShift systems

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published