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

Adding Kraken to PerfScale Pipeline #28

Merged
merged 1 commit into from
Aug 27, 2020

Conversation

yashashreesuresh
Copy link
Contributor

This commit adds Kraken to CI pipeline and thereby enabling chaos
scenarios to be injected on specified jump host. Link to the Jenkins job to achieve the same.

@yashashreesuresh
Copy link
Contributor Author

Please have a look @chaitanyaenr @mffiedler @paigerube14

@rht-perf-ci
Copy link

Can one of the admins verify this patch?

This commit adds kraken to CI pipeline and thereby enabling chaos
scenarios to be injected on specified jump host.
@chaitanyaenr
Copy link
Collaborator

@paigerube14 @mffiedler CI directory will store the configs being used by the PerfScale CI pipeline, the plan is to tweak them accordingly instead of changing the ones in the base dir of the Kraken.

Copy link
Collaborator

@chaitanyaenr chaitanyaenr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@paigerube14
Copy link
Collaborator

Are we able to update the config to point to the scenarios under the CI folder so we won't have to keep up with changing the scenarios in both places? Thoughts?

@chaitanyaenr
Copy link
Collaborator

Are we able to update the config to point to the scenarios under the CI folder so we won't have to keep up with changing the scenarios in both places? Thoughts?

The CI configs will be tailored to our cluster setup vs the defaults which is why we have a separate config and scenarios vs re-using the existing ones. The plan is to tweak the CI configs to meet our needs accordingly as we finalize what to run as part of the PerfScale CI. Thoughts?

@paigerube14
Copy link
Collaborator

Are we able to update the config to point to the scenarios under the CI folder so we won't have to keep up with changing the scenarios in both places? Thoughts?

The CI configs will be tailored to our cluster setup vs the defaults which is why we have a separate config and scenarios vs re-using the existing ones. The plan is to tweak the CI configs to meet our needs accordingly as we finalize what to run as part of the PerfScale CI. Thoughts?

That makes sense!

@paigerube14
Copy link
Collaborator

LGTM

@chaitanyaenr chaitanyaenr merged commit aac254c into krkn-chaos:master Aug 27, 2020
@yashashreesuresh yashashreesuresh deleted the kraken_CI branch November 18, 2020 15:32
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

Successfully merging this pull request may close these issues.

None yet

4 participants