Web app¶
It's based on Openshift. There are two projects dev-docconverter and doconverter that are using EOS as a backend. The setup has been done by Openshift crew (mainly Alberto Peon). Basically to the container running the flask application, an extra container is appended that handles mounting the /eos. In order to do this setup a keytab of the account used to access eos needs to be provided (see below).
| project | eos | endpoints |
|---|---|---|
| dev-doconverter | /eos/user/c/cdsconv | https://dev-doconverter.web.cern.ch |
| doconverter | /eos/project/d/doconverter | https://doconverter.web.cern.ch |
Keytab generation¶
[root@ ~]# ktutil
ktutil: addent -password -p cdsconv@CERN.CH -k 1 -e RC4-HMAC
Password for cdsconv@CERN.CN:
ktutil: wkt cdsconv.keytab
ktutil: q
ConfigMap¶
A configMap object is used to pass the configuration of both files doconverter.ini and logging.conf. Those files should be found at c:\doconverter\config on each windows server running the software.
Webhooks¶
Configure webhooks from github.com towards Openshift, so when a change is commited on github the process of applying those changes is automatic. This is the case for the qa branch, for the master branch this process needs to be done manually as it may impact users.
CPU and Memory limits¶
They need to be modified for the container running the application in order to cope with big files.
- Log in into openshift.cern.ch, select the project.
- On the overview page, click on Deployment Config
- The Actions -> Resource limits
- On Web services site, go to the site e.g. doconverter
- Click on View quota Usage an choose a flavour that allows the limits you fixed previously e.g. medium. Higher it will create difficulties to relocate the
