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

advance new TangoGQL prototype

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

Details

    • Obs Mgt & Controls
    • Hide

      Mitigation of security vulnerability.

      Porting to a more modern set of libraries to handle GraphQL.

      Enabling TangoGQL to handle more than one Tango database.

      Show
      Mitigation of security vulnerability. Porting to a more modern set of libraries to handle GraphQL. Enabling TangoGQL to handle more than one Tango database.
    • Hide

      Compared to the current TangoGQL implementation we have:

      • verified if the prototype supports multithreading (necessary for supporting multiple TLRs provided at runtime)
      • verified if the prototype supports the same mutations, queries, subscriptions used now
      • verified if the prototype is capable of same performances 
      • understood a suitable testing approach to follow for component testing
      Show
      Compared to the current TangoGQL implementation we have: verified if the prototype supports multithreading (necessary for supporting multiple TLRs provided at runtime) verified if the prototype supports the same mutations, queries, subscriptions used now verified if the prototype is capable of same performances  understood a suitable testing approach to follow for component testing
    • 3
    • 3
    • 0
    • Team_CREAM
    • Sprint 4
    • Hide

      Currently, TangoGQL Ariadne doesn't support accessing multiple Tango DBs.

      Performance evaluation and final decision captured here. Locust has been added to Taranta suite to enable future benchmarking. 

      An initial testing infrastructure has been added to the TnagoGQL-Ariadne project. MR available here. 

      Schema comparison available here

      As part of the evaluation we also considered the following: Compatibility with Taranta, the capacity needed to implement envisaged changes to the code (suggested as TODOs in the current version) and metrics functionalities. More details are available in the documentation linked to child stories.

      Show
      Currently, TangoGQL Ariadne doesn't support accessing multiple Tango DBs. Performance evaluation and final decision captured here . Locust has been added to Taranta suite to enable future benchmarking.  An initial testing infrastructure has been added to the TnagoGQL-Ariadne project. MR available here .  Schema comparison available here As part of the evaluation we also considered the following: Compatibility with Taranta, the capacity needed to implement envisaged changes to the code (suggested as TODOs in the current version) and metrics functionalities. More details are available in the documentation linked to child stories.
    • 23.6
    • Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
    • Taranta

    Description

      The current TangoGQL used in Taranta is obsolete. It uses python < 3.10 with key libraries like graphene and graphene-sockets which are not maintained any more. This constitute a serious potential security vulnerability and a potential disruption of future work.

      As a consequence, in MaxIV a new prototype of TangoQGL was developed and is being at the moment evaluated.

      We need to evaluate that prototype in order to determine its suitability w.r.t. SKAO needs.

      Attachments

        Issue Links

          informs

          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-4567 refactor TangoGQL to include Ariadne

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

          Structure

            Activity

              People

                g.brajnik Brajnik, Giorgio
                g.brajnik Brajnik, Giorgio
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (52.33%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do720.5
                  In Progress   00.0
                  Complete1022.5
                  Total1743.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel