Loading...

Xporter

XML

Word

Printable

Details

Type: Feature
Priority: Not Assigned
Fix Version/s: PI10
Component/s: None
Labels:

ARTs:

Obs Mgt & Controls
Benefit hypothesis:

Hide

Stakeholders can make more efficient use of computer resources to perform their work on their parts of the system without creating unknown dependencies or excessive need for separate integration testing afterwards.

Show
Stakeholders can make more efficient use of computer resources to perform their work on their parts of the system without creating unknown dependencies or excessive need for separate integration testing afterwards.
Acceptance criteria:
Hide

Specify the required number of dishes and subarrays, and deploy the appropriate number of Tango devices, along with correct Tango database properties. This will allow a developer to deploy a reduced system, e.g., 1 dish and 1 subarray.

No guarantee to support systems larger than we currently have with skampi (4 dishes, 3 subarrays), as this may require change in subsystem charts (e.g., CSP or SDP).

No guarantee for LOW configurability either.

Demonstrate the successful deployment for a specific set of selections (as above) and show how a particular stakeholder job can be done for that given deployment without creating uncertainties downstream in the results.

Note: the implementation of this feature should involve some planning and design before proceeding with a set of solutions. If the implementation of some parts of the proposed solution can not be done in the given amount of time, then a report must be given with recommendations for work in upcoming PIs to realize the missing parts.
Show
Specify the required number of dishes and subarrays, and deploy the appropriate number of Tango devices, along with correct Tango database properties. This will allow a developer to deploy a reduced system, e.g., 1 dish and 1 subarray. No guarantee to support systems larger than we currently have with skampi (4 dishes, 3 subarrays), as this may require change in subsystem charts (e.g., CSP or SDP). No guarantee for LOW configurability either. Demonstrate the successful deployment for a specific set of selections (as above) and show how a particular stakeholder job can be done for that given deployment without creating uncertainties downstream in the results. Note: the implementation of this feature should involve some planning and design before proceeding with a set of solutions. If the implementation of some parts of the proposed solution can not be done in the given amount of time, then a report must be given with recommendations for work in upcoming PIs to realize the missing parts.
Feature Points:
4
Initial Size:
4
WSJF:
0
Agile Teams:

Team_KAROO
Due Sprint:
Sprint 5
Story Point Burn-up:
Overdue:
Outcomes:

Hide

Parameterised skampi deployment enables investigation into skampi resource consumption (SP-458) by making it easier to deploy skampi at larger scale than what it is now, and therefore indirectly speaks to the INS-9 problem. ~~SP-1603~~ focusses on TMC, proving the concept and paving the way for adoption of parameterised deployment of other systems.

Show
Parameterised skampi deployment enables investigation into skampi resource consumption ( SP-458 ) by making it easier to deploy skampi at larger scale than what it is now, and therefore indirectly speaks to the INS-9 problem. SP-1603 focusses on TMC, proving the concept and paving the way for adoption of parameterised deployment of other systems.
Resolved PI.Sprint:
10.4

Feature Checklist:

Stories Completed, Outcomes Reviewed

Demos:
- OMC_ART_SystemDemo_5
- PI10_DEMO
Requirement Status:

PI22 - UNCOVERED
Labels_MIRO:
Cross_Team_Code_Review I&A MVP

Description

Using the existing technologies and infra mechanisms, change the configuration and design of components so as to allow for selective deployments (à la carte), achieving more effective use of resources for a given objective (or job to be done by a stakeholder).

Each allowable selection should result in a workable running system that has all the necessary dependencies running for sufficient execution of a particular stakeholder job but not more. Selections must also be "complete" for the particular job in that deploying additional parts does not affect the original outcome (e.g if I test configure subarray 1, adding a subarray 2 deployment should not change test configure subarray 1).

The addition or subtraction of a specific allowable element from a given deployment must be done via an upgrade command referencing an updated values.yaml file.

The following could be possible "courses" to choose from:

Skampi Lite: 1 subarray set (tmc,sdp,csp/mccs) plus master devices with 2 dishes/stations.
Skampi Facade: Taranta with tango test device but no subarray
Skampi sdp: Only sdp subarray devices with the rest "stubbed out or emulated" to test sdp functionality
Skampi csp: Only csp subarray devices with the rest "stubbed out or emulated" to test csp only resources.
Skampi dishes: Only dishes.
Skampi tmc: tmc only devices
Skampi oet: oet only devices

etc.

Attachments

Issue Links

is required by

SP-1690 TMC Configurable deployment: Next Steps

Done

relates to

SP-1267 Reduce Container Drag: Set cardinality of SKAMPI components

Discarded

SP-1524 Improve SDP configurability

Done

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

mentioned on

Merge request - SAR-210 Refactored the tmc-mid values.yaml file

(8 mentioned in, 1 mentioned on)

Structure

Activity

People

Assignee:: Le Roux, Gerhard [X] (Inactive)

Reporter:: Le Roux, Gerhard [X] (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Feature Progress

Story Point Burn-up: (100.00%)

Feature Estimate: 4.0

	Issues	Story Points
To Do	0	0.0
In Progress	0	0.0
Complete	3	6.5
Total	3	6.5

Dates

Created:: 05/Mar/21 10:37 AM

Updated:: 15/Apr/24 9:49 AM

Resolved:: 04/May/21 12:04 PM

Skampi à la carte (parametrised deployments) - TMC/dish focus