1. Igor Khokhriakov
Web Jive 2.0
24.08.2016

2. What do we do?

Browse Tango devices

Add/remove devices

Quick test new devices

Quick monitor existing devices

3. Tango solution – Jive. What is Jive?

4. Why do we need a new Jive?

Narrow down UI to actually used features:
– Remove unused settings and configurations
– Simplified device context menu
– Simplified server wizard

Benefit from web interface: wide screen; reorganize views

Lightweight and fast
Jive is like a swiss army knife...
80% of the time
we need 20% of its features
Our own new Jive:

5. Why do we need Web?

For our X-Environment: we need a monitoring application
– Collect logs: Tango built-in LogViewer; Elastic Logstash;
Custom developed protocol *
– Analyze collected logs: Elastic Kibana; Custom developed app
– Deliver analyzed data to an end user: TangORB, REST API
– Implement X-Platform UI: mTangoSDK

For Tango community: full-fill Tango Feature requests 5&6 (REST
API&WebApp)
* a simple prototype was implemented using Tango pipes

6. Web Jive 2.0 (current release version 0.1)

Dynamic Device tree (devices are loaded on demand)

Test device panel

Editable Device tab (Info, Properties, Attributes config,
Events etc)

Interactive Monitoring tab, aka embedded ATK Panel

Simplified Server wizard

Log console

7. Web Jive: All-in-one screenshot
L I V E D E M O...

8. High level architecture overview

9. Security concerns
●
In production integrated with DESY's kerberos
●
TangoAccessControl*
●
Outside access via VPN (SSH port forwarding)
* missing tango-cs user caused non-expandable device tree

10. Thank you!
Questions?