Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Production operation support and requirements #41

Open
kapilvgit opened this issue Jan 16, 2024 · 1 comment
Open

Production operation support and requirements #41

kapilvgit opened this issue Jan 16, 2024 · 1 comment

Comments

@kapilvgit
Copy link

kapilvgit commented Jan 16, 2024

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?

@kapilvgit kapilvgit changed the title Clarify production operation support and requirements Production operation support and requirements Jan 16, 2024
@p-j-l
Copy link
Contributor

p-j-l commented Feb 26, 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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants