Deployment

Standard deployment

The TMC Low is packaged as a helm chart and can be deployed uing helm commands. The default deployment configuration is assumed to be the SKA production environment. In the current version, TMC supports one subarray operation. Following list shows default number of instances deployed for each of the TMC component.

  1. Central Node - 1

  2. Subarray Node - 1

  3. CSP Master Leaf Node - 1

  4. CSP Subarray Leaf Node - 1

  5. SDP Master Leaf Node - 1

  6. SDP Subarray Leaf Node - 1

  7. MCCS Master Leaf Node - 1

  8. MCCS Subarray Leaf Node - 1

Warning

The number of instances of Central Node, MCCS Master Leaf Node, SDP Master, Leaf Node and CSP Master Leaf Node should always be one even though it is technically possible to deploy multiple instances.

To deploy the TMC use following command on the terminal:

helm install my-tmc-release https://artefact.skao.int/repository/helm-internal/ska-tmc-low --namespace ska-tmc-low

It is possible to customize the deployment as per need. To do so, the values.yaml file in TMC chart needs to be modified. The same can be done by using –set option in the command line while using the helm install command.

Basic Customization options

Number of subarrays

The number of subarrays can be deployed according to the need. A variable named subarray_count need to be set to the desired value. This option affects the number of instances of following components.

  1. Subarray Node

  2. CSP Subarray Leaf Node

  3. SDP Subarray Leaf Node

  4. MCCS Subarray Leaf Node

Tango host

This option allows to specify the desired Tango facility. The variable tango_host is used to specify the tango facility. By default, the value of this variable is set to databaseds-tango-base-test:10000.

Command timeout

This option sets the timeout value till which the TMC components wait for completion of commands invoked on lower level Tango devices. This timeout should be set for each TMC component. To set the desired timeout value, navigate to deviceServers -> <component name> in values.yaml file. Locate CommandTimeOut variable and set an integer value equivalant in seconds.

Warning

When setting the command timeout values, it is essential to set bigger timeout values Central Node and Subarray Node than any Leaf Node. This is because the as per TMC architecture, Central Node and Subarray Node are higher level in the hierarchy and Leaf Nodes are at lower level. The commands flow from Central Node, Subarray Node, to Leaf Nodes and then to the subsystems. The higher level nodes need to factor in the command timeout set on lower level components.

Advanced Customization options

Following are the advance options. These options are mainly useful for developers and AIV engineers for testing purpose. Customizing these parameters should be done carefully.

#. file : User can provide custom device server configuration file to nodes. Defaults are: configuration files.

  1. enabled : User can opt to disable any node by setting this value to False.Default is True for all nodes.

  2. Variables under global section

    1. domain : This value is present under global. It is the domain name of TMC TANGO device. The value is set to “low-tmc”.

    2. tmc_subarray_prefix : This value is present under global, User can use this to change the FQDN prefix of SubarrayNode.

    3. csp_subarray_ln_prefix : This value is present under global, User can use this to change the FQDN prefix of CspSubarrayLeafNode.

    4. sdp_subarray_ln_prefix : This value is present under global, User can use this to change the FQDN prefix of SdpSubarrayLeafNode.

    5. csp_master_ln : This value is present under global, User can use this to change the FQDN of CspMasterLeafNode.

    6. sdp_master_ln : This value is present under global, User can use this to change the FQDN of SdpMasterLeafNode.

    7. csp_subarray_prefix : This value is present under global, User can use this to change the FQDN prefix of CSP Subarray.

    8. sdp_subarray_prefix : This value is present under global, User can use this to change the FQDN prefix of SDP Subarray.

    9. csp_master : This value is present under global, User can use this to change the FQDN of CSP Master.

    10. sdp_master : This value is present under global, User can use this to change the FQDN of SDP Master.

    11. mccs_master : This value is present under global, User can use this to change the FQDN of MCCS Master.

    12. mccs_master_ln : This value is present under global, User can use this to change the FQDN of MCCS Master Leaf Node.

    13. mccs_subarray_prefix : This value is present under global, User can use this to change the FQDN prefix of MCCS Subarray.

    14. mccs_subarray_ln_prefix : This value is present under global, User can use this to change the FQDN prefix of MCCS Subarray Leaf Node.

Component specific configuration

This section specifies the configuration options for individual TMC component. Navigate to deviceServers.<component> section in values.yaml file.

Central Node

  1. SkuidService : This refers to the value for SKUID service. Currently defaults to “ska-ser-skuid-test-svc.ska-tmc-centralnode.svc.techops.internal.skao.int:9870”.

  2. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 0.5 seconds.

  3. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 0.5 seconds.

  4. CommandTimeOut : This refers to the Timeout (in seconds) for the command execution. Currently defaults to 80 seconds.

  5. AssignResourcesInterface : This refers to the interface value of AssignResources schema. Currently defaults to “https://schema.skao.int/ska-low-tmc-assignresources/4.0”.

  6. ReleaseResourcesInterface : This refers to the interface value of ReleaseResources schema. Currently defaults to “https://schema.skao.int/ska-low-tmc-releaseresources/3.0”.

  7. family : This refers to the family name of CentralNode TANGO device. Currently defaults to “central-node”.

  8. member : This refers to the member of CentralNode TANGO device. Currently defaults to “0”.

