TM Services: an architecture for monitoring and controlling the Square Kilometre Array (SKA) Telescope Manager (TM)

Domingos Barbosa,J Bruno Morgado,João Paulo Barraca,Matteo Canzari,Matteo Di Carlo,Mauro Dolci,Riccardo Smareglia

doi:10.1117/12.2309341

Abstract

The SKA project is an international effort (10 member and 10 associated countries with the involvement of 100 companies and research institutions) to build the world’s largest radio telescope. The SKA Telescope Manager (TM) is the core package of the SKA Telescope aimed at scheduling observations, controlling their execution, monitoring the telescope and so on. To do that, TM directly interfaces with the Local Monitoring and Control systems (LMCs) of the other SKA Elements (for example, Dishes, Correlator and so on), exchanging commands and data with them by using the TANGO controls framework (see [1]). TM in turn needs to be monitored and controlled, in order its continuous and proper operation is ensured and this higher responsibility has been assigned to the TM SER package.

Highlights

Telescope Manager (TM) in turn needs to be monitored and controlled, in order its continuous and proper operation is ensured
Starting, stopping and restarting of TM software applications, update and downgrade of TM software applications; x TM Logging, which includes the control of the destination of log messages, the transformation of the message and the query GUI; x Controlling of the virtualization system, according to the interface provided by the LINFRA team (“Instituto de Telecomunicações”, Portugal, Lisbon)
From the requirements analysis it has been extracted the main system’s functions that are described in the use cases document. They can be summarized in the following list: x TM generic monitoring and fault management in order to detect internal failure and gather TM performance; x TM lifecycle management in order to manage the versions of the TM and the TM applications which includes: configuration of TM software applications

Summary

PRINCIPLE OF WORK

The principle that drove the development of the present architecture is to study the best practises and known architectures that could solve the problems highlighted by the TM and SER requirements and reuse those concepts whenever possible. Starting, stopping and restarting of TM software applications, update and downgrade of TM software applications; x TM Logging, which includes the control of the destination of log messages, the transformation of the message (if required) and the query GUI; x Controlling of the virtualization system, according to the interface provided by the LINFRA (local infrastructure) team (“Instituto de Telecomunicações”, Portugal, Lisbon) Another important function of the system is the aggregation of the TM health status and the TM State (of the various TM applications) and reporting it to the Operator. From the requirements analysis (done with the help of the entire TM in the numerous discussion held) it has been extracted the main system’s functions that are described in the use cases document They can be summarized in the following list: x TM generic monitoring and fault management in order to detect internal failure and gather TM performance; x TM lifecycle management in order to manage the versions of the TM and the TM applications which includes: configuration of TM software applications,

ENTITY DECOMPOSITION

MODULES DECOMPOSITION

QUALITIES FOR TM

RUNTIME VIEW

VIRTUALIZATION SERVICE