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

Complete SRCNet v0.1 compulsory service documentation

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

Details

    • SRCnet
    • Hide

      SOG and SRCNet will benefit from having the documentation in one place for all the services that will be part of SRCNet v0.1, 

      Including a simple CI/CD procedure for those installation methods that allow it, it will be possible to validate if the installation is correct and functional, and therefore reliable, and also to know if new versions can be installed.

      Show
      SOG and SRCNet will benefit from having the documentation in one place for all the services that will be part of SRCNet v0.1,  Including a simple CI/CD procedure for those installation methods that allow it, it will be possible to validate if the installation is correct and functional, and therefore reliable, and also to know if new versions can be installed.
    • Hide

      AC1: The official SRCNet documentation includes complete deployment documentation for all compulsory local and global services required for SRCNet0.1

      AC2: Each page of the documentation has been peer reviewed by the SOG, including at least 2 SRCs - not including the page author(s)

      (Stretch) AC3: At least one person from each v0.1 SRC has contributed at least one update to the documentation.

      AC4: An integration test per compulsory local service is defined, to check the integration with the global service.

      (Stretch) AC5: For each compulsory service, at least one SRC has used the documentation to deploy the service without further assistance (hence validated the documentation)

      Show
      AC1: The official SRCNet documentation includes complete deployment documentation for all compulsory local and global services required for SRCNet0.1   https://ska-telescope.gitlab.io/src/kb/ska-src-docs-operator/ (see section 5 Software Stack  and https://miro.com/app/board/uXjVK0qVHVs=/ ) multiple new documentation articles need to be written as part of this feature AC2: Each page of the documentation has been peer reviewed by the SOG, including at least 2 SRCs - not including the page author(s) (Stretch) AC3: At least one person from each v0.1 SRC has contributed at least one update to the documentation. AC4: An integration test per compulsory local service is defined, to check the integration with the global service. (Stretch) AC5: For each compulsory service, at least one SRC has used the documentation to deploy the service without further assistance (hence validated the documentation)
    • 3
    • 2
    • 0
    • Team_CORAL

    • PI24 - UNCOVERED

    • PI24-PB SRCNet0.1

    Description

      In PI23: SP-4249 - Documentation of SRCNet v0.1 compulsory services deployment - Releasing.

      ) we compiled the available documentation on the installation of the SRCNet v.0.1 compulsory local services ( as listed within the implementation plan document, section Software Stack), including different versions and installation modes.

      For this feature the idea is to a) complete the documentation adding information related to the SRCNet v0.1 compulsory global services as well as the global/local optional services ( see Software Stack section in the Implementation plan document ), b) validate that the installation methods for all documented software are correct and work (both manual and CI/CD installations), and c) improve the organisation of the site documentation created in the Feature SP-4249 https://ska-telescope.gitlab.io/src/kb/ska-src-docs-operator/

       

      All feedback received on the linked item SP-4249. should be addressed.
      Consider the option of including video links where deployments have been demonstrated.
      Include troubleshooting documentation - steps to follow in case of errors / known issues.

      Attachments

        Issue Links

          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-4548 Science Gateway Deployment Improvements

          • 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.
          • Implementing
          mentioned in

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                b.mort Mort, Ben
                S.SanchezExposito Sanchez Exposito, Susana
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do22.0
                  In Progress   44.0
                  Complete00.0
                  Total66.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel