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

Use deployment instead of raw pod for storage perf tests #687

Conversation

mucahitkurt
Copy link
Contributor

Fix #666

Raw pod object templates are changed with deployment templates and the same pods definitions are used inside deployments. Deployment-Pod relation is 1-1.

Also test config files are changed according to these new deployment templates.

/sig storage
/assign @wojtek-t
cc @msau42

@k8s-ci-robot k8s-ci-robot added sig/storage Categorizes an issue or PR as relevant to SIG Storage. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jul 24, 2019
@k8s-ci-robot
Copy link
Contributor

Hi @mucahitkurt. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jul 24, 2019
@k8s-ci-robot k8s-ci-robot requested review from krzysied and mborsz July 24, 2019 21:39
@msau42
Copy link
Member

msau42 commented Jul 24, 2019

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 24, 2019
@msau42
Copy link
Member

msau42 commented Jul 24, 2019

@wojtek-t are scale tests run on regional clusters? I'm thinking of when we want to reuse these for PVC tests too and each PVC is restricted to a single zone. To support multiple PVCs in a Pod case, we would need to either:

  • Use delayed volume binding to ensure all pvcs within a pod are provisioned in the same zone as the pod. This will add provisioning into pod startup latency though.
  • Use StatefulSet, which hashes all PVCs within a StatefulSet to provision from the same zone.

@hantaowang
Copy link

How does this work for config and secret where the name of the config/secret is different for every pod?

@mucahitkurt
Copy link
Contributor Author

mucahitkurt commented Jul 25, 2019

How does this work for config and secret where the name of the config/secret is different for every pod?

@hantaowang I use N deployments for N pods, so the relation is 1-1, and volume matching shouldn't be different for the raw pod case, I create N volumes and match these volumes to the N pods inside the N deployments.

@@ -3,7 +3,7 @@

#Constants
{{$TOTAL_PODS := DefaultParam .TOTAL_PODS 1}}
{{$POD_TEMPLATE_PATH := DefaultParam .POD_TEMPLATE_PATH "../volume-types/emptydir/pod_with_emptydir.yaml"}}
{{$DEPLOYMENT_TEMPLATE_PATH := DefaultParam .DEPLOYMENT_TEMPLATE_PATH "../volume-types/emptydir/deployment_with_emptydir.yaml"}}
Copy link
Member

Choose a reason for hiding this comment

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

I'm sorry - I was blocking @hantaowang PRs for quite some time and your stuff, so this time I will do it the other way (unfortunately you're both touching the same stuff).
#688 is super useful, so I would like that one to merge first and then I will ask you to rebase this one on top.

@hantaowang
Copy link

Doesn't this then also stress the deployment controller? We may inadvertently become bottle necked by the deployment and replicaset controller despite the fact that so many deployments are rare. Deployments are definitely a dimension to stress on, but imo for storage that should be eliminated as a variable.

@wojtek-t
Copy link
Member

Doesn't this then also stress the deployment controller? We may inadvertently become bottle necked by the deployment and replicaset controller despite the fact that so many deployments are rare. Deployments are definitely a dimension to stress on, but imo for storage that should be eliminated as a variable.

Disagree - this number of deployments actually isn't very high (we're testing higher numbers). And we should be using what users are using not something artificial.

@hantaowang
Copy link

Is it that realistic to use 1 deployment per pod?

I'm thinking more for when the tests become larger scale (say 5000 nodes at 10 pods per node). I don't see anyone using 50000 deployments to manage this as that would definitely overload the controllers.

@wojtek-t
Copy link
Member

Is it that realistic to use 1 deployment per pod?

I've seen a bunch of large user clusters with a huge number of those - yes it is realistic.

I'm thinking more for when the tests become larger scale (say 5000 nodes at 10 pods per node). I don't see anyone using 50000 deployments to manage this as that would definitely overload the controllers.

I wouldn't be that convinced that this will for sure overload controllers.
We will see when we get to this scale - I think we will hit many other limitations before that.

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 25, 2019
@mucahitkurt
Copy link
Contributor Author

waiting for the PVC tests PR's merge to continue

@wojtek-t
Copy link
Member

That PR has just merged - can you please rebase?

@mucahitkurt mucahitkurt force-pushed the storage/perf-tests/use-deployment-instead-of-raw-pod branch from dc55398 to 3271c43 Compare July 30, 2019 20:40
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 30, 2019
@mucahitkurt
Copy link
Contributor Author

@wojtek-t, @hantaowang pod usages are converted to deployment usage

metadata:
name: {{.Name}}
labels:
app: {{.Name}}
Copy link
Member

Choose a reason for hiding this comment

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

What do we need "app" label for?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think we don't need it

configMap:
name: vol-{{AddInt $volumeIndex (MultiplyInt $index $volumesPerPod)}}
{{ end }}
dnsPolicy: Default
Copy link
Member

Choose a reason for hiding this comment

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

We don't need to set it - it will be defaulted anyway.

name: vol-{{AddInt $volumeIndex (MultiplyInt $index $volumesPerPod)}}
{{ end }}
dnsPolicy: Default
terminationGracePeriodSeconds: 1
Copy link
Member

Choose a reason for hiding this comment

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

Please remove - I don't think we need it for anything.

- key: "node.kubernetes.io/unreachable"
operator: "Exists"
effect: "NoExecute"
tolerationSeconds: 900
Copy link
Member

Choose a reason for hiding this comment

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

All the comments in this file apply to all other files too.

@mucahitkurt mucahitkurt force-pushed the storage/perf-tests/use-deployment-instead-of-raw-pod branch from 3271c43 to f9843f0 Compare July 31, 2019 19:06
@wojtek-t
Copy link
Member

wojtek-t commented Aug 1, 2019

/lgtm
/approve

thanks!

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 1, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mucahitkurt, wojtek-t

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 1, 2019
@k8s-ci-robot k8s-ci-robot merged commit 70affa1 into kubernetes:master Aug 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. sig/storage Categorizes an issue or PR as relevant to SIG Storage. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Don't use raw pods in storage experimental tests
5 participants