Attendees:
Off-Hours Guidelines
D4. Define guidelines/best practices around pausing/stopping environments when they're not in use - e.g. off-hours/weekends/etc.
...
- Yogesh Kumar still a few things to wrap up with Kitfox (updating document), hopefully wrapping up today.
- Peter Murray still to look at the weekend cost savings estimate for reference release environments.
Today:
Budgets / Cost Anomaly Detection
D5. Create AWS Budgets and AWS Budget Alerts for daily and monthly spend rates
...
- Review draft environment "price list" / "recipes" from Yogesh Kumar if ready.
- Yogesh presented: Namespace configurations costs estimation
- Consensus looks good!
- Yogesh Kumar will double-check Kafka embedded vs. shared – why is shared more expensive?
- Add "daily" by price in each table.
Today:
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)
...
- Mark Veksler draft guidelines on who should have permissions to what operations in AWS. What will each team be allowed to do. Link from ACRG doc.
- Permissions on operations in AWS? Right now AWS is just Kitfox, but Jenkins jobs are available to dev teams.
- Kitfox prefers a self-service model.
- Yogesh Kumar will update the environment lifecycle document to indicate what dev teams can do.
Today:
Off-hours shutdown during weekday evenings
Last time / prior:
- Kitfox is looking at this. What would work best for each team? Ticket pending.
- We can at least look at the findings, and decide to do something or not. Harder b/c geographical spread.
- Yogesh Kumar still investigating
Today:
One-time estimate?
Last time:
- So ACRG has something to base it on in future years. Estimate and how we made it.
- Treasurer probably about to ask anyway.
- Peter Murray think about a process. Reconstruct from past years, bring to the group.
...