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

Standard way to collect/share dashboards and to pack them

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

Details

    • Obs Mgt & Controls
    • Hide

      As said above, users different from dashboard developers have a way to locate, find, store dashboards that are relevant to a specific product.

      The need to pack dashboards is because:

      • during redeploy of Taranta existing dashboards are wiped out - in this way a user could store them locally and possibly re-import them.
      • if there are crashes of the persistent volume that stores Mongodb the user loses existing dashboards - the zip file acts as a backup
      • to populate the bucket store certain users could download all dashboards and then selectively upload them into the bucket.
      Show
      As said above, users different from dashboard developers have a way to locate, find, store dashboards that are relevant to a specific product. The need to pack dashboards is because: during redeploy of Taranta existing dashboards are wiped out - in this way a user could store them locally and possibly re-import them. if there are crashes of the persistent volume that stores Mongodb the user loses existing dashboards - the zip file acts as a backup to populate the bucket store certain users could download all dashboards and then selectively upload them into the bucket.
    • Hide

      Given an  environment where Taranta is running, there are mechanisms for:

      • discovering existing dashboards available for that environment
      • in the environment , dashboards are available to the user in the right versions and for the right products as deployed. (e.g. no DISH dashboard in LOW, no dashboard for CSP 2.0 if only CSP 1.0 is available … )
      • a user can examine available dashboards and decide which ones to open, edit and run
      • there are means for exporting, importing and backing up dashboard into such a mechanism
      Show
      Given an  environment where Taranta is running, there are mechanisms for: discovering existing dashboards available for that environment in the environment , dashboards are available to the user in the right versions and for the right products as deployed. (e.g. no DISH dashboard in LOW, no dashboard for CSP 2.0 if only CSP 1.0 is available … ) a user can examine available dashboards and decide which ones to open, edit and run there are means for exporting, importing and backing up dashboard into such a mechanism
    • Inter Program
    • 2
    • 3
    • 0

    • Component Version REL-1135 Taranta-Dashboards v1.5.0

      Sub-system Version REL-1134 Taranta v2.6.0

    • Team_CREAM
    • Sprint 3
    • Hide

      New releases:

      The new charts are released:

      Docs are updated: 

       

      There is a new presentation and demo record to explain the new system:

      This is still not officially working on all SKA servers since System Team needs to update the DNS on AWS so we can have a secure connection, that will be only done next sprint, hence it could be better to close this story to work on other matters and have a smaller one next sprint to help in anything that could be needed. 

      Show
      New releases: Taranta-Dashboards v1.5.0  https://jira.skatelescope.org/browse/REL-1135   Taranta v2.6.0  https://jira.skatelescope.org/browse/REL-1134   Taranta auth chart V 0.2.0  https://jira.skatelescope.org/browse/REL-1186   The new charts are released: Taranta:  ska-tango-taranta:2.6.0 TangoGQL:  ska-tango-tangogql:1.3.10 Taranta-Dashboard:  ska-tango-taranta-dashboard:1.5.0 Taranta-Auth:  ska-tango-taranta-auth:0.2.0 Docs are updated:  https://taranta.readthedocs.io/en/sp-3853-standard-way-collect-dashboard/sharing_dashboard.html https://taranta.readthedocs.io/en/sp-3853-standard-way-collect-dashboard/dashboard_env.html https://developer.skao.int/projects/ska-tango-taranta-suite/en/latest/   There is a new presentation and demo record to explain the new system: https://docs.google.com/presentation/d/164KbAHZ-02UfaBhZYQURkjYlLY2o-REm8-38iERKI7k/edit#slide=id.g2b52c01379d_0_0 https://drive.google.com/file/d/1y9XpNYbo661dZe-M9RnEQ0kWxSRw7b3M/view?usp=drive_link   This is still not officially working on all SKA servers since System Team needs to update the DNS on AWS so we can have a secure connection, that will be only done next sprint, hence it could be better to close this story to work on other matters and have a smaller one next sprint to help in anything that could be needed. 
    • 21.6
    • Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI24 - UNCOVERED

    • Taranta Team_CREAM

    Description

      We need a way to 

      Establish a standard way to collect and deploy Taranta dashboards across products  so that the following needs are fulfilled:

      • As a development team, how do I publish a taranta dashbboard so that it's available in the deployment of my software
      • As a user, how do I get to know what dashboards are available in the system as currently deployed 

      The above words are by m.bartolini in a miro board (with minor edits by GB): https://miro.com/app/board/uXjVMjgGvaY=/?moveToWidget=3458764568733374333&cot=14

      Important note

      • it is important that the storage mechanism can be accessed via http, so that we don't tie the solution to a specific provider (like AWS). 

      In addition, there should be a way from the Taranta GUI to locally export all existing dashboards  by packing them into a zip file that is downloaded to the local PC. 

      Attachments

        Issue Links

          Child Of

          Capability - SAFe program capability SS-117 Com-C3: Sub-system level software release & delivery improvements

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

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-1134 Taranta v2.6.0

          • Released

          Component Version - Component/module/library releases REL-1135 Taranta-Dashboards v1.5.0

          • Released
          mentioned in

          Page Loading...

          mentioned on

          GitLab Commit - SP-3853

          GitLab Commit - SP-3853: merge develop, fix conflicts

          GitLab Commit - SP-3853 allow widget library if dash is not selected

          GitLab Commit - SP-3853 Hide READ ONLY DASH msg when no dash is selected

          GitLab Commit - SP-3853 Move const to config

          GitLab Commit - SP-3853 removed extra code

          GitLab Commit - SP-3853 Reverted develop code

          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: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1426.0
                  Total1426.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel