We intend to refactor the current Scenario Plugin API and add a new feature in the plugin abstract class to restore all the changes performed by krkn in the cluster in case run method encounters some kind of exception before ending the execution and or if the run failed for external infrastructure failures. Expected Outcome: The cluster status should be rolled back to the original condition before the scenario execution.
No project history available for this organization.
Counts are based on projects listed in the Contribo catalog.
Showing 2 of 2 projects. Click any project card for scope, mentors, and proposal studio.
The idea is to define criteria to measure the resiliency score of a cluster after a set of chaos scenarios. Expected Outcome: - a page in our documentation website clearly explaining the scoring algorithm implemented and the best practices to leverage it on the user's environment - a set of functions in our API library to easily collect data and calculate the score - the implementation of the scoring method across all Krkn scenarios, and an update to our telemetry data structures to include the resiliency score to allow the collection by downstream observability systems
We intend to refactor the current Scenario Plugin API and add a new feature in the plugin abstract class to restore all the changes performed by krkn in the cluster in case run method encounters some kind of exception before ending the execution and or if the run failed for external infrastructure failures. Expected Outcome: The cluster status should be rolled back to the original condition before the scenario execution.