• start container
• use Astor on the VM to start a new instance of TangoTest within container

• On VM, setup TangoAccess device server to run as service
• Update DatabaseDs and Starter services to start with access controls
• Setup default permissions on each machine that give all users on all machines read/write permission

See: http://tango-controls.readthedocs.io/en/latest/administration/services/access-control.html?highlight=super_tango

mTango shell be installed in a dedicated container/image tangobox-web.

• mTango running on the container
• REST api running on the container
• browser links created on the VM desktop

• create a container for demos
• install elinac device servers on the container

Follows #15

• Mambo installed on VM
• Desktop link created
• Example parameters from simulated linac and motors configured with Mambo for HDB
• Example parameters from simulated linac and motors configured with Mambo for TDB, 2weeks buffer.
• Example view presents selected parameters
• History checked

Claudio sent a bunch of examples to be provided on the VM.

training.zip

I am testing RC7 and I noticed that the Database is started but not Tango AccessControl. Then when I start jive I cannot do anything because access control is configured but there is not AccessControl service running. How do you manage to use it? Is there some magic command I have to run first?

For the moment I cannot test much more. Any tips what I am doing wrong?

Docker-compose file to run all containers an the VM

• docker-compose.yml file
• systemd service file for docker-compose
• file on Desktop with links to each container
  Containers:
• tangobox-archive
• tangobox-base
• tangobox-com
• tangobox-sardana
• tangobox-sim
• tangobox-web

• Get sources from: http://www.tango-controls.org/resources/dsc/ds/321/
• Compile

Follows #21
Bensikin is a tool to mange SNAPshots.

• Bensikin isntalled on the VM
• 2 Example contexts created
• Example snapshots taken
• Test load of example snapshots

• Create a dedicated container/image tangobox-sardana
• Install Sardana device servers there
• Install/configure example SardanaGUI/demo on the VM

• PyPLC install: http://www.tango-controls.org/resources/dsc/ds/1094/
• Setup of an example device (connecting to the same simulator as ModbusDS)

• Get sources of ModbusDS: http://www.tango-controls.org/resources/dsc/ds/318/
• Get sources of ModbusComposer: http://www.tango-controls.org/resources/dsc/ds/335/
• Compile ModbusComposer and ModbusDS
• Setup an example simulator
• ...

After downloading and testing RC8 here is some feedback :

1. TangoAccessControl does not start. Main problem seems to be linked to use of NAT on VM and the hostname (tangobox-vm) being incorrectly resolved. One solution was to change TANGO_HOST to point to localhost:10000 in /etc/tangorc and all the startup scripts in systemd. With this change access control, the TangoAccessControl and Starter started correctly. After that Starter started TangoTest and PyAlarm correctly.
2. Following applications (at least) need to be updated: Jive, Astor, and Pogo. Latest versions are on bintray (https://bintray.com/tango-controls/maven)
3. Desktop has a number of errors and looks messy. Need to move all documents into sub-directories e.g. README. Move taurus icons to sub-directory. Organise Desktop.
4. JupyTango works out-of-the-box but needs an icon on the desktop. See screenshot.
5. How to work with the Docker images is not clear. I propose to prefix all docker images with docker instead of tangobox e.g. docker-sim. All images should be prebuilt. So far only the sim one seems to be built. At the same time rename host "tangobox-vm" i.e. in small letters.
6. Linac simulation does not start. How to start it?
7. Missing REST server,

• hdb++,
• simulations, ...

8. Disk of 25G should be enough. I propose to remove unused applications like libreoffice, Unity etc.
9. Is conda installed? Does not seem to be. It will be useful for the PyTango demo

Snapshot device servers should go to tangobox-archiving container/image.

• Taurus installed with prefix /usr/local
• Taurus tools shortcuts available from desktop

The archiving device servers should be running within dedicated docker container / image.
Image name should be tangobox-archiving. It should contain MariaDB for data.
Archiving package is available here: http://www.tango-controls.org/downloads/tools/

• Download package, read included documenation
• Database configured for HDB/TDB data
• Running ArchivingManager
• Running 2 HDB archiver device
• Running 2 TDB archivier devcie
• Runinng Watchers
• Running Extractor

• Copy TaurusGUI configuration from old tango-box to the new VM
• Setup desktop link to start TaurusGUI with copied configuration
• Make missing related device (servers) from tango-box run on demo-container

• Contact Claudio for help
• E-giga installation in a tangobox-web container

• Contact Nicolas Leclercq - he agreed to do the task
• JupyTango instalalation in /home/tango-cs/JupyTango
• ~/bin/jupytango.sh script too start juptyerlab

• Contact Claudio for support
• Install Canone on the same image as e-giga?

This image shell provide:

• Ubuntu 16.04 LTS, 64bit
• Python 2.7
• Tango Controls
• PyTango
• Starter device server running as service
• setup TANGO_HOST = tangobox:10000

Important: it should not start DatabaseDs as service

Relates to #19

• Panic installed on VM
• Example alarms configured and tested

PyAlarm shell be installed on a base docker image as well as on the VM

• PyAlarm installed on VM
• PyAlarm added to docker base image

PyAlarm instances running on each container and on VM

• VM
• base
• archiving
• web
• sardana
• sim

Hi,

could you please update TangoWebapp to the newest version: link?

Thanks,

I notice the virtual disk (.vmdk) is 12 GB in size. Is there any way to reduce this? If not we will need to inform the users that they need 12-15 GB free disk.

Hi,

here are the official Tango icons to be used for the desktop and where possible the applications. These icons have beeen created by Fabienne Mengoni of the ESRF. Let us know if you need different resolution images or there are some icons missing just let us know.

Thanks!

tango_icons.zip

The HDB++ servers should be installed on the container/imagetangobox-archivning (see, #15)

• QTango compiled and installe in /usr/local
• Check if any demo is available, see contacts below

For qtango support you can contact Giacomo Strangolino ([email protected]), for e-giga you can contact Lucio Zambon ([email protected])

Low priority

After #48 the RC8 should be improved to make sure all services and images starts correctly with some minor fixes:

• access control properly starts or is disabled (see #51)
• docker containers starts (unfortunately without archive)
• desktop organized
• disk size extended
• new versions of tools installed

The specification shell:

• list Tango packages to be installed
• packages shell be prioritized
• define what will be deployed as containers
• file structure shell be defined (where certain parts should go)
  The specification shell go to Github Wiki

The RC10 release should provide all what is needed for ICALEPCS, with the following priorities:

• HDB++ #17 , #18
• Visual Studio Code #29
• E-giga #32
• Order on desktop
• documenation from doc/_build/html copied to Desktop/documents/manual and its index.html linked from the desktop directly
• doc/_build/text/index.txt copied to desktop and renamed as README.txt
• tangobox-sardana container stopped and hidden if Sardana does not work properly
• tangobox-archiving container stopped
• tangobox-hdbpp container stopped
• tangobox-sim container stopped
• tangobox-web2 renamed to tangobox-egiga
• /etc/hosts updated with proper egiga container name
• TangoWebApp running on tangobox-web, proper shortcut on the desktop
• after export check import and if it starts as defined above (so containers listed remains stopped :) )
  Optional:
• Sardana #33
• new version of WebApp #58

• copy JLinac GUI demo from old tango-box to VM
• create a link to JLinac GUI on the VM desktop
• check if it works with linac simulation form #9

Thanks for the new version of TangoBox RC9! It fixes a number of the issues and is working "out of the box" as expected including the docker containers and jupytango - very nice work!

I ran it on my laptop and noticed some performance issues which I wanted to propose you address in RC10:

(1) PyAlarm is CPU intensive takes 10% of a core. With 4 copies of PyAlarm running this is almost half a CPU. I propose to not start PyAlarm at startup and to change the Astor settings to have it as defined but un controlled. It can be started by manually if needed.

• .

(2) same for the Linac servers. Maybe not start them at startup either. Theey can be started on request.

• .

(3) Only start TangoTest at startup. Rename the instance name from test1 and test2 to 1 and 2.

• .

(4) rename the host from TangoBox-VM to tangobox-vm

• .

(5) Taurus elinac demo fails with this message: cannot create panel Finder ... problem with Vacca attribute.

• .

(6) We need a README about the TangoBox including a description about what it contains, how to start and stop docker containers + how to start and stop Panic, HDB++ etc.

• .

In RC10 I would configure it not to start archiving automatically. It should be started manually otherwise it will start filling the disk and cpu from the start.

That's all for now. We are almost ready for ICALEPCS!

This release will include

• tangobox-archive starting properly
• tangobox-web running and providing mTango REST server - #23
• shortcuts to connect to containers consoles

The following shell be done, too:

• /home/tango-cs/bin/run-tangobox-container-root which will run a container with --user root
• RC9 branch shell be created with
  • added web dockerfile and resources
  • added run-tangobox-container-root
  • added /home/tango-cs/Desktop/* to vm folder
• New Pogo (9.6.1) - #47
• New ATK (9.2.9) - #47
• set password to tango
• sample client programs #40
• updated icons for Pogo and Bensikin - #26
• export

• PyTango installed in /usr/local
• PyTango in PYTHONPATH

Use --prefix when used pip install

• Install PyCharm

Follows #17
The clients

• Configuration tool installed on VM
• View/browser application installe on VM
• Example archiving configured
• History logged (checked with browser application)

The docker containers should start as services after VM tango-db and tango-access starts.

• Install Visuaul Studio Code on the VM
• Install a python plugin
• Install a java plugin
• Create a project for TangoTest
• Create a project for some PyTango application (to be defined yet)

• How to install VM
• Description what is installed
• deployment diagram
• Documentation moved to main tango-doc
• Screenshots in the texts
• RtD configured
• PDF from RtD documentation

The time setting seems to be set to Warsaw and the language in Polish. Could the language be changed to English and maybe the timezone to Brussels / Paris? Thanks.

• onedrive folder for .ova image
• VPN to connect
• VirtualBox running the VM

The image shell be:

• Ubuntu 16.04 LTS, 64bit
• python 2.7
• User account: tango-cs, password: tango
• Window manager: Metacity

Update standard tango tools to the newest versions (check what can be updated, first)

• Source code from tango-controls.org
• Read INSTALL and README
• Install dependencies - development tools (gcc, java), ZMQ, OmniOrb, MariaDB or MySQL
• compile with prefix=/usr/local
• Read about SystemD
• Setup services for DatabaseDS, Starter

• SimulatorDS configured to simulate containers with flows and valves
• Synoptic demo for this simulation
• TaurusGUI application for it