Skip to content
Snippets Groups Projects
README.md 2.66 KiB
Newer Older
Te-Hung Tseng's avatar
Te-Hung Tseng committed
# Archiver Appliance Config AA Linac Prod
Luis Contreras's avatar
Luis Contreras committed

Luis Contreras's avatar
Luis Contreras committed
This repository is used to store mainly scalar PVs and also have imports from archiver-linac-prod.
Sky Brewer's avatar
Sky Brewer committed
Rule of thumb is PVs with more than 2046 elements should be in the
[wf config](https://gitlab.esss.lu.se/archiver-appliance/archiver-appliance-config-aa-waveform) and not this repository.

Te-Hung Tseng's avatar
Te-Hung Tseng committed
## Introduction

For each IOC, the list of PVs to archive should be saved in a file named `<ioc name>.archive`.
The file should be put under the files directory
Luis Contreras's avatar
Luis Contreras committed
Here is the list of current archiver appliances for wave form cluster:

- **archiver-linac-01.tn.esss.lu.se** for Scalar form Prod
- **archiver-linac-02.tn.esss.lu.se** for Scalar form Prod
- **archiver-linac-03.tn.esss.lu.se** for Scalar form Prod
- **archiver-linac-04.tn.esss.lu.se** for Scalar form Prod
- **archiver-linac-05.tn.esss.lu.se** for Scalar form Prod
- **archiver-linac-06.tn.esss.lu.se** for Scalar form Prod
- **archiver-linac-07.tn.esss.lu.se** for Scalar form Prod
- **archiver-linac-08.tn.esss.lu.se** for Scalar form Prod

Te-Hung Tseng's avatar
Te-Hung Tseng committed
**ALL WaveForm have to be archived at 1Hz** (see Archive File Format below).
**PV Rename and Delete not supported** - see the [Archiver FAQ](https://confluence.esss.lu.se/display/SW/Archiver+FAQ#expand-Howtopauserenameordeleteapv) for more information.
Sky Brewer's avatar
Sky Brewer committed

Te-Hung Tseng's avatar
Te-Hung Tseng committed
## Archive File format

The files shall be in CSV format (space separated) and include one PV name per line.
A file can also include the name of the policy to force (optional).
Empty lines and lines starting with "#" (comments) are allowed.
Te-Hung Tseng's avatar
Te-Hung Tseng committed
```
# PV name    Policy
ISrc-010:PwrC-CoilPS-01:CurS
ISrc-010:PwrC-CoilPS-01:CurR    1Hz
# Comments are allowed
LEBT-010:Vac-VCG-30000:PrsStatR
The string after the PV name should be an existing policy to force.
In the above example, the policy "1Hz" would be applied to the PV "ISrc-010:PwrC-CoilPS-01:CurR".
The default policy would be applied to other PVs.

Te-Hung Tseng's avatar
Te-Hung Tseng committed
## Workflow

When pushing to master, the PVs are automatically added to the archiver.
Te-Hung Tseng's avatar
Te-Hung Tseng committed

The `process_archives.py` script looks at files that changed since last commit.
All the PVs from those files are sent to the proper appliance for archiving.
Benjamin Bolling's avatar
Benjamin Bolling committed
### Maintainer rules

- If configuration files have PV namechanges or deletions, the merge request shall have the name of the [INFRA-ticket-number] for the PVs changing names and being deleted.
Benjamin Bolling's avatar
Benjamin Bolling committed
- If there are merge conflicts, the developer requesting the merge request shall resolve the conflicts on their end (preferably by re-basing to master followed by re-applying the changes from the merge request).
- Ensure PVs added are online (see [accop-pytools-archiver-mr-check](https://gitlab.esss.lu.se/accop/pytools/archiver-mr-check) for example script).