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

Resolve two-namespaces-one-volume issues in Cavern

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

Details

    • SRCnet
    • Hide

      When deploying the Science Platform CANFAR stack, which is part of the v0.1 optional services (but is often used to provide mandatory services, such as containerised visualisation tools), one of the services comprising this stack is Cavern. There's an issue where the Cavern deployment can't be automatically deployed, requiring manual intervention to fix an issue related to a single volume that needs to be available on two different namespaces.

      Resolving this would bring Cavern on par with the other services of the platform which can be deployed via standard tools such as Helm/kubectl without requiring further intervention/patching, and alleviate the maintenance as well.

      Show
      When deploying the Science Platform CANFAR stack, which is part of the v0.1 optional services (but is often used to provide mandatory services, such as containerised visualisation tools), one of the services comprising this stack is Cavern. There's an issue where the Cavern deployment can't be automatically deployed, requiring manual intervention to fix an issue related to a single volume that needs to be available on two different namespaces. Resolving this would bring Cavern on par with the other services of the platform which can be deployed via standard tools such as Helm/kubectl without requiring further intervention/patching, and alleviate the maintenance as well.
      • Cavern can be deployed via standard tools without requiring additional manual patching/intervention.

    • PI24 - UNCOVERED

    • PI24-PB SRCNet0.x Team_RED

    Description

      Multiple SRCs have deployed Cavern as part of the Science Platform stack, but due to the two-namespace-single-volume issue, manual intervention has always been necessary. This issue and a way to fix this via some manual patching have been documented here: https://confluence.skatelescope.org/display/SRCSC/Sharing+storage+between+PVCs+across+namespaces.

      This feature is for finding a solution to this issue. 

      It would probably be in everybody's interest if this manual intervention was not required, allowing for not just seamless installations using only standard tools, but also for maintainability for not having to keep around a "special" PV that was manually patched, which might be brittle (if the original PV changes for any reason, one would have to again manually patch the other clone, etc).

      (Some discussion around this topic happend in the past in Slack here here)

      Attachments

        Structure

          Activity

            People

              P.Llopis Llopis, Pablo
              P.Llopis Llopis, Pablo
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Feature Progress

                Story Point Burn-up: (0%)

                Feature Estimate: 0.0

                IssuesStory Points
                To Do00.0
                In Progress   00.0
                Complete00.0
                Total00.0

                Dates

                  Created:
                  Updated:

                  Structure Helper Panel