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

Configuring the Low telescope for deployment from telmodel

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

Details

    • LOW ART
    • Hide

      With four stations soon to become sixteen and then sixty, and end-to-end system integration well underway in AA0.5, now is the time to put in place a scalable solution for software configurability covering all Low subsystems.

      The benefits of doing so are already clear from the work done to this point for MCCS:

      • The ability to easily configure for deployment across a range of target platforms including AA0.5, Low ITF, AAVS3, the MCCS development platforms and the Low PSI.
      • Good scalability as platforms grow beyond the point where manually managing application configuration is feasible, especially during assembly, integration and verification when change is frequent.
      • Decoupling the management of facts about the target platforms from the mechanics of software configuration, i.e. Helm values.
      • Architectural clarity - many valuable insights have flowed from the development of this model and tooling.
      • A well-maintained single source of truth has proven useful beyond its original purpose and has already been taken up by commissioning scientists, site deployment and station integration and other teams. There are already cases of MCCS, SDP, and CBF having their own versions of the same facts, which we want to resolve as soon as possible.
      Show
      With four stations soon to become sixteen and then sixty, and end-to-end system integration well underway in AA0.5, now is the time to put in place a scalable solution for software configurability covering all Low subsystems. The benefits of doing so are already clear from the work done to this point for MCCS: The ability to easily configure for deployment across a range of target platforms including AA0.5, Low ITF, AAVS3, the MCCS development platforms and the Low PSI. Good scalability as platforms grow beyond the point where manually managing application configuration is feasible, especially during assembly, integration and verification when change is frequent. Decoupling the management of facts about the target platforms from the mechanics of software configuration, i.e. Helm values. Architectural clarity - many valuable insights have flowed from the development of this model and tooling. A well-maintained single source of truth has proven useful beyond its original purpose and has already been taken up by commissioning scientists, site deployment and station integration and other teams. There are already cases of MCCS, SDP, and CBF having their own versions of the same facts, which we want to resolve as soon as possible.
    • Hide
      • A versioned telmodel schema with support for multiple datacentres
      • Versioned telmodel data for AA0.5 and Low-ITF, extending beyond MCCS (i.e. at least addressing at least one other subsystem)
      • All subsystems using Low telmodel data aligned to a single source of truth - TMC, SDP, and CBF
      • Multiple subsystems can be at least partially configured for deployment from telmodel data
      Show
      A versioned telmodel schema with support for multiple datacentres Versioned telmodel data for AA0.5 and Low-ITF, extending beyond MCCS (i.e. at least addressing at least one other subsystem) All subsystems using Low telmodel data aligned to a single source of truth - TMC, SDP, and CBF Multiple subsystems can be at least partially configured for deployment from telmodel data
    • 3
    • 3
    • 0
    • Team_VULCAN

    • PI24 - UNCOVERED

    • Team_VULCAN
    •  Low G4

    Description

      To date, Low software system integration has focused on integration of the software itself. Less attention has been paid to integration of the telmodel data that underpins the software configuration. Thus, there is currently no unified Low telescope model.

      The maturity of telmodel use and development across the Low software subsystems varies from none whatsoever, up to the MCCS subsystem, whose deployment configuration can be fully determined from telmodel data. As a result there already exists a detailed telescope model that describes all of the salient facts about the aperture array from the MCCS software point of view.

      This feature will expand the scope of this model and associated deployment tooling, to allow all Low subsystems to be configured for deployment in the same way.

      Attachments

        Issue Links

          Child Of

          Capability - SAFe program capability SS-155 Low AA0.5 multi-station interferometry

          • High - Serious problem that could block progress.
          • Implementing

          Structure

            Activity

              People

                Vani.Naram Naram, Vani
                Drew.Devereux Devereux, Drew
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (88.89%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   12.0
                  Complete1116.0
                  Total1218.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel