Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-1603

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

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • Obs Mgt & Controls
    • 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.
    • Hide
      1. 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.
      2. 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).
      3. 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.
    • 4
    • 4
    • 0
    • Team_KAROO
    • Sprint 5
    • 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.
    • 10.4
    • Stories Completed, Outcomes Reviewed

    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:

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

      etc.

       

      Attachments

        Issue Links

          is required by

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1690 TMC Configurable deployment: Next Steps

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          relates to

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1267 Reduce Container Drag: Set cardinality of SKAMPI components

          • Not Assigned - Priority is not assigned yet.
          • Discarded

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1524 Improve SDP configurability

          • Not Assigned - Priority is not assigned yet.
          • 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

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

          Structure

            Activity

              People

                g.leroux Le Roux, Gerhard [X] (Inactive)
                g.leroux 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

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete36.5
                  Total36.5

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel