-
Notifications
You must be signed in to change notification settings - Fork 698
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
170 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,71 @@ | ||
| title | authors | creation-date | last-updated | | ||
|--------------------------------------------------|------------------------------------------|---------------|--------------| | ||
| Adding a New Chaos Fault - AWS RDS Instance Stop | [@jongwooo](https://github.com/jongwooo) | 2024-09-02 | 2024-09-02 | | ||
|
||
# Adding a New Chaos Fault - AWS RDS Instance Stop | ||
|
||
- [Summary](#summary) | ||
- [Motivation](#motivation) | ||
- [Goals](#goals) | ||
- [Non-Goals](#non-goals) | ||
- [Proposal](#proposal) | ||
- [Use Cases](#use-cases) | ||
- [Implementation Details](#implementation-details) | ||
- [Risks and Mitigations](#risks-and-mitigations) | ||
- [Upgrade / Downgrade Strategy](#upgrade--downgrade-strategy) | ||
- [Drawbacks](#drawbacks) | ||
- [Alternatives](#alternatives) | ||
- [References](#references) | ||
|
||
## Summary | ||
|
||
[Amazon Relational Database Service (RDS)](https://aws.amazon.com/en/rds/) is a managed relational database service provided by AWS. It is a fully managed database service that makes it easy to set up, operate, and scale a relational database in the cloud. | ||
So I want to add a new chaos fault(rds instance stop) to Litmus ChaosHub. | ||
|
||
## Motivation | ||
|
||
Litmus ChaosHub has plenty of Chaos Faults. But there is no Chaos Fault for RDS. RDS is a widely used service in AWS. So I want to add a new Chaos Fault for RDS. Adding 'rds instance stop' Chaos Fault to Litmus ChaosHub can help create a more resilient system. | ||
### Goals | ||
|
||
- Adding a 'rds instance stop' Chaos Fault to [Litmus ChaosHub](https://hub.litmuschaos.io/) | ||
- Fixing [litmus-go](https://github.com/litmuschaos/litmus-go) and [chaos-charts](https://github.com/litmuschaos/chaos-charts) codes | ||
|
||
### Non-Goals | ||
|
||
- Fixing Litmus codes except for [litmus-go](https://github.com/litmuschaos/litmus-go) and [chaos-charts](https://github.com/litmuschaos/chaos-charts) is a non-goal | ||
|
||
## Proposal | ||
|
||
### Use Cases | ||
|
||
#### Use case 1 | ||
|
||
In Chaos Studio, Users can select 'rds instance stop' Chaos Fault as part of the Chaos Experiment. They can compose it with other Chaos Faults. | ||
|
||
### Implementation Details | ||
|
||
Here's a Chaos Fault Scenario. | ||
|
||
![rds-fault-scenario](./images/rds-fault-scenario.png) | ||
|
||
#### Phase 1 - Add scenario to the litmus-go repository | ||
|
||
I will use `litmuschaos/go-runner` image. So I am going to add a new case in the litmus-go repository. | ||
|
||
#### Phase 2 - Add a new Chaos Fault to the Litmus ChaosHub | ||
|
||
After Phase 1 PR gets merged, I will raise a PR that adds a 'rds instance stop' Chaos Fault to the `chaos-charts` repository. When all is done, the user can easily assault the AWS RDS instance. | ||
|
||
## Risks and Mitigations | ||
|
||
We need to grant proper RBAC permissions to the runner container. Granting override permissions may affect other systems. | ||
|
||
## Upgrade / Downgrade Strategy | ||
|
||
## Drawbacks | ||
|
||
## Alternatives | ||
|
||
## References | ||
|
||
- [Amazon Relational Database Service (RDS)](https://aws.amazon.com/en/rds/) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
| title | authors | creation-date | last-updated | | ||
|-------|------------------------------------------|---------------|--------------| | ||
| Replace mongoDB features not supported by AWS | [@kwx4957](https://github.com/kwx4957) | | | | ||
|
||
### Summary | ||
|
||
There are some operators that are supported by mongoDB but not by aws documentDB. Enhancing this feature with other features or code would make LitmusChaos more developer-friendly on AWS. | ||
|
||
### Goals | ||
|
||
- Changing features not supported by the cloud environment (AWS) with alternative operators or in code | ||
|
||
### Implementation Details | ||
[AWS support api scanning](https://docs.aws.amazon.com/documentdb/latest/developerguide/migration-playbook.html) | ||
|
||
As a result of using these features, the two operators $facet and $bucket are not supported by AWS. We are using the following features in graphQL and expect that modifying them with other features or code will make it easier to run LitmusChaos on AWS. | ||
|
||
``` | ||
he following 2 unsupported operators were found: | ||
$facet | found 8 time(s) | ||
$bucket | found 1 time(s) | ||
Unsupported operators by filename and line number: | ||
$facet | lines = found 8 time(s) | ||
../../litmus/chaoscenter/graphql/server/pkg/chaos_infrastructure/service.go | lines = [664, 841] | ||
../../litmus/chaoscenter/graphql/server/pkg/chaos_experiment/handler/handler.go | lines = [733, 955, 1131] | ||
../../litmus/chaoscenter/graphql/server/pkg/chaos_experiment_run/handler/handler.go | lines = [531] | ||
../../litmus/chaoscenter/graphql/server/pkg/environment/handler/handler.go | lines = [346] | ||
../../litmus/chaoscenter/graphql/server/pkg/chaoshub/service.go | lines = [922] | ||
$bucket | lines = found 1 time(s) | ||
../../litmus/chaoscenter/graphql/server/pkg/chaos_experiment/handler/handler.go | lines = [1106] | ||
``` | ||
|
||
|
||
## References | ||
[issue#4459](https://github.com/litmuschaos/litmus/issues/4459) | ||
[AWS support api](https://docs.aws.amazon.com/documentdb/latest/developerguide/mongo-apis.html#w144aac17c19b5b3) | ||
[Azure support api](https://learn.microsoft.com/es-es/azure/cosmos-db/mongodb/feature-support-36#aggregation-stages) |