*[Create the CSP.LMC Common Software python package](#python-package)
*[CSP_Mid LMC](#CSP_Mid.LMC)
*[CSP_Mid LMC Deployment in Kubernetes](#Mid-CSP.LMC-Kubernetes-Deployment-via-Helm-Charts)
*[CSP_Mid LMC Deployment in Kubernetes](#mid-CSP.LMC-Kubernetes-Deployment-via-Helm-Charts)
*[CSP_Low LMC](#csp-low-lmc)
*[Run in containers](#how-to-run-in-docker-containers)
*[Known bugs](#known-bugs)
@@ -207,23 +207,27 @@ Other Makefile targets, such as `describe` and `logs`, provide some useful infor
The project includes a set of tests for the `MidCspMaster` and `MidCspSubarray` TANGO Devices
that can be found in the project `tests` folder.<br/>
To run the tests on the local k8s cluster, issue the command
To run the tests on the local k8s cluster, issue the command:
<code><pre>make k8s_test</pre></code>
```bash
make k8s_test
```
from the root project directory.<br/>
This command first deploys the system and then executes the integration tests.
After tests end, run the command:
<code><pre>make delete</pre></code>
```bash
make delete
```
to uninstall the HELM charts of the `test` release.
## Gitlab continuos integration tests
Continuos integration tests in Gitlab rely on the `.gitlab-ci.yml` configuration file that provides al the scripts to build, test and deploy the application. <br/>
This file has been updated to run test in K8s environment and any reference to the use of `docker-compose` as containers manager, has been removed <br/>.
This file has been updated to run test in K8s environment and any reference to the use of `docker-compose` as containers manager,
has been removed. <br/>
A new job has been added in the pipline `publish` stage to release the the `csp-proto` helm chart in the SKA Helm charts repositoryhostes under `nexus`.
## Docker-compose support
@@ -232,14 +236,12 @@ Support to `docker-compose` has not been completely removed even if all the main
performed in kubernetes environment.<br/>
Use of `docker-compose` has been maintened only to simplify the development on machines that
are not capable to run minikube in a virtual machine.<br/>
The docker folder of the project contains all the files required to run the system via the
The `docker` folder of the project contains all the files required to run the system via the
docker-compose tool.
From the docker folder of the project, one can still:
• build the image running <code><pre> make build </pre></code>
• start the system dockers with docker-compose executing
make up
• run the test on the local machine calling:
make test
• build the image running `make build`
• start the system dockers with docker-compose executing `make up`
• run the test on the local machine calling `make test`
The Docker containers running the CBF_Mid devices are instantiated pulling the `mid-cbf-mcs:test` project image from the [Nexus repository](https://nexus.engageska-portugal.pt). <br/>
The CSP_Mid.LMC project provides a [Makefile](Makefile) to start the system containers and the tests.<br/>
@@ -251,7 +253,7 @@ The containerised environment relies on three YAML configuration files:
Each file includes the stages to run the the `CSP_Mid.LMC TANGO DB`, the `CSP_Mid.LMC` devices and `Mid-CBF.LMC` TANGO Devices inside separate docker containers.<br/>
These YAML files are used by `docker-compose` to run both the CSP_Mid.LMC and CBF.LMC TANGO device
instances, that is, to run the whole `CSP_Mid.LMC` prototype.>br\>
instances, that is, to run the whole `CSP_Mid.LMC` prototype.<br/>
In this way, it's possible to execute some preliminary integration tests, as for example the assignment/release of receptors to a `CSP_Mid Subarray` and its configuration to execute a scan in Imaging mode.<br/>
The `CSP_Mid.LMC` and `Mid-CBF.LMC TANGO` Devices are registered with the same TANGO DB, and its
configuration is performed via the `dsconfig` TANGO Device provided by the [dsconfig project](https://gitlab.com/MaxIV-KitsControls/lib-maxiv-dsconfig). <br/>
