Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-31444

Portal application: devise a means to configure the list of known TAP servers without rebuilding the Portal/suit container image

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: In Progress
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: SUIT
    • Labels:
      None
    • Story Points:
      10
    • Team:
      Portal

      Description

      The RSP is being deployed at multiple sites.

      We have received a reasonable request from the staff at those other sites to facilitate their including additional (typically local) TAP services in the list that is pre-configured into the Portal application. Currently this list is expressed as JavaScript code in the lsst/suit repository.

      While this would be easy to change in a fork, or in an entirely custom site-specific application, it would be simpler for the remote sites, and (I suspect) possibly less likely to produce confusion and support requests in deployments, if the server list (and perhaps other application parameters - Firefly calls them "properties") could be overridden via some mechanism layered on top of the Rubin-built container images for the Portal.

      Configurations on the Firefly server side of the client-server pair are easier to override in this way because of the ability to set up filesystem contents visible inside the running container at the time the container is started (e.g., via content in Helm charts).

      It is less obvious how to provide container-start-time overrides accessible to the Firefly JavaScript code.

      The task in this ticket is to work with both SQuaRE and the core Firefly team to devise a mechanism by which deployment-time overrides can be configured which are accessible to the Portal JavaScript code.

      This will undoubtedly be useful beyond the remote-site deployments - it's easy to see how this would be helpful just in managing the O(10) internal deployments and their different features.

        Attachments

          Issue Links

            Activity

            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            Note that subsequently DM-33531 and DM-34492 have been filed covering essentially the same point.

            Show
            gpdf Gregory Dubois-Felsmann added a comment - Note that subsequently DM-33531 and DM-34492 have been filed covering essentially the same point.
            Hide
            gpdf Gregory Dubois-Felsmann added a comment - - edited

            Shadowed by https://jira.ipac.caltech.edu/browse/FIREFLY-995 at IPAC.

            Copied from that ticket:


            [Other] top items for Helm-chart configuration would be:

            • The image dataset(s) to be used for context/coverage images
            • In particular, the HiPS image to be used, and control over whether or not any source of FITS images is used instead of HiPS when zooming in
            • The "curated" list of HiPS image maps available in the "Change HiPS" menu

            These items will be essential to be changeable between different Rubin deployments, because:

            • The "Data Preview 0" deployment(s) will need to have access to HiPS image maps created and hosted by Rubin and based on simulated data, and coverage images should never zoom in to 2MASS or any other real-sky images
            • The Rubin summit-related deployments (e.g., for AuxTel and ComCam) should default to real-sky images
            Show
            gpdf Gregory Dubois-Felsmann added a comment - - edited Shadowed by https://jira.ipac.caltech.edu/browse/FIREFLY-995 at IPAC. Copied from that ticket: [Other] top items for Helm-chart configuration would be: The image dataset(s) to be used for context/coverage images In particular, the HiPS image to be used, and control over whether or not any source of FITS images is used instead of HiPS when zooming in The "curated" list of HiPS image maps available in the "Change HiPS" menu These items will be essential to be changeable between different Rubin deployments, because: The "Data Preview 0" deployment(s) will need to have access to HiPS image maps created and hosted by Rubin and based on simulated data, and coverage images should never zoom in to 2MASS or any other real-sky images The Rubin summit-related deployments (e.g., for AuxTel and ComCam) should default to real-sky images
            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            Loi Ly has previously suggested that the solution to this will look like a request from the client to the Firefly server for the TAP service list, rather than embedding the TAP service list in the JavaScript application code for the client.

            Show
            gpdf Gregory Dubois-Felsmann added a comment - Loi Ly has previously suggested that the solution to this will look like a request from the client to the Firefly server for the TAP service list, rather than embedding the TAP service list in the JavaScript application code for the client.
            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            Supported by Firefly 2022.2, currently in pre-release testing on the IDF RSP.

            Show
            gpdf Gregory Dubois-Felsmann added a comment - Supported by Firefly 2022.2, currently in pre-release testing on the IDF RSP.

              People

              Assignee:
              roby Trey Roby
              Reporter:
              gpdf Gregory Dubois-Felsmann
              Watchers:
              Frossie Economou, Gregory Dubois-Felsmann, Loi Ly, Russ Allbery, Trey Roby
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:

                  Jenkins Builds

                  No builds found.