Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-1598

Load Test automation - Automate Spinning Up/Down Sandbox environment

    Details

    • Sprint:
      CFAMX 2019R2 Sprint 2
    • SCRUM Team:
      Globogym Purple Cobras
    • SOW (Time Tracking) Project:
      44918
    • Work Type Classification:
      Sustaining

      Description

      As a developer I want a way that I can easily spin up/spin down the sandbox environment so that the environment is not running when not in use

      Notes

      • App Server - AWSCFASBAPPV001
      • Web Servers - AWSCFASBWEBV001, AWSCFASBWEBV002, AWSCFASBWEBV003
      • DB Server - AWSCFASBSQLV001
      • Redis Server - AWSCFAREDV001
      • This solution should be built in such a way that it can plug in to a larger automation framework

      Acceptance Criteria

      1. There is a one click solution that allows the environment to be spun up
      2. There is a one click solution that allows the environment to be spun down
      3. Investigate options into scheduling the shutdown
      4. Credentials should be passed in to be used to access AWS

        Attachments

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              • Assignee:
                will.englefield Will Englefield (Inactive)
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 48h Original Estimate - 48h
                  48h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 61h 35m
                  61h 35m

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.