-
Notifications
You must be signed in to change notification settings - Fork 102
Add comprehensive dataplane scaling and performance documentation #1724
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
base: main
Are you sure you want to change the base?
Conversation
This commit adds comprehensive documentation for scaling and performance tuning of dataplane deployments: - New: dataplane_performance_tuning_large_scale.adoc - Comprehensive guide covering NodeSet grouping strategies, parallel execution patterns, Ansible performance tuning, ansible-limit usage, scaling strategy comparisons, best practices, and troubleshooting. - Renamed: scaling.adoc -> dataplane_scaling_out.adoc - Existing scaling out/in procedures now in more descriptively named file. - Updated: dataplane.adoc - Added includes for both new performance tuning guide and renamed scaling operations guide. Key topics covered: - Single vs. multiple NodeSet strategies with performance comparisons - Ansible environment variables for tuning (ANSIBLE_FORKS, pipelining, etc.) - Using ansible-limit for gradual rollouts and targeted deployments - Detailed 100-node deployment comparison showing 2x speedup with multiple NodeSets - Best practices for monitoring, optimization, and troubleshooting 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Jira: OSPRH-18952 Signed-off-by: James Slagle <jslagle@redhat.com>
|
Unable to freeze job graph: Job podified-multinode-edpm-deployment-crc depends on openstack-k8s-operators-content-provider which was not run. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: slagle The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@slagle: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
This is just docs, so I don't see any reason to recheck/retest failing CI jobs. |
| * <<ceilometerspeccore,CeilometerSpecCore>> | ||
| * <<ceilometerstatus,CeilometerStatus>> | ||
| * <<ksmstatus,KSMStatus>> | ||
| * <<cloudkittyapi,CloudKittyAPI>> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes look unrelated.
| | customServiceConfig | ||
| | CustomServiceConfig - customize the service config using this parameter to change service defaults, or overwrite rendered information using raw OpenStack config format. The content gets added to /etc/+++<service>+++/+++<service>+++.conf.d directory a custom config file.+++</service>++++++</service>+++ | ||
| | CustomServiceConfig - customize the service config using this parameter to change service defaults, or overwrite rendered information using raw OpenStack config format. The content gets added to to /etc/+++<service>+++/+++<service>+++.conf.d directory a custom config file.+++</service>++++++</service>+++ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"to to" looks like the doc string have typo[1] hence generated like that.
| 4. Operator starts deployment for `compute-group-4` → ansible-runner pod launches | ||
| 5. All four ansible-runner pods execute in parallel | ||
|
|
||
| This means *4 separate Ansible executions run simultaneously*, each processing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it's mentioned elsewhere I missed, we can probably mention about AnsibleJobNodeSelector for deployments that can distribute them across worker nodes.
This commit adds comprehensive documentation for scaling and
performance tuning of dataplane deployments:
New: dataplane_performance_tuning_large_scale.adoc - Comprehensive
guide covering NodeSet grouping strategies, parallel execution
patterns, Ansible performance tuning, ansible-limit usage, scaling
strategy comparisons, best practices, and troubleshooting.
Renamed: scaling.adoc -> dataplane_scaling_out.adoc - Existing
scaling out/in procedures now in more descriptively named file.
Updated: dataplane.adoc - Added includes for both new performance
tuning guide and renamed scaling operations guide.
Key topics covered:
multiple NodeSets
🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com
Jira: OSPRH-18952
Signed-off-by: James Slagle jslagle@redhat.com