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

Pull containers from alternate repositories for CANFAR Science Platform

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

Details

    • SRCnet
    • Hide

      BH: Enable the use of public Docker images from registries other than Harbor with the v0.1 Science Platform. This is required to use the Science Platform to execute the many tests for v0.1 that already exist in SRCNet gitlab and other repositories.

       

      Show
      BH: Enable the use of public Docker images from registries other than Harbor with the v0.1 Science Platform. This is required to use the Science Platform to execute the many tests for v0.1 that already exist in SRCNet gitlab and other repositories.  
    • Hide

      AC: A mechanism to cache image listings from Harbor repositories has been developed (met in PI23).

      AC: A skaha that is configured with a Harbor registry and a local docker registry can retrieve images from each of the registries and launch that image. This can be done for each of the four types of currently supported skaha Job types.

      Show
      AC: A mechanism to cache image listings from Harbor repositories has been developed (met in PI23). AC: A skaha that is configured with a Harbor registry and a local docker registry can retrieve images from each of the registries and launch that image. This can be done for each of the four types of currently supported skaha Job types.
    • 3
    • 1
    • 0
    • Team_INDIGO
    • Sprint 4

    • PI24 - UNCOVERED

    • PI24-PB SRC23-PB SRCNet0.1 science-platform-services
    • SPO-3479

    Description

      If the Docker image labels that direct the skaha service behaviour when launching a user sessions (`type`) are provided as part of a curl CLI invocation, this will enable the use of public images from non-Harbor image repositories.

      Is the current Harbor query non-standard?

      Constraint: need to know the label/type of the image before it's started, so that it can be started properly.

      Constraint: do not lose the capability to "label" an image without having to completely rebuild the image.

      [update]: with the removal of support for proprietary images, the approach to the implementation of this Feature has changed. See the comment with content from Brian Major for a more complete description.

       

      Steps:

      1. Figure out the delta between Harbor and the OCI spec.
        1. Is listing a standard of OCI registries?
      2. Is it possible to get all the metadata from the images so that skaha has the information before it launches the jobs.
      3. If all calls are OCI-compliant, determine how to fill in what the Harbor API provides.

      Attachments

        Issue Links

          Child Of

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-4869 Science Gateway v0.1 - Roadmap

          • Not Assigned - Priority is not assigned yet.
          • Implementing
          mentioned in

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                S.Mookherjee Mookherjee, Saurabh
                s.goliath sharon goliath
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do53.0
                  In Progress   10.0
                  Complete00.0
                  Total63.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel