The Square Kilometre Array Observatory (SKAO) is a next-generation radio telescope that is being built in two locations in the Karoo region of South Africa and the Murchison region of Western Australia forming one Observatory run from a global headquarters based in the United Kingdom at Jodrell Bank. At the heart of the SKA software, there will be a database that persists and replicates its metadata between these three sites that have different functions. This paper will describe the main requirements for the SKA database, how this has been done in the past at the Atacama Large Millimeter/Sub millimeter Array (ALMA) in Chile, the lessons learned there from the ten years of operations and what new options have appeared to handle the SKA, three site telescope needs. The solution needs to be highly available, performant, cost effective and easy to implement and maintain in the long term.
ALMA has been operating since 2013 and it keeps on adding an ever-growing new set of capabilities. Every new feature implies among other things a new software release that has to be implemented, tested and deployed around the world. In this paper we present the new deployment process that allowed ALMA to deliver faster releases to reliable testing and production environments. This was achieved through the use of container-based services, both for applications and data. This implied that tasks that in the past were done manually, are now fully automated, in order to avoid human errors and maintain consistency between what was tested and what is finally installed in production. All this, under a unique and complex operation environment that includes the two main operation facilities in Chile at ALMA Operation Site Facilities (OSF) and Santiago Central Office (SCO), and the different executive headquarters located across the ALMA global network. We also explain how we managed to address the issue of ever-growing observational data, which made it difficult to replicate the production environment data into our testing infrastructure. Our solution consisted in using a container-based database that allowed us to create a full copy of the production database in a very short time. All those changes enabled JAO to improve its software testing process allowing a monthly release cycle.
Access to the requested content is limited to institutions that have purchased or subscribe to SPIE eBooks.
You are receiving this notice because your organization may not have SPIE eBooks access.*
*Shibboleth/Open Athens users─please
sign in
to access your institution's subscriptions.
To obtain this item, you may purchase the complete book in print or electronic format on
SPIE.org.
INSTITUTIONAL Select your institution to access the SPIE Digital Library.
PERSONAL Sign in with your SPIE account to access your personal subscriptions or to use specific features such as save to my library, sign up for alerts, save searches, etc.