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

CAR Caching proxies for upstream dependent artefacts for helm charts

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

Details

    • Services
    • Hide

      In order to have a reliable, secured supply chain any artefact required by SKAO should be hosted within SKAO where we can access it safely, quickly and maintain its lifecycle. To achieve this we need to host both our own artefacts and any upstream artefacts we depend on. This is also in line with 7 R's of a supply chain (in the logistics world: Getting the Right product, in the Right quantity, in the Right condition, at the Right place, at the Right time, to the Right customer, at the Right price).

       

      To achieve a complete supply chain, it's important we first start with CAR as a first step and trickle down to each location as proxies and caches.

      Show
      In order to have a reliable, secured supply chain any artefact required by SKAO should be hosted within SKAO where we can access it safely, quickly and maintain its lifecycle. To achieve this we need to host both our own artefacts and any upstream artefacts we depend on. This is also in line with 7 R's of a supply chain (in the logistics world: Getting the Right product, in the Right quantity, in the Right condition, at the Right place, at the Right time, to the Right customer, at the Right price) .   To achieve a complete supply chain, it's important we first start with CAR as a first step and trickle down to each location as proxies and caches.
    • Hide
      • Following types of upstream artefacts are cached in CAR by setting up proxies: helm
        • Investigate and use OCI registries as helm repositories [Helm | Use OCI-based registries|https://helm.sh/docs/topics/registries/]
      • CAR and proxies is connected with the appliances. i.e. 
        • playbooks are updated to use CAR as a proxy 
        • Servers are redeployed with the above config
      Show
      Following types of upstream artefacts are cached in CAR by setting up proxies: helm Investigate and use OCI registries as helm repositories  [Helm | Use OCI-based registries|https://helm.sh/docs/topics/registries/] CAR and proxies is connected with the appliances. i.e.  playbooks are updated to use CAR as a proxy  Servers are redeployed with the above config
    • 1
    • 1
    • 0

    • PI23 - UNCOVERED

    • Team_SYSTEM

    Description

      The SKAO provides a Central Artefact Repository based on Nexus Repository Manager3.  This has built in capabilities for caching from upstream sources for most artefact types (formats) that it can support.  The key SKAO published artefacts are OCI Images, Python libraries, Conan packages, Helm charts, and Raw artefact types. 

      The SKAO will also provide mirroring of upstream official artefact repositories - these include OCI Images (docker.io, quay.io, gcr.io), Apt (Ubuntu), Helm (public, Ceph, GitHub, GitLab), PyPi.

      These two caches will provide an authoritative source and logistics support for SKAO related artefacts.  The PoP Nexus instance points to these to provide local caching services for any software deployments and will be integrated with deployment and software building processes in the PoP location - eg: Kubernetes, containers, Docker, Podman etc.

      The caching facility will help with the speed of deployment issues in geographically dispersed locations, and the cache can be primed to support use cases where it is necessary to avoid the first-hit latency problem.

      Attachments

        Issue Links

          Child Of

          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-142 AA0.5 software configuration & deployment

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Implementing
          clones

          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-3098 CAR Caching proxies for upstream dependent artefacts for apt packages

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done

          Structure

            Activity

              People

                P.Harding Harding, Piers
                U.Yilmaz Yilmaz, Ugur
                Votes:
                0 Vote for this issue
                Watchers:
                1 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:

                    Structure Helper Panel