Skip to content

Conversation

@slagle
Copy link
Contributor

@slagle slagle commented Dec 9, 2025

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

Co-Authored-By: Claude noreply@anthropic.com
Jira: OSPRH-18952
Signed-off-by: James Slagle jslagle@redhat.com

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>
@softwarefactory-project-zuul
Copy link

Unable to freeze job graph: Job podified-multinode-edpm-deployment-crc depends on openstack-k8s-operators-content-provider which was not run.

@openshift-ci openshift-ci bot requested review from fultonj and viroel December 9, 2025 12:07
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 9, 2025

[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

Details 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

@openshift-ci openshift-ci bot added the approved label Dec 9, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 9, 2025

@slagle: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/openstack-operator-build-deploy-kuttl 803e981 link true /test openstack-operator-build-deploy-kuttl

Full PR test history. Your PR dashboard.

Details

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.

@slagle
Copy link
Contributor Author

slagle commented Dec 9, 2025

This is just docs, so I don't see any reason to recheck/retest failing CI jobs.

@slagle slagle requested a review from rabi December 11, 2025 16:55
* <<ceilometerspeccore,CeilometerSpecCore>>
* <<ceilometerstatus,CeilometerStatus>>
* <<ksmstatus,KSMStatus>>
* <<cloudkittyapi,CloudKittyAPI>>
Copy link
Contributor

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>+++
Copy link
Contributor

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.

[1] https://github.com/openstack-k8s-operators/manila-operator/blob/main/api/v1beta1/common_types.go#L77-L78

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
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants