openshift-docs
openshift-docs copied to clipboard
OSDOCS-8015: Adding a total resource usage table
[OSDOCS#8015]: Adding a total resource usage table
Version(s):
Issue: https://issues.redhat.com/browse/OSDOCS-8015
Link to docs preview: https://77127--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/configuring-operator.html
QE review:
- [ ] QE has approved this change.
Additional information: Table mockup: https://docs.google.com/document/d/1xyBeIehZwyV_p7GkP9uJbr1ay5vFFcWsZwi3SENtB70/edit?usp=sharing
@mpandya15: This pull request references OSDOCS-10726 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.
In response to this:
[OSDOCS#10726]: Adding a total resource usage table
Version(s):
Issue: https://issues.redhat.com/browse/OSDOCS-10726
Link to docs preview:
QE review:
- [ ] QE has approved this change.
Additional information:
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 openshift-eng/jira-lifecycle-plugin repository.
🤖 Mon Jul 22 20:20:29 - Prow CI generated the docs preview:
https://77127--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/configuring-operator.html
/retest
@mpandya15: This pull request references OSDOCS-10726 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.
In response to this:
[OSDOCS#10726]: Adding a total resource usage table
Version(s):
Issue: https://issues.redhat.com/browse/OSDOCS-8015
Link to docs preview:
QE review:
- [ ] QE has approved this change.
Additional information:
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 openshift-eng/jira-lifecycle-plugin repository.
@mpandya15: This pull request references OSDOCS-8015 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.
In response to this:
[OSDOCS#10726]: Adding a total resource usage table
Version(s):
Issue: https://issues.redhat.com/browse/OSDOCS-8015
Link to docs preview:
QE review:
- [ ] QE has approved this change.
Additional information:
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 openshift-eng/jira-lifecycle-plugin repository.
@mpandya15: This pull request references OSDOCS-8015 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.
In response to this:
[OSDOCS#8015]: Adding a total resource usage table
Version(s):
Issue: https://issues.redhat.com/browse/OSDOCS-8015
Link to docs preview:
QE review:
- [ ] QE has approved this change.
Additional information:
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 openshift-eng/jira-lifecycle-plugin repository.
Hi @mpandya15 @skrthomas FYI here's more recommendations after running fine-tuning tests: https://issues.redhat.com/browse/NETOBSERV-1702?focusedId=24983810&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-24983810
10-nodes cluster: cacheMaxSize = 50000, Kafka consumer replicas: N/A 25-nodes cluster: cacheMaxSize = 100000 (default), Kafka consumer replicas: 6 65-nodes cluster: cacheMaxSize = 100000 (default), Kafka consumer replicas: 12 120-nodes cluster: cacheMaxSize = 100000 (default), Kafka consumer replicas: 18
cc @memodi
10-nodes cluster: set cacheMaxSize to 50000 25-nodes cluster: use 6 FLP replicas 65-nodes cluster: use 12 FLP replicas 120-nodes cluster: use 18 FLP replicas
cc @stleerh thanks @jotak. Any reason why we'd recommend cacheMaxSize to 50K? I thought you mentioned no noticeable improvements were observed altering the cacheMaxSIze.
@memodi it's extrapolated from my 6-nodes cluster, using my own tests (where fine-tuning leads me to 10K size). I don't think we have a test procedure for 10 nodes, do we?
I don't think we have a test procedure for 10 nodes, do we?
that's right, we don't. I am thinking several of our customers could fall into this category where they could have several smaller clusters < 10 nodes and based on these recommendation it would mean they'd have to change from default cacheMaxSize to 50k in flowcollector, is that something we want?
@memodi they don't have to, this is only recommendations, and ideally they should do their own tuning. But they can definitely start with that. cf https://netobserv.io/documents/blogs/agent_metrics_perf/
@mpandya15: This pull request references OSDOCS-8015 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.
In response to this:
[OSDOCS#8015]: Adding a total resource usage table
Version(s):
Issue: https://issues.redhat.com/browse/OSDOCS-8015
Link to docs preview:
QE review:
- [ ] QE has approved this change.
Additional information: Table mockup: https://docs.google.com/document/d/1xyBeIehZwyV_p7GkP9uJbr1ay5vFFcWsZwi3SENtB70/edit?usp=sharing
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 openshift-eng/jira-lifecycle-plugin repository.
Hi @mpandya15 @skrthomas FYI here's more recommendations after running fine-tuning tests: https://issues.redhat.com/browse/NETOBSERV-1702?focusedId=24983810&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-24983810
10-nodes cluster: set cacheMaxSize to 50000 25-nodes cluster: use 6 FLP replicas 65-nodes cluster: use 12 FLP replicas 120-nodes cluster: use 18 FLP replicas
cc @memodi
Hi Joel, thanks for bringing this up. We plan to include the cacheMaxFlows updates in a separate PR to update the existing info in the resource recommendations table.
@mpandya15: This pull request references OSDOCS-8015 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.
In response to this:
[OSDOCS#8015]: Adding a total resource usage table
Version(s):
Issue: https://issues.redhat.com/browse/OSDOCS-8015
QE review:
- [ ] QE has approved this change.
Additional information: Table mockup: https://docs.google.com/document/d/1xyBeIehZwyV_p7GkP9uJbr1ay5vFFcWsZwi3SENtB70/edit?usp=sharing
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 openshift-eng/jira-lifecycle-plugin repository.
@mpandya15: This pull request references OSDOCS-8015 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.
In response to this:
[OSDOCS#8015]: Adding a total resource usage table
Version(s):
Issue: https://issues.redhat.com/browse/OSDOCS-8015
Link to docs preview: https://77127--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/configuring-operator.html
QE review:
- [ ] QE has approved this change.
Additional information: Table mockup: https://docs.google.com/document/d/1xyBeIehZwyV_p7GkP9uJbr1ay5vFFcWsZwi3SENtB70/edit?usp=sharing
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 openshift-eng/jira-lifecycle-plugin repository.
Hey @memodi @skrthomas @jotak @stleerh, I've addressed your feedback and made the required changes. PTAL at my latest updates and let me know if there's other changes. Thank you! 😊
thanks @mpandya15
/label qe-approved
@mpandya15: This pull request references OSDOCS-8015 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.
In response to this:
[OSDOCS#8015]: Adding a total resource usage table
Version(s):
Issue: https://issues.redhat.com/browse/OSDOCS-8015
Link to docs preview: https://77127--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/configuring-operator.html
QE review:
- [ ] QE has approved this change.
Additional information: Table mockup: https://docs.google.com/document/d/1xyBeIehZwyV_p7GkP9uJbr1ay5vFFcWsZwi3SENtB70/edit?usp=sharing
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 openshift-eng/jira-lifecycle-plugin repository.
/label peer-review-needed
@mpandya15: This pull request references OSDOCS-8015 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.17.0" version, but no target version was set.
In response to this:
[OSDOCS#8015]: Adding a total resource usage table
Version(s):
Issue: https://issues.redhat.com/browse/OSDOCS-8015
Link to docs preview: https://77127--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/configuring-operator.html
QE review:
- [x] QE has approved this change.
Additional information: Table mockup: https://docs.google.com/document/d/1xyBeIehZwyV_p7GkP9uJbr1ay5vFFcWsZwi3SENtB70/edit?usp=sharing
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 openshift-eng/jira-lifecycle-plugin repository.
Hello @mpandya15, Just a couple of comments/suggestions, otherwise LGTM. Good job! Thanks.
New changes are detected. LGTM label has been removed.
/label merge-review-needed
@mpandya15: all tests passed!
Full PR test history. Your PR dashboard.
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-sigs/prow repository. I understand the commands that are listed here.
/cherrypick enterprise-4.12
/cherrypick enterprise-4.13
/cherrypick enterprise-4.14
/cherrypick enterprise-4.15
/cherrypick enterprise-4.16
@skrthomas: new pull request created: #79236
In response to this:
/cherrypick enterprise-4.12
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-sigs/prow repository.