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

Reduce Container Drag: Group TMC subarray nodes with subarray leaf nodes into a single device server

    XporterXMLWordPrintable

Details

    • Feature
    • Won't have (this time)
    • PI15
    • None
    • None
    • Obs Mgt & Controls
    • Hide

      This ticket arose from a problem workshop (see https://miro.com/app/board/o9J_koKNl68=/?moveToWidget=3074457349549897367&cot=12)

      By reducing the number of containers and interprocess communication I have less need for a large execution environment for development. Changing inter processing to intra-processing communication should also reduce the latency involved in communicating between two parallel routines. 

      Show
      This ticket arose from a problem workshop (see  https://miro.com/app/board/o9J_koKNl68=/?moveToWidget=3074457349549897367&cot=12 ) By reducing the number of containers and interprocess communication I have less need for a large execution environment for development. Changing inter processing to intra-processing communication should also reduce the latency involved in communicating between two parallel routines. 
    • 1
    • 6
    • 19.5

    • PI22 - UNCOVERED

    Description

      As a Deployer/Installer, I want to deploy and instantiate the TMC subarray node and subarray leave nodes (SDP and CSP) as a single tango device server instance on a Kubernetes pod. Thus reducing the number of container processes for subarrays by two-thirds.

      The means to achieve this configuration must be done by only having to change configurational parameters according to a well-defined schema in the chart's "values.yaml" . In other words the outcome of https://jira.skatelescope.org/browse/SP-1266 will be used to implement this feature.

       

      Attachments

        Issue Links

          Child Of

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SS-8 Technical Debt - Feature Set

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Done

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SS-55 SKAMPI development configuration

          • Not Assigned - Priority is not assigned yet.
          • Discarded
          Is affected by

          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-1266 Reduce Container Drag: generate a multi device server using chart based paramaters only (values.yaml)

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

          Structure

            Activity

              People

                g.leroux Le Roux, Gerhard [X] (Inactive)
                g.leroux Le Roux, Gerhard [X] (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 1.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete00.0
                  Total00.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel