Skip to content

Latest commit

 

History

History
507 lines (370 loc) · 10.9 KB

slideshow.md

File metadata and controls

507 lines (370 loc) · 10.9 KB
Raw

name: empty layout layout: true

name: title class: center, middle

Tango configuration tool

M. Lindberg, A. Dupre

07 June 2018

MaxIV-KitsControls/lib-maxiv-dsconfig

name: Background layout: true

This presentation is not about Ansible

At MAX IV we use Ansible to configure all control system servers and client computers.

  • Our configurations are standardized
  • Deployment can be automated
  • Configuration is maintained under version control
  • Idempotency

adjective: idempotent

    denoting an element of a set which is unchanged in value 
    when multiplied or otherwise operated on by itself

name: Background layout: true

The problem at hand

Several controlsystems (Tango databases)

  • Accelerator and storage rings ~ 10 000 devices
  • One per beamline ~ 700 devices x 15
  • Other systems such as testlabs ~ 500 devices each

Total number of Tango devices at MAX IV > 20 000

Multiple sources of information from the different subsystems that make up a synchrotron:

  • Magnets
  • various xls-files
  • Vacuum and Diagnostics
  • Allen Bradley PLC tag lists in csv format
  • Cable database
  • Motorization
  • yet another xls file

name: Problem layout: true

Creating order

###We need to:

  • Keep our configuration consistent and correct
  • Keep up with demands for updates and changes
  • Keep track of changes

###How do we do it?

  • Ensure consistency of source files (the format is up to the subsystem)
  • MAXIV naming convention is common ground
  • Track versions
  • Parsing tools for each type of source file
  • Intermediate Json format that can be used by a
  • Simple deployment tool (DsConfig!) that also allows us to
  • Track our configuration

name:situation layout: true

A comfortable situation?

The current state

  • Source files are delivered to us with versioning through Alfresco
  • Beamline installation process is well defined
  • Updates are applied in a safe and predictable manner

Plans

  • Web interface to allow subsystem owners to check their source files
  • Add parsing tools for even more subsystems
  • Allow some subsystems owners to apply their own updates

name:situation layout: true class: center, middle

Overview

.center[dsconfig]

name: Dsconfig layout: true

The Json format

Close to the jive server view:

    "servers": {
        "some-server/instance": {
            "SomeDeviceClass": {
                "some/device/1": {
                    "properties": {
                        "someImportantProperty": [
                            "foo",
                            "bar"
                        ],
                        "otherProperty": ["7"]
                    },
                    "attribute_properties": {
                        "anAttribute": {
                            "min_value": ["-5"],
                            "unit": ["mV"]
                        }
                    }
                }
            }
        }
    },

name: Dsconfig layout: true

Deployment

 antdup@w-v-kitslab-cc-0: json2tango someconfig.json 
+ Device: some/device/1
  Server: some-server/instance
  Class: SomeDeviceClass
  Properties:
    + otherProperty
      7
    + someImportantProperty
      foo
      bar
  Attribute properties:
    anAttribute
      + unit
        mV


Summary:
Add 1 servers.
Add 1 devices to 1 servers.
Add/change 2 device properties in 1 devices.
Add/change 2 device attribute properties in 1 devices.

name: Dsconfig layout: true

Renaming

- Device: some/device/1
  Server: some-server/instance
  Class: SomeDeviceClass

+ Device: some/device/2
  Server: some-server/instance
  Class: SomeDeviceClass
  Properties:
    + otherProperty
      7
    + someImportantProperty
      foo
      bar
  Attribute properties:
    anAttribute
      + unit
        mV


Summary:
Add 1 devices to 1 servers.
Delete 1 devices.
Add/change 2 device properties in 1 devices.
Add/change 2 device attribute properties in 1 devices.

name: Dsconfig layout: true

Editing

= Device: some/device/1
  Properties:
    + extraProperty
      89
    = otherProperty
      - 7
      + 8


Summary:
Add/change 2 device properties in 1 devices.

name: Getting to the Json layout: true

Magnet Configuration

The magnet properties are converted to the json file format by a script that needs a total of four input sources:

  1. A lattice file that contains all the magnets in the Linac, their type and length
  2. A magnet to power supply mapping file (xls)
  3. The xls sheet of calibration data
  4. A sheet of alarm interlock tags from the PLC

