Creating and sharing knowledge for telecommunications

A cyber infrastructure for the SKA Telescope Manager

Barbosa , D. ; Barraca, JPB ; Carvalho, B. ; Maia, D. ; Gupta, Y. ; Natarajan, S. ; Roux, G. ; Swart, P.

A cyber infrastructure for the SKA Telescope Manager, Proc SPIE - Astronomical Telescopes + Instrumentatio Software and Cyberinfrastructure for Astronomy IV SPIE 9913, Edimburgh, United Kingdom, Vol. 9913, pp. 1 - 11, July, 2016.

Digital Object Identifier: dx.doi.org/10.1117/12.2234002

Abstract
The Square Kilometre Array Telescope Manager (SKA TM) will be responsible for assisting the SKA Operations and Observation Management, carrying out System diagnosis and collecting Monitoring and Control data from the SKA subsystems and components. To provide adequate compute resources, scalability, operation continuity and high availability, as well as strict Quality of Service, the TM cyber-infrastructure (embodied in the Local Infrastructure - LINFRA) consists of COTS hardware and infrastructural software (for example: server monitoring software, host operating system, virtualization software, device firmware), providing a specially tailored Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) solution. The TM infrastructure provides services in the form of computational power, software defined networking, power, storage abstractions, and high level, state of the art IaaS and PaaS management interfaces. This cyber platform will be tailored to each of the two SKA Phase 1 telescopes (SKA_MID in South Africa and SKA_LOW in Australia) instances, each presenting different computational and storage infrastructures and conditioned by location. This cyber platform will provide a compute model enabling TM to manage the deployment and execution of its multiple components (observation scheduler, proposal submission tools, MandC components, Forensic tools and several Databases, etc). In this sense, the TM LINFRA is primarily focused towards the provision of isolated instances, mostly resorting to virtualization technologies, while defaulting to bare hardware if specifically required due to performance, security, availability, or other requirement.