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.

Sign up for GitHub

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

Jump to bottom

As a user, I want the registry to have 99.9999999% uptime #176

Closed
jordanpadams opened this issue Mar 23, 2023 · 2 comments
Closed

As a user, I want the registry to have 99.9999999% uptime #176

jordanpadams opened this issue Mar 23, 2023 · 2 comments
Assignees
@sjoshi-jpl
Labels
B14.1 i&t.skip p.must-have requirement the current issue is a requirement

Comments

@jordanpadams
Copy link
Member

jordanpadams commented Mar 23, 2023 •
edited
Loading

Checked for duplicates

Yes - I've already checked

🧑‍🔬 User Persona(s)

Node Operator, EN Operator, Manager

💪 Motivation

...so that I can ensure the registry/OpenSearch is deployed in such a manner that it will recover from a critical failure ensuring our uptime goals.

📖 Additional Details

No response

Acceptance Criteria

Given
When I perform
Then I expect

⚙️ Engineering Details

No response
@jordanpadams jordanpadams added p.must-have requirement the current issue is a requirement labels Mar 23, 2023
@jordanpadams jordanpadams self-assigned this Mar 23, 2023
@jordanpadams jordanpadams mentioned this issue Apr 12, 2023
Closed
@jordanpadams jordanpadams changed the title As a EN Operator, I want to the registry to be fault tolerant As a EN Operator, I want the registry to be fault tolerant Jul 19, 2023
@jordanpadams jordanpadams changed the title As a EN Operator, I want the registry to be fault tolerant As a EN Operator, I want the registry to be fault tolerant for lack of storage Jul 19, 2023
@jordanpadams jordanpadams changed the title As a EN Operator, I want the registry to be fault tolerant for lack of storage As a EN Operator, I want the registry to be fault tolerant for lack of storage available Jul 19, 2023
@jordanpadams jordanpadams changed the title As a EN Operator, I want the registry to be fault tolerant for lack of storage available As a user, I want the registry to have 99.999% uptime Jul 19, 2023
@jordanpadams jordanpadams mentioned this issue Jul 19, 2023
Closed
@jordanpadams jordanpadams added B14.1 and removed B14.0 labels Aug 25, 2023
@jordanpadams jordanpadams changed the title As a user, I want the registry to have 99.999% uptime As a user, I want the registry to have 99.9999999% uptime Sep 22, 2023
@jordanpadams
Copy link
Member Author

Per #211, we have setup notifications to ensure minimal registry crashes. Have also increased storage capacity for OpenSearch instances to avoid crashes. Closing this as completed for the time being. A move to OpenSearch serverless will hopefully add even more robustness here.

@tloubrieu-jpl
Copy link
Member

I&T cannot test that but we need to add a requirement "As a manager, I want to check the availability statistics for the registry"

@tloubrieu-jpl tloubrieu-jpl mentioned this issue Feb 5, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sjoshi-jpl sjoshi-jpl

Labels
B14.1 i&t.skip p.must-have requirement the current issue is a requirement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jimmie @gxtchen @jordanpadams @tloubrieu-jpl @sjoshi-jpl