The result is Json configuration files for all the powersupply, magnet and circuit devices in the accelerator, as well as PyAlarm devices.

name: Getting to the Json layout: true

PLC-controlled Devices

For the devices that are controlled via PLC the situation is much simpler.

  1. The input source is a raw dump from the PLC program.
  • Tag names follow the MAXIV naming convention
  • The Json configuration is generated from jinja-templates
  • High Level Facade-devices based on PLC-tags

Thermocouple HLDevice:

ITango [4]: Thermocouple("r3-301m1/dia/tco-02").get_attribute_list()
Result [4]: 
['ByPassed',
'HighWarning',
'HighAlarm',
'LowWarning',
'Temperature',
'LowAlarm',
'State',
'Status ']

PLC tag format:

AI_R3_301M1_DIA_TCO02_U     #T Chamber thermocouple value
B_R3_301M1_DIA_TCO02_BYP_C  #T Bypass Alarm Signal commando
FB_R3_301M1_DIA_TCO02_AA    #T Thermocouple Chamber temperature alarm

"servers": {
  "Thermocouple/R3-301": {
    "Thermocouple": {
      "R3-301M1/DIA/TCO-02": {
        "properties": {
          "ByPassedAttribute": [
              "R3-301/VAC/PLC-01/B_R3_301M1_DIA_TCO02_BYP_C"],
          "Coefficient": ["0.1"],
          "HighAlarmAttribute": [
              "R3-301/VAC/PLC-01/FB_R3_301M1_DIA_TCO02_AA__HHInAlarm"],
          "HighWarningAttribute": [
              "R3-301/VAC/PLC-01/FB_R3_301M1_DIA_TCO02_AA__HInAlarm"],
          "LowAlarmAttribute": [
              "R3-301/VAC/PLC-01/FB_R3_301M1_DIA_TCO02_AA__LLInAlarm"],
          "LowWarningAttribute": [
              "R3-301/VAC/PLC-01/FB_R3_301M1_DIA_TCO02_AA__LInAlarm"],
          "TemperatureAttribute": [
              "R3-301/VAC/PLC-01/AI_R3_301M1_DIA_TCO02_U"]

PyAlarm devices generated

PyAlarm/R3-301-VAC": {
  "PyAlarm": {
    "R3-301/VAC/ALARM-01": {
      "properties": {
        "AlarmDescriptions": [
          "FB_R3_301M1_DIA_TCO02_AA__HHInAlarm:Thermocouple Chamber temperature alarm",
          "FB_R3_301M1_DIA_TCO02_AA__HInAlarm:Thermocouple Chamber temperature alarm",
          "FB_R3_301M1_DIA_TCO02_AA__LInAlarm:Thermocouple Chamber temperature alarm",
          "FB_R3_301M1_DIA_TCO02_AA__LLInAlarm:Thermocouple Chamber temperature alarm",
        ],
        "AlarmList": [
          "FB_R3_301M1_DIA_TCO02_AA__HHInAlarm:R3-301/VAC/PLC-01/FB_R3_301M1_DIA_TCO02_AA__HHInAlarm.quality == ATTR_VALID and R3-301/VAC/PLC-01/FB_R3_301M1_DIA_TCO02_AA__HHInAlarm",
          "FB_R3_301M1_DIA_TCO02_AA__HInAlarm:R3-301/VAC/PLC-01/FB_R3_301M1_DIA_TCO02_AA__HInAlarm.quality == ATTR_VALID and R3-301/VAC/PLC-01/FB_R3_301M1_DIA_TCO02_AA__HInAlarm",
          "FB_R3_301M1_DIA_TCO02_AA__LInAlarm:R3-301/VAC/PLC-01/FB_R3_301M1_DIA_TCO02_AA__LInAlarm.quality == ATTR_VALID and R3-301/VAC/PLC-01/FB_R3_301M1_DIA_TCO02_AA__LInAlarm",
          "FB_R3_301M1_DIA_TCO02_AA__LLInAlarm:R3-301/VAC/PLC-01/FB_R3_301M1_DIA_TCO02_AA__LLInAlarm.quality == ATTR_VALID and R3-301/VAC/PLC-01/FB_R3_301M1_DIA_TCO02_AA__LLInAlarm",
        ],

Cable DB

Equip. A                       |   Equip. B
R3-A111611-CAB02-VAC-IPCUA-01  |   R3-316L-VAC-IPFC-01

.center[ionpump]

User autonomy

  • Json file can be generated automatically from gitlab runner.
  • Source files are downloaded from Alfresco.
  • One config file is generated per tango devices.
  • Static error checking.
  • Json2tango display changes.
-rw-r--r-- 1 antdup antdup 896K Jun  1 11:34 config-eip.json
-rw-r--r-- 1 antdup antdup  35K Jun  1 11:34 config-fge.json
-rw-r--r-- 1 antdup antdup  943 Jun  1 11:34 config-frontend.json
-rw-r--r-- 1 antdup antdup  26K Jun  1 11:34 config-fsw.json
-rw-r--r-- 1 antdup antdup  13K Jun  1 11:34 config-ha.json
-rw-r--r-- 1 antdup antdup  769 Jun  1 11:34 config-hlplc.json
-rw-r--r-- 1 antdup antdup  27K Jun  1 11:34 config-ip.json
-rw-r--r-- 1 antdup antdup 766K Jun  1 11:34 config-pyalarm.json
-rw-r--r-- 1 antdup antdup 4.2K Jun  1 11:34 config-stepperdriver5p.json
-rw-r--r-- 1 antdup antdup 583K Jun  1 11:34 config-tco.json
-rw-r--r-- 1 antdup antdup  50K Jun  1 11:34 config-tse.json
-rw-r--r-- 1 antdup antdup  35K Jun  1 11:34 config-valve.json
-rw-r--r-- 1 antdup antdup  29K Jun  1 11:34 config-vgc.json

Error handling

Process config-fsw.json : 
 No missing tag 
========================================
Process config-ha.json : 
 Missing tag HeatAbsorber/B308A, HeatAbsorber, B308A-FE/VAC/HA-01, StatusOpenAttribute
 Missing tag HeatAbsorber/B308A, HeatAbsorber, B308A-FE/VAC/HA-01, StatusClosedAttribute
 Missing tag HeatAbsorber/B308A, HeatAbsorber, B308A-FE/VAC/HA-01, ErrorAttribute
 Missing tag HeatAbsorber/B308A, HeatAbsorber, B308A-FE/VAC/HA-01, CloseAttribute
 Missing tag HeatAbsorber/B308A, HeatAbsorber, B308A-FE/VAC/HA-01, OpenAttribute
 Missing tag HeatAbsorber/B308A, HeatAbsorber, B308A-FE/VAC/HA-01, ByPassedAttribute
 Missing tag HeatAbsorber/B303A, HeatAbsorber, B303A-FE/VAC/HA-01, StatusOpenAttribute
 Missing tag HeatAbsorber/B303A, HeatAbsorber, B303A-FE/VAC/HA-01, StatusClosedAttribute
 Missing tag HeatAbsorber/B303A, HeatAbsorber, B303A-FE/VAC/HA-01, ErrorAttribute
 Missing tag HeatAbsorber/B303A, HeatAbsorber, B303A-FE/VAC/HA-01, CloseAttribute
 Missing tag HeatAbsorber/B303A, HeatAbsorber, B303A-FE/VAC/HA-01, OpenAttribute
 Missing tag HeatAbsorber/B303A, HeatAbsorber, B303A-FE/VAC/HA-01, ByPassedAttribute

name: HDB++ configuration layout: true

HDB++ configuration

  • Keep configuration on git repository.

  • Configuration per Tango class

    • polling configuration
    • event filtering
    • event from the code

  • Easily display misconfiguration or missing attributes.

{
    "classes": {
        "DanfysikSysController": {
            "Current": 140,
            "Interlocked": 1000,
            "Resistance": 1000,
            "State": 140,
            "Voltage": 1000
        },

name: Sardana devices layout: true

Sardana Devices

  • Custom xls file from the Hardware group

    • Motor name
    • Motor type
    • Properties (motor step, encoder range, offset ... )

  • Generate the sardana environment

    • Sardana Pool
    • Element ID
    • Controller ID
    • Alias
    • ...

  • Easy diff between production and stored configuration.