Architecture

── 

...

README.md

...

├── config

...

│

...

   ├── applications

...

│   ├── iocs
│   └── services
├── deploy
│   ├── Chart.yaml
│   ├── templates
│   └── values.yaml
├── opi
│   ├── Launcher.bob
│   ├── README.md
│   ├── deploy
│   ├── env.sh
│   ├── phoebus_mrf_interface
│   ├── ptts
│   ├── rp-opi
│   ├── settings.ini
│   ├── settings_template.ini
│   └── start.sh
└── sparc-deploy.yaml

Each beamline in EPIK8S has a GIT project associated. This GIT project has:

1. opi directory that points to a OPI git project that contains the interface of the given beamline
2. deploy directory that has the format of an helm chart and contains instruction on what deploy on k8s
3. config directory that contains initialisations and configurations for:
   1. iocs: iocs of your beamline
   2. services: epics services (cagateway, archivers...)
   3. applications: things that are not iocs nor services, typically support applications for importing, simulation, cronjobs.

This structure allows:

1. separate development of OPIs and IOCs
2. update control room OPIs accessing just the GIT repository of the OPI.