Deploying InvenioRDM

First of all, log in and select the right project in your OpenShift cluster:

$ oc login <your.openshift.cluster>
$ oc project invenio


Before deploying, you need to provide the credentials so the application can access the different services. Replace the credentials and configuration below with your own:

Invenio secret key:

console $ SECRET_KEY=$(openssl rand -hex 8) $ oc create secret generic \ --from-literal="INVENIO_SECRET_KEY=$SECRET_KEY" \ invenio-secrets

Database secrets:

$ POSTGRESQL_PASSWORD=$(openssl rand -hex 8)
$ oc create secret generic \
secret "db-secrets" created

RabbitMQ secrets:

$ RABBITMQ_DEFAULT_PASS=$(openssl rand -hex 8)
$ oc create secret generic \
  --from-literal="CELERY_BROKER_URL=amqp://guest:$RABBITMQ_DEFAULT_PASS@mq:5672/" \
secret "mq-secrets" created

Elasticsearch secrets:

Elasticsearch variables

Currently, and until invenio-search#198 has been addressed, the Elasticsearch configuration has to be loaded in a single environment variable.

$ export INVENIO_SEARCH_ELASTIC_HOSTS="[{'host': 'localhost', 'timeout': 30, 'port': 9200, 'use_ssl': True, 'http_auth':('USERNAME_CHANGEME', 'PASSWORD_CHANGEME')}]"
$ oc create secret generic \

Extra configuration is possible

Note that you might need to add extra configuration to the Elasticsearch hosts, such as certificate verification (verify_certs), prefixing (url_prefix) and more.

Install InvenioRDM

Before installing you need to configure two things in your values.yml file. The rest are optional and you can read more about them here:

  • The host.
  • The web/worker docker images.
host: yourhost.localhost

  image: your/invenio-image

  image: your/invenio-image

INVENIO_SITE_HOSTNAME needs to be set up

The Helm charts need to be updated to support this variable in the values.yaml. In the meantime, this value can be set manually in the ConfigMap, or hardcode it in the web charts. The value should be the URL or your instance (Same as the host above).

Image registries

You can get to know more about where and how to store you instance's docker image here.

The next step is the installation itself, with your own configuration in the values.yaml. If you added the repository, you can install it by using the chart name and the desired version:

$ helm install -f values.yaml invenio helm-invenio/invenio --version 0.2.0

If you want to install from GitHub, in a clone you can do so as follows:

$ cd helm-invenio/
$ helm install -f values.yaml invenio ./invenio [--disable-openapi-validation]

In both cases the output will be:

NAME: invenio
LAST DEPLOYED: Mon Mar  9 16:25:15 2020
NAMESPACE: default
STATUS: deployed
NOTES:Invenio is ready to rock :rocket:

Bypassing openapi validation

We must pass --disable-openapi-validation as there is currently a problem with OpenShift objects and Helm when it comes to client side validation, see issue.

Setup the instance

Once the instance has been installed you have to set up the services. Note that this step is only needed the first time, if you are upgrading the instance this is not needed.

Get a bash terminal in a web pod:

$ oc get pods
$ oc exec -it <web-pod> bash

Setup the instance using the invenio commands:

$ . scl_source enable rh-python36
$ invenio db init # If the db does not exist already, otherwise `create` is enough
$ invenio db create
$ invenio index init
$ invenio index queue init purge
$ invenio files location --default 'default-location'  $(invenio shell --no-term-title -c "print(app.instance_path)")'/data'
$ invenio roles create admin
$ invenio access allow superuser-access role admin

Launching jobs

One time job

In some cases you might want to run jobs, for example to populate the instance with records.

$ oc process -f job.yml --param JOB_NAME='demo-data-1' \
  --param JOB_COMMAND='invenio rdm-records demo' | oc create -f -

Cron job

Now, imagine you have some bulk record indexing, or any other task that you have to do periodically.

For that, you can define cronjobs:

$ oc process -f cronjob.yml --param JOB_NAME=index-run \
  --param JOB_COMMAND=invenio index run -d | oc create -f -

Upgrade your instance

If you have performed some changes to your instance (e.g. configuration) or you want to upgrade the version of the chart, you can do so with the upgrade command of helm.

Not supported yet

Note that you still need to disable the openapi validation which is not supported yet in version 3.1.2 (However, it is merged into the master branch and should come out soon). For now we will have to helm uninstall and then install again.

$ helm upgrade -f values.yaml --disable-openapi-validation