Commit f96a1424 authored by Julien Leduc's avatar Julien Leduc
Browse files

Updating documentation for the continuous integration kubernetes infrastructure

parent da417183
......@@ -19,18 +19,20 @@ This is basically the command that is run by the `gitlab CI` in the [CI pipeline
Only one command is run in this build:
```
$ cd continuousintegration/orchestration/; \
./run_systemtest.sh -n ${NAMESPACE} -p ${CI_PIPELINE_ID} -s tests/systest.sh
./run_systemtest.sh -n ${NAMESPACE} -p ${CI_PIPELINE_ID} -s tests/archive_retrieve.sh
```
`CI_PIPELINE_ID` is not needed to run this command interactively: you can just launch:
```
[root@ctadevjulien CTA]# cd continuousintegration/orchestration/
[root@ctadevjulien orchestration]# ./run_systemtest.sh -n mynamespace -s tests/systest.sh
[root@ctadevjulien orchestration]# ./run_systemtest.sh -n mynamespace -s tests/archive_retrieve.sh
```
But be careful: this command instantiate a CTA test instance, runs the tests and **immediately deletes it**.
If you want to keep it after the test script run is over, just add the `-k` flag to the command.
**By default, this command uses local VFS for the objectstore and local filesystem for an `sqlite` database,** you can add `-D` and `-O` flags to respectively use the central Oracle database account and the Ceph account associated to your system.
The following sections just explain what happens during the system test step and gives a few tricks and useful kubernetes commands.
## List existing test instances
......@@ -242,13 +244,18 @@ If something goes wrong, please check the logs from the various containers runni
* The tape server SSS to be used by the EOS mgm to authenticate file transfer requests from the tape servers.
5. `ctacli`
* The cta command-line tool to be used by tape operators.
* This pod has the keytab of `ctaadmin1` who is allowed to type `cta` admin commands.
6. `ctafrontend`
* One CTA front-end.
* The CTA SSS of the EOS instance that will be used by the CTA front end to authenticate the cta command-line run by the workflow engine of the EOS instance.
7. `tpsrvXXX` *No two pods in the same namespace can have the same name, hence each tpsrv pod will be numbered differently*
7. `tpsrvXX` *No two pods in the same namespace can have the same name, hence each tpsrv pod will be numbered differently*
* One `cta-taped` daemon running in `taped` container of `tpsrvxxx` pod.
* One `rmcd` daemon running in `rmcd` container of `tpsrvxxx` pod.
* The tape server SSS to be used by cta-taped to authenticate its file transfer requests with the EOS mgm (all tape servers will use the same SSS).
8. `client`
* The `cta` command-line tool to be used by `eosusers`.
* The `eos` command-line tool.
* This pod has the keytab of `user1` who is allowed to read-write file in `root://ctaeos//eos/ctaeos/cta`.
# post-mortem analysis
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment