You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to get more clarity on what it would take to operationalize B&A services in production, including change and incident management. This document is listing some of the issues but would be nice to get to the next level of detail. For example, what is the full lifecycle when new versions of services are released, how will upgrades be staged?
The text was updated successfully, but these errors were encountered:
kapilvgit
changed the title
Clarify production operation support and requirements
Production operation support and requirements
Jan 16, 2024
I'm going to put this on the agenda for this week's call but I'd like to widen the discussion a little to include what a B&A or KV Server that's "generally available" should look like.
(I'm thinking of the questions that @kapilvgit has above but also things like monitoring, logging, alerting, etc, etc.)
It would be great to get more clarity on what it would take to operationalize B&A services in production, including change and incident management. This document is listing some of the issues but would be nice to get to the next level of detail. For example, what is the full lifecycle when new versions of services are released, how will upgrades be staged?
The text was updated successfully, but these errors were encountered: