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

Production update

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Joshua Hoblitt some requirements for the SQuaSH production update

      We are going to use branch DM-8976 since there are some improvements to do before merging to master, but we decided to update production anyway. Here is the git ref

      https://github.com/lsst-sqre/qa-dashboard/commit/ec73d32887a76a68251294b5c844ed5fc70fb0ba

      This version of SQuaSH requires post-qa 1.3.1, note that there are some changes in the post-qa command line, in particular the API URL which now points to the root, a typical command line I use for testing is:

      post-qa --lsstsw ~/Projects/lsstsw/lsstsw/ --qa-json tests/data/Cfht_output_r.json --api-url  http://localhost:8000/dashboard/api/ --api-user nobody --api-password admin
      

      There is also a new DB migration 0004 that was successfully tested using a dump of the production database following the instructions at:

      https://github.com/lsst-sqre/sandbox-jenkins-demo/blob/42fdaaf8c53771c1ae940efedba43a68b4dc654b/squash.md

        Attachments

          Issue Links

            Activity

            Hide
            afausti Angelo Fausti added a comment -

            Joshua Hoblitt just merged DM-8976 before deployment, my test instance is running on master now:

            https://angelo-squash-squash.lsst.codes

            Show
            afausti Angelo Fausti added a comment - Joshua Hoblitt just merged DM-8976 before deployment, my test instance is running on master now: https://angelo-squash-squash.lsst.codes
            Hide
            afausti Angelo Fausti added a comment - - edited

            End-to-end test with post-qa 1.3.1

            Follow SQuaSH README to set up a fresh installation and start SQuaSH

            Running post-qa 1.3.1 locally with the same DB user password set in the previous step:

            post-qa --lsstsw ~/Projects/lsstsw/lsstsw/ --qa-json tests/data/Cfht_output_r.json --api-url  http://localhost:8000/dashboard/api/ -api-user <user> --api-password <passwd>
            

            You should get the following output:

             
            POST http://localhost:8000/dashboard/apimetrics/ status: 201
            POST http://localhost:8000/dashboard/apijobs/ status: 201
            

            Show
            afausti Angelo Fausti added a comment - - edited End-to-end test with post-qa 1.3.1 Follow SQuaSH README to set up a fresh installation and start SQuaSH Running post-qa 1.3.1 locally with the same DB user password set in the previous step: post-qa --lsstsw ~ /Projects/lsstsw/lsstsw/ --qa-json tests /data/Cfht_output_r .json --api-url http: //localhost :8000 /dashboard/api/ -api-user <user> --api-password < passwd > You should get the following output:   POST http: //localhost :8000 /dashboard/apimetrics/ status: 201 POST http: //localhost :8000 /dashboard/apijobs/ status: 201
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            Problems with the hypermedia urls being returned by DRF being http intead of https were discovered post deployment. This is causing post-qa to silently fail.

            Show
            jhoblitt Joshua Hoblitt added a comment - Problems with the hypermedia urls being returned by DRF being http intead of https were discovered post deployment. This is causing post-qa to silently fail.

              People

              Assignee:
              jhoblitt Joshua Hoblitt
              Reporter:
              afausti Angelo Fausti
              Watchers:
              Angelo Fausti, Frossie Economou, Joshua Hoblitt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: