Attendees:
Agenda:
Reviewing Environments to Shut Down
D2. Define a process for reviewing existing tools and environments for candidates to be shut down (e.g. when a team leaves the project or the env is no longer needed)
- Drafted AWS Environment Lifecycle sections on "Dev Team Review / Extending an Environment" and "Monitoring Existing Environments" from discussion last week.
- Feedback?
- Who should actually start up and shut down the environments – dev teams or Kitfox? Should dev teams be admins?
AWS Cost Review Group
D3. Identify who is responsible for each part of these processes and what reporting requirements are needed
- Re-drafted AWS Cost Review Group from discussion last week.
- Feedback?
Off-Hours Guidelines
D4. Define guidelines/best practices around pausing/stopping environments when they're not in use - e.g. off-hours/weekends/etc.
- Kitfox completed RANCHER-685 to study solutions. Wrote up: Downscale modules instances during weekend(night) RANCHER-685
- Is that doc the "guidelines / best practices"? Or is there additional work to pick one of the two proposed solutions as the best practice?
- Minutes last week say "This will take effect from 6PM EST (Friday) until 6:30 PM EST (Sunday) starting from 21st of April." but not in the guidelines?
- Where the AWS Environment Request asks "Will the dev team be following (these guidelines) ... Explain any planned divergence from those guidelines"... does that make sense?
Budgets / Cost Anomaly Detection
D5. Create AWS Budgets and AWS Budget Alerts for daily and monthly spend rates
D6. Explore AWS Cost Anomaly Detection and Rightsizing Recommendations
- Are there Jiras for these yet? Sprints identified?