Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 197 to 195 | ||||||||
{ pattern { H, N, CRATE, CH } { LMD, MUPIX:LV:P0:H1, 192.168.0.5, u0 } | ||||||||
Changed: | ||||||||
< < | { LMD, MUPIX:LV:P0:H1, 192.168.0.5, u1 } | |||||||
> > | { LMD, MUPIX:LV:P0:H2, 192.168.0.5, u1 } | |||||||
}
| ||||||||
Line: 210 to 208 | ||||||||
dbLoadTemplate ("/config/wienerpl_demo.sub" ) | ||||||||
Changed: | ||||||||
< < | iocInit() | |||||||
> > | iocInit() | |||||||
-- FlorianFeldbauer - 01 Jul 2022 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 17 to 17 | ||||||||
Imagesepics-ioc | ||||||||
Changed: | ||||||||
< < | The epics-ioc image provides a ready to use EPICS IOC with the following device support routines: | |||||||
> > | The epics-ioc image is based on a minimal Debian Bullseye image and contains the complete EPICS installation including the following device support modules: | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
aarch64 and arm/v7 | ||||||||
Line: 35 to 36 | ||||||||
docker run -dit -v <LOCAL_DIR>:/config --name <NAME_OF_CONTAINER> [OPTIONS] paluma.ruhr-uni-bochum.de/epics/ioc <IOC_STARTUP_SCRIPT>The epics-ioc image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the IOC startup script, and substitution files which is mounted at `/config` An IOC startup script looks like this | ||||||||
Deleted: | ||||||||
< < |
#!/epicsIoc | |||||||
Changed: | ||||||||
< < | epicsEnvSet( "STREAM_PROTOCOL_PATH", "/epics/protocols" ) dbLoadDatabase( "/epics/dbd/epicsIoc.dbd", 0, 0 ) | |||||||
> > |
#!/epics/ioc/bin/linux-<ARCH>/epicsIoc epicsEnvSet( "STREAM_PROTOCOL_PATH", "/epics/ioc/protocols/" ) ## Register all support components dbLoadDatabase( "/epics/ioc/dbd/epicsIoc.dbd", 0, 0 ) | |||||||
epics Ioc_registerRecordDeviceDriver( pdbbase ) ## Load device drivers | ||||||||
Line: 56 to 61 | ||||||||
and you should see the EPICS IOC command prompt. To detach from the container again use `CTRL+p CTRL+q` OPTIONS: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Line: 68 to 75 | ||||||||
Tags | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
ca-gatewayDocker Image providing the Channel Access gateway. | ||||||||
Line: 79 to 85 | ||||||||
UsageDefault run command (PC with two NICs required): | ||||||||
Changed: | ||||||||
< < |
docker run -d --network host -v <LOCAL_DIR>:/config paluma.ruhr-uni-bochum.de/epics/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist -access | |||||||
> > |
docker run -d --network host -v <LOCAL_DIR>:/config paluma.ruhr-uni-bochum.de/epics/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -pvlist <PVLIST_FILE> -access <ACCESS_FILE> | |||||||
The ca-gateway image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the gateway configuration (access file and pvlist) which is mounted at `/config` The CLIENT IP is the broadcast address of the network with the IOCs, the SERVER IP is the local IP address of the network to the supervisory layer.
Tags | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
phoebusThe phoebus image provides the Phoebus GUI toolchain, to create, edit and run OPIs. | ||||||||
Line: 100 to 105 | ||||||||
The phoebus image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the display files and custom configuration settings which is mounted at `/config` Tags | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
archive-engineThe archive-engine image provides the Phoebus RDB archiver. | ||||||||
Line: 117 to 120 | ||||||||
The CA address list must be configured manually in settings file (or use `--network host`).
Tags | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
sncseq base imageThis is a base image to create Docker images for sequencer programs and cannot be used directly. The Sequencer programs are collected at our PANDA Gitlab server | ||||||||
Line: 128 to 130 | ||||||||
Examples of using the epics-iocHameg HMP4040 LV Power Supply
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
{ pattern { CHAN, PORT } { 0, hmp_1 } | ||||||||
Line: 141 to 143 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
epicsIoc_registerRecordDeviceDriver( pdbbase ) ## Connect to R&S HMP4040 with HO732 via usb-serial interface | ||||||||
Changed: | ||||||||
< < | drvAsynSerialPortConfigure( "hmp_1", "/dev/ttyAMA0", 0, 0, 0 ) | |||||||
> > | drvAsynSerialPortConfigure( "hmp_1", "/dev/ttyS0", 0, 0, 0 ) | |||||||
asynSetOption( "hmp_1", 0, "baud", "9600" ) asynSetOption( "hmp_1", 0, "bits", "8" ) asynSetOption( "hmp_1", 0, "parity", "none" ) | ||||||||
Line: 163 to 168 | ||||||||
iocInit()
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
epicsIoc_registerRecordDeviceDriver( pdbbase ) ## Connect to R&S HMP4040 with HO732 via ethernet | ||||||||
Line: 180 to 188 | ||||||||
iocInit()
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Wiener PL5xx and Wiener MPOD LV power supplies (SNMP)
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
file "/databases/WienerPL500.db"{pattern { subsys, dev, sector, CRATE, CH }{ LMD, MUPIX, P0:H1:D3:S2, 192.168.0.5, u0 }{ LMD, MUPIX, P0:H1:D3:S2, 192.168.0.5, u1}}
| |||||||
> > |
| |||||||
epicsEnvSet( "WCR", "guru WIENER-CRATE-MIB::" ) | ||||||||
Deleted: | ||||||||
< < |
dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 )
pandaIoc_registerRecordDeviceDriver( pdbbase )## Load record instances
dbLoadTemplate ("/config/wiener_demo.sub" )iocInit()
%ENDCODE%
docker run -dit -v ${HOME}/wiener_demo:/config paluma.rub.de/panda-ioc ./wiener_demo.cmd | |||||||
Changed: | ||||||||
< < | -- PeterZumbruch - 12 Nov 2019 | |||||||
> > |
## Register all support components
dbLoadDatabase( "/epics/ioc/dbd/epicsIoc.dbd", 0, 0 )
epicsIoc_registerRecordDeviceDriver( pdbbase )
dbLoadTemplate ("/config/wienerpl_demo.sub" )
iocInit()
-- FlorianFeldbauer - 01 Jul 2022 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 34 to 34 | ||||||||
Default run command (standalone):
docker run -dit -v <LOCAL_DIR>:/config --name <NAME_OF_CONTAINER> [OPTIONS] paluma.ruhr-uni-bochum.de/epics/ioc <IOC_STARTUP_SCRIPT> | ||||||||
Changed: | ||||||||
< < |
Example:
docker run -dit -v /home/florian/epics-docker/test/ioc-config:/config --name hameg-demo --device /dev/ttyS0:/dev/ttyHameg paluma.ruhr-uni-bochum.de/epics/ioc /config/hameg_demo.cmdThe epics-ioc image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the IOC startup script, and substitution files which is mounted at `/config` An example IOC startup script looks like this | |||||||
> > |
The epics-ioc image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the IOC startup script, and substitution files which is mounted at `/config` An IOC startup script looks like this | |||||||
#!/epicsIoc epicsEnvSet( "STREAM_PROTOCOL_PATH", "/epics/protocols" ) | ||||||||
Line: 47 to 42 | ||||||||
epics Ioc_registerRecordDeviceDriver( pdbbase ) ## Load device drivers | ||||||||
Changed: | ||||||||
< < | drvAsynSerialPortConfigure( "hmp_1", "/dev/ttyHameg", 0, 0, 0 ) asynSetOption( "hmp_1", 0, "baud", "9600" ) asynSetOption( "hmp_1", 0, "bits", "8" ) asynSetOption( "hmp_1", 0, "parity", "none" ) asynSetOption( "hmp_1", 0, "stop", "1" ) asynSetOption( "hmp_1", 0, "clocal", "Y" ) asynSetOption( "hmp_1", 0, "crtscts", "N" ) asynSetOption( "hmp_1", 0, "ixon", "N" ) asynSetOption( "hmp_1", 0, "ixoff", "N" ) asynSetOption( "hmp_1", 0, "ixany", "N" ) | |||||||
> > | [...] | |||||||
## Load record instances | ||||||||
Changed: | ||||||||
< < | dbLoadTemplate( "/config/hameg_demo.sub" ) | |||||||
> > | [...] | |||||||
iocInit() | ||||||||
Line: 84 to 70 | ||||||||
Tags
| ||||||||
Changed: | ||||||||
< < | -- | |||||||
> > |
| |||||||
ca-gatewayDocker Image providing the Channel Access gateway. | ||||||||
Line: 99 to 85 | ||||||||
The CLIENT IP is the broadcast address of the network with the IOCs, the SERVER IP is the local IP address of the network to the supervisory layer.
Tags | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
phoebusThe phoebus image provides the Phoebus GUI toolchain, to create, edit and run OPIs.UsageDefault run command (standalone) | ||||||||
Changed: | ||||||||
< < |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v :/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings | |||||||
> > |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v <LOCAL_DIR>:/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.ruhr-uni-bochum.de/epics/phoebus -settings <CONFIG_FILE> | |||||||
On the host system a user with `UID=1000` has to exists with read/write access to the X server of the host system. | ||||||||
Changed: | ||||||||
< < |
The phoebus image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the display files and custom configuration settings which is mounted at `/home/panda-dcs/config` | |||||||
> > |
The phoebus image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the display files and custom configuration settings which is mounted at `/config` | |||||||
Tags | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
archive-engineThe archive-engine image provides the Phoebus RDB archiver.UsageDefault run command (standalone): | ||||||||
Deleted: | ||||||||
< < |
docker run -d -v :/home/panda-dcs/config -p 4812 paluma.rub.de/archive-engine -engine <ENGINE> -settings | |||||||
Changed: | ||||||||
< < |
The archive-engine image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing custom configuration settings and engine-configuration file(s) which is mounted at `/home/panda-dcs/config` | |||||||
> > |
docker run -d -v <LOCAL_DIR>:/config -p 4812 paluma.ruhr-uni-bochum.de/epics/archive-engine -engine <ENGINE> -settings <CONFIG_FILE>The archive-engine image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing custom configuration settings and engine-configuration file(s) which is mounted at `/config` | |||||||
Changed: | ||||||||
< < | When the container is started for the first time, any `*.xml` files present in `/home/panda-dcs/config` are imported as new engines into the archiver configuration (using `-replace_engine -steal_channels`). The basename of the xml-files is used as engine name. | |||||||
> > | When the container is started for the first time, any `*.xml` files present in `/config` are imported as new engines into the archiver configuration (using `-replace_engine -steal_channels`). The basename of the xml-files is used as engine name. | |||||||
The CA address list must be configured manually in settings file (or use `--network host`).
Tags | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
sncseq base imageThis is a base image to create Docker images for sequencer programs and cannot be used directly. The Sequencer programs are collected at our PANDA Gitlab server The image is available for amd64, aarch64 and arm/v7 | ||||||||
Changed: | ||||||||
< < |
Examples of using the panda-ioc | |||||||
> > |
Examples of using the epics-ioc | |||||||
Hameg HMP4040 LV Power Supply
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
{ pattern { CHAN, PORT } { 0, hmp_1 } { 1, hmp_1 } { 2, hmp_1 } { 3, hmp_1 } | ||||||||
Changed: | ||||||||
< < |
}
%ENDCODE%
| |||||||
> > |
}
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
## Connect to R&S HMP4040 with HO732 via usb-serial interface drvAsynSerialPortConfigure( "hmp_1", "/dev/ttyAMA0", 0, 0, 0 ) | ||||||||
Line: 181 to 161 | ||||||||
## Load record instances dbLoadTemplate ("/config/hameg_demo.sub" ) | ||||||||
Changed: | ||||||||
< < |
iocInit()
%ENDCODE%
| |||||||
> > |
iocInit()
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Changed: | ||||||||
< < | ## Connect to R&S HMP4040 with HO732 via usb-serial interface | |||||||
> > | ## Connect to R&S HMP4040 with HO732 via ethernet | |||||||
drvAsynIPPortConfigure( "hmp_1", "192.168.0.5:5025 TCP", 0, 0, 0 ) ## Load record instances dbLoadTemplate ("/config/hameg_demo.sub" ) | ||||||||
Changed: | ||||||||
< < |
iocInit()
%ENDCODE%
docker run -dit -v ${HOME}/hameg_demo:/config paluma.rub.de/panda-ioc ./hameg_demo.cmd | |||||||
> > |
iocInit()
| |||||||
Wiener PL5xx and Wiener MPOD LV power supplies (SNMP)
| ||||||||
Line: 217 to 191 | ||||||||
| ||||||||
Changed: | ||||||||
< < | file "/databases/WienerPL500.db" { pattern { subsys, dev, sector, CRATE, CH } { LMD, MUPIX, P0:H1:D3:S2, 192.168.0.5, u0 } { LMD, MUPIX, P0:H1:D3:S2, 192.168.0.5, u1 } } %ENDCODE% | |||||||
> > | file "/databases/WienerPL500.db"{pattern { subsys, dev, sector, CRATE, CH }{ LMD, MUPIX, P0:H1:D3:S2, 192.168.0.5, u0 }{ LMD, MUPIX, P0:H1:D3:S2, 192.168.0.5, u1}}%ENDCODE% | |||||||
| ||||||||
Changed: | ||||||||
< < | pandaIoc_registerRecordDeviceDriver( pdbbase ) ## Load record instances dbLoadTemplate ("/config/wiener_demo.sub" ) iocInit() | |||||||
> > | pandaIoc_registerRecordDeviceDriver( pdbbase )## Load record instances dbLoadTemplate ("/config/wiener_demo.sub" )iocInit() | |||||||
%ENDCODE%
docker run -dit -v ${HOME}/wiener_demo:/config paluma.rub.de/panda-ioc ./wiener_demo.cmd |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 10 to 10 | ||||||||
Docker Container | ||||||||
Changed: | ||||||||
< < |
The PANDA DCS Software will be distributed and maintained using Docker containers. All containers have been tested extensively under Debian 9 and 10. The gateway and IOC containers were also tested under Windows 10 (only connection to network devices!)
All docker images listed below can be downloaded and used with:
docker pull paluma.rub.de/<IMAGENAME> | |||||||
> > |
The PANDA DCS Software will be distributed and maintained using Docker containers. All containers have been tested extensively under Debian 9-11. The gateway and IOC containers were also tested under Windows 10 (only connection to network devices!) | |||||||
For a deeper look in the docker build process, you might have a look at the build repository https://panda-repo.gsi.de/f.feldbauer/epics-docker.
| ||||||||
Line: 32 to 27 | ||||||||
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
The image is available for amd64, aarch64 and arm/v7
UsageDefault run command (standalone): | ||||||||
Added: | ||||||||
> > |
docker run -dit -v <LOCAL_DIR>:/config --name <NAME_OF_CONTAINER> [OPTIONS] paluma.ruhr-uni-bochum.de/epics/ioc <IOC_STARTUP_SCRIPT> | |||||||
Changed: | ||||||||
< < |
docker run -dit -v :/config [OPTIONS] paluma.rub.de/epics-ioc ./ | |||||||
> > |
Example:
docker run -dit -v /home/florian/epics-docker/test/ioc-config:/config --name hameg-demo --device /dev/ttyS0:/dev/ttyHameg paluma.ruhr-uni-bochum.de/epics/ioc /config/hameg_demo.cmd | |||||||
Changed: | ||||||||
< < |
The panda-ioc image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the IOC startup script, and substitution files which is mounted at `/config` | |||||||
> > |
The epics-ioc image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the IOC startup script, and substitution files which is mounted at `/config` | |||||||
An example IOC startupscript looks like this | ||||||||
Changed: | ||||||||
< < | %CODE% #!/epicsIoc epicsEnvSet( "STREAM_PROTOCOL_PATH", "/protocols" ) dbLoadDatabase( "/dbd/epicsIoc.dbd", 0, 0 ) | |||||||
> > |
#!/epicsIoc epicsEnvSet( "STREAM_PROTOCOL_PATH", "/epics/protocols" ) dbLoadDatabase( "/epics/dbd/epicsIoc.dbd", 0, 0 ) | |||||||
epics Ioc_registerRecordDeviceDriver( pdbbase ) | ||||||||
Changed: | ||||||||
< < | ## Load device drivers and records at this point drvAsynIPPortConfigure( "huber", "192.168.0.5 TCP", 0, 0, 0 ) | |||||||
> > | ## Load device drivers drvAsynSerialPortConfigure( "hmp_1", "/dev/ttyHameg", 0, 0, 0 ) asynSetOption( "hmp_1", 0, "baud", "9600" ) asynSetOption( "hmp_1", 0, "bits", "8" ) asynSetOption( "hmp_1", 0, "parity", "none" ) asynSetOption( "hmp_1", 0, "stop", "1" ) asynSetOption( "hmp_1", 0, "clocal", "Y" ) asynSetOption( "hmp_1", 0, "crtscts", "N" ) asynSetOption( "hmp_1", 0, "ixon", "N" ) asynSetOption( "hmp_1", 0, "ixoff", "N" ) asynSetOption( "hmp_1", 0, "ixany", "N" ) | |||||||
## Load record instances | ||||||||
Changed: | ||||||||
< < | dbLoadRecords( "/database/Huber_Unistate_425.db", "subsys=LMD, sector=H1, PORT=huber" ) | |||||||
> > | dbLoadTemplate( "/config/hameg_demo.sub" ) iocInit() | |||||||
Changed: | ||||||||
< < | iocInit() %ENDCODE% | |||||||
> > | The preinstalled database files provided with this Docker image are located at `/epics/databases` within the container's filesystem. A list of all available database and protocol files can be found on the PANDA Gitlab server. | |||||||
Changed: | ||||||||
< < | The preinstalled database files provided with this Docker image are located at `/databases` within the container's filesystem. A list of all available database and protocol files can be found on the PANDA Gitlab server. | |||||||
> > |
To run commands within the IOC container use
docker attach <CONTAINER_ID/NAME> | |||||||
Changed: | ||||||||
< < |
To run commands within the IOC container use `docker attach <CONTAINER ID/NAME>` and you should see the EPICS IOC command prompt. To detach from the container again use `CTRL+p CTRL+q` | |||||||
> > |
and you should see the EPICS IOC command prompt. To detach from the container again use `CTRL+p CTRL+q` | |||||||
OPTIONS: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Tags | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
--
ca-gateway | ||||||||
Line: 87 to 93 | ||||||||
UsageDefault run command (PC with two NICs required): | ||||||||
Changed: | ||||||||
< < |
docker run -d --network host -v :/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist -access | |||||||
> > |
docker run -d --network host -v <LOCAL_DIR>:/config paluma.ruhr-uni-bochum.de/epics/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist -access | |||||||
The ca-gateway image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the gateway configuration (access file and pvlist) which is mounted at `/config` The CLIENT IP is the broadcast address of the network with the IOCs, the SERVER IP is the local IP address of the network to the supervisory layer.
Tags | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
--
phoebus |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 20 to 20 | ||||||||
For a deeper look in the docker build process, you might have a look at the build repository https://panda-repo.gsi.de/f.feldbauer/epics-docker.
Images | ||||||||
Changed: | ||||||||
< < |
panda-ioc | |||||||
> > |
epics-ioc | |||||||
Changed: | ||||||||
< < | The panda-ioc image provides a ready to use EPICS IOC with the following device support routines: | |||||||
> > | The epics-ioc image provides a ready to use EPICS IOC with the following device support routines: | |||||||
| ||||||||
Line: 31 to 31 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
Changed: | ||||||||
< < | The image is available for amd64 and arm/v7 | |||||||
> > |
The image is available for amd64, aarch64 and arm/v7 | |||||||
UsageDefault run command (standalone): | ||||||||
Changed: | ||||||||
< < |
docker run -dit -v :/config [OPTIONS] paluma.rub.de/panda-ioc ./ | |||||||
> > |
docker run -dit -v :/config [OPTIONS] paluma.rub.de/epics-ioc ./ | |||||||
The panda-ioc image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the IOC startup script, and substitution files which is mounted at `/config` An example IOC startupscript looks like this %CODE% | ||||||||
Changed: | ||||||||
< < | #!/pandaIoc | |||||||
> > | #!/epicsIoc | |||||||
epicsEnvSet( "STREAM_PROTOCOL_PATH", "/protocols" ) | ||||||||
Changed: | ||||||||
< < | dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 ) pandaIoc_registerRecordDeviceDriver( pdbbase ) | |||||||
> > | dbLoadDatabase( "/dbd/epicsIoc.dbd", 0, 0 ) epics Ioc_registerRecordDeviceDriver( pdbbase ) | |||||||
## Load device drivers and records at this point drvAsynIPPortConfigure( "huber", "192.168.0.5 TCP", 0, 0, 0 ) | ||||||||
Line: 74 to 76 | ||||||||
Tags | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
--
ca-gatewayDocker Image providing the Channel Access gateway. | ||||||||
Changed: | ||||||||
< < | The image is available for amd64 and arm/v7 | |||||||
> > | The image is available for amd64, aarch64 and arm/v7 | |||||||
UsageDefault run command (PC with two NICs required): | ||||||||
Line: 90 to 93 | ||||||||
The CLIENT IP is the broadcast address of the network with the IOCs, the SERVER IP is the local IP address of the network to the supervisory layer.
Tags | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
--
phoebus | ||||||||
Line: 104 to 107 | ||||||||
The phoebus image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the display files and custom configuration settings which is mounted at `/home/panda-dcs/config` Tags | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
--
archive-engine | ||||||||
Line: 120 to 123 | ||||||||
The CA address list must be configured manually in settings file (or use `--network host`).
Tags | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
--
sncseq base imageThis is a base image to create Docker images for sequencer programs and cannot be used directly. The Sequencer programs are collected at our PANDA Gitlab server | ||||||||
Changed: | ||||||||
< < | The image is available for amd64 and arm/v7 | |||||||
> > | The image is available for amd64, aarch64 and arm/v7 | |||||||
Examples of using the panda-iocHameg HMP4040 LV Power Supply | ||||||||
Line: 148 to 150 | ||||||||
{ 3, hmp_1 } } %ENDCODE% | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 177 to 177 | ||||||||
iocInit() %ENDCODE% | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 37 to 37 | ||||||||
Default run command (standalone): | ||||||||
Changed: | ||||||||
< < |
docker run -dit -v <PATH_ON_HOST>:/config [OPTIONS] paluma.rub.de/panda-ioc ./<YOUR_ST.CMD> | |||||||
> > |
docker run -dit -v :/config [OPTIONS] paluma.rub.de/panda-ioc ./ | |||||||
The panda-ioc image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the IOC startup script, and substitution files which is mounted at `/config` | ||||||||
Line: 62 to 62 | ||||||||
To run commands within the IOC container use `docker attach <CONTAINER ID/NAME>` and you should see the EPICS IOC command prompt. To detach from the container again use `CTRL+p CTRL+q` OPTIONS:
| ||||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Line: 85 to 84 | ||||||||
UsageDefault run command (PC with two NICs required): | ||||||||
Changed: | ||||||||
< < |
docker run -d --network host -v <PATH_ON_HOST>:/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PV_LIST> -access <ACCESS_FILE> | |||||||
> > |
docker run -d --network host -v :/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist -access | |||||||
The ca-gateway image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the gateway configuration (access file and pvlist) which is mounted at `/config` | ||||||||
Line: 99 to 98 | ||||||||
UsageDefault run command (standalone) | ||||||||
Changed: | ||||||||
< < |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v <PATH_ON_HOST>:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings <SETTINGS_FILE> | |||||||
> > |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v :/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings | |||||||
On the host system a user with `UID=1000` has to exists with read/write access to the X server of the host system. | ||||||||
Line: 113 to 112 | ||||||||
UsageDefault run command (standalone): | ||||||||
Changed: | ||||||||
< < |
docker run -d -v <PATH_ON_HOST>:/home/panda-dcs/config -p 4812 paluma.rub.de/archive-engine -engine <ENGINE> -settings <SETTINGS_FILE> | |||||||
> > |
docker run -d -v :/home/panda-dcs/config -p 4812 paluma.rub.de/archive-engine -engine <ENGINE> -settings | |||||||
The archive-engine image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing custom configuration settings and engine-configuration file(s) which is mounted at `/home/panda-dcs/config` | ||||||||
Line: 133 to 132 | ||||||||
Hameg HMP4040 LV Power Supply
| ||||||||
Changed: | ||||||||
< < |
mkdir ${HOME}/hameg_demo
| |||||||
> > |
| |||||||
inside this newly created directory with the following content to get access to all for channels of this device %CODE{"bash"}% file "/databases/hmp4040.db" | ||||||||
Line: 146 to 148 | ||||||||
{ 3, hmp_1 } } %ENDCODE% | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
%CODE{"bash"}% #!/pandaIoc epicsEnvSet( "STREAM_PROTOCOL_PATH", "/protocols" ) | ||||||||
Line: 175 to 177 | ||||||||
iocInit() %ENDCODE% | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
%CODE{"bash"}% #!/pandaIoc epicsEnvSet( "STREAM_PROTOCOL_PATH", "/protocols" ) | ||||||||
Line: 195 to 199 | ||||||||
dbLoadTemplate ("/config/hameg_demo.sub" ) iocInit() | ||||||||
Changed: | ||||||||
< < | %ENDCODE% | |||||||
> > | %ENDCODE% | |||||||
docker run -dit -v ${HOME}/hameg_demo:/config paluma.rub.de/panda-ioc ./hameg_demo.cmd | ||||||||
Deleted: | ||||||||
< < | ||||||||
Wiener PL5xx and Wiener MPOD LV power supplies (SNMP)
| ||||||||
Changed: | ||||||||
< < |
mkdir ${HOME}/wiener_demo | |||||||
> > |
| |||||||
| ||||||||
Line: 218 to 223 | ||||||||
{ LMD, MUPIX, P0:H1:D3:S2, 192.168.0.5, u1 } } %ENDCODE% | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
%CODE{"bash"}% #!/pandaIoc epicsEnvSet( "WCR", "guru WIENER-CRATE-MIB::" ) | ||||||||
Line: 230 to 235 | ||||||||
iocInit() %ENDCODE% | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
docker run -dit -v ${HOME}/wiener_demo:/config paluma.rub.de/panda-ioc ./wiener_demo.cmd |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 62 to 62 | ||||||||
To run commands within the IOC container use `docker attach <CONTAINER ID/NAME>` and you should see the EPICS IOC command prompt. To detach from the container again use `CTRL+p CTRL+q` OPTIONS:
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Line: 231 to 233 | ||||||||
docker run -dit -v ${HOME}/wiener_demo:/config paluma.rub.de/panda-ioc ./wiener_demo.cmd | ||||||||
Changed: | ||||||||
< < | -- PeterZumbruch - 17 Oct 2019 | |||||||
> > | -- PeterZumbruch - 12 Nov 2019 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 37 to 37 | ||||||||
Default run command (standalone): | ||||||||
Changed: | ||||||||
< < |
docker run -dit -v <PATH_ON_HOST>:/config [OPTIONS] paluma.rub.de/panda-ioc ./<YOUR_ST.CMD> | |||||||
> > |
docker run -dit -v <PATH_ON_HOST>:/config [OPTIONS] paluma.rub.de/panda-ioc ./<YOUR_ST.CMD> | |||||||
The panda-ioc image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the IOC startup script, and substitution files which is mounted at `/config` | ||||||||
Line: 83 to 83 | ||||||||
UsageDefault run command (PC with two NICs required): | ||||||||
Changed: | ||||||||
< < |
docker run -d --network host -v <PATH_ON_HOST>:/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PV_LIST> -access <ACCESS_FILE> | |||||||
> > |
docker run -d --network host -v <PATH_ON_HOST>:/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PV_LIST> -access <ACCESS_FILE> | |||||||
The ca-gateway image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the gateway configuration (access file and pvlist) which is mounted at `/config` | ||||||||
Line: 97 to 97 | ||||||||
UsageDefault run command (standalone) | ||||||||
Changed: | ||||||||
< < |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v <PATH_ON_HOST>:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings <SETTINGS_FILE> | |||||||
> > |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v <PATH_ON_HOST>:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings <SETTINGS_FILE> | |||||||
On the host system a user with `UID=1000` has to exists with read/write access to the X server of the host system. | ||||||||
Line: 111 to 111 | ||||||||
UsageDefault run command (standalone): | ||||||||
Changed: | ||||||||
< < |
docker run -d -v <PATH_ON_HOST>:/home/panda-dcs/config -p 4812 paluma.rub.de/archive-engine -engine <ENGINE> -settings <SETTINGS_FILE> | |||||||
> > |
docker run -d -v <PATH_ON_HOST>:/home/panda-dcs/config -p 4812 paluma.rub.de/archive-engine -engine <ENGINE> -settings <SETTINGS_FILE> | |||||||
The archive-engine image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing custom configuration settings and engine-configuration file(s) which is mounted at `/home/panda-dcs/config` | ||||||||
Line: 230 to 230 | ||||||||
%ENDCODE%
docker run -dit -v ${HOME}/wiener_demo:/config paluma.rub.de/panda-ioc ./wiener_demo.cmd | ||||||||
Deleted: | ||||||||
< < | ||||||||
-- PeterZumbruch - 17 Oct 2019 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 175 to 175 | ||||||||
%ENDCODE%
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | %CODE% | |||||||
> > | %CODE{"bash"}% | |||||||
#!/pandaIoc epicsEnvSet( "STREAM_PROTOCOL_PATH", "/protocols" ) dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 ) | ||||||||
Line: 193 to 193 | ||||||||
dbLoadTemplate ("/config/hameg_demo.sub" ) iocInit() | ||||||||
Changed: | ||||||||
< < | %ENDCODE% | |||||||
> > | %ENDCODE% | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
docker run -dit -v ${HOME}/hameg_demo:/config paluma.rub.de/panda-ioc ./hameg_demo.cmd | ||||||||
Added: | ||||||||
> > |
| |||||||
Wiener PL5xx and Wiener MPOD LV power supplies (SNMP)
| ||||||||
Changed: | ||||||||
< < |
mkdir ${HOME}/wiener_demo | |||||||
> > |
mkdir ${HOME}/wiener_demo | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
%CODE% file "/databases/WienerPL500.db" { | ||||||||
Line: 214 to 217 | ||||||||
}
%ENDCODE%
| ||||||||
Changed: | ||||||||
< < | %CODE% | |||||||
> > | %CODE{"bash"}% | |||||||
#!/pandaIoc epicsEnvSet( "WCR", "guru WIENER-CRATE-MIB::" ) dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 ) | ||||||||
Line: 229 to 232 | ||||||||
docker run -dit -v ${HOME}/wiener_demo:/config paluma.rub.de/panda-ioc ./wiener_demo.cmd | ||||||||
Changed: | ||||||||
< < | -- FlorianFeldbauer - 21 Aug 2019 | |||||||
> > | -- PeterZumbruch - 17 Oct 2019 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 16 to 16 | ||||||||
docker pull paluma.rub.de/<IMAGENAME> | ||||||||
Added: | ||||||||
> > | For a deeper look in the docker build process, you might have a look at the build repository https://panda-repo.gsi.de/f.feldbauer/epics-docker. | |||||||
Imagespanda-ioc | ||||||||
Line: 72 to 74 | ||||||||
Tags
| ||||||||
Added: | ||||||||
> > | -- | |||||||
ca-gatewayDocker Image providing the Channel Access gateway. | ||||||||
Line: 87 to 90 | ||||||||
The CLIENT IP is the broadcast address of the network with the IOCs, the SERVER IP is the local IP address of the network to the supervisory layer.
Tags
| ||||||||
Added: | ||||||||
> > | -- | |||||||
phoebusThe phoebus image provides the Phoebus GUI toolchain, to create, edit and run OPIs. | ||||||||
Line: 100 to 104 | ||||||||
The phoebus image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the display files and custom configuration settings which is mounted at `/home/panda-dcs/config` Tags
| ||||||||
Added: | ||||||||
> > | -- | |||||||
archive-engineThe archive-engine image provides the Phoebus RDB archiver. | ||||||||
Line: 115 to 120 | ||||||||
The CA address list must be configured manually in settings file (or use `--network host`).
Tags
| ||||||||
Added: | ||||||||
> > | -- | |||||||
sncseq base imageThis is a base image to create Docker images for sequencer programs and cannot be used directly. The Sequencer programs are collected at our PANDA Gitlab server | ||||||||
Line: 124 to 130 | ||||||||
Examples of using the panda-iocHameg HMP4040 LV Power Supply
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
mkdir ${HOME}/hameg_demo
| |||||||
file "/databases/hmp4040.db" { pattern { CHAN, PORT } | ||||||||
Line: 137 to 144 | ||||||||
{ 3, hmp_1 } } %ENDCODE% | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | %CODE% | |||||||
> > | %CODE{"bash"}% | |||||||
#!/pandaIoc epicsEnvSet( "STREAM_PROTOCOL_PATH", "/protocols" ) dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 ) | ||||||||
Line: 164 to 173 | ||||||||
iocInit() %ENDCODE% | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 219 to 227 | ||||||||
%ENDCODE%
| ||||||||
Added: | ||||||||
> > | ||||||||
-- FlorianFeldbauer - 21 Aug 2019 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 35 to 35 | ||||||||
Default run command (standalone): | ||||||||
Changed: | ||||||||
< < |
docker run -dit -v :/config [OPTIONS] paluma.rub.de/panda-ioc ./ | |||||||
> > |
docker run -dit -v <PATH_ON_HOST>:/config [OPTIONS] paluma.rub.de/panda-ioc ./<YOUR_ST.CMD> | |||||||
The panda-ioc image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the IOC startup script, and substitution files which is mounted at `/config` | ||||||||
Line: 80 to 80 | ||||||||
UsageDefault run command (PC with two NICs required): | ||||||||
Changed: | ||||||||
< < |
docker run -d --network host -v :/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist -access | |||||||
> > |
docker run -d --network host -v <PATH_ON_HOST>:/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PV_LIST> -access <ACCESS_FILE> | |||||||
The ca-gateway image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the gateway configuration (access file and pvlist) which is mounted at `/config` | ||||||||
Line: 93 to 93 | ||||||||
UsageDefault run command (standalone) | ||||||||
Changed: | ||||||||
< < |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v :/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings | |||||||
> > |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v <PATH_ON_HOST>:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings <SETTINGS_FILE> | |||||||
On the host system a user with `UID=1000` has to exists with read/write access to the X server of the host system. | ||||||||
Line: 106 to 106 | ||||||||
UsageDefault run command (standalone): | ||||||||
Changed: | ||||||||
< < |
docker run -d -v :/home/panda-dcs/config -p 4812 paluma.rub.de/archive-engine -engine <ENGINE> -settings | |||||||
> > |
docker run -d -v <PATH_ON_HOST>:/home/panda-dcs/config -p 4812 paluma.rub.de/archive-engine -engine <ENGINE> -settings <SETTINGS_FILE> | |||||||
The archive-engine image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing custom configuration settings and engine-configuration file(s) which is mounted at `/home/panda-dcs/config` | ||||||||
Line: 164 to 164 | ||||||||
iocInit() %ENDCODE% | ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Line: 184 to 186 | ||||||||
iocInit() %ENDCODE% | ||||||||
Added: | ||||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCSUsefull links: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
Docker ContainerThe PANDA DCS Software will be distributed and maintained using Docker containers. All containers have been tested extensively under Debian 9 and 10. The gateway and IOC containers were also tested under Windows 10 (only connection to network devices!) | ||||||||
Deleted: | ||||||||
< < | When installing Docker CE for Windows 10, chose "Linux Containers" when aksed which kind of containers you want to use on your system. | |||||||
All docker images listed below can be downloaded and used with: | ||||||||
Changed: | ||||||||
< < |
docker pull paluma.rub.de/<IMAGENAME>You can also download a specific version by appending `:<TAG>` to the above command, but it is recommended to use `:latest` (default) | |||||||
> > |
docker pull paluma.rub.de/<IMAGENAME> | |||||||
Changed: | ||||||||
< < | All images are rebuild and reuploaded to the registry server every Saturday night. | |||||||
> > | You can also download a specific version by appending `:<TAG>` to the above command, but it is recommended to use `:latest` (default) | |||||||
Imagespanda-ioc | ||||||||
Line: 38 to 34 | ||||||||
UsageDefault run command (standalone): | ||||||||
Deleted: | ||||||||
< < |
docker run -dit -v <PATH_ON_YOUR_HOST>:/config [OPTIONS] paluma.rub.de/panda-ioc ./<YOUR_ST.CMD> | |||||||
Changed: | ||||||||
< < |
The panda-ioc image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the IOC startup script, and substitution files which is mounted at `/config` | |||||||
> > |
docker run -dit -v :/config [OPTIONS] paluma.rub.de/panda-ioc ./ You need a directory on your host containing the IOC startup script, and substitution files which is mounted at `/config` | |||||||
An example IOC startupscript looks like this | ||||||||
Changed: | ||||||||
< < |
#!/pandaIoc | |||||||
> > | %CODE% #!/pandaIoc | |||||||
epicsEnvSet( "STREAM_PROTOCOL_PATH", "/protocols" ) dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 ) pandaIoc_registerRecordDeviceDriver( pdbbase ) ## Load device drivers and records at this point | ||||||||
Added: | ||||||||
> > | drvAsynIPPortConfigure( "huber", "192.168.0.5 TCP", 0, 0, 0 ) | |||||||
## Load record instances | ||||||||
Changed: | ||||||||
< < | dbLoadRecords( "/config/dbExample2.db", "user=Test, no=1, scan='1 second'" ) | |||||||
> > | dbLoadRecords( "/database/Huber_Unistate_425.db", "subsys=LMD, sector=H1, PORT=huber" ) | |||||||
Changed: | ||||||||
< < | iocInit() | |||||||
> > | iocInit() %ENDCODE% | |||||||
The preinstalled database files provided with this Docker image are located at `/databases` within the container's filesystem. A list of all available database and protocol files can be found on the PANDA Gitlab server. | ||||||||
Added: | ||||||||
> > |
To run commands within the IOC container use `docker attach <CONTAINER ID/NAME>` and you should see the EPICS IOC command prompt. To detach from the container again use `CTRL+p CTRL+q` | |||||||
OPTIONS:
| ||||||||
Line: 68 to 70 | ||||||||
| ||||||||
Deleted: | ||||||||
< < |
To run commands within the IOC container use `docker attach <CONTAINER ID/NAME>` and you should see the EPICS IOC command prompt. To detach from the container again use `CTRL+p CTRL+q` | |||||||
Tags
ca-gateway | ||||||||
Line: 79 to 80 | ||||||||
UsageDefault run command (PC with two NICs required): | ||||||||
Changed: | ||||||||
< < |
docker run -d --network host -v <PATH_ON_HOST>:/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PVLIST_FILE> -access <ACCESS_FILE> | |||||||
> > |
docker run -d --network host -v :/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist -access | |||||||
The ca-gateway image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the gateway configuration (access file and pvlist) which is mounted at `/config` | ||||||||
Line: 92 to 93 | ||||||||
UsageDefault run command (standalone) | ||||||||
Changed: | ||||||||
< < |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v <PATH_ON_HOST>:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings <SETTINGS_FILE> | |||||||
> > |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v :/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings | |||||||
On the host system a user with `UID=1000` has to exists with read/write access to the X server of the host system. | ||||||||
Line: 105 to 106 | ||||||||
UsageDefault run command (standalone): | ||||||||
Changed: | ||||||||
< < |
docker run -d -v <PATH_ON_HOST>:/home/panda-dcs/config -p 4812 paluma.rub.de/archive-engine -engine <ENGINE> -settings <SETTINGS_FILE> | |||||||
> > |
docker run -d -v :/home/panda-dcs/config -p 4812 paluma.rub.de/archive-engine -engine <ENGINE> -settings | |||||||
The archive-engine image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing custom configuration settings and engine-configuration file(s) which is mounted at `/home/panda-dcs/config` | ||||||||
Line: 122 to 123 | ||||||||
Examples of using the panda-iocHameg HMP4040 LV Power Supply | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
{ pattern { CHAN, PORT } { 0, hmp_1 } { 1, hmp_1 } { 2, hmp_1 } { 3, hmp_1 } | ||||||||
Changed: | ||||||||
< < | } | |||||||
> > | } %ENDCODE% | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
epicsEnvSet( "STREAM_PROTOCOL_PATH", "/protocols" ) dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 ) pandaIoc_registerRecordDeviceDriver( pdbbase ) | ||||||||
Line: 155 to 162 | ||||||||
## Load record instances dbLoadTemplate ("/config/hameg_demo.sub" ) | ||||||||
Changed: | ||||||||
< < | iocInit() | |||||||
> > | iocInit() %ENDCODE% | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
epicsEnvSet( "STREAM_PROTOCOL_PATH", "/protocols" ) dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 ) pandaIoc_registerRecordDeviceDriver( pdbbase ) | ||||||||
Line: 171 to 182 | ||||||||
## Load record instances dbLoadTemplate ("/config/hameg_demo.sub" ) | ||||||||
Changed: | ||||||||
< < | iocInit() | |||||||
> > | iocInit() %ENDCODE% | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Wiener PL5xx and Wiener MPOD LV power supplies (SNMP) | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
epicsEnvSet( "WCR", "guru WIENER-CRATE-MIB::" ) dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 ) pandaIoc_registerRecordDeviceDriver( pdbbase ) | ||||||||
Line: 187 to 211 | ||||||||
## Load record instances dbLoadTemplate ("/config/wiener_demo.sub" ) | ||||||||
Changed: | ||||||||
< < |
iocInit()
| |||||||
> > |
iocInit()
%ENDCODE%
| |||||||
-- FlorianFeldbauer - 21 Aug 2019 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 15 to 15 | ||||||||
When installing Docker CE for Windows 10, chose "Linux Containers" when aksed which kind of containers you want to use on your system. All docker images listed below can be downloaded and used with: | ||||||||
Deleted: | ||||||||
< < | ||||||||
docker pull paluma.rub.de/<IMAGENAME> | ||||||||
Changed: | ||||||||
< < | You can also download a specific version by appending `:<TAG>` to the above command, but it is recommended to use `latest` (default) | |||||||
> > | You can also download a specific version by appending `:<TAG>` to the above command, but it is recommended to use `:latest` (default) All images are rebuild and reuploaded to the registry server every Saturday night. | |||||||
| ||||||||
Changed: | ||||||||
< < |
Usage | |||||||
> > |
Images | |||||||
panda-ioc | ||||||||
Added: | ||||||||
> > |
The panda-ioc image provides a ready to use EPICS IOC with the following device support routines:
Usage | |||||||
Default run command (standalone): | ||||||||
Added: | ||||||||
> > |
docker run -dit -v <PATH_ON_YOUR_HOST>:/config [OPTIONS] paluma.rub.de/panda-ioc ./<YOUR_ST.CMD> | |||||||
Changed: | ||||||||
< < |
docker run -dit [VOLUMES] [OPTIONS] paluma.rub.de/panda-ioc ./[ST.CMD] Volumes: | |||||||
> > |
The panda-ioc image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the IOC startup script, and substitution files which is mounted at `/config` An example IOC startupscript looks like this #!/pandaIoc epicsEnvSet( "STREAM_PROTOCOL_PATH", "/protocols" ) dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 ) pandaIoc_registerRecordDeviceDriver( pdbbase ) ## Load device drivers and records at this point ## Load record instances dbLoadRecords( "/config/dbExample2.db", "user=Test, no=1, scan='1 second'" ) | |||||||
Changed: | ||||||||
< < |
The panda-ioc image offers three mountable Volumes
OPTIONS can be: | |||||||
> > |
iocInit()
The preinstalled database files provided with this Docker image are located at `/databases` within the container's filesystem. A list of all available database and protocol files can be found on the PANDA Gitlab server.
OPTIONS: | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
To run commands within the IOC container use `docker attach <CONTAINER ID/NAME>` and you should see the EPICS IOC command prompt. To detach from the container again use `CTRL+p CTRL+q | |||||||
> > |
To run commands within the IOC container use `docker attach <CONTAINER ID/NAME>` and you should see the EPICS IOC command prompt. To detach from the container again use `CTRL+p CTRL+q` Tags
| |||||||
ca-gateway | ||||||||
Added: | ||||||||
> > |
Docker Image providing the Channel Access gateway.
The image is available for amd64 and arm/v7
Usage | |||||||
Default run command (PC with two NICs required): | ||||||||
Added: | ||||||||
> > |
docker run -d --network host -v <PATH_ON_HOST>:/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PVLIST_FILE> -access <ACCESS_FILE> | |||||||
Changed: | ||||||||
< < |
docker run -d --network host -v <PATH_ON_HOST>:/home/panda-dcs/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PVLIST_FILE> -access <ACCESS_FILE> | |||||||
> > |
The ca-gateway image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the gateway configuration (access file and pvlist) which is mounted at `/config` | |||||||
Changed: | ||||||||
< < |
The directory `/home/panda-dcs/config` must contain the configuration files for the gateway, i.e. PVLIST_FILE and ACCESS_FILE.
Phoebus | |||||||
> > |
The CLIENT IP is the broadcast address of the network with the IOCs, the SERVER IP is the local IP address of the network to the supervisory layer.
Tags
phoebus | |||||||
Changed: | ||||||||
< < | Default run command (standalone) | |||||||
> > |
The phoebus image provides the Phoebus GUI toolchain, to create, edit and run OPIs.
Usage | |||||||
Changed: | ||||||||
< < |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v ${PWD}/phoebus-config:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings <SETTINGS_FILE> | |||||||
> > |
Default run command (standalone)
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v <PATH_ON_HOST>:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings <SETTINGS_FILE> | |||||||
On the host system a user with `UID=1000` has to exists with read/write access to the X server of the host system. | ||||||||
Changed: | ||||||||
< < |
The directory `/home/panda-dcs/config` contains configuration files and bob files (display-files)
Archive-Engine | |||||||
> > |
The phoebus image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing the display files and custom configuration settings which is mounted at `/home/panda-dcs/config` Tags
archive-engineThe archive-engine image provides the Phoebus RDB archiver.Usage | |||||||
Default run command (standalone): | ||||||||
Added: | ||||||||
> > |
docker run -d -v <PATH_ON_HOST>:/home/panda-dcs/config -p 4812 paluma.rub.de/archive-engine -engine <ENGINE> -settings <SETTINGS_FILE> | |||||||
Changed: | ||||||||
< < |
docker run -d -v ${PWD}/phoebus-config:/home/panda-dcs/config -p 4812:4812 paluma.rub.de/archive-engine -engine Test -settings <SETTINGS_FILE> | |||||||
> > |
The archive-engine image works with Volumes. With volumes you can mount a local directory from your host system into the Docker container (see `-v` option). You need a directory on your host containing custom configuration settings and engine-configuration file(s) which is mounted at `/home/panda-dcs/config` | |||||||
Changed: | ||||||||
< < |
If there are any `*.xml` files present in the `/home/panda-dcs/config` directory at the first start of the container, the archive engine will import them as new engines (using `-replace_engine -steal_channels`). The basename of the xml-files is used as engine name. CA address list must be configured manually in settings file (or use `--network host`). | |||||||
> > |
When the container is started for the first time, any `*.xml` files present in `/home/panda-dcs/config` are imported as new engines into the archiver configuration (using `-replace_engine -steal_channels`). The basename of the xml-files is used as engine name.
The CA address list must be configured manually in settings file (or use `--network host`).
Tags
sncseq base imageThis is a base image to create Docker images for sequencer programs and cannot be used directly. The Sequencer programs are collected at our PANDA Gitlab server The image is available for amd64 and arm/v7 | |||||||
| ||||||||
Changed: | ||||||||
< < |
Examples | |||||||
> > |
Examples of using the panda-ioc | |||||||
Hameg HMP4040 LV Power Supply
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
{ pattern { CHAN, PORT } { 0, hmp_1 } | ||||||||
Line: 84 to 134 | ||||||||
}
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
pandaIoc_registerRecordDeviceDriver( pdbbase ) | ||||||||
Deleted: | ||||||||
< < | ## Load drivers | |||||||
## Connect to R&S HMP4040 with HO732 via usb-serial interface drvAsynSerialPortConfigure( "hmp_1", "/dev/ttyAMA0", 0, 0, 0 ) asynSetOption( "hmp_1", 0, "baud", "9600" ) | ||||||||
Line: 109 to 153 | ||||||||
asynSetOption( "hmp_1", 0, "ixany", "N" ) ## Load record instances | ||||||||
Changed: | ||||||||
< < | dbLoadTemplate ("/home/panda-dcs/config/hameg_demo.sub" ) | |||||||
> > | dbLoadTemplate ("/config/hameg_demo.sub" ) | |||||||
iocInit() | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
pandaIoc_registerRecordDeviceDriver( pdbbase ) | ||||||||
Deleted: | ||||||||
< < | ## Load drivers | |||||||
## Connect to R&S HMP4040 with HO732 via usb-serial interface drvAsynIPPortConfigure( "hmp_1", "192.168.0.5:5025 TCP", 0, 0, 0 ) ## Load record instances | ||||||||
Changed: | ||||||||
< < | dbLoadTemplate ("/home/panda-dcs/config/hameg_demo.sub" ) | |||||||
> > | dbLoadTemplate ("/config/hameg_demo.sub" ) | |||||||
iocInit() | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Wiener PL5xx and Wiener MPOD LV power supplies (SNMP)
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
epicsEnvSet( "WCR", "guru WIENER-CRATE-MIB::" ) | ||||||||
Changed: | ||||||||
< < | ## Register all support components dbLoadDatabase( "$(TOP)/dbd/pandaIoc.dbd", 0, 0 ) | |||||||
> > | dbLoadDatabase( "/dbd/pandaIoc.dbd", 0, 0 ) | |||||||
pandaIoc_registerRecordDeviceDriver( pdbbase ) ## Load record instances | ||||||||
Changed: | ||||||||
< < | dbLoadTemplate ("/home/panda-dcs/config/wiener_demo.sub" ) | |||||||
> > | dbLoadTemplate ("/config/wiener_demo.sub" ) | |||||||
iocInit() | ||||||||
Changed: | ||||||||
< < |
List of Images and Tagsepics-baseThis image is only needed if you want do create your own IOC Docker image. It is just a base image for the panda-ioc and ca-gateway images.
panda-iocImage with ready-to-use EPICS IOC. Includes asyn, stream, autosave, calc, modbus and snmp device support modules
ca-gatewayImage with ready to use CA-Gateway
PhoebusImage with the main Phoebus product
Archive-EngineImage with the archive-engine from Phoebus
| |||||||
> > |
| |||||||
-- FlorianFeldbauer - 21 Aug 2019 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 7 to 7 | ||||||||
Added: | ||||||||
> > | ||||||||
Docker ContainerThe PANDA DCS Software will be distributed and maintained using Docker containers. All containers have been tested extensively under Debian 9 and 10. The gateway and IOC containers were also tested under Windows 10 (only connection to network devices!) | ||||||||
Line: 22 to 24 | ||||||||
panda-iocDefault run command (standalone): | ||||||||
Deleted: | ||||||||
< < |
docker run -dit -v ${PWD}/ioc-config:/home/panda-dcs/config [OPTIONS] paluma.rub.de/panda-ioc ./[ST.CMD] | |||||||
Changed: | ||||||||
< < | The panda-ioc image offers three mountable volumes: | |||||||
> > |
docker run -dit [VOLUMES] [OPTIONS] paluma.rub.de/panda-ioc ./[ST.CMD] Volumes:The panda-ioc image offers three mountable Volumes | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
OPTIONS can be:
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
To detach from the container again use `CTRL+p CTRL+q | |||||||
> > |
To detach from the container again use `CTRL+p CTRL+q | |||||||
ca-gatewayDefault run command (PC with two NICs required): | ||||||||
Deleted: | ||||||||
< < |
docker run -d --network host -v ${PWD}/ioc-config:/home/panda-dcs/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PVLIST_FILE> -access <ACCESS_FILE> | |||||||
Changed: | ||||||||
< < | The directory `/home/panda-dcs/config` contains the configuration files for the gateway, i.e. PVLIST_FILE and ACCESS_FILE | |||||||
> > |
docker run -d --network host -v <PATH_ON_HOST>:/home/panda-dcs/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PVLIST_FILE> -access <ACCESS_FILE>The directory `/home/panda-dcs/config` must contain the configuration files for the gateway, i.e. PVLIST_FILE and ACCESS_FILE. | |||||||
PhoebusDefault run command (standalone) |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCSUsefull links: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Docker Container | ||||||||
Changed: | ||||||||
< < | The PANDA DCS Software will be distributed and maintained using Docker containers. All containers have been tested extensively under Debian 9 and 10. The gateway and IOC containers were also tested under Windows 10. | |||||||
> > | The PANDA DCS Software will be distributed and maintained using Docker containers. All containers have been tested extensively under Debian 9 and 10. The gateway and IOC containers were also tested under Windows 10 (only connection to network devices!) | |||||||
When installing Docker CE for Windows 10, chose "Linux Containers" when aksed which kind of containers you want to use on your system. All docker images listed below can be downloaded and used with: | ||||||||
Changed: | ||||||||
< < |
docker pull paluma.rub.de/<IMAGENAME>:<TAG> | |||||||
> > |
docker pull paluma.rub.de/<IMAGENAME> | |||||||
Changed: | ||||||||
< < | It is recommended to always use tag `latest`. | |||||||
> > | You can also download a specific version by appending `:<TAG>` to the above command, but it is recommended to use `latest` (default) | |||||||
| ||||||||
Changed: | ||||||||
< < |
List of Images and Tagsepics-baseBase image for panda-ioc and ca-gateway images.
panda-iocImage with ready-to-use EPICS IOC. Includes asyn, stream, autosave, calc, modbus and snmp device support modules
ca-gatewayImage with ready to use CA-Gateway
PhoebusImage with the main Phoebus product
Archive-EngineImage with the archive-engine from Phoebus
Usagepanda-ioc | |||||||
> > |
Usagepanda-ioc | |||||||
Default run command (standalone): | ||||||||
Line: 56 to 28 | ||||||||
The panda-ioc image offers three mountable volumes:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 71 to 43 | ||||||||
To detach from the container again use `CTRL+p CTRL+q | ||||||||
Changed: | ||||||||
< < |
ca-gateway | |||||||
> > |
ca-gateway | |||||||
Default run command (PC with two NICs required):
docker run -d --network host -v ${PWD}/ioc-config:/home/panda-dcs/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PVLIST_FILE> -access <ACCESS_FILE>The directory `/home/panda-dcs/config` contains the configuration files for the gateway, i.e. PVLIST_FILE and ACCESS_FILE | ||||||||
Changed: | ||||||||
< < |
Phoebus | |||||||
> > |
Phoebus | |||||||
Default run command (standalone) | ||||||||
Line: 87 to 59 | ||||||||
On the host system a user with `UID=1000` has to exists with read/write access to the X server of the host system. The directory `/home/panda-dcs/config` contains configuration files and bob files (display-files) | ||||||||
Changed: | ||||||||
< < |
Archive-Engine | |||||||
> > |
Archive-Engine | |||||||
Default run command (standalone): | ||||||||
Line: 180 to 152 | ||||||||
dbLoadTemplate ("/home/panda-dcs/config/wiener_demo.sub" ) iocInit() | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
List of Images and Tagsepics-baseThis image is only needed if you want do create your own IOC Docker image. It is just a base image for the panda-ioc and ca-gateway images.
panda-iocImage with ready-to-use EPICS IOC. Includes asyn, stream, autosave, calc, modbus and snmp device support modules
ca-gatewayImage with ready to use CA-Gateway
PhoebusImage with the main Phoebus product
Archive-EngineImage with the archive-engine from Phoebus
| |||||||
-- FlorianFeldbauer - 21 Aug 2019 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 161 to 161 | ||||||||
iocInit()
| ||||||||
Added: | ||||||||
> > |
Wiener PL5xx and Wiener MPOD LV power supplies (SNMP)
| |||||||
Added: | ||||||||
> > |
## Register all support components
dbLoadDatabase( "$(TOP)/dbd/pandaIoc.dbd", 0, 0 )
pandaIoc_registerRecordDeviceDriver( pdbbase )
## Load record instances
dbLoadTemplate ("/home/panda-dcs/config/wiener_demo.sub" )
iocInit()
| |||||||
-- FlorianFeldbauer - 21 Aug 2019 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 94 to 94 | ||||||||
docker run -d -v ${PWD}/phoebus-config:/home/panda-dcs/config -p 4812:4812 paluma.rub.de/archive-engine -engine Test -settings <SETTINGS_FILE>If there are any `*.xml` files present in the `/home/panda-dcs/config` directory at the first start of the container, the archive engine will import them as new engines (using `-replace_engine -steal_channels`). The basename of the xml-files is used as engine name. CA address list must be configured manually in settings file (or use `--network host`). | ||||||||
Added: | ||||||||
> > |
ExamplesHameg HMP4040 LV Power Supply
| |||||||
-- FlorianFeldbauer - 21 Aug 2019 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCSUsefull links: | ||||||||
Added: | ||||||||
> > | ||||||||
Docker Container | ||||||||
Line: 45 to 46 | ||||||||
Archive-EngineImage with the archive-engine from Phoebus | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Usagepanda-iocDefault run command (standalone): | ||||||||
Changed: | ||||||||
< < |
docker run -dit -v ${TOP}/ioc-config:/home/panda-dcs/config [OPTIONS] paluma.rub.de/panda-ioc ./hameg_demo.cmdThe directory `ioc-config` contains the start-up script (e.g. hameg_demo.cmd) and the needed substitution files. | |||||||
> > |
docker run -dit -v ${PWD}/ioc-config:/home/panda-dcs/config [OPTIONS] paluma.rub.de/panda-ioc ./[ST.CMD] | |||||||
Added: | ||||||||
> > |
The panda-ioc image offers three mountable volumes:
| |||||||
OPTIONS can be:
| ||||||||
Line: 68 to 70 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
To run commands within the IOC container use `docker attach <CONTAINER ID>` and you should see the EPICS IOC command prompt. To detach from the container again use `CTRL+p CTRL+q` | |||||||
> > |
To run commands within the IOC container use `docker attach <CONTAINER ID>` and you should see the EPICS IOC command prompt. To detach from the container again use `CTRL+p CTRL+q | |||||||
ca-gateway | ||||||||
Changed: | ||||||||
< < | Default run command (standalone on PC with two NICs, not tested): | |||||||
> > | Default run command (PC with two NICs required): | |||||||
Changed: | ||||||||
< < |
docker run -d --network host -v ${TOP}/ioc-config:/home/panda-dcs/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist gw_pvlist -access gw_access | |||||||
> > |
docker run -d --network host -v ${PWD}/ioc-config:/home/panda-dcs/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist <PVLIST_FILE> -access <ACCESS_FILE> | |||||||
Changed: | ||||||||
< < | The directory `ioc-config` contains the configuration files for the gateway (e.g. gw_pvlist, gw_access) | |||||||
> > | The directory `/home/panda-dcs/config` contains the configuration files for the gateway, i.e. PVLIST_FILE and ACCESS_FILE | |||||||
PhoebusDefault run command (standalone) | ||||||||
Changed: | ||||||||
< < |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v ${TOP}/phoebus-config:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings phoebus-settings.ini | |||||||
> > |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v ${PWD}/phoebus-config:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings <SETTINGS_FILE> | |||||||
On the host system a user with `UID=1000` has to exists with read/write access to the X server of the host system. | ||||||||
Changed: | ||||||||
< < | The directory `phoebus-config` contains configuration files and bob files (display-files) | |||||||
> > | The directory `/home/panda-dcs/config` contains configuration files and bob files (display-files) | |||||||
Archive-EngineDefault run command (standalone): | ||||||||
Changed: | ||||||||
< < |
docker run -d -v ${TOP}/phoebus-config:/home/panda-dcs/config -p 4812:4812 paluma.rub.de/archive-engine -engine Test -settings archiver-settings.ini | |||||||
> > |
docker run -d -v ${PWD}/phoebus-config:/home/panda-dcs/config -p 4812:4812 paluma.rub.de/archive-engine -engine Test -settings <SETTINGS_FILE> | |||||||
If there are any `*.xml` files present in the `/home/panda-dcs/config` directory at the first start of the container, the archive engine will import them as new engines (using `-replace_engine -steal_channels`). The basename of the xml-files is used as engine name. CA address list must be configured manually in settings file (or use `--network host`). |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 19 to 20 | ||||||||
List of Images and Tagsepics-base | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
Base image for panda-ioc and ca-gateway images.
| |||||||
panda-ioc | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
Image with ready-to-use EPICS IOC. Includes asyn, stream, autosave, calc, modbus and snmp device support modules
| |||||||
ca-gateway | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
Image with ready to use CA-Gateway
| |||||||
Phoebus | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
Image with the main Phoebus product
| |||||||
Archive-Engine | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
Image with the archive-engine from Phoebus
| |||||||
Usagepanda-ioc |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Container Virtualization for PANDA DCS | ||||||||
Line: 19 to 19 | ||||||||
List of Images and Tagsepics-base | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
panda-ioc
| ||||||||
Line: 39 to 39 | ||||||||
panda-iocDefault run command (standalone): | ||||||||
Changed: | ||||||||
< < |
docker run -dit -v ${TOP}/ioc-config:/home/panda-dcs/config [OPTIONS] panda-ioc:7.0.2 ./hameg_demo.cmd | |||||||
> > |
docker run -dit -v ${TOP}/ioc-config:/home/panda-dcs/config [OPTIONS] paluma.rub.de/panda-ioc ./hameg_demo.cmd | |||||||
The directory `ioc-config` contains the start-up script (e.g. hameg_demo.cmd) and the needed substitution files. | ||||||||
Line: 59 to 59 | ||||||||
ca-gatewayDefault run command (standalone on PC with two NICs, not tested): | ||||||||
Changed: | ||||||||
< < |
docker run -d --network host -v ${TOP}/ioc-config:/home/panda-dcs/config ca-gateway:7.0.2 -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist gw_pvlist -access gw_access | |||||||
> > |
docker run -d --network host -v ${TOP}/ioc-config:/home/panda-dcs/config paluma.rub.de/ca-gateway -cip <CLIENT IP> -sip <SERVER IP> -server -pvlist gw_pvlist -access gw_access | |||||||
The directory `ioc-config` contains the configuration files for the gateway (e.g. gw_pvlist, gw_access)
PhoebusDefault run command (standalone) | ||||||||
Changed: | ||||||||
< < |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v ${TOP}/phoebus-config:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix phoebus:openjdk11 -settings phoebus-settings.ini | |||||||
> > |
docker run --network host -e DISPLAY=$DISPLAY --device /dev/dri -v ${TOP}/phoebus-config:/home/panda-dcs/config -v /tmp/.X11-unix:/tmp/.X11-unix paluma.rub.de/phoebus -settings phoebus-settings.ini | |||||||
On the host system a user with `UID=1000` has to exists with read/write access to the X server of the host system. | ||||||||
Line: 73 to 73 | ||||||||
Archive-EngineDefault run command (standalone): | ||||||||
Changed: | ||||||||
< < |
docker run -d -v ${TOP}/phoebus-config:/home/panda-dcs/config -p 4812:4812 archive-engine:openjdk11 -engine Test -settings archiver-settings.ini | |||||||
> > |
docker run -d -v ${TOP}/phoebus-config:/home/panda-dcs/config -p 4812:4812 paluma.rub.de/archive-engine -engine Test -settings archiver-settings.ini | |||||||
If there are any `*.xml` files present in the `/home/panda-dcs/config` directory at the first start of the container, the archive engine will import them as new engines (using `-replace_engine -steal_channels`). The basename of the xml-files is used as engine name. CA address list must be configured manually in settings file (or use `--network host`). |