Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-2484

Investigate: Tooling to automate testing Terrain API

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Story Points:
      2
    • Sprint:
      Summer 5: 3 Aug - 14 Aug, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Fall 1: 14 Sep - 25 Sep, Fall 2: 28 Sep - 9 Oct, Fall 3: Oct 12 - Oct 23

      Description

      We use the Terrain API to communicate with CyVerse resources.

      We need some kind of "health check" systems for the APIs to ensure that if CyVerse changes their API, we will know about it right away.

      For this task, investigate tooling we could use for this.

      Develop a proof-of-concept prototype that demonstrates testing an endpoint.

        Attachments

          Issue Links

            Activity

            Hide
            cdias1 Chester Dias (Inactive) added a comment -

            will do that

            Show
            cdias1 Chester Dias (Inactive) added a comment - will do that
            Hide
            cdias1 Chester Dias (Inactive) added a comment -

            Nowlan Freese Please let me know the status of the points we discussed during the meeting.

            Show
            cdias1 Chester Dias (Inactive) added a comment - Nowlan Freese Please let me know the status of the points we discussed during the meeting.
            Hide
            nfreese Nowlan Freese added a comment - - edited

            [~aloraine] - Chester and I had a couple of questions:

            Should we configure the database to only store the last ~2 weeks of data?

            • AL - this sounds fine. Probably you do not need that much. Mainly you just need to make sure that if the API changes you will know about it.

            We are not sure how much data is generated every 24 hours, but there are around 30 endpoints generating data every 10 minutes.

            • AL - every ten minutes is too much. Once an hour or even once a day is probably fine.

            What do we need to do to configure the EC2 to not be shut down each night?

            • AL - Change "Stack" tag to "Prod"

            Since these questions may expand the scope of this ticket we may need to close this ticket and create additional tickets.

            I've created a brief document with the notes I took from Chester's demo: https://docs.google.com/document/d/1U6VMjM7FsxGGCsYvaCcsWSBrnhQQwwun2GA-iLC8NWE/edit?usp=sharing

            Show
            nfreese Nowlan Freese added a comment - - edited [~aloraine] - Chester and I had a couple of questions: Should we configure the database to only store the last ~2 weeks of data? AL - this sounds fine. Probably you do not need that much. Mainly you just need to make sure that if the API changes you will know about it. We are not sure how much data is generated every 24 hours, but there are around 30 endpoints generating data every 10 minutes. AL - every ten minutes is too much. Once an hour or even once a day is probably fine. What do we need to do to configure the EC2 to not be shut down each night? AL - Change "Stack" tag to "Prod" Since these questions may expand the scope of this ticket we may need to close this ticket and create additional tickets. I've created a brief document with the notes I took from Chester's demo: https://docs.google.com/document/d/1U6VMjM7FsxGGCsYvaCcsWSBrnhQQwwun2GA-iLC8NWE/edit?usp=sharing
            Hide
            ann.loraine Ann Loraine added a comment -

            Please create a Jira ticket to automate the startup process.

            Currently the steps are manual as per the documentation above:

            In the event that the EC2 is turned off, the various services need to be manually turned back on in the correct order for the dashboard to work correctly:

            cd /home/ubuntu/influxdb-1.8.2-1/usr/bin
            nohup ./influxd -config ../../etc/influxdb/influxdb.conf &
            cd /home/ubuntu/telegraf-1.15.3/usr/bin
            nohup ./telegraf -config ../../etc/telegraf/telegraf.conf &
            cd /home/ubuntu/grafana-7.2.0/bin
            nohup ./grafana-server &

            Show
            ann.loraine Ann Loraine added a comment - Please create a Jira ticket to automate the startup process. Currently the steps are manual as per the documentation above: In the event that the EC2 is turned off, the various services need to be manually turned back on in the correct order for the dashboard to work correctly: cd /home/ubuntu/influxdb-1.8.2-1/usr/bin nohup ./influxd -config ../../etc/influxdb/influxdb.conf & cd /home/ubuntu/telegraf-1.15.3/usr/bin nohup ./telegraf -config ../../etc/telegraf/telegraf.conf & cd /home/ubuntu/grafana-7.2.0/bin nohup ./grafana-server &
            Hide
            nfreese Nowlan Freese added a comment -

            Created IGBF-2570.

            Show
            nfreese Nowlan Freese added a comment - Created IGBF-2570 .

              People

              • Assignee:
                cdias1 Chester Dias (Inactive)
                Reporter:
                ann.loraine Ann Loraine
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: