Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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:

  • Maccabee Levine From discussion with PC, prefer not to consider reference environments for night/weekend shutdowns.  Consensus agrees.
    • Peter Murray didn't calculate estimate since councils didn't want to do it.  If time allows still put into report, otherwise never mind.
  • Yogesh Kumar what was left?  weekday schedule?  Yogesh will review through Monday.  Let us know in Slack one way or the other.

Budgets / Cost Anomaly Detection

...

Today:

  • Yogesh Kumar will ask again about Kafka difference.  Or forget about it.

Reviewing Environments to Shut Down

...

  • 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:

  • Yogesh Kumar will wrap up dev permissions by early next week.

Off-hours shutdown during weekday evenings (team environments)

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:

  • If time.  Otherwise just go with weekends for phase 1.

One-time estimate?

Last time:

...