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

redirect sw.lsstcorp.org -> eups.lsst.codes

    Details

      Description

      So as to not 'orphan' pre-existing newinstall.sh installs that have an EUPS_PKGROOT pointed at sw.lsstcorp.org, an http redirect should be put in place to the new URL.

      Iain Goodenow has agreed to change the sw.lsstcorp.org CNAME when we are ready. Bill Glick has provided a copies of the tls private key/cert.

        Attachments

          Issue Links

            Activity

            Hide
            jhoblitt Joshua Hoblitt added a comment -

            Adam Thornton The gem turned out to be a bit of a pita on el7 due to the old system ruby but I think I've come up with a reasonable solution by using an SCL. I've opened a PR that adds cut'n'pastable install instructions for sensu-plugins-http, checks for sw.lsstcorp.org, and additional checks for eups.lsst.codes. Needless to say, the nagios configs are untested as there is no automated deployment to test with.

            Show
            jhoblitt Joshua Hoblitt added a comment - Adam Thornton The gem turned out to be a bit of a pita on el7 due to the old system ruby but I think I've come up with a reasonable solution by using an SCL. I've opened a PR that adds cut'n'pastable install instructions for sensu-plugins-http , checks for sw.lsstcorp.org, and additional checks for eups.lsst.codes. Needless to say, the nagios configs are untested as there is no automated deployment to test with.
            Hide
            athornton Adam Thornton added a comment -

            I guess that's a good reason to do this. Please document what the package requirements are for Ruby although since creation of status is not in fact automated it's less of a priority than it would be if the thing were properly put together in the first place.

            This would be a good example of the prototype sticking around, I guess.

            Show
            athornton Adam Thornton added a comment - I guess that's a good reason to do this. Please document what the package requirements are for Ruby although since creation of status is not in fact automated it's less of a priority than it would be if the thing were properly put together in the first place. This would be a good example of the prototype sticking around, I guess.
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            The motivation here is that the redirect url already got broken once by accident.

            Show
            jhoblitt Joshua Hoblitt added a comment - The motivation here is that the redirect url already got broken once by accident.
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            The `-f` flag only states checks that there is a redirect, not what url is redirected to.

            Show
            jhoblitt Joshua Hoblitt added a comment - The `-f` flag only states checks that there is a redirect, not what url is redirected to.
            Hide
            athornton Adam Thornton added a comment -

            What is the advantage of pulling Ruby in versus adding the -f follow option to the existing check_http check?

            https://www.monitoring-plugins.org/doc/man/check_http.html

            Show
            athornton Adam Thornton added a comment - What is the advantage of pulling Ruby in versus adding the -f follow option to the existing check_http check? https://www.monitoring-plugins.org/doc/man/check_http.html

              People

              • Assignee:
                jhoblitt Joshua Hoblitt
                Reporter:
                jhoblitt Joshua Hoblitt
                Reviewers:
                Adam Thornton
                Watchers:
                Adam Thornton, Angelo Fausti, Bill Glick, John Swinbank, Jonathan Sick, Joshua Hoblitt, Kian-Tat Lim, Tim Jenness
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel