Contribute to revised integration and acceptance testing of SDP in SKAMPI

Having a robust testable solution for the integration of SKA software products/systems is very much key to the success of the project both for AA0.5 and in the longer term.

Contributing to this activity is important to ensure that it is a success and by contributing to this activity we will be participating in knowledge sharing across the ARTs, something that will be vital when developing new acceptance tests of a robust SKA software deployment that includes SDP.

• Timeboxed activity to contribute to the task team being created for SS-82. Possibly present on:
  • SDP sub-system test solution developed for SP-1610
  • SDP control system design using configuration database
• Capture and socialise next steps in approach to the integration of SDP with other SKA software (via SKAMPI)
  • e.g. how to adapt LMC such that it is compatible with the long-running commands proposal

We have participated in the architecture sync and MVP meetings to track the progress of SS-82. The work has not required any direct involvement from the ORCA team because it has focussed on refactoring the TMC central node and the CI pipeline infrastructure. (Notes from these meetings about things that may be relevant to SDP have been captured in the linked Spike tickets.)

We made a presentation about testing SDP with simulated component failures at an MVP meeting. As part of this, we sought advice about a better way how to control the Tango devices in the tests. This led us to investigate TangoGQL as a way of controlling the Tango devices, which has subsequently been implemented in the tests (see SP-1884 and SP-1845).

The implementation of the long-running commands in the Tango base classes was released in sprint 12.5 so there has not been time to investigate how to adapt this for the SDP Tango devices.