...
Here below a sketch of an existing beamline repo referring to SCS.
Beamline tree
| Anchor | ||||
|---|---|---|---|---|
|
Each beamline in EPIK8S has a GIT project associated. This GIT project has:
- opi directory that points to a OPI git project that contains the interface of the given beamline;
- deploy directory that has the format of an helm chart and contains instruction on what deploy on k8s (Kubernetes);
- config directory that contains initialisations and configurations for:
- iocs: iocs of your beamline;
- services: epics services (cagateway, archivers...);
- applications: things that are not iocs nor services, typically support applications for importing, simulation, cronjobs.
As you can see in , the Beamline Tree can be composed by other git submodules.
...
A bunch of tools have been developed to help epik8s beamline EPIK8s beamlines creation and management.
Install EPIK8S tools
...
This command will create a Beamline tree, the script needs some information coming from K8S installation.
In particular if you want to fix IPs of your IOC to work around CA/PVA bugs you need to know the service cidr.
iocbaseip = service cidr
cagatewayip = first unused IP from metallb metallb
pvagatewayip = second unused IP from metallb metallb