Subarray Node

  1. CspAssignResourcesInterfaceURL : Interface version for CSP assign resources command. Currently defaults to “https://schema.skao.int/ska-low-csp-assignresources/3.0”

  2. CspScanInterfaceURL : Interface version for CSP scan command. Currently defaults to “https://schema.skao.int/ska-low-csp-scan/2.0”

  3. SdpScanInterfaceURL : Interface version for SDP scan command. Currently defaults to “https://schema.skao.int/ska-sdp-scan/0.4”

  4. MccsConfigureInterfaceURL : Interface version for MCCS configure command. Currently defaults to “https://schema.skao.int/ska-low-mccs-configure/1.0”

  5. MccsScanInterfaceURL : Interface version for MCCS scan command. Currently defaults to “https://schema.skao.int/ska-low-mccs-scan/3.0”

  6. JonesURI : URI for Jones Matrix. Currently defaults to “tango://jones.skao.int/low/stn-beam/1”.

  7. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 0.5 seconds.

  8. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 0.5 seconds.

  9. CommandTimeOut : This refers to the timeout (in seconds) for the command execution. Currently defaults to 70 seconds.

  10. AbortCommandTimeOut : This refers to the timeout for the Subarray ABORTED obsState transition. Once the AbortCommandTimeOut exceeds, SubarrayNode transitions to obsState FAULT. Currently defaults to 40 seconds.

  11. family : This refers to the family name of SubarrayNode TANGO device. Currently defaults to “subarray”.

SDP Subarray Leaf Node

  1. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 0.5 seconds.

  2. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 0.5 seconds.

  3. CommandTimeOut : This refers to the timeout (in seconds) for the command execution. Currently defaults to 50 seconds.

  4. AdapterTimeOut : This refers to the timeout (in seconds) for the adapter creation. This property is for internal use. Currently defaults to 2 seconds.

  5. family : This refers to the family name of SDP Subarray Leaf Node TANGO device. Currently defaults to “subarray-leaf-node-sdp”.

SDP Master Leaf Node

  1. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 0.5 seconds.

  2. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 0.5 seconds.

  3. AdapterTimeOut : This refers to the timeout (in seconds) for the adapter creation. This property is for internal use. Currently defaults to 2 seconds.

  4. family : This refers to the family name of SDP Master Leaf Node TANGO device. Currently defaults to “leaf-node-sdp”.

  5. member : This refers to the member of SDP Master Leaf Node TANGO device. Currently defaults to “0”.

CSP Master Leaf Node

  1. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 0.5 seconds.

  2. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 0.5 seconds.

  3. AdapterTimeOut : This refers to the timeout (in seconds) for the adapter creation. This property is for internal use. Currently defaults to 2 seconds.

  4. family : This refers to the family name of CSP Master Leaf Node TANGO device. Currently defaults to “leaf-node-csp”.

  5. member : This refers to the member of CSP Master Leaf Node TANGO device. Currently defaults to “0”.

CSP Subarray Leaf Node

  1. DelayCadence : This refers to the time difference (in seconds) between each publication of delay values to the delayModel attribute on the CspSubarrayLeafNode. Currently defaults to 300 seconds.

  2. DelayValidityPeriod : This represents the duration (in seconds) for which delay values remain valid after being published. Currently defaults to 600 seconds.

  3. DelayModelTimeInAdvance : This indicates the time in seconds by which delay values need to be available in advance. Currently defaults to 600 seconds.

  4. PSTDelayCadence : This refers to the time difference (in seconds) between each publication of delay values for the PST beam. Currently defaults to 300 seconds.

  5. PSTDelayValidityPeriod : This represents the duration (in seconds) for which delay values remain valid after being published. Currently defaults to 600 seconds.

  6. PSTDelayModelTimeInAdvance : This indicates the time in seconds by which delay values need to be available in advance. Currently defaults to 600 seconds.

  7. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 0.5 seconds.

  8. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 0.5 seconds.

  9. CommandTimeOut : This refers to the timeout (in seconds) for the command execution. Currently defaults to 50 seconds.

  10. AdapterTimeOut : This refers to the timeout (in seconds) for the adapter creation. This property is for internal use. Currently defaults to 2 seconds.

  11. family : This refers to the family name of CSP Subarray Leaf Node TANGO device. Currently defaults to “subarray-leaf-node-csp”.

MCCS Master Leaf Node

  1. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 0.5 seconds.

  2. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 0.5 seconds.

  3. CommandTimeOut : This refers to the timeout (in seconds) for the command execution. Currently defaults to 50 seconds.

  4. AdapterTimeOut : This refers to the timeout (in seconds) for the adapter creation. This property is for internal use. Currently defaults to 2 seconds.

  5. family : This refers to the family name of MCCS Master Leaf Node TANGO device. Currently defaults to “leaf-node-mccs”.

  6. member : This refers to the member of MCCS Master Leaf Node TANGO device. Currently defaults to “0”.

MCCS Master Leaf Node

  1. LivelinessCheckPeriod : This refers to the Period (in seconds) for the liveliness probe to monitor each device in a loop. Currently defaults to 0.5 seconds.

  2. EventSubscriptionCheckPeriod : This refers to the Period (in seconds) for the event subscriber to check the device subscriptions in a loop. Currently defaults to 0.5 seconds.

  3. CommandTimeOut : This refers to the timeout (in seconds) for the command execution. Currently defaults to 50 seconds.

  4. AdapterTimeOut : This refers to the timeout (in seconds) for the adapter creation. This property is for internal use. Currently defaults to 2 seconds.

  5. family : This refers to the family name of MCCS Subarray Leaf Node TANGO device. Currently defaults to “subarray-leaf-node-mccs”.