2023-07-28 Minutes
Attendees:
CC Feedback
- Simeon re the Cost Review Group page: I like this proposal. Should there be a specific goals for "periodic" review of user permissions and the timeline of reporting on the budget?
- User permissions:
- Mark Veksler : align with flower releases. Less frequent can be a security risk if someone rolls off the project. Shouldn't take long.
- Group agrees.
- Budget reporting:
- Mark Veksler set annual budget at start of FY. Submit to CC for approval. Review in alignment with flower releases.
- Change 'review" to "set" the budgets, budget alerts, etc. annually.
- Kitfox reports on actual AWS costs after every sprint (2w). Report maybe monthly on their portion? If Peter Murray turned it into the overall report.
- Mark Veksler set annual budget at start of FY. Submit to CC for approval. Review in alignment with flower releases.
- User permissions:
- Mark Veksler can join CC meeting on 8/14.
Rollout and Communication Plans
- Yogesh Kumar formal announcement. we have steps documented for teams to follow.
- Mark Veksler announce at TC, PC, CC, join PO meeting, team leads meeting. explain that it starts at Q release (timing TBD, but in Spring '24).
- Maccabee Levine TC, PC, CC announcements.
- Mark Veksler schedule time with PO meeting and team leads meeting, Maccabee Levine present to them with Mark Veksler and Yogesh Kumar both joining to help address questions.
- Maccabee Levine #development, #stripes, #sys-ops, #devops. after above communication.
- Will need to remind people (in those channels) closer to releases: ACRG.
- Maccabee Levine start of the announcing late September when people are paying attention, ahead of October release planning.
Cost Increase due to timing of running Automated Tests
- Mark Veksler Regression tests (Karate integration, end-to-end incl migration) run overnight daily after PR merges into master branch. Migration tests run in a scratch environment, so not migration tests. So master branch may be polluted until overnight. Yogesh Kumar introducing a shift-left strategy running automated tests as early as possible. Stepping stone is every few hours.
- Yogesh Kumar Can be dozens of merged PRs in a day, so earlier narrows it down.
- Mark Veksler Team looking at multiple models, leaning to less expensive. Five new environments needed to support, roughly $300/environment/mo, so $1,500 per month additional. $18k/yr. Run rate from 15,5k to 17k /month. Eventual goal is to reduce bugfest time period, and becomes user acceptance testing rather than thorough manual testing.
- Maccabee Levine would be great to bring this to ACRG if it had been approved. Visibility for CC into the parts of their $240k spend.
- Mark Veksler snapshot environments (1 and 2) may not be needed with this approach. maybe small $200/m saving.
- Maccabee Levine would require snapshot users not using that env during certain hours?
- Yogesh Kumar differences in new environment like enabling consortium mode and read/write separation.
- Maccabee Levine maybe bring this to TC for concerns.
- Yogesh Kumar Both sets may be needed, one with consortium one without